Score C · 6.15/10Free to read$100K Hackathon · November 16, 2026 → December 16, 2026Nov 15, 2026

Cohort Autopsy

Uploads a raw event CSV exported from Mixpanel, Amplitude or PostHog and returns a board-ready retention teardown PDF in minutes.

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.

Speculative6.15/10
MVP build (solo)
5 days
Launch price
$0
Sales to $1,000 revenue
not meaningful at this price
First paying customer
Direct DMs to founders and PMs who posted in the last 7 days on Reddit r/SaaS, Indie Hackers or X about broken retention data, churn or an upcoming investor update.
Who pays

Founder, Head of Product or Growth lead at a 5-50 person SaaS that already ships product events and has a board, investor or retention-review meeting within 30 days; secondary: freelance analytics consultants producing client reports.

Biggest execution risk

Monetization potential 4.5/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 5 days; the plan targets a first sale on day 10; strongest signal is speed to first revenue at 8.1/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

10 concrete actions. Tick them off as you go — nothing is saved or sent.

0/10
Entry price
$0
Solo build
5 days
30d base revenue
$2,136
30d hackathon profit
$2,070
Section 1 of 8

Product opportunity and positioning

Target customer

Founder, Head of Product or Growth lead at a 5-50 person SaaS that already ships product events and has a board, investor or retention-review meeting within 30 days; secondary: freelance analytics consultants producing client reports.

Why now

The buyer already has the data and a dated meeting, so there is no SDK install, procurement cycle or data-collection wait between first contact and a paid artifact.

Problem

They own the event data but cannot turn a messy CSV export into a defensible retention story without 6-10 hours of spreadsheet pivoting right before a meeting where the numbers get challenged.

Solution

Upload an event CSV (IDs optionally hashed client-side); the product canonicalizes messy event names into ordered intent steps with an LLM, proposes an activation funnel, computes weekly cohort retention and per-step drop-off, ranks instrumentation gaps, and emails a PDF plus read-only share link after a $149 Stripe checkout.

Differentiation · Not a dashboard, not a tracking-plan bot, not an agency retainer: one fixed-price artifact produced from a file the buyer already has, delivered in the same day.

The gap Cohort Autopsy fills

Product analytics tools won the instrumentation war and lost the interpretation war. A 5-50 person SaaS on Mixpanel, Amplitude or PostHog has thousands of events and no agreed answer to "is retention actually improving?" The dashboard exists; the story does not. When a board meeting or an unexplained retention drop forces the question, someone exports a CSV and spends six to ten hours in Sheets reconciling inconsistent event names (signup_complete, Sign Up, onboarding_done_v2) before producing a chart nobody fully trusts.

The buyer is specific: a founder, Head of Product or Growth lead at a 5-50 person SaaS who already ships events and has a dated meeting. The trigger is external and near-term — a board update, an investor ask, a retention review. That trigger is what makes a $149 one-time purchase easy: the alternative is an analyst, a consultant retainer, or another wasted afternoon that ends in a chart the CEO pokes holes in.

Why this wedge and not a broader one

The narrowness is the point. Cohort Autopsy does not ingest events, does not run a JS snippet, does not persist a tracking plan and does not claim to be a system of record. It converts one file into one artifact. That removes every classic blocker a solo founder cannot clear in 30 days: no integration approval, no security review, no procurement, no migration, no learning curve. The buyer's only action is an upload.

The deliverable maps directly onto a meeting that already exists on the buyer's calendar. A teardown with weekly cohort curves, D1/D7/D30 retention, an auto-identified activation funnel with per-step drop-off, and a ranked list of the events missing from the file answers the question that gets asked in the room — and the instrumentation-gap list quietly reframes the conversation from "our retention is bad" to "here is what we cannot measure yet," which is a more flattering and more actionable story for the person presenting.

Positioning against the alternatives

Against a dashboard: a dashboard shows a number; Cohort Autopsy produces a narrative with an appendix. Against an analyst or agency: same artifact in minutes, not weeks, and no retainer. Against hand-pivoting in Sheets: the event-name canonicalization and the funnel ordering are the work, and they are the part a spreadsheet cannot do. Against free retention views in PostHog or GA4: those views are computed on live data but still require the buyer to decide what an activation step is; Cohort Autopsy makes that decision for them and shows its reasoning.

The defensibility is honestly weak — this can be copied. The 30-day advantage is speed and artifact quality: a PDF a Head of Product will forward to their board without editing it first. Every hour in the month should be spent on that artifact and on the DM-to-CSV conversion loop, not on features.

Commercial shape

Three SKUs: a free graded preview that unlocks one chart, a $149 single teardown, and a $499 five-pack for freelance analytics consultants who bill reports to clients. The 5-pack is the repeat-purchase path the concept's JEV weakness (monetization) points at: a consultant who delivers one client report will deliver five. All projected figures in this report are hypotheses, not verified traction.

Section 2 of 8

Smallest sellable MVP

A web page that accepts an event CSV, produces a retention teardown PDF with a free unlocked chart, and charges $149 to unlock and email the full PDF plus share link — fully automated, no human in the loop.

Must-have features

  • CSV upload with auto-detected user_id / event / timestamp columns and an optional client-side hash-ID mode
  • LLM event canonicalizer that clusters raw event names into ordered intent steps and proposes an editable activation funnel
  • Weekly cohort retention engine with D1/D7/D30 and a funnel drop-off table
  • Ranked instrumentation-gap list of steps that cannot be measured from the uploaded file
  • PDF teardown (summary page plus appendix charts) rendered server-side
  • Read-only signed share link per report
  • Stripe Checkout that unlocks the full PDF after a free graded preview
  • Automated Resend email delivery of the PDF and link

Explicitly out of scope

  • No SDK, JS snippet or live event ingestion
  • No persistent dashboards or BI workspace
  • No GitHub/PR bot and no tracking-plan CRUD
  • No warehouse connectors (Snowflake, BigQuery) in the first 30 days
  • No team seats, SSO, SOC 2 or DPA promises
  • No human analyst review or custom consulting

Demo flow (what the buyer sees)

  1. Buyer lands on the site and drops in a Mixpanel/Amplitude/PostHog CSV export (IDs optionally hashed in-browser).
  2. Parser detects columns, normalizes timestamps and reports row, user and event counts.
  3. LLM canonicalizer maps raw event names to ordered intent steps and proposes an activation funnel.
  4. Engine computes weekly cohorts, D1/D7/D30 retention and per-step drop-off; buyer sees a letter grade and one unlocked chart.
  5. Stripe checkout for $149 unlocks the full PDF; webhook triggers render.
  6. PDF plus read-only share link is emailed within minutes.
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres + storage for uploads and report recordsAnthropic or OpenAI API for event-name canonicalizationTypeScript cohort and funnel computationReact-PDF for report renderingStripe Checkout on a TrustMRR-connected accountResend for delivery email

Architecture

A Next.js app on Vercel handles upload, analysis and delivery. Uploads stream to a private Supabase storage bucket and rows land in a Postgres table keyed by report_id; hashing happens in the browser before upload when the buyer opts in. The analyzer runs as a serverless route: schema detection, then an LLM call that returns a JSON funnel of canonical step names mapped to raw event names, then a pure TypeScript pass that builds weekly cohorts and funnel drop-off from the normalized rows. Metrics and the funnel JSON are persisted. The preview page renders the grade and one chart from those metrics. Stripe Checkout is created with report_id in metadata; the webhook flips the report to unlocked, triggers React-PDF rendering to a Supabase object, and sends a Resend email with a signed URL that expires in 30 days. Nothing runs long enough to need a queue: every step is under the serverless limit or split into two calls.

Build steps

  1. Scaffold Next.js + Vercel project, Supabase project, storage bucket, and Stripe products ($149 Teardown, $499 Agency 5-Pack) on the TrustMRR-connected account.
  2. Build the upload route: multipart CSV, column auto-detection for user id / event / timestamp, timestamp normalization, client-side hash mode.
  3. Write the TypeScript cohort engine: weekly cohort matrix, D1/D7/D30 retention, funnel step conversion and drop-off, with unit tests on three synthetic datasets.
  4. Build the LLM canonicalizer: prompt that takes the distinct event name list plus sample ordering and returns ordered intent steps, a proposed activation funnel, and a confidence score; cache by hash of the event-name list.
  5. Build the instrumentation-gap ranker: mark funnel steps with no matching events in the file, rank by funnel position weight.
  6. Render the PDF with React-PDF: summary page, cohort heatmap, retention curves, funnel table, gap list, appendix.
  7. Add the free preview gate and Stripe checkout/webhook unlock flow with idempotent webhook handling.
  8. Add Resend delivery and signed read-only share links.
  9. Deploy to production, run five real CSVs through end to end, log LLM cost and runtime per report.
  10. Add a per-report cost log and a failure-mode fallback: if the LLM call fails, fall back to frequency-ranked event steps so no upload is a dead end.

AI components

  • Event-name canonicalizer: an LLM clusters raw event names into ordered intent steps and proposes the activation funnel
  • Gap narrative: a short LLM-written paragraph explaining the top instrumentation gap in plain language
  • Fallback path: frequency-ranked step ordering when the model call fails or returns invalid JSON
Hardest technical risk: Messy real-world CSVs — custom timestamp formats, anonymous or null user IDs, duplicate events — breaking the cohort math or producing a report the buyer distrusts.
Section 3 of 8

Pricing and monetization

Retention Grade

Entry offer
$0 one-time

For Founders testing the workflow with their own export

  • Letter grade for the uploaded dataset
  • One unlocked chart
  • Locked preview of the full teardown

Teardown

$149 one-time

For Founder or Head of Product with a board or investor meeting this month

  • Full retention teardown PDF
  • Cohort curves and per-step funnel drop-off
  • Ranked instrumentation-gap list
  • Read-only share link

Agency 5-Pack

$499 one-time

For Freelance analytics consultant billing reports to clients

  • Five teardown credits
  • Client logo on the PDF cover
  • Share links per client

Model: One-time per-artifact pricing: a free graded preview, a $149 single teardown, and a $499 five-pack for consultants; no subscription in the first 30 days.

First revenue offer: Send an event CSV export with IDs hashed and I will send back a free one-page retention teardown within 24 hours; the full PDF with the cohort appendix and gap list is $149 if it is useful.

Expected ACV: $149

Upsell path: Single teardown buyers who mention client work are offered the $499 five-pack; consultants who redeem two credits in 30 days get the pack offer directly. No subscription until repeat usage is observed.

Target customers
25
Revenue model
$3,725
Costs
$80
Profit model
$3,645
Section 4 of 8

First-customer acquisition

Primary channel

Direct DMs to founders and PMs who posted in the last 7 days on Reddit r/SaaS, Indie Hackers or X about broken retention data, churn or an upcoming investor update.

Where to find them

  • r/SaaS posts mentioning retention, churn or Mixpanel exports in the last 7 days
  • Indie Hackers forum threads on retention and investor updates
  • X search for 'retention' + 'Mixpanel' / 'Amplitude' / 'PostHog' within 7 days
  • X search for 'board deck metrics' and 'churn is up' within 7 days
  • Freelance analytics consultants listing 'Mixpanel' or 'Amplitude' in their bio
  • Public Slack and Discord communities for product and growth operators

Exact outreach motions

  • Three-line DM offering a free one-page teardown from their own CSV export within 24 hours.
  • Public weekly post in r/SaaS and Indie Hackers showing an anonymized before/after teardown.
  • 72-hour follow-up naming the single biggest instrumentation gap found in their own file.
  • Reply to their post thread (not DM) when they describe a broken dashboard, with the same free-teardown offer.
  • Consultant outreach: offer one free client-branded PDF so they can see the 5-pack output before buying.

Message template

Saw your post on retention. Send me a Mixpanel/Amplitude/PostHog event CSV export with user IDs hashed and I'll send back a free one-page retention teardown within 24h. If it's useful, the full PDF with cohort curves and a tracking-gap list is $149.
Week-one goal: 75 DMs sent, 5 CSVs received, 1 paid teardown.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 5First sale target: day 1030 days planned
Week 1 · Build & validate · 7 days
Day 1Scaffold

Ship the rails

  • Init Next.js on Vercel and Supabase project with a private uploads bucket.
  • Create Stripe products ($149, $499) on the TrustMRR-connected account.
  • Deploy a placeholder page with the offer copy.

Deliverable: Live URL and checkout objects in test mode.

Day 2Ingest

Make any export parse

  • Build the CSV upload route with column auto-detection for user_id, event, timestamp.
  • Add timestamp normalization and client-side hash-ID mode.
  • Persist normalized rows to Supabase.

Deliverable: Three real exports from Mixpanel, Amplitude and PostHog parse without error.

Day 3Engine

Cohorts and funnels

  • Write the weekly cohort matrix and D1/D7/D30 retention in TypeScript.
  • Add per-step funnel conversion and drop-off.
  • Unit-test against synthetic datasets with known answers.

Deliverable: Deterministic metrics JSON for any uploaded file.

Day 4Canonicalizer

Messy names to intent steps

  • Build the LLM prompt that maps distinct event names to ordered intent steps.
  • Return a proposed activation funnel plus confidence, cached by event-name hash.
  • Log tokens and cost per run.

Deliverable: Ordered funnel with raw-to-canonical mapping on five messy files.

Day 5ArtifactMVP shipped

PDF and delivery

  • Render the PDF: summary page, cohort heatmap, curves, funnel table, gap list.
  • Add read-only signed share links and Resend email delivery.
  • Wire the Stripe webhook to unlock and render.

Deliverable: End-to-end teardown from upload to inbox under four minutes.

Day 6Paywall

Turn it into a product

  • Ship the free graded preview with one unlocked chart.
  • Gate the full PDF behind Stripe Checkout in live mode.
  • Run five full test purchases and refund them.

Deliverable: Production product accepting real payments.

Day 7Launch

Public day one

  • Post the free-teardown offer on r/SaaS and Indie Hackers.
  • Build a 25-handle list from posts in the last 7 days.
  • Send the first 25 DMs.

Deliverable: Product live, 25 DMs sent, first inbound CSV.

Week 2 · Launch & first sale · 7 days
Day 8Outreach

Volume and turnaround

  • Send 25 more DMs from X and Indie Hackers searches.
  • Deliver every received CSV teardown within 24 hours.
  • Log reply rate by source.

Deliverable: 50 DMs cumulative, 3 free teardowns delivered.

Day 9Conversion

From free to paid

  • Email each free-teardown recipient the $149 link with their own gap list quoted.
  • Add a one-click 'unlock this report' link inside the preview page.
  • Fix the top two CSV parsing failures seen in real files.

Deliverable: First paid attempt on warm recipients.

Day 10First saleFirst sale target

Close revenue

  • Send 25 DMs plus 72-hour follow-ups naming each recipient's biggest instrumentation gap.
  • Post an anonymized before/after teardown publicly.
  • Personally walk any hesitating recipient through the PDF on a 10-minute call.

Deliverable: First $149 collected through the TrustMRR-connected account.

Day 11Consultants

The $499 path

  • DM 15 freelance analytics consultants with a free client-branded PDF.
  • Add client-logo cover support to the PDF renderer.
  • Build a 5-pack credit ledger in Supabase.

Deliverable: 5-pack purchasable and one consultant conversation live.

Day 12Polish

Artifact credibility

  • Tighten the summary page wording so it reads as an executive narrative.
  • Add a methodology footnote to the PDF.
  • Reduce report render time below 90 seconds.

Deliverable: PDF a Head of Product would forward without editing.

Day 13Distribution

Second public surface

  • Publish the weekly public post with a new anonymized teardown.
  • Send 25 fresh DMs.
  • Reply in five threads where someone describes a broken dashboard.

Deliverable: 75 DMs cumulative, second public post live.

Day 14Review

Kill or double down

  • Compute DM reply rate, CSV receipt rate and free-to-paid rate.
  • Kill the worst-performing source and reallocate to the best.
  • Fix every CSV that failed this week.

Deliverable: Written channel scorecard with a decision for week three.

Week 3 · Repeat & systematize · 7 days
Day 15Scale outreach

Repeat what worked

  • Send 30 DMs on the best-performing source only.
  • Add a short Loom-style screen recording to the DM for cold recipients.
  • Deliver all teardowns same day.

Deliverable: 30 DMs, same-day delivery, reply rate tracked.

Day 16Consultants

Repeat purchase

  • Follow up with every consultant contacted on day 11.
  • Offer the 5-pack to any buyer who mentioned a client.
  • Ship per-client share links.

Deliverable: First 5-pack conversation or sale.

Day 17Reliability

No dead-end uploads

  • Add the frequency-ranked fallback when the LLM call fails.
  • Add a plain-language error message per parse failure type.
  • Add retry on email delivery failure.

Deliverable: Zero silent failures across the last 20 uploads.

Day 18Trust

Privacy objections

  • Document the client-side hashing flow on the upload page.
  • Add an automatic delete-after-30-days statement for uploaded files.
  • Test the flow with a hashed-ID-only file.

Deliverable: Privacy objection answerable in one screen.

Day 19Outreach

Volume

  • Send 30 DMs.
  • Post the third weekly public teardown.
  • Reply in five new threads.

Deliverable: 105 DMs cumulative.

Day 20Conversion

Warm close

  • Send 72-hour follow-ups to every recipient from days 15-19.
  • Test a $99 first-time price against $149 on new recipients.
  • Log which price converts.

Deliverable: Price test result recorded.

Day 21Review

Midpoint audit

  • Recompute all conversion rates and paid count.
  • Decide whether to keep or drop the price test.
  • List the three most common buyer objections verbatim.

Deliverable: Midpoint scorecard and objection list.

Week 4 · Scale what works · 7 days
Day 22Objections

Answer them in the product

  • Add the top objection answer to the preview page copy.
  • Add a sample teardown PDF link on the landing page.
  • Send 30 DMs referencing the sample.

Deliverable: Updated landing page with a public sample.

Day 23Consultants

Pack revenue

  • DM 20 more consultants with the pack offer.
  • Add a 10-pack quote-by-email option for interest above 5 credits.
  • Ship the client logo upload.

Deliverable: Pack pipeline list of 20 consultants.

Day 24Outreach

Volume

  • Send 30 DMs.
  • Post the fourth weekly public teardown.
  • Reply in five new threads.

Deliverable: 135 DMs cumulative.

Day 25Conversion

Close the backlog

  • Follow up on every unredeemed free teardown with their gap list.
  • Offer a same-day turnaround guarantee on paid reports.
  • Walk one hesitant buyer through the PDF live.

Deliverable: Backlog of free teardowns converted or closed.

Day 26Delivery

Speed promise

  • Cut render time to under 60 seconds.
  • Add a status page line on the preview ('report generating').
  • Verify every emailed link opens.

Deliverable: Sub-60-second median render.

Day 27Referral

Second-degree reach

  • Ask every paid buyer for one intro to a peer with a board meeting.
  • Add a 'share this teardown' line in the email footer.
  • Send 20 DMs sourced from buyer-adjacent accounts.

Deliverable: Referral asks sent to all paid buyers.

Day 28Outreach

Final push

  • Send 30 DMs.
  • Post the fifth weekly public teardown.
  • Reply in five new threads.

Deliverable: 165 DMs cumulative.

Days 29-30 · Consolidate · 2 days
Day 29Close

Last conversions

  • Send a deadline-neutral follow-up to every recipient who received a free teardown.
  • Offer the 5-pack to any buyer with two or more reports.
  • Verify every payment cleared through the TrustMRR-connected account.

Deliverable: Final conversion sweep and payment reconciliation.

Day 30Wrap

Record and hand off

  • Reconcile revenue, refunds, fees and ad spend into a single ledger.
  • Write the channel and price scorecard with next-month decisions.
  • Email every buyer a thank-you and a support address.

Deliverable: Final ledger and 30-day scorecard.

Section 6 of 8

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

  • Base case assumes ~6% of roughly 165 cold DMs reply and send a CSV, and ~10% of free teardowns convert to paid (projection, unvalidated).
  • Base case ARPU of $178 reflects a mix of ~11 single teardowns at $149 and ~1 Agency 5-Pack at $499.
  • Upside ARPU of $205 reflects a mix of ~21 teardowns and ~4 five-packs at $499.
  • Payment processing assumed at Stripe standard 2.9% + $0.30 per transaction, roughly 3% of collected revenue.
  • Ad spend is zero in Conservative and Base because the channel is organic DMs; Upside includes a $100 test of one sponsored community post.
  • Operating costs cover Vercel, Supabase, Resend, domain, and LLM canonicalization at about $0.40 per report including free previews.
  • Conservative assumes 4 paid reports, no refunds, and about 25 free preview runs.
  • Upside assumes one $149 refund on a disputed report and zero chargebacks across the month.
  • All scenarios are 30-day projections, not verified revenue, customers or traction.

Conservative

4 customers
$596
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$19
Paid marketing
$0
Hackathon profit
$577
Operating costs
$25
Business profit
$552

Base case

12 customers
$2,136
collected revenue · avg payment $178
Refunds
$0
Chargebacks
$0
Payment fees
$66
Paid marketing
$0
Hackathon profit
$2,070
Operating costs
$55
Business profit
$2,015

Optimistic

25 customers
$5,125
collected revenue · avg payment $205
Refunds
$149
Chargebacks
$0
Payment fees
$156
Paid marketing
$100
Hackathon profit
$4,720
Operating costs
$110
Business profit
$4,610

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$588
Payment fees (3.9%)
$23
Paid marketing
$0
Hackathon profit
$565
Business profit
$510

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.

All figures are projections built from stated assumptions for a 30-day window. They are not verified revenue, existing customers or real traction, and no sales exist at the time of writing.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold DM reply rates fall far below the 6% assumption, leaving fewer than four paying customers.

Mitigation

Diversify within the same channel: DM, thread replies, and a weekly public teardown post; kill the worst source at day 14 and day 21.

Validation experiment

Send 25 DMs on day 7 and count replies within 72 hours; anything under 2 replies triggers a message rewrite and a switch to thread replies.

Kill criteria

Abandon the DM-only channel if 50 DMs produce zero CSVs by day 9; switch to public before/after posts as the primary surface.

Risk 2Buyers refuse to export or upload event data for privacy or contractual reasons.

Mitigation

Client-side hashing of user IDs, an explicit 30-day delete statement, and a hashed-only demo file that needs no real data.

Validation experiment

Ask the first ten DM recipients directly whether hashed IDs would be acceptable; log every refusal verbatim.

Kill criteria

If more than half of qualified replies cite privacy as the blocker, pivot the artifact to a sanitized sample dataset walkthrough rather than a live upload.

Risk 3Messy CSVs (custom timestamp formats, anonymous IDs, duplicate events) break the pipeline and consume founder days on manual fixes.

Mitigation

Schema detection with explicit per-failure error messages, a frequency-ranked fallback when the LLM call fails, and a single-file regression suite grown from every real upload.

Validation experiment

Push ten real exports from three different tools through the pipeline on days 2 and 3 and count parse failures.

Kill criteria

If fewer than six of ten real exports parse without manual intervention by day 9, narrow the supported formats to one tool and rename the offer accordingly.

Risk 4The LLM canonicalizer mislabels events and the buyer distrusts the report, killing referral and repeat purchase.

Mitigation

Show the raw-event-to-canonical-step mapping in the appendix so the buyer can audit it, and let them reorder the funnel before paying.

Validation experiment

Show five canonicalized funnels to five different recipients and ask one question: would you present this funnel to your board?

Kill criteria

If fewer than three of five say yes, drop the auto-funnel claim and sell the cohort retention teardown alone.

Risk 5Free built-in retention views in PostHog or GA4 are judged good enough by price-sensitive founders.

Mitigation

Sell the artifact, not the metric: the PDF, the narrative and the instrumentation-gap list are what a dashboard does not produce.

Validation experiment

In the day 9 follow-up, ask every non-buyer what they did instead; record whether it was a dashboard, a spreadsheet or nothing.

Kill criteria

If more than 60% of non-buyers say their existing dashboard answered the question, reposition to the consultant 5-pack where the deliverable is client-facing.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Vercel project, Supabase project, uploads bucket and Stripe products ($149, $499) on the TrustMRR-connected account.
  • Write the one-paragraph offer and the DM template into a single doc.

Output: Live repo, connected payment account, and a locked offer document.

Hours 3-5

  • Build the CSV upload route with column auto-detection for user_id, event and timestamp.
  • Add timestamp normalization and the client-side hash-ID toggle.

Output: A page that accepts a real export and prints row, user and event counts.

Hours 6-8

  • Run three real exports (Mixpanel, Amplitude, PostHog) through the parser.
  • Log every failure mode into a regression list.

Output: A parse report: passes, failures and the exact error strings.

Hours 9-10

  • Scaffold the TypeScript cohort matrix (weekly cohorts, D1/D7/D30) against the normalized table.
  • Print a rough retention table on screen, unstyled.

Output: First raw retention numbers computed from a real customer-shaped file.

Hours 11-12

  • Draft the 25-handle outreach list from posts in the last 7 days on r/SaaS, Indie Hackers and X.
  • Queue the first five DMs but do not send until the product can produce a teardown.

Output: A 25-handle list with post URLs and the exact DM queued per handle.

Complete report

Full 30-day launch report

Read the full generated report

Cohort Autopsy — 30-Day Launch Report

1. Product opportunity and positioning

The buyer is not looking for analytics. They are looking for something to say in a meeting. A 5-50 person SaaS already runs Mixpanel, Amplitude or PostHog; the events exist, the dashboard exists, and still nobody can answer "is retention improving?" in a way that survives a board question. The work that stands between the export and the answer — reconciling signup_complete against Sign Up against onboarding_done_v2, deciding what counts as activation, computing cohorts by week — is six to ten hours of spreadsheet labour performed under deadline.

Cohort Autopsy sells that artifact, not the tool. One CSV in, one PDF plus read-only share link out, $149 flat. Free preview shows a graded result and a single unlocked chart; the full teardown, cohort appendix and instrumentation-gap list sit behind one Stripe link. No SDK, no ingestion, no tracking plan, no dashboard. The narrowness is what makes it shippable by one person in four days and buyable without procurement.

Why it is sellable now: the buyer already owns the data and already has the meeting. There is no integration wait and no data-collection lag between first contact and a paid deliverable.

2. Smallest sellable MVP

The MVP is a single page: upload a CSV, get a letter grade and one chart free, pay $149 to unlock a rendered PDF emailed to you within minutes. Everything runs unattended.

The seven must-haves: CSV upload with column auto-detection and client-side hashing; an LLM canonicalizer that maps raw event names to ordered intent steps and proposes an activation funnel; a TypeScript engine for weekly cohorts, D1/D7/D30 and per-step drop-off; a ranked instrumentation-gap list; a React-PDF teardown; a Stripe Checkout unlocked by webhook; and automated email delivery via Resend.

Not built in 30 days: no SDK or JS snippet, no persistent dashboards, no GitHub PR bot, no tracking-plan CRUD, no warehouse connectors, no seats or SSO, no human analyst review. Each of those is a week of work that does not move the first sale.

3. Technical implementation plan

Next.js on Vercel, Supabase Postgres and private storage, Anthropic or OpenAI for canonicalization, React-PDF for the artifact, Stripe Checkout on a TrustMRR-connected account, Resend for delivery.

Upload streams to a private bucket; rows land in Postgres keyed by report_id. Hashing happens in the browser when the buyer opts in, so raw user IDs never leave their machine. The analyzer is a serverless route in two passes: schema detection, then an LLM call returning JSON that maps canonical steps to raw event names with a confidence score, then a pure function that builds the cohort matrix and funnel drop-off. Metrics and funnel JSON persist. Stripe metadata carries report_id; the webhook flips the report to unlocked, renders the PDF, stores it, and emails a signed 30-day link.

The hardest technical risk is dirty input — non-standard timestamps, null user IDs, duplicated events. Mitigations on day 17: frequency-ranked step fallback when the model fails, explicit error text per parse failure, and a regression suite grown from every real upload received during outreach.

4. Pricing and monetization

Three SKUs only. Retention Grade free (grade, one chart, locked preview) to remove the upload objection. Teardown at $149 one-time for the founder with a board meeting. Agency 5-Pack at $499 for freelance analytics consultants who bill client reports — this is the repeat-purchase path the JEV score correctly flags as missing.

No subscription in the first 30 days. Subscriptions require observed repeat usage; the buyer's cadence is quarterly at best. The 5-pack is the honest answer to a low-value one-time charge: a consultant who delivers one client report delivers five.

5. First-customer acquisition

One channel: direct DMs to founders and PMs who posted in the last 7 days on r/SaaS, Indie Hackers or X about retention, churn or an upcoming investor update.

The loop is fixed. Each morning, search and log 25 handles. Send a three-line DM: send an event CSV with hashed IDs, get a free one-page teardown in 24 hours. Run their file through the pipeline, deliver the free grade plus one chart with the $149 link attached. Follow up once at 72 hours naming the single biggest instrumentation gap found in their own file. Post one anonymized teardown publicly each week as the inbound surface.

Week-one target: 75 DMs, 5 CSVs received, 1 paid teardown.

6. 30-day roadmap

Days 1-2 build the rails: repo, Supabase, Stripe on the TrustMRR account, upload route, column detection, hashing. Days 3-4 build the engine and the canonicalizer, tested against three real exports. Day 5 renders the PDF, signs share links and wires email. Day 6 ships the free-preview paywall and runs five refunded live-mode test purchases. Day 7 is public launch and the first 25 DMs.

Days 8-14 are outreach and conversion: 25 DMs (day 8), paid attempt on warm recipients (day 9), first sale target (day 10), consultant pack outreach (day 11), artifact polish (day 12), second public post (day 13), and a channel scorecard with a kill decision (day 14).

Days 15-21 scale what converted: 30 DMs and same-day delivery (day 15), consultant follow-up (day 16), reliability fallback and retries (day 17), privacy documentation (day 18), third public post (day 19), a $99 versus $149 price test (day 20), and a midpoint audit (day 21).

Days 22-28 answer objections in the product and push volume: sample PDF on the landing page (day 22), 20 more consultants (day 23), 30 DMs (day 24), backlog conversion (day 25), sub-60-second render (day 26), referral asks to every buyer (day 27), final 30 DMs (day 28).

Days 29-30 close and reconcile: final conversion sweep, payment reconciliation, ledger, scorecard, buyer thank-you.

7. Revenue and profit scenarios

All three scenarios are projections from stated assumptions. No customers, revenue or traction exist today.

Conservative: 4 paid reports at $149 blended ARPU, $596 gross, $19 processing, $25 operating. Base: 12 customers at $178 blended ARPU (eleven teardowns plus one 5-pack), $2,136 gross, $66 processing, $55 operating. Upside: 25 customers at $205 blended ARPU (twenty-one teardowns, four 5-packs), $5,125 gross, one $149 refund, $156 processing, $100 ad test, $110 operating.

Hackathon profit excludes hosting and AI delivery cost; business profit subtracts it. Under the base case, hackathon profit is roughly $2,070 and business profit roughly $2,015.

8. Risks and validation experiments

The DM reply rate is the load-bearing assumption. Test 25 DMs on day 7 and count replies within 72 hours; under two replies forces a message rewrite and a shift to thread replies. If 50 DMs yield zero CSVs by day 9, the DM channel is dead and public posts become primary.

Privacy refusal is the second. Ask the first ten recipients whether hashed IDs are acceptable, and log refusals verbatim. If over half of qualified replies cite privacy, the artifact moves to a sanitized sample dataset.

Dirty CSVs are the third. Ten real exports through the pipeline by day 9; if fewer than six parse cleanly, narrow support to one tool.

Distrust of the auto-funnel is the fourth. Show five canonicalized funnels to five recipients and ask whether they would present it to their board. Under three yes answers, sell the cohort teardown alone and drop the funnel claim.

9. First 24 hours

Hours 1-2: Vercel, Supabase, Stripe products on the TrustMRR-connected account, plus one locked offer doc. Hours 3-5: upload route with column detection, timestamp normalization and the hash toggle. Hours 6-8: three real exports through the parser, with every failure mode logged. Hours 9-10: cohort matrix scaffold producing raw retention numbers on a real file. Hours 11-12: a 25-handle outreach list with each DM pre-written and unsent until the product can produce a teardown.

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 →