Churn Receipts
Turns a B2B SaaS cancellation-survey CSV into a one-page, revenue-weighted churn brief where every stated reason is locked to verbatim customer quotes.
One product, one founder, thirty days. Everything below is built to be executed inside the contest window — the official rules still decide what counts.
Decide in 20 seconds
The facts that decide whether this is worth thirty days of yours.
Founder or Head of Customer Success at a 10-50 person B2B SaaS company (US/UK/EU) that already runs a cancellation or exit survey and exports responses to CSV, triggered by a monthly churn review or an investor update.
Market demand 4.9/10
Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.
Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 10; 7 sales at $149 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.2/10.
Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.
Your first 24 hours
12 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Founder or Head of Customer Success at a 10-50 person B2B SaaS company (US/UK/EU) that already runs a cancellation or exit survey and exports responses to CSV, triggered by a monthly churn review or an investor update.
Why now
The buyer already owns the input file and already owes someone the output document, so the offer needs no integration, no onboarding call, no procurement and no brand trust.
Problem
The churn review is anecdotal: someone skims the CSV, cherry-picks quotes, and guesses at priorities, so reasons get mis-bucketed and the same churn repeats with no defensible number attached to any reason.
Solution
Pay, upload the cancellation CSV, and receive a PDF plus Markdown brief in minutes: top seven reasons ranked by frequency x MRR-at-risk, each with at least two verbatim quotes, a fix-first note, and a save-offer draft.
Churn Receipts - Product Opportunity and Positioning
The buyer is a founder or Head of Customer Success at a 10-50 person B2B SaaS company that already runs a cancellation or exit survey and exports responses to CSV. They face a recurring deadline: the monthly churn review, or an investor update where they must explain why customers leave. Today that explanation is assembled by hand. Someone opens the CSV, skims the comment column, and picks three quotes that support the story they already believe. "Too expensive" gets logged as a pricing problem when the verbatim text says the buyer could not get SSO approved. The roadmap fix lands in the wrong place and the same churn repeats next quarter with no number attached to it.
Churn Receipts replaces that ritual with a fixed-format artifact. The buyer pays, uploads the CSV, and receives a one-page PDF plus Markdown brief within minutes: the top seven reasons ranked by frequency x MRR-at-risk, each reason locked to at least two verbatim quotes drawn from their own file, plus a fix-first recommendation and a copy-ready save-offer draft for reason #1. The Quote Lock rule is the product's whole trust argument. A reason that cannot be evidenced by two real rows in the uploaded data is dropped, not softened.
Positioning. The narrow wedge is the entire strategy. This is not a feedback analytics platform, not a dashboard, and not an integration. It has no connectors to Zendesk, Intercom or SurveyMonkey, no trend-over-time view, no team seats, no free tier. The buyer supplies a file they already own and receives the document they already owe. That is the whole transaction, priced one-time so it clears any approval threshold without a procurement cycle.
The alternatives are two: enterprise feedback platforms that require integration work, an onboarding call and a signed contract, and a general-purpose chatbot where the buyer must still do the structuring, the clustering and the ranking themselves - and has no way to prove the output came from real rows. Churn Receipts wins on the second point. Every claim in the brief traces to a quote that was string-matched against the uploaded CSV.
Why the timing and the trigger matter. JEV scores this concept 63.1/100 in band C. Its strongest criterion is speed to first revenue at 8.18/10: the offer can be sent by direct message this week with nothing built beyond a landing page. Its weakest criterion is market demand at 4.94/10, and the fix is focus, not invention. "Churn analytics" is a vague, low-urgency category. "You have a churn review on Thursday and a CSV of cancellation reasons" is an urgent, already-budgeted moment. Every outreach message, sample brief and follow-up in this plan is tied to that trigger event rather than to the category.
The deliverable a buyer can hand to their board is the wedge. Founders do not want a dashboard they must interpret; they want a page that survives scrutiny. Churn Receipts is sold as that page, in minutes, for $149.
Smallest sellable MVP
A paid upload page: Stripe checkout, CSV upload with column auto-mapping, quote-locked reason clustering, and a one-page PDF plus Markdown brief delivered by email - sold as a single $149 run.
Must-have features
- CSV upload with auto-mapped reason/comment, MRR, plan and date columns plus manual override dropdowns
- LLM clustering call constrained to a strict JSON schema: reason name, one-line definition, 2-5 quotes
- Quote Lock validator that string-matches every returned quote against uploaded rows and drops failing reasons
- Revenue-weighted scoring (frequency x MRR-at-risk) with rank-by-frequency fallback when no MRR column exists
- One-page PDF renderer plus Markdown export with ranked table, quotes, plan/date tags and fix-first note
- Copy-ready save-offer draft for the top-ranked reason
- Stripe Checkout, webhook confirmation, Resend email with PDF attachment and magic-link job page
- Internal run log table (status, row count, dropped-reason count) for debugging only
Explicitly out of scope
- No Zendesk, Intercom, SurveyMonkey or app-store review connectors
- No trend dashboards, heatmaps or multi-user team seats
- No non-English handling in the first 30 days
- No free tier or self-serve trial; only a small number of hand-built free sample briefs used as outreach
- No public API, Slack or Notion integration, white-label or SSO
- No human analyst review queue or 24/7 support promise
Demo flow (what the buyer sees)
- Buyer clicks a Stripe Checkout link for the Single Brief at $149
- Checkout succeeds; webhook creates a job and emails a magic link to the upload page
- Buyer uploads the cancellation CSV and confirms the auto-mapped columns
- Pipeline normalizes rows, clusters comments into named reasons and validates every quote against the file
- Reasons below two verified quotes are dropped and logged
- Surviving reasons are scored by frequency x MRR-at-risk and ranked
- PDF and Markdown brief render and land in the buyer's inbox with a download link
- Buyer downloads the one-pager and pastes the Markdown into their investor doc
Technical implementation plan
Stack
Architecture
A single Next.js app holds the landing page, a Stripe Checkout redirect, a webhook endpoint, an upload page protected by a magic-link token, and a job runner. Uploaded CSVs land in Supabase Storage; parsed rows and job state go into Postgres. The job runner sends a compact row sample plus MRR totals to the LLM with a strict JSON schema, then runs the Quote Lock pass locally: each returned quote is normalized for whitespace and matched as a substring of the uploaded rows. Reasons with fewer than two verified matches are deleted. Surviving reasons are scored and passed to the PDF renderer, the PDF is stored and emailed via Resend, and the buyer gets a magic-link job page with the download. The internal run log records status, row count and dropped-reason count for debugging.
Build steps
- Create Next.js repo, deploy an empty app to Vercel, provision Supabase project with jobs, rows and uploads tables
- Build CSV upload endpoint, Papa Parse header detection and the column-mapping UI with manual override dropdowns
- Write the LLM clustering prompt and JSON schema; persist raw model output alongside the parsed rows
- Implement the Quote Lock validator, drop threshold and frequency x MRR-at-risk scoring with frequency fallback
- Build the PDF renderer and Markdown export from a single brief model object
- Create Stripe products and prices, wire Checkout and the webhook to job creation
- Add magic-link tokens, the job page and Resend delivery of the PDF
- Add run log, failed-run alert to the founder, and one retry against the fallback model
- Rehearse three end-to-end runs on messy real-shaped CSVs and fix renderer breakage
AI components
- LLM clustering of cancellation comments into named reasons with definitions and supporting quotes, constrained to JSON schema
- Optional LLM pass to draft the fix-first note and the save-offer text from the top reason's verbatim quotes
Pricing and monetization
Single Brief
Entry offerFor SaaS founder with up to ~1,000 survey responses who needs one defensible churn readout
- One revenue-weighted churn brief (PDF + Markdown)
- Top 7 reasons with verbatim quotes and fix-first notes
- Copy-ready save-offer draft for the top reason
- One free re-run after a column-mapping mistake
Full History Brief
For CS lead preparing a board or investor churn narrative with 1,000-10,000 responses
- Full-history brief with up to 4 plan or segment cuts
- Ranked reasons table with MRR-at-risk per reason
- Quotes tagged with plan and cancellation date
- Markdown export for the investor doc
Monthly Churn Receipt
For Teams running the same review every month who want the delta
- One brief per month on their fresh CSV
- New, vanished and persisting reasons against the prior run
- Email delivery to the buyer's account
Model: One-time per brief with a monthly subscription option for teams who run the same review every month.
First revenue offer: Send the CSV, I'll send back a one-page churn brief ranked by MRR at risk within 24 hours - free, no signup. If it is useful, the next one is $149.
Expected ACV: $199
Upsell path: Start every buyer at $149, pitch $299 Full History when their export exceeds 1,000 rows, then convert repeat buyers to $99/month so the same review recurs without new outreach.
First-customer acquisition
Direct cold DMs and emails to B2B SaaS founders and CS leads who publicly post about churn, offering a free sample brief built from their own exported CSV.
Where to find them
- r/SaaS and r/Entrepreneur churn and cancellation threads from the last 90 days
- Indie Hackers posts tagged churn, retention or 'why customers leave'
- LinkedIn search: Head of Customer Success at 10-50 person B2B SaaS, seed to Series A
- Product Hunt launches from the last 12 months in B2B SaaS categories
- SaaS Slack and Discord communities with an explicit self-promo or feedback channel
- Founders publicly posting monthly revenue or churn updates on X
Exact outreach motions
- Send 30 DMs offering a free one-page brief from their own cancellation CSV export
- Deliver every returned sample within 4 hours and quote their strongest verbatim line back
- Follow up on day 3 and day 7 quoting one line from their own data, never a generic reminder
- Attach a Stripe link for $149 once the sample has been delivered and acknowledged
- Publish one anonymized public teardown in r/SaaS with a tracked link to the free-sample offer
- Ask every paying customer for one intro to another SaaS founder immediately after delivery
Message template
Hey {first} - saw your post about customers leaving. If you already export cancellation reasons to CSV, send it over and I'll send back a one-page brief: top reasons ranked by MRR at risk, every reason tied to verbatim quotes from your own file. Free, no signup, back within 24h. If it is useful the next one is $149.30-day execution roadmap
Week 1 · Build & validate · 7 days
Deploy the empty product
- Create Next.js repo and deploy to Vercel
- Provision Supabase tables and storage bucket
- Create Stripe prices for $149, $299 and $99/mo
- Draft landing page headline and privacy copy
Deliverable: Deployed empty app with Stripe test keys
Get a file in and mapped
- Build upload endpoint writing to Supabase Storage
- Auto-detect reason, MRR, plan and date columns
- Add manual override dropdowns
- Cap rows at 10,000 with a clear error
Deliverable: Uploaded CSV renders mapped columns
Reasons out of comments
- Write the clustering prompt and strict JSON schema
- Send a row sample plus MRR totals
- Persist raw model output per job
- Handle malformed JSON with one retry
Deliverable: One CSV produces a JSON reason list
Evidence or drop
- Implement whitespace-normalized substring matching of quotes against rows
- Drop reasons with fewer than two verified quotes
- Score by frequency x MRR-at-risk with frequency fallback
- Log dropped-reason count per run
Deliverable: Scored, quote-verified reason list
End-to-end paid run
- Render the one-page PDF and Markdown export
- Wire Stripe Checkout and webhook to job creation
- Send the PDF via Resend with a magic-link job page
- Run a full paid test on your own sample CSV
Deliverable: Live end-to-end run at $149
150 named buyers
- Collect 150 companies from churn threads, Indie Hackers and Product Hunt
- Add LinkedIn Head of CS contacts at 10-50 person SaaS
- Record size, contact, source URL and churn trigger
- Mark the 60 strongest as Tier A
Deliverable: 150-row outreach spreadsheet
Prove the artifact
- Hand-build 3 briefs from publicly posted churn data
- Fix renderer breakage found in those runs
- Publish the privacy page explaining CSV handling
- Add the free-sample offer above the fold
Deliverable: 3 sample PDFs and a live privacy page
Week 2 · Launch & first sale · 7 days
First 30 messages
- Send 30 DMs and emails with the free-sample offer
- Log every send, open and reply
- Reply to inbound within 2 hours
Deliverable: 30 messages sent, funnel sheet started
Deliver fast
- Send 30 more messages to Tier A list
- Deliver every returned sample within 4 hours
- Record change requests in the buyer's own words
Deliverable: 5+ sample briefs delivered
First dollar
- Send day-3 follow-ups quoting their strongest verbatim line
- Attach the $149 Stripe link to every warmed lead
- Ask each lead their monthly cancellation volume
Deliverable: First paid checkout attempts
Raise output quality
- Run 4 more sample briefs
- Patch the top 3 renderer complaints
- Tune the Quote Lock threshold if briefs are thin
Deliverable: Renderer v2 shipped
Second segment
- Send 25 connection notes to Heads of CS
- Post one anonymized brief excerpt
- Offer free samples to everyone who reacts
Deliverable: 25 touches and one public post
Convert samples to paid
- Message every sample recipient with the $149 or $299 choice
- Offer one free re-run as the close
- Log each outcome by company
Deliverable: Paid conversion tally
Fix the message, not the volume
- Compute reply, sample and paid rates per segment
- Rewrite the template around the best subject line
- Cut the weakest segment entirely
Deliverable: Revised template and one-page funnel sheet
Week 3 · Repeat & systematize · 7 days
Earn inbound
- Post an anonymized 'why these customers left' breakdown in r/SaaS
- Include a tracked link to the free-sample offer
- Answer every comment the same day
Deliverable: Live post with tracked link
Scale the best segment
- Send 40 messages to the best-performing segment
- Log every reply verbatim
- Reply to inbound within 2 hours
Deliverable: 40 messages sent
Raise average order
- Pitch $299 Full History to any buyer above 1,000 rows
- Pitch $99/month to repeat buyers
- Deliver every pending brief same day
Deliverable: Upsell offers sent to all prior buyers
Borrow trust
- Ask every paying customer for one intro
- Send a short thank-you with the shareable sample
- Log referral source per new lead
Deliverable: 8 referral asks sent
Stay solo
- Add fallback model provider and one automatic retry
- Alert the founder by email on any failed run
- Strip manual steps from the runbook
Deliverable: Runbook with under 15 minutes manual time per brief
Keep both taps open
- Send 40 messages
- Publish a second anonymized excerpt on LinkedIn
- Reply to all thread comments
Deliverable: 40 sent and one post live
Reallocate
- Compare collected revenue against the base scenario
- Cut the two lowest-yield activities
- Double the single best-performing channel
Deliverable: Revised plan for days 22-30
Week 4 · Scale what works · 7 days
Recurring revenue
- Create the Stripe $99/month subscription price
- Offer it to every one-time buyer
- Add new, vanished and persisting reason highlighting
Deliverable: Subscription tier live
Community channels
- Send 40 messages in Indie Hackers and permitted SaaS Slacks
- Share the sample offer where self-promo is allowed
- Log which community converts
Deliverable: 40 messages sent
Make the page convert
- Deliver all pending briefs
- Write one anonymized before-and-after note
- Add a proof section to the landing page
Deliverable: Landing page proof section live
Borrow audiences
- Message 10 SaaS newsletter writers and community mods
- Offer one free brief for their audience
- Track opens from each placement
Deliverable: 10 amplifier asks sent
Remove friction
- Collapse to a single Stripe payment link
- Add a 3-question upload intake
- Test the full mobile flow
Deliverable: Shortened mobile checkout
Final volume
- Send 40 messages
- Follow up all second-touch leads
- Deliver every brief the same day
Deliverable: 40 sent, all second touches closed
Clean ledger
- Chase unpaid or failed payments
- Confirm all settlements in the TrustMRR-connected account
- Resolve any refund request within 24 hours
Deliverable: Clean payment ledger
Days 29-30 · Consolidate · 2 days
Last-call offer
- Send 50 messages with a 48-hour offer
- Email past sample recipients the $149 last call
- Deliver all pending briefs
Deliverable: 50 touches plus last-call email
Ship and document
- Deliver every outstanding brief before 13:00 UTC
- Export run log and revenue summary
- Write the post-mortem with refunds and drop rates
Deliverable: Final ledger and post-mortem
Revenue and profit scenarios
How the numbers are defined
Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.
Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).
The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.
Stated assumptions
- Conservative: 6 paid briefs at a $149 blended price, treating outreach response as weak
- Base: 18 paid briefs at a $199 blended price across Single Brief and Full History
- Upside: 35 paid briefs at a $199 blended price, matching the concept's monetization hypothesis
- Payment processing assumed at roughly 3.5-4% of collected revenue via Stripe
- Refunds modelled as one $149 refund in base and upside, zero in conservative
- No paid marketing in conservative and base; upside includes $150 of sponsored post or affiliate payouts
- Operating costs cover Vercel, Supabase, LLM inference, PDF rendering and email at under $3 per brief
- All figures are projections from stated assumptions, not observed revenue or customers
Conservative
6 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $32
- Paid marketing
- $0
- Hackathon profit
- $862
- Operating costs
- $30
- Business profit
- $832
Base case
18 customers- Refunds
- $149
- Chargebacks
- $0
- Payment fees
- $143
- Paid marketing
- $0
- Hackathon profit
- $3,290
- Operating costs
- $55
- Business profit
- $3,235
Optimistic
35 customers- Refunds
- $149
- Chargebacks
- $0
- Payment fees
- $279
- Paid marketing
- $150
- Hackathon profit
- $6,387
- Operating costs
- $95
- Business profit
- $6,292
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $2,682
- Payment fees (3.9%)
- $105
- Paid marketing
- $0
- Hackathon profit
- $2,577
- Business profit
- $2,522
Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.
Scenario models from stated assumptions, not verified revenue. Projections only - no customers, revenue or traction exist at launch.
Main risks and validation experiments
Risk 1Cold outreach response rates fall far below the assumption and 35 paid briefs become unreachable in 30 days.
Front-load all outreach into days 6-20, measure reply rate daily, and cut any segment below a 5% reply rate after 40 messages.
Send 30 messages on day 8 and count replies within 72 hours before writing any more copy.
Fewer than 2 replies from the first 60 messages means the message or segment is wrong; rewrite the offer before sending message 61.
Risk 2Quote Lock rejects legitimately clustered reasons on messy CSVs, producing thin briefs and refund requests.
Normalize whitespace and punctuation before matching, allow partial-phrase matching above a length threshold, and re-run any brief with fewer than three surviving reasons at no charge.
Run 10 messy real-shaped CSVs through the pipeline and record the dropped-reason count for each.
If more than 40% of reasons are dropped on average across 10 runs, the clustering prompt or the matcher must be rebuilt before selling.
Risk 3Buyers refuse to upload customer verbatims without a clear privacy answer.
Publish a plain privacy page: file stored encrypted, used only for that run, deletable on request, not used for training.
A/B the upload page with and without a visible one-line privacy reassurance on the first 20 samples offered.
If more than half of interested leads ask about data handling and then go silent, ship a delete-after-7-days guarantee before continuing outreach.
Risk 4A founder pastes the same CSV into a general chatbot for free and never pays $149.
Lead every sample with the Quote Lock proof: every reason traced to a named row, plus the MRR-at-risk number they cannot get without the ranking step.
Ask the first five sample recipients directly whether they had already tried a chatbot on the same file.
If 4 of 5 say a chatbot output was good enough, reposition from 'analysis' to 'the artifact your board will accept' or stop.
Risk 5Single LLM provider outage or price change stalls delivery inside the revenue window.
Keep a second provider configured behind a feature flag with the identical JSON schema, and retry automatically once before alerting.
Force a provider failure in staging on day 19 and confirm a brief still lands in the buyer's inbox.
If a forced failover takes more than 15 minutes of manual work, stop selling volume until the retry path is automated.
Hour-by-hour: the first 24 hours
Hours 1-2
- Create Next.js repo and deploy an empty page to Vercel
- Provision Supabase project with jobs and uploads tables
- Create Stripe products and prices for all three tiers
Output: Deployed shell with Stripe test keys
Hours 3-5
- Build CSV upload to Supabase Storage
- Add Papa Parse header detection for reason, MRR, plan and date
- Ship the manual override dropdowns
Output: Working upload with mapped columns
Hours 6-9
- Write the clustering prompt and strict JSON schema
- Call the LLM on a sample file and persist the raw output
- Run Quote Lock against the returned quotes
Output: First quote-locked reason list from a real CSV
Hours 10-12
- Render the one-page PDF and Markdown export from the reason list
- Eyeball the artifact against what a churn review actually needs
- Log every layout failure to fix on day 2
Output: First complete draft brief PDF
Full 30-day launch report
Read the full generated report
Churn Receipts - 30-Day Launch Report
1. Product opportunity and positioning
A 10-50 person B2B SaaS company already runs a cancellation or exit survey. The responses sit in a CSV that nobody wants to read. Once a month, or once a quarter before an investor update, the founder or Head of Customer Success has to explain why customers leave. That explanation is currently built by hand: open the file, skim the comment column, and pick three quotes that support the story already believed. "Too expensive" gets logged as a pricing problem when the underlying comment says the buyer could not get SSO approved. The roadmap fix lands in the wrong place and the same churn repeats.
Churn Receipts sells one artifact that replaces that ritual. The buyer pays, uploads the CSV, and receives a one-page PDF plus Markdown brief within minutes: the top seven reasons ranked by frequency multiplied by MRR-at-risk, each reason locked to at least two verbatim quotes from their own file, plus a fix-first recommendation and a copy-ready save-offer draft for reason one.
Quote Lock is the trust argument. A reason that cannot be evidenced by two real rows in the uploaded data is deleted, not softened. That single rule separates this from a chatbot session where the buyer has to take the model's word for it. It also gives the buyer something a chatbot cannot: a number per reason, defensible in front of a board.
The positioning is deliberately narrow. No integrations, no dashboard, no trend tracking, no team seats, no free tier. The buyer supplies a file they already own and receives the document they already owe. That transaction is priced one-time so it clears any approval threshold without procurement.
JEV scores this concept 63.1 out of 100 in band C. Speed to first revenue is the strongest criterion at 8.18/10. Market demand is the weakest at 4.94/10, and the correction here is focus, not invention. "Churn analytics" is a vague category. "You have a churn review and a CSV of cancellation reasons" is a trigger. Every message in this plan names the trigger.
2. Smallest sellable MVP
One paid path: Stripe Checkout, a CSV upload with auto-mapped reason/MRR/plan/date columns, an LLM clustering call constrained to a strict JSON schema, a local Quote Lock validator, frequency x MRR-at-risk scoring, and a one-page PDF plus Markdown delivered by email with a magic-link job page.
The only internal surface is a run log recording status, row count and dropped-reason count. Nothing customer-facing resembles a dashboard. Five build days, deadline day 5.
3. Technical implementation plan
Next.js on Vercel handles the landing page, Checkout redirect, webhook, upload page and job runner. Supabase holds uploads, parsed rows and job state. The clustering call goes to OpenAI with JSON-schema output and Anthropic as a fallback behind a flag. Quote Lock runs locally after the call, matching normalized quotes as substrings of parsed rows. Survivors are scored, rendered with @react-pdf/renderer, stored, and emailed through Resend. No headless browser, no queue infrastructure beyond a scheduled retry.
The riskiest step is Quote Lock on messy data. The mitigation is normalization before matching, a re-run at no charge for any brief under three surviving reasons, and a hard check on day 4 before payment is wired on day 5.
4. Pricing and monetization
Single Brief at $149 one-time, Full History at $299 one-time, Monthly Churn Receipt at $99/month. A $199 expected blended value assumes most buyers land on Single Brief with a meaningful share upgrading once their export turns out to exceed a thousand rows. The monthly tier exists to convert repeat buyers so the recurring review needs no new outreach.
5. First-customer acquisition
Direct DMs and emails to founders and CS leads who publicly post about churn, in r/SaaS, Indie Hackers, LinkedIn and Product Hunt launches from the last year. The offer is a free sample brief built from the buyer's own exported CSV, delivered within 24 hours, no signup. Once delivered, the next run is $149 with a Stripe link attached. Follow-ups on day 3 and day 7 quote a line from the buyer's own data rather than sending a reminder. Week-one target: 150 companies listed, 60 messages sent, six CSVs received, five sample briefs delivered.
6. 30-day execution roadmap
Days 1-5 build: skeleton and Stripe prices, CSV ingest and column mapping, clustering with JSON schema, Quote Lock and scoring, then the PDF renderer plus Checkout plus email, closing with one end-to-end paid test run. Day 5 is the MVP deadline.
Days 6-14 sell: build the 150-company list, hand-build three public sample briefs, then two 30-message waves, same-day sample delivery, day-3 follow-ups quoting the buyer's own verbatim lines, a LinkedIn push to Heads of CS, a paid conversion push, and a day-14 funnel review that rewrites the template. First sale target is day 10.
Days 15-21: a public anonymized teardown in r/SaaS, 40 messages, upsell to Full History for anyone above 1,000 rows, referral asks, ops hardening with provider failover, and a midpoint review that cuts the two weakest activities.
Days 22-30: launch the $99 monthly tier with delta highlighting, three more 40-message waves, a landing page proof section, ten amplifier asks to newsletter writers and community mods, checkout simplification, ledger cleanup, a 50-message last-call push, and a day-30 close before 13:00 UTC.
7. Revenue and profit scenarios
All figures below are projections from stated assumptions. No customers, revenue or traction exist at launch.
Conservative: 6 briefs at $149 = $894 gross. Refunds $0, chargebacks $0, processing $32, ad spend $0, operating costs $30. Hackathon profit $862; business profit $832.
Base: 18 briefs at $199 = $3,582 gross. Refunds $149, chargebacks $0, processing $143, ad spend $0, operating costs $55. Hackathon profit $3,290; business profit $3,235.
Upside: 35 briefs at $199 = $6,965 gross. Refunds $149, chargebacks $0, processing $279, ad spend $150, operating costs $95. Hackathon profit $6,387; business profit $6,292.
Processing is modelled at roughly 3.5-4% through Stripe. Operating cost stays under $3 per brief across hosting, inference, rendering and email, so every sale clears its own delivery cost.
8. Main risks and validation experiments
Outreach response. Send 30 messages on day 8 and count replies within 72 hours. Fewer than two replies from 60 messages means the message or the segment is wrong.
Quote Lock over-rejection. Run ten messy real-shaped CSVs and record dropped-reason rates. Above 40% average, rebuild the prompt or matcher before selling.
Data privacy hesitation. A/B the upload page with and without a one-line privacy reassurance. If half of interested leads ask about data handling and go silent, ship a delete-after-seven-days guarantee.
The free chatbot substitute. Ask the first five sample recipients whether they already tried a chatbot on the same file. If four of five say that output was good enough, reposition from analysis to board-defensible artifact or stop.
Provider dependency. Force a failover in staging on day 19. If it takes more than 15 minutes of manual work, stop selling volume until the retry path is automated.
9. First 24-hour action plan
Hours 1-2: deploy the Next.js shell, provision Supabase, create all three Stripe prices. Hours 3-5: upload with Papa Parse header detection and manual override dropdowns. Hours 6-9: clustering prompt with strict JSON schema, persisted output, first Quote Lock run. Hours 10-12: render the first draft PDF and Markdown, then log every layout failure for day 2.
By hour 12 there is a real brief produced from a real CSV. Everything after that is repetition, outreach and collection.
This brief was generated from public data about established startups, then narrowed and scored for a solo 30-day launch. Revenue and profit figures are scenario models, not verified results, guarantees or evidence of existing customers. Validate demand yourself before you spend a month on it — and check the contest rules for what counts toward your score.
Related ideas
All ideas →Chargeback Evidence Forge
Turns a disputed order's support messages and tracking into a reason-code-matched evidence PDF for Stripe chargeback responses.
BriefToBoard Compiler
Turns a signed client brief into an importable project board, a one-page scope memo, and a missing-inputs checklist for small web-design and branding agencies.
MissedCall Quote Card
Turns a missed call plus a customer photo into a ready-to-send SMS quote card for solo home-service pros.