What changed
Cheap open-weight LLMs (DeepSeek/GLM-class, cited at ~29% of production token volume) make it near-free to draft jurisdiction-flavored legal-style letters from user inputs — the drafting cost that would have made a $19 packaged product uneconomic has collapsed.
Why now
A concrete, fresh consumer pain (a RetellAI customer publicly reporting they cannot delete their card or account and Mercury/Stripe offer no recourse despite a California CCPA deletion demand) coincides with hardened CCPA/CPRA deletion rights and cheap templated drafting. HYPOTHESIS: this pain generalizes beyond one vendor.
Converging signals
Cheap open-weight inference (FACT, cited Vercel index) × a real 'can't delete card / stop charges' complaint (FACT, cited HN post). Two signals — a capability and a single complaint — not a mandate.
Customer pain
FACT (from the HN post): a consumer is being repeatedly charged, cannot remove their card or delete the account due to vendor bugs, and their bank says it cannot block the merchant. The pain is acute and financial (money bleeding monthly). Breadth of the pain beyond this one poster is HYPOTHESIS — only one complaint is provided.
Who pays
Consumers currently trapped in a recurring charge they can't stop; they pay once to 'make it stop.' The beneficiary and buyer are the same person here — a discretionary, one-time, low-loyalty buyer.
Solved today
Free CCPA deletion-letter templates (privacy nonprofits, state AG pages), free chargeback dispute flows built into every card issuer's app, DoNotPay-style bots, subscription-canceler apps (Rocket Money), and simply calling the bank to revoke authorization / issue a new card number.
Why current solutions are bad
Existing help is fragmented across three separate actions (deletion demand, chargeback, authorization revocation) and generic; the user has to assemble the right combination themselves. But each individual piece is already free and often adequate — that is the core weakness of the paid version.
Proposed product
A guided web form → outputs a populated CCPA/CPRA deletion demand letter, a card-issuer chargeback narrative with the required dispute elements, and a written revocation-of-payment-authorization notice, all filled and ready to send. Cheap LLM fills vendor- and state-specific templates.
MVP version
Single-page guided form (vendor name, dates, amounts, state, card issuer) → three generated documents as PDF/copy-paste, gated behind a $19 Stripe payment. Buildable in days on free/cheap tiers.
30-day build
Ship the generator with 5-10 pre-tuned vendor templates and the 3 document types; seed it in the exact complaint venues (HN, r/personalfinance, r/CreditCards, Trustpilot review threads for offending vendors) where people describe this pain; instrument conversion vs. a free single-letter variant to answer the kill test directly.
60-day build
If paid conversion beats the free template, add a 'stuck subscription' vendor directory (SEO surface for '[vendor] won't let me cancel / delete card') and expand states beyond CA (add other deletion-right states + generic FTC/authorization-revocation angle).
90-day revenue plan
Revenue is pay-per-case at $19; 90-day revenue depends entirely on organic-search + complaint-thread capture volume, since there is no repeat purchase and paid acquisition would exceed the price point. Realistic path is thin, SEO-driven trickle unless a vendor's cancellation scandal spikes traffic.
Distribution path
SEO on '[vendor] can't cancel / won't delete my card,' complaint-thread seeding, and affiliate/embed in subscription-tracker communities. No forced buyer, no deadline — pure discretionary, cold-traffic acquisition, which is the hardest part.
Pricing hypothesis
$19 one-time per case. No recurring revenue; low LTV; each customer is acquired once and never returns.
Technical difficulty
Low. Templates + cheap LLM fill + Stripe. The hard part is not the build.
Legal / regulatory risk
Moderate. Generating filled legal-style letters and a chargeback 'narrative' flirts with unauthorized practice of law in some states if it crosses from blank template to specific legal advice; keep it template-fill and add clear 'not legal advice' framing. Advising a chargeback where goods/services were partly received can be characterized as facilitating improper disputes — reputational and card-network risk if abused.
Platform dependency
Low — no app-store or government-portal gatekeeper. Depends on Stripe for payment (some irony given the pain is Stripe-processed charges) and on SEO, which is the real dependency.
Founder fit
Modest. This is NOT the founder's proven government-portal / forced-filer shape (no mandate, no per-filing forced buyer, no portal integration). It's a discretionary consumer micro-tool with cold-traffic distribution and a suspected zero-margin problem — the opposite of his highest-fit pattern. His compliance-monitoring / public-records strengths are only tangentially used.
Breakout potential
Low-to-moderate. Could become a 'stuck subscription escape kit' brand with SEO moat, but there is no network effect, no recurring revenue, and incumbents (Rocket Money, DoNotPay, card issuers) can absorb this feature trivially.
Final recommendation
WATCH / LOW-PRIORITY. Fast and cheap to prototype, but the kill test (free templates convert equally) is probably fatal to the margin, distribution is cold-traffic-only, there's no recurring revenue, and it sits well outside the founder's high-fit government-portal thesis. Only worth a weekend spike to A/B the paid dossier vs. a free single letter; if paid does not clearly win, drop it.
Next action
Build a one-day landing page with the free-single-letter vs. $19-full-dossier A/B and post it in the exact HN/Reddit complaint threads to measure whether anyone pays before investing further.