ExitLens Brief
Turns a SaaS company's raw cancellation reasons into a one-page churn-cause brief with the top fix ranked by dollars at risk.
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.
Head of Product or founder at a B2B SaaS with 20-200 employees who just saw a churn spike and has cancellation reasons sitting unused.
Monetization potential 4.1/10
Tie the price to a measurable money or time outcome and add a recurring or repeat-purchase path instead of a single low-value charge.
Why this could work in 30 days: one founder can ship the MVP in 4 days; the plan targets a first sale on day 12; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.6/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
15 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Head of Product or founder at a B2B SaaS with 20-200 employees who just saw a churn spike and has cancellation reasons sitting unused.
Why now
Churn pressure is immediate and the buyer already owns the needed text, so no integration, recruitment or procurement cycle is required.
Problem
Cancellation reasons and exit-survey text pile up in Stripe, Intercom or a spreadsheet, and nobody has time to cluster them into a prioritized fix.
Solution
Buyer uploads or pastes cancellation reasons plus MRR per account; the pipeline clusters themes, scores dollars at risk, and delivers a one-page ranked churn brief as PDF and Markdown.
Product opportunity and positioning
ExitLens Brief is a paid artifact, not a research platform. The buyer is a Head of Product or founder at a 20-200 person B2B SaaS who has just seen churn move and already has cancellation reasons in Stripe, Intercom, a helpdesk export or a spreadsheet. The pain is not data collection. It is synthesis: nobody has time to cluster messy cancellation text, attach money to each theme, and decide what to fix first. ExitLens Brief converts that unused text into one page with named churn-cause themes, evidence quotes, estimated dollars at risk per theme, and a ranked top fix.
JEV scores the concept 60.1/100 in band C. The strong axes are speed to first revenue (8.57 normalized) and solo build feasibility (7.83). The weak axes are market demand (4.29) and monetization potential (4.10). The launch plan responds directly: narrow the trigger to a recent churn spike, sell a single $99 brief before building anything broad, and add a $249 quarterly pack for repeat use. The product does not compete with full research suites. It wins by being the fastest path from messy cancellation text to a decision the buyer can forward to their team the same day. No integration, recruitment, procurement or trust cycle is required because the buyer already owns the data and can upload it in minutes.
Smallest sellable MVP
A paid intake page that accepts pasted or CSV cancellation reasons, generates a ranked churn-cause brief, and emails PDF plus Markdown within 24 hours.
Must-have features
- CSV or paste intake for cancellation reasons plus MRR per account
- LLM clustering into named churn-cause themes
- Dollar-at-risk scoring per theme from uploaded MRR
- One-page brief renderer to PDF and Markdown
- Stripe Checkout with instant order confirmation
- Resend email delivery of brief links
- Simple job queue so each order processes without manual work
- One revision pass handled through a simple request form
Explicitly out of scope
- No live Stripe or Intercom webhook integration
- No participant recruitment or interviews
- No Linear or Jira export
- No dashboard or ongoing analytics
- No team seats or admin console
- No mobile app
Demo flow (what the buyer sees)
- Buyer lands on the ExitLens Brief page.
- Buyer pays $99 through Stripe Checkout.
- Buyer uploads CSV or pastes cancellation reasons plus MRR.
- Job is queued and validated.
- LLM clusters themes and extracts evidence quotes.
- Dollar-at-risk scoring runs on MRR inputs.
- PDF and Markdown brief are rendered.
- Email delivery sends both files.
- Buyer submits one revision request if needed.
Technical implementation plan
Stack
Architecture
Next.js serves the landing page and intake form on Vercel. Stripe Checkout confirms payment and writes the order to Supabase. The buyer uploads a CSV or pastes text; a server action validates columns and stores the job. A worker picks up the job, calls OpenAI with a strict JSON schema for themes, evidence quotes and fix recommendations, then deterministic code computes dollars at risk from MRR. React-PDF renders the one-page brief, Supabase Storage holds the files, and Resend emails the links. No manual processing is required after launch, but failed jobs are monitored daily.
Build steps
- Scaffold Next.js and Supabase.
- Add Stripe Checkout and order table.
- Build intake and validation.
- Implement LLM prompt and JSON schema.
- Add dollar-at-risk scoring.
- Build PDF and Markdown renderer.
- Wire Resend email delivery.
- Add queue and retry handling.
- Run three redacted test briefs.
- Deploy to production.
AI components
- Theme extraction and naming
- Duplicate-theme merging
- Fix recommendation drafting
- Optional revision summary drafting
Pricing and monetization
Single Churn Brief
Entry offerFor Founder or Head of Product with one churn question to answer now
- One ranked churn-cause brief as PDF and Markdown
- Dollar-at-risk scoring per theme
- One revision pass
Quarterly Pack
For Teams wanting three briefs across a quarter
- Three briefs
- Comparison of theme movement between briefs
- Email delivery
Model: One-time brief purchases, with a quarterly three-brief pack for repeat use; no subscription is required.
First revenue offer: Send a free redacted sample brief and offer a $99 single churn brief with 24-hour turnaround; payment via Stripe Checkout before data upload.
Expected ACV: $99
Upsell path: After the first brief, offer the $249 Quarterly Pack when the buyer wants to track whether the top fix moved the theme.
First-customer acquisition
Direct outreach to founders and Heads of Product posting publicly about churn or cancellation feedback on LinkedIn and X.
Where to find them
- LinkedIn posts containing churn spike
- LinkedIn posts asking what to do with cancellation reasons
- X posts about exit survey feedback
- X posts from founders discussing lost customers
- Indie Hackers SaaS churn threads
- r/SaaS churn and cancellation discussion threads
Exact outreach motions
- Search LinkedIn and X daily for public churn posts and log 20 qualified profiles.
- Reply to a public post with a useful note and offer a redacted sample brief.
- DM the poster with the $99 single-brief offer and 24-hour turnaround.
- Follow up once after three days with the sample PDF attached.
- Ask interested contacts for one referral to another product leader with churn pressure.
Message template
Saw your post about churn. I turn raw cancellation reasons into a one-page ranked churn brief with dollars at risk. Want a free sample built from a redacted example? If useful, $99 gets your data processed in 24h.
30-day execution roadmap
Week 1 · Build & validate · 7 days
Set up build and payment rails
- Create Next.js repo on Vercel.
- Create Supabase project and order table.
- Configure Stripe test keys and Resend.
Deliverable: Working repo, database and payment test account.
Make a paid intake possible
- Build landing page and intake fields.
- Add Stripe Checkout and order status.
- Store buyer uploads against the order.
Deliverable: Paid test order with stored intake.
Turn text into ranked themes
- Write LLM prompt and JSON schema.
- Add evidence-quote requirement.
- Build dollar-at-risk scoring fixture.
Deliverable: Sample cluster output with scores.
Ship the brief artifact
- Build React-PDF one-page template.
- Add Markdown output.
- Wire Resend delivery and job queue.
Deliverable: End-to-end test brief delivered by email.
Deploy the live product
- Deploy production build.
- Run three redacted test briefs.
- Fix blockers only.
Deliverable: Live MVP accepting paid orders.
Create proof for outreach
- Generate a redacted sample brief.
- Add sample proof section to landing page.
- Write short FAQ on data handling.
Deliverable: Sample PDF and landing proof.
Build the first 100 prospects
- Collect 100 qualified LinkedIn and X profiles.
- Log trigger post and contact field in a sheet.
- Draft three message variants.
Deliverable: 100-profile outreach list and message variants.
Week 2 · Launch & first sale · 7 days
Start direct conversations
- Publish launch post with redacted sample.
- Send 15 personalized DMs.
- Log replies and objections.
Deliverable: 15 touches and reply log.
Find willing sample requests
- Send 20 DMs.
- Reply to 5 public churn posts.
- Record objections in one sheet.
Deliverable: 20 touches and objection log.
Convert interest into sample requests
- Send 20 DMs with sample offer.
- Book 5 sample-brief requests.
- Set 24-hour response expectation.
Deliverable: 5 sample requests.
Recover quiet prospects
- Follow up 10 day-8 contacts.
- Refine message based on objections.
- Add FAQ answer to landing page.
Deliverable: 10 follow-ups and copy update.
Close one paid brief
- Offer $99 brief to warm contacts.
- Close one Stripe payment.
- Process and deliver within 24 hours.
Deliverable: First payment and delivered brief.
Improve the artifact
- Ask first buyer for revision notes.
- Fix output issues found in delivery.
- Update sample if needed.
Deliverable: Revision notes and fixes.
Revive sample requesters
- Follow up 5 sample requesters.
- Publish redacted example.
- Track next action for each contact.
Deliverable: 5 follow-ups and public sample.
Week 3 · Repeat & systematize · 7 days
Expand prospect list
- Send 25 new DMs.
- Update landing copy with objections.
- Log qualified replies.
Deliverable: 25 touches and landing update.
Reduce delivery errors
- Add CSV preview and required columns.
- Test malformed files.
- Add sample CSV download.
Deliverable: Validation release.
Test repeat-purchase interest
- Send 25 DMs.
- Offer Quarterly Pack to interested leads.
- Track pack interest separately.
Deliverable: 25 touches and 5 pack offers.
Create a public example
- Publish redacted churn-brief teardown.
- Add post link to outreach profile.
- Pin the sample offer.
Deliverable: Public teardown post.
Keep conversations moving
- Send 25 DMs.
- Follow up 10 prior contacts.
- Update reply tracker.
Deliverable: 25 touches and updated tracker.
Keep turnaround under 24 hours
- Process all paid orders.
- Track delivery start and finish times.
- Log any failed jobs.
Deliverable: Delivery log.
Keep or kill outreach angles
- Calculate reply and sample conversion.
- Identify best-performing message angle.
- Write channel decision memo.
Deliverable: Channel memo.
Week 4 · Scale what works · 7 days
Ship the repeat offer
- Add $249 pack checkout.
- Build comparison template.
- Test pack order flow.
Deliverable: Quarterly Pack live.
Target two sales this week
- Send 30 DMs.
- Book 5 new sample requests.
- Prioritize buyers with recent churn posts.
Deliverable: 30 touches and 5 sample requests.
Test pack demand
- Offer Quarterly Pack to buyers.
- Offer pack to sample requesters.
- Log objections.
Deliverable: 10 pack offers.
Improve brief usefulness
- Strengthen evidence quotes section.
- Clarify ranked top fix section.
- Rebuild sample PDF.
Deliverable: Updated brief template.
Add warm paths
- Send 30 DMs.
- Ask happy contacts for referrals.
- Track referral source.
Deliverable: 30 touches and referral log.
Clear the queue
- Deliver all pending briefs.
- Collect revision requests.
- Confirm files were received.
Deliverable: Zero pending orders.
Adjust messaging only
- Review week-4 conversion.
- Review refunds and revisions.
- Write metrics memo.
Deliverable: Metrics memo.
Days 29-30 · Consolidate · 2 days
Maximize inside-window sales
- Send 40 DMs.
- Publish redacted sample again.
- Follow up all warm contacts.
Deliverable: 40 touches and follow-up log.
Verify and document
- Verify payments in TrustMRR.
- Deliver remaining briefs.
- Write next-step memo.
Deliverable: Final profit inputs and next-step memo.
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: 3 buyers at $99, organic outreach only.
- Base: 10 buyers at $99, organic outreach only.
- Upside: 25 buyers at $99, includes $150 paid marketing.
- Payment fees assume Stripe Checkout at roughly 4.1% blended.
- Refunds are 0 in conservative and base; upside assumes one $99 refund.
- Chargebacks are 0 in all scenarios.
- Operating costs cover Vercel, Supabase, OpenAI usage, Resend and domains.
- Paid ad spend is paid marketing only; organic outreach is $0.
- Scenarios are projections, not verified revenue or existing customers.
Conservative
3 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $12
- Paid marketing
- $0
- Hackathon profit
- $285
- Operating costs
- $25
- Business profit
- $260
Base case
10 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $40
- Paid marketing
- $0
- Hackathon profit
- $950
- Operating costs
- $45
- Business profit
- $905
Optimistic
25 customers- Refunds
- $99
- Chargebacks
- $0
- Payment fees
- $97
- Paid marketing
- $150
- Hackathon profit
- $2,129
- Operating costs
- $90
- Business profit
- $2,039
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $990
- Payment fees (3.9%)
- $39
- Paid marketing
- $0
- Hackathon profit
- $951
- Business profit
- $906
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.
Main risks and validation experiments
Risk 1Buyers may refuse to share customer cancellation text with an unknown solo founder.
Offer a redacted sample first, state a clear deletion policy, and collect payment before upload.
Ask 20 qualified prospects if they would share an export for a $99 brief.
Change the concept if fewer than 2 of 20 say yes.
Risk 2LLM clustering may produce themes too generic to act on.
Require named themes, evidence quotes and a ranked top fix; include one revision pass.
Run three synthetic cancellation datasets and have a product friend rank the top fix.
Change the output format if the top fix is not actionable in two of three tests.
Risk 3Churn briefs may be one-off purchases with no repeat revenue.
Ship the $249 Quarterly Pack with theme movement comparison.
Offer the pack to 10 sample requesters and interested leads.
Revisit monetization if fewer than 1 of 10 shows interest.
Risk 4Outreach from a no-audience account may be throttled or ignored.
Use personalized low-volume messages on LinkedIn and X and build in public with redacted samples.
Send 100 touches and measure reply rate and sample requests.
Change the channel angle if reply rate stays under 5% after 100 touches.
Risk 5A refund-heavy week could erase projected profit.
Keep scope tight, deliver in 24 hours, show the sample before purchase, and offer one revision.
Track refund requests and revision requests per order.
Tighten the offer if refunds exceed 10% of paid orders.
Hour-by-hour: the first 24 hours
Hours 1-2
- Lock landing copy and create the repo.
- Create Supabase project and Stripe test account.
- Configure Resend API key.
Output: Working repo and environment.
Hours 3-4
- Build intake form fields.
- Create order table.
- Connect form to order creation.
Output: Intake page and order schema.
Hours 5-6
- Write LLM clustering prompt.
- Define JSON schema for themes and quotes.
- Create a synthetic test fixture.
Output: Prompt v1 and test fixture.
Hours 7-8
- Build PDF and Markdown renderer.
- Render a brief from synthetic data.
- Fix layout issues.
Output: Sample brief file.
Hours 9-12
- Wire Stripe Checkout.
- Wire Resend delivery.
- Deploy a private test and send three test briefs.
Output: End-to-end MVP test and bug list for day 2.
Full 30-day launch report
Read the full generated report
ExitLens Brief - 30-Day Launch Report
1. Product opportunity and positioning
ExitLens Brief is a paid artifact, not a research platform. The buyer is a Head of Product or founder at a 20-200 person B2B SaaS who has just seen churn move and already has cancellation reasons in Stripe, Intercom, a helpdesk export or a spreadsheet. The pain is not data collection. It is synthesis: nobody has time to cluster messy cancellation text, attach money to each theme, and decide what to fix first. ExitLens Brief converts that unused text into one page with named churn-cause themes, evidence quotes, estimated dollars at risk per theme, and a ranked top fix.
JEV scores the concept 60.1/100 in band C. The strong axes are speed to first revenue (8.57 normalized) and solo build feasibility (7.83). The weak axes are market demand (4.29) and monetization potential (4.10). The launch plan responds directly: narrow the trigger to a recent churn spike, sell a single $99 brief before building anything broad, and add a $249 quarterly pack for repeat use. The product does not compete with full research suites. It wins by being the fastest path from messy cancellation text to a decision the buyer can forward to their team the same day. No integration, recruitment, procurement or trust cycle is required because the buyer already owns the data and can upload it in minutes.
2. Smallest sellable MVP
The smallest sellable MVP is a paid intake page that accepts pasted or CSV cancellation reasons plus MRR per account, generates a ranked churn-cause brief, and emails a PDF and Markdown file within 24 hours. Must-have features: CSV or paste intake; LLM clustering into named themes; dollar-at-risk scoring from uploaded MRR; one-page PDF and Markdown renderer; Stripe Checkout; Resend delivery; simple job queue; one revision pass. Out of scope: live Stripe or Intercom webhooks, participant recruitment, interviews, Linear or Jira export, dashboard, team seats, admin console, mobile app. Demo flow: buyer lands, pays $99, uploads reasons and MRR, job queues, LLM clusters and scores, renderer creates PDF and Markdown, email delivers links, buyer requests one revision. Build time is four days.
3. Technical implementation plan
Stack: Next.js on Vercel, Supabase Postgres, OpenAI API, Stripe Checkout, Resend, React-PDF, and a lightweight job queue. Architecture: the landing page and intake form run on Next.js. Stripe Checkout confirms payment and writes the order to Supabase. The buyer uploads a CSV or pastes text; a server action validates columns and stores the job. A worker picks up the job, calls OpenAI with a strict JSON schema for themes, evidence quotes and fix recommendations, then deterministic code computes dollars at risk from MRR. React-PDF renders the one-page brief, Supabase Storage holds the files, and Resend emails the links. No manual processing is required after launch, but failed jobs are monitored daily.
Build steps: scaffold Next.js and Supabase; add Stripe Checkout and order table; build intake and validation; implement LLM prompt and JSON schema; add dollar scoring; build PDF and Markdown renderer; wire Resend; add queue and retry; run three redacted test briefs; deploy to production. Hardest technical risk: messy CSV or paste and inconsistent account labels can misallocate dollar risk or produce generic themes. Mitigate with column preview, required headers, a sample CSV, evidence-quote requirements, and a manual revision path. AI components: theme extraction and naming, duplicate-theme merging, fix recommendation drafting; dollar math stays deterministic in code.
4. Pricing and monetization
Pricing is one-time, not subscription. Single Churn Brief is $99 and includes one ranked brief as PDF and Markdown, dollar-at-risk scoring per theme, and one revision pass. Quarterly Pack is $249 and includes three briefs plus a comparison of theme movement between briefs. The first-revenue offer is a free redacted sample brief plus a $99 single brief with 24-hour turnaround; payment happens through Stripe Checkout before data upload. Expected first ACV is $99. The upsell path is the Quarterly Pack when the buyer wants to track whether the top fix moved the theme. This keeps the first purchase low-friction and gives repeat revenue without a subscription promise the solo founder cannot yet support.
5. First-customer acquisition
Primary channel: direct outreach to founders and Heads of Product posting publicly about churn or cancellation feedback on LinkedIn and X. Find them by searching LinkedIn and X for phrases like churn spike, cancellation reasons, exit survey, and lost a customer because. Build a daily list of 100 qualified profiles. Reply or DM with a specific note and a redacted sample brief, not their data. Offer the $99 brief with 24-hour turnaround. Follow up once after three days with the sample attached. Week-one goal: 30 personalized outreach messages and 5 sample-brief requests, with the first paid brief targeted by day 12.
Message template: Saw your post about churn. I turn raw cancellation reasons into a one-page ranked churn brief with dollars at risk. Want a free sample built from a redacted example? If useful, $99 gets your data processed in 24h.
6. 30-day execution roadmap
Days 1-4 build the MVP: repo, Stripe, intake, LLM clustering, dollar scoring, PDF and Markdown, Resend, queue. Day 5 is the MVP deadline: deploy and run three redacted test briefs. Days 6-7 create the redacted sample and a 100-profile outreach list. Days 8-12 launch outreach, send 55 personalized messages, collect sample requests, and close the first $99 brief by day 12. Days 13-21 deliver first orders, add CSV validation, publish a redacted example, and review conversion angles. Days 22-28 add the $249 Quarterly Pack checkout, send 30 new touches, process all orders, and collect revision feedback. Days 29-30 run a final 40-touch push, verify payments in TrustMRR, deliver remaining briefs, and write the next-step memo. The JSON roadmap contains the exact day-by-day tasks and deliverables.
7. Revenue and profit scenarios
These are projections, not verified revenue. Conservative: 3 customers at $99 equals $297 gross; refunds $0, chargebacks $0, payment fees $12, ad spend $0, operating costs $25. Base: 10 customers at $99 equals $990 gross; refunds $0, chargebacks $0, payment fees $40, ad spend $0, operating costs $45. Upside: 25 customers at $99 equals $2,475 gross; refunds $99, chargebacks $0, payment fees $97, ad spend $150, operating costs $90. Payment fees assume Stripe Checkout at roughly 4.1% blended. Hackathon profit is gross revenue minus refunds, chargebacks, payment fees and paid ad spend; business profit additionally subtracts operating costs. The conservative case tests whether one brief can sell. The base case assumes the outreach plan produces 10 buyers. The upside case assumes the sample brief converts and the Quarterly Pack lifts repeat purchase.
8. Main risks and validation experiments
Data-sharing refusal: buyers may not share customer text with an unknown solo founder. Mitigate with a redacted sample, clear deletion policy, and payment before upload. Test with 20 DMs asking if they would share an export for $99; kill if fewer than 2 say yes. Generic themes: LLM output may be too vague. Require evidence quotes, named themes and a ranked fix; test three synthetic datasets and have a product friend rank the top fix. Kill if the top fix is not actionable. One-off purchase: mitigate with the $249 Quarterly Pack and theme movement comparison; test by offering the pack to 10 sample requesters. Kill if fewer than 1 shows interest. Outreach throttling: use personalized low-volume messages on two platforms and build in public; kill the angle if 100 touches produce under 5% reply. Refund risk: keep scope tight, deliver in 24 hours, offer one revision; kill if refunds exceed 10% of orders.
9. First 24-hour action plan
Hours 1-2: lock the landing copy and create the repo, Supabase project, and Stripe test account. Output: working repo and environment. Hours 3-4: build the intake form fields and order table. Output: intake page. Hours 5-6: write the LLM clustering prompt and JSON schema. Output: prompt v1 and test fixture. Hours 7-8: build the PDF and Markdown renderer with a synthetic dataset. Output: sample brief file. Hours 9-12: wire Stripe Checkout and Resend, deploy a private test, and send three test briefs to yourself. Output: end-to-end MVP test and a bug list for day 2.
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 →Proofwright
Proofwright runs the customer interview on autopilot and returns a publish-ready case study draft, pull quotes and social copy, white-labeled under the writer's own brand.
Listing Foundry
Listing Foundry turns phone photos of a property into a print-ready 'Just Listed' flyer and a 5-slide Instagram carousel in under 3 minutes.
Bridge Brief
Turns a founder's own LinkedIn connections export into a ranked warm-intro map against a specific target list, with a ready-to-send ask for every path.