What changed
FACT: A cheap fast-tier LLM (Gemini 3.7 Flash) makes per-case generation of tailored legal-adjacent letter packets nearly free (cited). FACT: A documented HN case shows RetellAI continuing to charge a user while bugs block card/account removal and a CCPA deletion demand is ignored, with the bank (Mercury) unable to block the transactions (cited). HYPOTHESIS: DoNotPay's FTC trust problems left the narrow 'transparent document-prep' niche open.
Why now
FACT: FTC reports record ~$16B in reported consumer fraud losses for 2025, up ~25% YoY (cited) — though this figure covers fraud broadly, not failed cancellations specifically, so it is context, not direct demand proof. The direct evidence of the specific pain is a single HN thread. HYPOTHESIS: dark-pattern billing complaints recur constantly across Reddit/HN; note the FTC's Click-to-Cancel rule was vacated in mid-2025, meaning regulators will NOT solve this for consumers soon, which keeps the pain alive.
Converging signals
Recurring can't-cancel/can't-delete complaint pattern (1 documented case in input) x near-zero-cost LLM letter generation x a wounded incumbent (DoNotPay). This is a pain-x-cheap-capability quick-win shape, not a mandate shape — graded on the broke-solo-dev rubric.
Customer pain
Every month of delay costs the victim a subscription fee they cannot stop; the standard remedies (in-app cancel, support tickets, bank block) have all failed. Pain is urgent and monetary. However, the input contains only ONE direct pain datapoint; volume is asserted, not evidenced.
Who pays
The billed consumer or solo dev, paying by card immediately ($19 one-time; $39 nuclear tier). Buyer and beneficiary are the same person, reachable at the moment of maximum pain via the search/threads where they vent.
Solved today
Free paths: dispute the charge with the card issuer, reissue the card, file a free CFPB/state-AG complaint, or ask ChatGPT to draft the letters. Paid paths: Rocket Money's cancellation concierge, DoNotPay subscription (~$36/2mo).
Why current solutions are bad
For most consumers with a normal bank, card reissue + chargeback is genuinely adequate — this is the product's biggest problem. The tool wins only in the residue: business banks without dispute tooling (as in the cited Mercury case), merchants that re-bill new card numbers via account updater, and users who also want the CCPA deletion enforced (a chargeback doesn't delete data). ChatGPT drafts comparable letters free; the paid value is correct statutory citations, jurisdiction routing, the pre-filled AG form, and done-for-you mailing instructions.
Proposed product
One-page form (merchant, charges, what you tried, state) -> generated packet: CCPA/state-equivalent deletion demand with statutory cites, card-network dispute letter documenting the failed-cancellation record, pre-filled state-AG complaint, tracked-mail instructions. Clearly disclaimed document preparation, not legal advice. No accounts, no stored card data, order records only.
MVP version
Static landing page + Stripe Checkout + one Gemini Flash prompt chain with a 50-state statute lookup table. 3-5 days of build on free/cheap tiers — fits the broke-dev bar.
30-day build
Days 1-5 build; days 5-19 run the convergence's own kill test: place the landing page where the complaints already recur (HN threads, r/personalfinance, r/SaaS, r/Scams — as helpful comments, not spam), plus 'how to cancel [merchant]' SEO pages for the 50 most-complained-about merchants. Kill threshold per input: <10 paid cases in 14 days.
60-day build
If alive: add the $39 nuclear tier (card-network arbitration draft + AG follow-up), auto-generate merchant-specific SEO pages from complaint scraping (this is the founder's complaint-mining strength), collect outcome testimonials ('refund obtained') as the trust asset.
90-day revenue plan
HYPOTHESIS: 100-300 cases/mo at blended ~$24 = $2.4k-7.2k/mo requires ranking for cancel-intent long-tail queries; realistic only if SEO pages take hold. No path to this via paid ads at a $19 AOV.
Distribution path
SEO on '[merchant] won't let me cancel' long-tail + presence in recurring complaint threads. Weakness: no owned channel, thread-posting risks moderator bans, and the purchase is one-time so every sale must be re-acquired.
Pricing hypothesis
$19 one-time / $39 nuclear tier. Fat margin (~95%) but tiny LTV; no recurrence unless expanded into adjacent packet types.
Technical difficulty
Low. The hard part is legal accuracy of the 50-state privacy-statute table and dispute-code citations, which is research labor, not engineering.
Legal / regulatory risk
Moderate: unauthorized-practice-of-law lines vary by state — pure document preparation with disclaimers and no case-specific advice is the established lawful lane (LegalZoom precedent), but the 'nuclear' tier must not drift into advising strategy. DoNotPay's FTC settlement shows the exact failure mode to avoid: never claim lawyer-equivalence or guaranteed outcomes.
Platform dependency
None material. Gemini API is swappable with any LLM; Stripe is standard. No marketplace, no platform owner.
Founder fit
Medium-low (5). It uses his complaint-mining and fast-prototyping strengths and sells through demonstrated value, but it is a one-shot consumer product dependent on content distribution — outside his proven government-portal/per-filing edge, with no forced buyer, no recurring revenue, and no moat he specifically can defend. It is a side experiment, not a thesis play.
Breakout potential
Modest. Best case it becomes a 'consumer enforcement packet' factory (data-deletion, debt validation, security-deposit recovery, warranty claims) — a portfolio of $19-39 SKUs sharing one engine. It does not compound into a defensible platform; Rocket Money or a ChatGPT feature caps the ceiling.
Final recommendation
TEST CHEAPLY, DO NOT COMMIT. The build cost is ~5 days and the input already specifies a clean falsifiable kill test (10 paid cases in 14 days from organic placement). Run exactly that. Score-wise this is a C-tier side experiment: real urgent pain, honest fat-margin quick-win shape, but thin evidence of volume, a strong free substitute, and weak fit with the founder's proven edge. It should never displace mandate-shaped work; it is a lottery ticket whose ticket price is one week.
Next action
Before writing any code, spend 2 hours harvesting volume evidence: count distinct 'can't cancel / won't delete my card' complaints across HN Algolia and PullPush for the last 90 days. If fewer than ~30 distinct cases with named merchants, kill without building. If the volume is there, build the 5-day MVP and run the 14-day paid-case kill test.