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

Thread Ledger

Forward a messy client email thread to a private address and get back a versioned one-page Project Brief — decisions locked, owners, deadlines, open questions, with citations — for agency project leads who just inherited or must report on a project.

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.

Speculative5.86/10
MVP build (solo)
5 days
Launch price
$49
Sales to $1,000 revenue
21 customers
First paying customer
Direct one-to-one outreach to agency project and account leads offering a free brief on one real thread before asking for money.
Who pays

Project or account lead, or ops manager, at a 5-30 person marketing, design or consulting agency (US/UK/EU) who has just inherited a project, is handing one off, or must answer a client status question today.

Biggest execution risk

Market demand 3.8/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 11; 21 sales at $49 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.

0/12
Entry price
$49
Solo build
5 days
30d base revenue
$1,568
30d hackathon profit
$1,419
Section 1 of 8

Product opportunity and positioning

Target customer

Project or account lead, or ops manager, at a 5-30 person marketing, design or consulting agency (US/UK/EU) who has just inherited a project, is handing one off, or must answer a client status question today.

Why now

The buyer can forward a thread 60 seconds after paying, with no OAuth, no IT approval and no team rollout, and the urgent trigger event is already on their calendar this week.

Problem

Project state is trapped in email threads; whoever needs it must re-read the whole chain, still misses decisions, owners and dates agreed in passing, and has no durable record that survives the next handover.

Solution

Forward the thread to a private per-project address; the pipeline strips quotes and signatures, extracts decisions, owners, due dates, open questions and risks with a citation to the source message, merges them into a persistent ledger, and renders a dated one-page Brief as PDF plus a tokenized share link with a delta versus the previous version.

Differentiation · A general chatbot forgets the project and cannot cite; Thread Ledger keeps a per-project ledger, cites every item back to a source message, and produces a what-changed delta the buyer can forward to the client.

Thread Ledger - 30-Day Launch Report

1. Product opportunity and positioning

Thread Ledger exists because of one recurring, unpaid-for moment: a project lead inherits a client project, hands one off, or opens the email that says where are we. The answer lives in a thread of 80 messages, with a decision buried in reply 41 and a deadline agreed in reply 63. The lead re-reads it, misses things, and writes a status update from memory. Nothing durable survives the next handover.

The buyer is a project or account lead, or an ops manager, at a 5-30 person marketing, design or consulting agency in the US, UK or EU. They are not shopping for a collaboration suite. They are one person with one document due today. That is why the wedge is a document, not a workspace: the buyer can forward a thread 60 seconds after paying, with no OAuth, no IT ticket and no team rollout.

The JEV score of 58.6/100 (band C) is honest about the risk. Speed to first revenue scored 8.24 because the buyer is reachable, the price is small and the trigger is urgent. Market demand scored 3.82 and operational simplicity 3.91. These 30 days attack those two numbers directly: narrow the segment to agencies with a live handover trigger, and keep human steps out of delivery after day 5.

Differentiation is persistence, not summarization. A chatbot summary is gone tomorrow and cannot be cited. Thread Ledger keeps a ledger per project, cites every item to a source message, and turns each later forward into a what-changed-since-v3 delta. The buyer forwards that delta to the client, so switching cost grows with every version.

All revenue figures in this report are projections. No customers, revenue or partnerships exist at the start.

2. Smallest sellable MVP

One inbound address per project. Forward a thread, get an email back confirming the brief is ready, open a link and see a one-page Brief as HTML and PDF with a citation on every line item. Forward a second batch from the same project and get Brief v2 with a delta block at the top.

Seven things must work: the inbound webhook, the quote and signature stripper, the schema-constrained extraction with citations, the persistent ledger with versions, the diff engine, the PDF and share link, and Stripe checkout. Anything else is deferred. No Gmail or Slack integration, no boards, no seats logic beyond a counter, no mobile app, no SSO, no admin console. The product is deliberately single-player: one buyer, one client thread, one dated document.

3. Technical implementation plan

Next.js on Vercel plus Supabase for Postgres, storage and magic-link auth. Postmark inbound parses each forward and hits a webhook route. A normalizer strips quoted replies, signatures and legal boilerplate and orders messages chronologically, keeping sender, date and subject as metadata. An LLM call with a JSON-schema-constrained prompt returns decisions, owners, due dates, open questions and risks, each requiring a resolvable source message id; items that cannot cite are dropped, not guessed. A diff engine compares the new item set to the last brief version and classifies added, changed and resolved. A renderer produces one-page HTML with print CSS, a hosted service turns that into PDF, and a revocable token gives a read-only share link. Resend sends the post-forward delta email. Stripe Checkout and Billing Portal handle money; a usage meter enforces plan limits.

The highest technical risk is extraction accuracy on messy, long, multi-sender threads, especially owner and due-date attribution. The mitigation is a citation requirement, a low-confidence flag, and a 10-thread regression set built from real free briefs by day 24.

4. Pricing and monetization

Three prices, same pipeline. Single Brief at $49 one-time for an urgent handover, one project, one ingestion, one free re-run. Project Ledger at $149 per month for up to 5 active projects with unlimited forwards, deltas and client share links. Agency Desk at $349 per month for up to 20 projects, 5 seats and priority processing. The first-month offer to anyone who has seen their own free brief is $99 on Project Ledger.

The $49 tier exists to remove the subscription objection at the moment of urgency and to prove willingness to pay inside the contest window. Expected blended ARPU is $99-$134 depending on mix. Upsell runs Single Brief, then Project Ledger on the second project, then Agency Desk when an ops manager wants handovers standardized. Delivery cost per active project is roughly $5-9 per month in inference and hosting, so no tier sells below cost.

5. First-customer acquisition

One channel: direct one-to-one outreach to agency project and account leads, opened with a free brief on a real thread. Build a list from public agency directories, LinkedIn titles and agency-owner communities. Send three lines, deliver the brief by hand within four hours, then ask for money.

The message: I build a tool that turns a client email thread into a one-page project brief with owners, deadlines and open questions. Forward me your messiest thread and I will send back the brief in four hours, free, no signup. If it is useful we can talk about keeping it updated.

Week one goal: 60 named leads, 40 messages sent, 5 free briefs delivered, 2 paid checkouts attempted. Follow up on day 5 with the buyer's own unresolved items, because their three open questions are the strongest reason to buy again.

6. 30-day execution roadmap

Week 1 (days 1-7) is build plus first outreach. Days 1-4 build ingestion, extraction, ledger, brief and delta. Day 5 is billing and the MVP deadline: a forwarded thread produces a paid-for brief end to end. Days 6-7 are the concierge launch, 20 outreach messages and the first three hand-delivered free briefs, plus the privacy note and an anonymized sample page.

Week 2 (days 8-14) is conversion. 25 more sends, offers to every brief recipient, funnel instrumentation, and the first-sale target on day 11 via a live 15-minute onboarding call. Days 13-14 publish the before-and-after brief and recompute reply and close rates.

Week 3 (days 15-21) is volume and retention. 30 sends with the rewritten message, delta emails to every paying user, reliability work on the inbound path, an Agency Desk test with three multi-project leads, and two short customer interviews.

Week 4 (days 22-28) is scale and hardening. 35 sends, a retention digest, a locked prompt against a 10-thread regression set, a 7-day expiring $99 offer, permissioned proof assets, and spend caps plus a manual review queue for low-confidence briefs.

Week 5 (days 29-30) is reconciliation and the next plan: Stripe reconciled to TrustMRR, every warm lead contacted, a one-page next-30-days plan based on observed rates.

7. Revenue and profit scenarios

These are projections with no verified basis. Conservative: 4 customers at a blended $99, $396 gross, $13 processing, $30 operating, zero ad spend. Base: 14 customers at $112 blended, $1,568 gross, $50 processing, $99 refunds, $110 operating. Upside: 45 customers at $134 blended, $6,030 gross, $190 processing, $199 refunds, $150 paid marketing, $420 operating.

Hackathon profit is gross revenue minus refunds, chargebacks, processing and paid marketing; hosting and inference are not deducted there, so base shows roughly $1,309. Business profit subtracts operating costs and lands near $1,199. Upside hackathon profit is about $5,491 and business profit about $5,071. Conservative is about $383 and $353. Processing assumes Stripe at 2.9% plus $0.30 per charge.

None of these approach $100K. The goal is proving paid demand and a repeatable channel inside the window.

8. Risks and validation experiments

Confidentiality objection is the killer. Test it by asking three leads to forward a redacted thread before the privacy note is finished, and kill the positioning if nobody will forward within 48 hours of a live handover.

Wrong owners and dates destroy trust faster than no brief. Run a 5-thread accuracy check on day 4 and day 24; if item-level accuracy stays under 80 percent, stop selling subscriptions and sell reviewed Single Briefs only.

Commodity chatbot pressure is real. The counter is the delta and the citation, validated by asking every brief recipient whether they would pay $49 for the next one.

Churn after the trigger ends is expected. Test the digest email in week 4; if fewer than a third of paying users forward again within 14 days, monthly pricing is wrong and the model should move to per-brief credits.

Outreach conversion may never arrive. If 150 sends produce fewer than 5 replies by day 18, change the segment from general agencies to consulting firms with named account managers, not the product.

9. First 24 hours

Hours 0-2: Stripe account, TrustMRR connection, domain, Supabase project. Hours 2-6: Postmark inbound webhook and the normalizer, verified by forwarding one real thread. Hours 6-10: extraction prompt with mandatory citations against three synthetic threads. Hours 10-14: ledger, diff and the HTML brief. Hours 14-18: PDF, share link and checkout in test mode. Hours 18-24: build the first 60-lead list and send the first 10 messages, including the free-brief offer.

Section 2 of 8

Smallest sellable MVP

A paid inbound address per project that turns one forwarded client email thread into a dated one-page Project Brief as PDF plus share link, with a citation on every item and a delta on the second forward.

Must-have features

  • Per-project inbound forwarding address via Postmark webhook
  • Thread normalizer that strips quoted replies, signatures and legal boilerplate and orders messages chronologically
  • Schema-constrained LLM extraction of decisions, owners, due dates, open questions and risks with a mandatory source message citation
  • Persistent per-project ledger in Postgres with version history
  • Diff engine classifying added, changed and resolved items between brief versions
  • One-page HTML brief with print CSS, hosted PDF render, and revocable tokenized share link
  • Magic-link login, Stripe Checkout and a project usage meter per plan
  • Post-forward delta email listing three changes and the open questions still unanswered

Explicitly out of scope

  • No Gmail, Outlook, Slack or Drive OAuth in the first 30 days
  • No kanban board, task assignment or team chat
  • No native mobile app
  • No real-time sync or collaborative editing
  • No SSO, admin console or audit export
  • No custom or fine-tuned models
  • No self-serve onboarding wizard beyond the forward address

Demo flow (what the buyer sees)

  1. Buyer pays via Stripe Checkout and receives a project address instantly
  2. Buyer forwards a messy client thread to that address
  3. Pipeline strips quotes and signatures and orders the messages
  4. Extraction returns cited items with a low-confidence flag where needed
  5. Brief v1 renders as HTML, PDF and a share link the buyer can send to the client
  6. Buyer forwards a second batch and receives Brief v2 with a delta block
  7. Delta email lands in the buyer inbox with three changes and open questions
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres, storage and magic-link authPostmark inbound webhookAnthropic or OpenAI API with JSON-schema-constrained outputResend for delta and transactional emailStripe Checkout and Billing PortalHosted HTML-to-PDF rendering serviceTrustMRR-connected Stripe account for verified revenue

Architecture

Postmark receives each forward and posts it to a Next.js webhook route. The route stores the raw message, runs the normalizer to strip quotes and signatures, writes ordered message chunks with sender and date metadata to Supabase, then calls the LLM with a fixed schema where every item must carry a source message id. Accepted items merge into a per-project ledger table with version rows; the diff engine compares the new set to the previous brief and labels items added, changed or resolved. The renderer builds a one-page HTML brief with print CSS, sends it to a hosted PDF service, and stores both behind a revocable token. Resend delivers the post-forward delta email. Stripe gates access and a usage meter counts active projects against the plan limit.

Build steps

  1. Create Stripe account, connect TrustMRR, confirm no pre-launch customers or payments
  2. Provision domain, Supabase project, Postmark inbound and Resend accounts
  3. Add Postmark webhook route and store raw forwarded messages
  4. Build normalizer: quote stripping, signature heuristics, chronological ordering
  5. Write the schema-constrained extraction prompt with mandatory citations
  6. Create ledger, brief version and item tables in Postgres
  7. Implement the diff engine for added, changed and resolved items
  8. Render one-page HTML brief with print CSS and tokenized share links
  9. Add hosted PDF export from the rendered HTML
  10. Wire Stripe Checkout for $49 one-time, $149 and $349 monthly
  11. Add magic-link login and the active-project usage meter
  12. Send the post-forward delta email with three changes and open questions
  13. Add extraction retry, dead-letter and a no-webhook-in-24h alert
  14. Build a 10-thread regression set and lock the prompt version

AI components

  • LLM extraction of decisions, owners, due dates, open questions and risks under a fixed JSON schema
  • Citation enforcement: any item without a resolvable source message id is dropped
  • Low-confidence flagging for items whose evidence is weak or ambiguous
Hardest technical risk: Owner and due-date attribution across long multi-sender threads, where a plausible but wrong name on a brief is worse than a missing line.
Section 3 of 8

Pricing and monetization

Single Brief

Entry offer
$49 one-time

For A lead with one urgent handover or client status request

  • One project, one thread ingestion
  • One-page Brief as PDF plus share link
  • One free re-run after corrections

Project Ledger

$149 / month

For Agency project or account lead running several concurrent client projects

  • Up to 5 active projects with unlimited forwards
  • Versioned briefs with delta sections
  • Client-facing share links
  • Delta email after every forward

Agency Desk

$349 / month

For Ops manager or founder standardizing handovers across a 10-30 person agency

  • Up to 20 active projects
  • Up to 5 login seats
  • Archived project export as PDF bundle
  • Priority processing queue

Model: Freemium-free concierge entry followed by a $49 one-time brief and monthly subscriptions at $149 and $349.

First revenue offer: Forward me your messiest client thread. I will send back a one-page brief with owners, deadlines and open questions in four hours, free, no signup. If it is useful, your first month of Project Ledger is $99 instead of $149.

Expected ACV: $134

Upsell path: Free brief converts to $49 Single Brief or the $99 first month of Project Ledger, then to $149 recurring when a second project arrives, then to $349 Agency Desk when an ops manager standardizes handovers across the agency.

Target customers
45
Revenue model
$6,705
Costs
$360
Profit model
$6,345
Section 4 of 8

First-customer acquisition

Primary channel

Direct one-to-one outreach to agency project and account leads offering a free brief on one real thread before asking for money.

Where to find them

  • Public agency directories filtered to 5-30 person marketing and design shops
  • LinkedIn titles: project lead, account director, account manager, ops manager
  • Agency-owner Slack and Discord communities
  • Public threads asking how to handle project handovers or client status updates
  • Job posts mentioning handover or parental leave cover at small agencies
  • Referrals named by each brief recipient

Exact outreach motions

  • Send a 3-line LinkedIn message offering a free brief on a real thread, no signup
  • Reply in public handover threads with an anonymized brief, not a pitch
  • Follow up on day 5 with the buyer's own three unresolved items
  • Offer $99 first month to anyone who has seen their own brief
  • Ask every delivered brief for one named referral to another agency lead

Message template

Hi {first_name} - I build a tool that turns a client email thread into a one-page project brief with owners, deadlines and open questions, cited back to the email. Forward me your messiest thread and I will send the brief back in four hours, free, no signup. If it is useful we can talk about keeping it updated.
Week-one goal: 60 named leads, 40 messages sent, 5 free briefs delivered, 2 paid checkouts attempted.
Section 5 of 8

30-day execution roadmap

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

Accounts live before any code

  • Create Stripe account and connect TrustMRR before any customer exists.
  • Buy the domain and open Postmark, Resend and Supabase accounts.
  • Create the Supabase project with Postgres, storage and auth.

Deliverable: Live Stripe plus TrustMRR connection, domain and Supabase project.

Day 2Inbound pipeline

A forwarded thread lands in the database

  • Wire the Postmark inbound webhook to a Next.js route on Vercel.
  • Build the normalizer to strip quotes and signatures and order messages.
  • Persist raw message plus parsed chunks with sender and date metadata.

Deliverable: A real forwarded thread stored as ordered, cleaned chunks.

Day 3Extraction

Cited items out of a schema

  • Write the schema-constrained extraction prompt with mandatory source message ids.
  • Drop any item that cannot cite a resolvable message and flag low confidence.
  • Test against three synthetic threads and log wrong owners and dates.

Deliverable: Structured, cited items extracted from one real forwarded thread.

Day 4Brief and delta

The artifact exists

  • Merge accepted items into a versioned per-project ledger.
  • Build the diff engine for added, changed and resolved items.
  • Render one-page HTML with print CSS, a PDF and a tokenized share link.

Deliverable: Brief v1 and v2 with a working delta and share link.

Day 5Billing and MVP deadlineMVP shipped

Money can be collected

  • Add Stripe Checkout for $49 one-time, $149 and $349 monthly.
  • Add magic-link login and the active-project usage meter.
  • Record a full end-to-end walkthrough in Stripe test mode.

Deliverable: MVP sellable: pay, forward, receive a cited brief with a share link.

Day 6Concierge launch

Free briefs before money

  • Build a list of 60 agencies with named project or account leads.
  • Send 20 three-line messages offering a free brief on one real thread.
  • Deliver the first three free briefs by hand within four hours of each reply.

Deliverable: 20 sends, 3 hand-delivered briefs, 1 anonymized sample asset.

Day 7Trust assets

Remove the confidentiality objection

  • Publish a one-page privacy and DPA-style note as a PDF.
  • Fix the top five extraction errors seen in the free briefs.
  • Publish the anonymized sample brief page as the public demo.

Deliverable: Public sample brief plus privacy note and a fixed error list.

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

More conversations

  • Send 25 new messages and follow up day-5 non-repliers.
  • Answer two handover threads in agency-owner communities with the sample.
  • Log every reply and objection in one sheet with counts.

Deliverable: 45 total sends and a counted objection list.

Day 9Convert briefs

Ask for money

  • Send the $99 first-month Project Ledger offer to the three brief recipients.
  • Add a $49 Single Brief button to the sample page.
  • Ask each recipient for one named referral.

Deliverable: Three offers out and the first live checkout attempt.

Day 10Friction

Time to first brief

  • Instrument the signup to first-forward to first-brief funnel.
  • Add a copy block telling buyers exactly what to forward.
  • Cut median time to first brief below five minutes.

Deliverable: Funnel dashboard with measured median time to brief.

Day 11First saleFirst sale target

Close a paying customer

  • Send a voice note or call the five warmest leads.
  • Close the first paid customer on $49 or the $99 first month.
  • Onboard them live on the phone in 15 minutes.

Deliverable: First payment received in the TrustMRR-connected Stripe account.

Day 12Deliver well

Accuracy on a paid brief

  • Hand-review the first paid brief line by line against the thread.
  • Ship any accuracy fix the same day.
  • Ask for a one-sentence testimonial and one referral.

Deliverable: Reviewed brief sent with testimonial or a logged decline.

Day 13Proof content

Slow inbound alongside outbound

  • Publish one anonymized before-and-after brief post.
  • Reply to five public project handover or status threads.
  • Add 25 new leads to the list.

Deliverable: One post live, five replies, list at 110 leads.

Day 14Week 2 review

Read the numbers

  • Compute reply rate, brief-to-paid rate and minutes per brief.
  • Kill the worst-performing message angle.
  • Rewrite the outreach message using the best-performing angle.

Deliverable: Metrics sheet and outreach message v2.

Week 3 · Repeat & systematize · 7 days
Day 15Volume

Send more with a better message

  • Send 30 messages using message v2.
  • Deliver up to five free briefs, capped at 45 minutes each.
  • Ask every brief recipient for a referral by name.

Deliverable: 30 sends, 5 briefs delivered, referral count logged.

Day 16Delta value

Make the version history felt

  • Email the what-changed delta for every live project.
  • Add a three unresolved items line to the delta email.
  • Verify share-link revocation works.

Deliverable: Delta emails sent and link revocation tested.

Day 17Second sale

Convert warm leads

  • Follow up the five warmest leads with their own open questions.
  • Offer $49 Single Brief to leads who fear a subscription.
  • Close two to three additional paid customers.

Deliverable: Two to three more paying customers.

Day 18Reliability

Silent failures are the worst failure

  • Alert if no inbound webhook arrives in 24 hours.
  • Add extraction retry with a dead-letter queue.
  • Add error logging on every pipeline stage.

Deliverable: Alerting, retry and logging live in production.

Day 19Agency Desk test

Price ceiling check

  • Pitch $349 Agency Desk to three multi-project leads.
  • Attach a one-page handover SOP PDF as a bonus.
  • Log every pricing objection verbatim.

Deliverable: Three Desk pitches and a pricing objection list.

Day 20Community

Cheap organic reach

  • Post the second anonymized brief in two communities.
  • Give three free briefs to community thread repliers.
  • Add 30 leads to the list.

Deliverable: Two posts, three briefs, list at 140 leads.

Day 21Review

Retention signal

  • Identify who forwarded a second time and who did not.
  • Interview two paying users for 10 minutes each.
  • Cut one feature nobody used.

Deliverable: Retention notes and one scope cut shipped.

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

Bigger top of funnel

  • Send 35 messages and A/B two subject lines.
  • Add a LinkedIn follow-up to non-openers.
  • Target agencies with handover or leave-cover job posts.

Deliverable: 35 sends and two subject-line results.

Day 23Retention

Survive month two

  • Send a monthly digest listing idle projects.
  • Nudge users with unresolved open questions.
  • Add a cancellation reason question.

Deliverable: Digest live and churn reasons collected.

Day 24Accuracy pass

Lock quality

  • Build a 10-thread regression set from real free briefs.
  • Re-run the prompt and record item-level accuracy.
  • Lock the prompt version and archive the previous one.

Deliverable: Regression set and a recorded accuracy number.

Day 25Conversion push

Expiring offer

  • Offer brief recipients a 7-day $99 first month expiring Friday.
  • Call the five warmest leads directly.
  • Ask three paying users for referrals by name.

Deliverable: Five calls made and three named referrals.

Day 26Proof assets

Show, do not tell

  • Publish three permissioned anonymized briefs with owner quotes.
  • Add a 40-second forward-to-brief screen recording.
  • Add an FAQ answering the confidentiality question.

Deliverable: Demo page v2 with video, quotes and confidentiality FAQ.

Day 27Ops hardening

Cost and quality guardrails

  • Cap LLM spend per project and per day.
  • Add a manual review queue for low-confidence briefs.
  • Write a five-minute delivery runbook.

Deliverable: Spend caps, review queue and runbook.

Day 28Review

Decide with numbers

  • Recount sends, replies, briefs delivered and paid customers.
  • Compute delivery cost per paying customer.
  • Decide keep or drop on the worst-converting segment.

Deliverable: Numbers sheet with written keep or drop decisions.

Days 29-30 · Consolidate · 2 days
Day 29Final push

Clear the backlog

  • Send the last 40 messages to the warmest backlog.
  • Offer every free-brief holder the $99 first month.
  • Close pending checkouts by phone.

Deliverable: Every warm lead contacted before the window closes.

Day 30Wrap

Reconcile and plan

  • Reconcile Stripe to TrustMRR and confirm all payments inside the window.
  • Write a one-page next-30-days plan from observed rates.
  • Publish the anonymized results post.

Deliverable: Reconciled revenue figure and next-30 plan.

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

  • Conservative: 4 paid customers at a blended $99 ARPU, mostly $49 Single Briefs plus two $99 first months.
  • Base: 14 paid customers at a blended $112 ARPU from 150 sends, roughly 25 replies and 20 hand-delivered free briefs.
  • Upside: 45 paid customers at a blended $134 ARPU requiring about 350 sends, community inbound and two Agency Desk conversions.
  • All scenarios assume Stripe processing at 2.9% plus $0.30 per charge, about 3-4% effective on these ticket sizes.
  • Conservative and Base carry zero ad spend because acquisition is one-to-one organic outreach only.
  • Upside includes $150 of paid marketing: one sponsored community placement and one paid newsletter slot.
  • Operating costs cover Vercel, Supabase, Postmark inbound, Resend, PDF rendering, domain and LLM inference at roughly $5-9 per active project per month.
  • No salary, contractor or office cost is included anywhere in any scenario.
  • Every scenario assumes most buyers arrive through a free concierge brief on their own thread, which is unproven.
  • All figures are projections, not verified revenue, customers or traction.

Conservative

4 customers
$396
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$13
Paid marketing
$0
Hackathon profit
$383
Operating costs
$30
Business profit
$353

Base case

14 customers
$1,568
collected revenue · avg payment $112
Refunds
$99
Chargebacks
$0
Payment fees
$50
Paid marketing
$0
Hackathon profit
$1,419
Operating costs
$110
Business profit
$1,309

Optimistic

45 customers
$6,030
collected revenue · avg payment $134
Refunds
$199
Chargebacks
$0
Payment fees
$190
Paid marketing
$150
Hackathon profit
$5,491
Operating costs
$420
Business profit
$5,071

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$686
Payment fees (3.9%)
$27
Paid marketing
$0
Hackathon profit
$659
Business profit
$549

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 scenarios are projections derived from stated assumptions, not verified revenue, customers or traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Confidentiality objection kills conversion before the product is ever used.

Mitigation

Project-specific inbound address, revocable tokenized share links, a one-page privacy and DPA-style note, and an explicit no-training statement.

Validation experiment

Ask three agency leads with a live handover this week to forward a redacted thread before the privacy note is published.

Kill criteria

If fewer than one of five warm leads will forward a thread within 48 hours, reposition away from client email to internal notes and call transcripts.

Risk 2Wrong owner or due date on a brief damages trust faster than no brief at all.

Mitigation

Citation required on every item, low-confidence flagging, manual review queue and same-day fixes on paid briefs.

Validation experiment

Score a 10-thread regression set for item-level accuracy on day 4 and again on day 24.

Kill criteria

If item-level accuracy stays below 80 percent after two prompt revisions, sell only hand-reviewed Single Briefs and drop subscriptions.

Risk 3A free chatbot produces a summary that looks good enough to block a $149 subscription.

Mitigation

Lead every message and demo with the delta and the citation, not the summary.

Validation experiment

Ask every brief recipient whether they would pay $49 for the next brief on a different project.

Kill criteria

If fewer than one in five brief recipients pays for a second brief, the wedge is not a product and the concept changes.

Risk 4Churn after the triggering handover ends, cancelling in month two.

Mitigation

Delta emails, monthly digests and unresolved-question nudges keep the ledger in use after the urgent project closes.

Validation experiment

Measure how many paying users forward a thread again within 14 days of their first brief.

Kill criteria

If under a third forward again in 14 days, replace monthly subscriptions with per-brief credit packs.

Risk 5Outreach conversion is assumed, not observed, and the funnel may never open.

Mitigation

Message rewriting at day 14, subject-line A/B at day 22 and a segment shift from general agencies to consulting firms with named account managers.

Validation experiment

Track replies and free-brief acceptances across the first 150 sends.

Kill criteria

If 150 sends produce fewer than 5 replies by day 18, change the target segment rather than the product.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 0-2

  • Create the Stripe account and connect it to TrustMRR before any customer exists.
  • Buy the domain and open Postmark, Resend and Supabase accounts.

Output: Live payment rail and all provider accounts.

Hours 2-6

  • Deploy the Next.js app with a Postmark inbound webhook route.
  • Build the normalizer to strip quoted replies and signatures.

Output: A real forwarded thread stored as ordered, cleaned chunks.

Hours 6-10

  • Write the schema-constrained extraction prompt with mandatory citations.
  • Run it against three synthetic threads and log wrong owners and dates.

Output: Cited item list and a first error log.

Hours 10-14

  • Create ledger and version tables.
  • Build the diff engine and the one-page HTML brief with print CSS.

Output: Brief v1 and a working delta between versions.

Hours 14-18

  • Add hosted PDF export and revocable share links.
  • Wire Stripe Checkout for $49 one-time and $149 monthly in test mode.

Output: PDF, share link and a testable checkout.

Hours 18-24

  • Build a 60-lead list of small agencies with named project leads.
  • Send the first 10 free-brief outreach messages.

Output: 60-lead list and 10 messages sent.

Complete report

Full 30-day launch report

Read the full generated report

Thread Ledger - 30-Day Launch Report

1. Product opportunity and positioning

Thread Ledger exists because of one recurring, unpaid-for moment: a project lead inherits a client project, hands one off, or opens the email that says where are we. The answer lives in a thread of 80 messages, with a decision buried in reply 41 and a deadline agreed in reply 63. The lead re-reads it, misses things, and writes a status update from memory. Nothing durable survives the next handover.

The buyer is a project or account lead, or an ops manager, at a 5-30 person marketing, design or consulting agency in the US, UK or EU. They are not shopping for a collaboration suite. They are one person with one document due today. That is why the wedge is a document, not a workspace: the buyer can forward a thread 60 seconds after paying, with no OAuth, no IT ticket and no team rollout.

The JEV score of 58.6/100 (band C) is honest about the risk. Speed to first revenue scored 8.24 because the buyer is reachable, the price is small and the trigger is urgent. Market demand scored 3.82 and operational simplicity 3.91. These 30 days attack those two numbers directly: narrow the segment to agencies with a live handover trigger, and keep human steps out of delivery after day 5.

Differentiation is persistence, not summarization. A chatbot summary is gone tomorrow and cannot be cited. Thread Ledger keeps a ledger per project, cites every item to a source message, and turns each later forward into a what-changed-since-v3 delta. The buyer forwards that delta to the client, so switching cost grows with every version.

All revenue figures in this report are projections. No customers, revenue or partnerships exist at the start.

2. Smallest sellable MVP

One inbound address per project. Forward a thread, get an email back confirming the brief is ready, open a link and see a one-page Brief as HTML and PDF with a citation on every line item. Forward a second batch from the same project and get Brief v2 with a delta block at the top.

Seven things must work: the inbound webhook, the quote and signature stripper, the schema-constrained extraction with citations, the persistent ledger with versions, the diff engine, the PDF and share link, and Stripe checkout. Anything else is deferred. No Gmail or Slack integration, no boards, no seats logic beyond a counter, no mobile app, no SSO, no admin console. The product is deliberately single-player: one buyer, one client thread, one dated document.

3. Technical implementation plan

Next.js on Vercel plus Supabase for Postgres, storage and magic-link auth. Postmark inbound parses each forward and hits a webhook route. A normalizer strips quoted replies, signatures and legal boilerplate and orders messages chronologically, keeping sender, date and subject as metadata. An LLM call with a JSON-schema-constrained prompt returns decisions, owners, due dates, open questions and risks, each requiring a resolvable source message id; items that cannot cite are dropped, not guessed. A diff engine compares the new item set to the last brief version and classifies added, changed and resolved. A renderer produces one-page HTML with print CSS, a hosted service turns that into PDF, and a revocable token gives a read-only share link. Resend sends the post-forward delta email. Stripe Checkout and Billing Portal handle money; a usage meter enforces plan limits.

The highest technical risk is extraction accuracy on messy, long, multi-sender threads, especially owner and due-date attribution. The mitigation is a citation requirement, a low-confidence flag, and a 10-thread regression set built from real free briefs by day 24.

4. Pricing and monetization

Three prices, same pipeline. Single Brief at $49 one-time for an urgent handover, one project, one ingestion, one free re-run. Project Ledger at $149 per month for up to 5 active projects with unlimited forwards, deltas and client share links. Agency Desk at $349 per month for up to 20 projects, 5 seats and priority processing. The first-month offer to anyone who has seen their own free brief is $99 on Project Ledger.

The $49 tier exists to remove the subscription objection at the moment of urgency and to prove willingness to pay inside the contest window. Expected blended ARPU is $99-$134 depending on mix. Upsell runs Single Brief, then Project Ledger on the second project, then Agency Desk when an ops manager wants handovers standardized. Delivery cost per active project is roughly $5-9 per month in inference and hosting, so no tier sells below cost.

5. First-customer acquisition

One channel: direct one-to-one outreach to agency project and account leads, opened with a free brief on a real thread. Build a list from public agency directories, LinkedIn titles and agency-owner communities. Send three lines, deliver the brief by hand within four hours, then ask for money.

The message: I build a tool that turns a client email thread into a one-page project brief with owners, deadlines and open questions. Forward me your messiest thread and I will send back the brief in four hours, free, no signup. If it is useful we can talk about keeping it updated.

Week one goal: 60 named leads, 40 messages sent, 5 free briefs delivered, 2 paid checkouts attempted. Follow up on day 5 with the buyer's own unresolved items, because their three open questions are the strongest reason to buy again.

6. 30-day execution roadmap

Week 1 (days 1-7) is build plus first outreach. Days 1-4 build ingestion, extraction, ledger, brief and delta. Day 5 is billing and the MVP deadline: a forwarded thread produces a paid-for brief end to end. Days 6-7 are the concierge launch, 20 outreach messages and the first three hand-delivered free briefs, plus the privacy note and an anonymized sample page.

Week 2 (days 8-14) is conversion. 25 more sends, offers to every brief recipient, funnel instrumentation, and the first-sale target on day 11 via a live 15-minute onboarding call. Days 13-14 publish the before-and-after brief and recompute reply and close rates.

Week 3 (days 15-21) is volume and retention. 30 sends with the rewritten message, delta emails to every paying user, reliability work on the inbound path, an Agency Desk test with three multi-project leads, and two short customer interviews.

Week 4 (days 22-28) is scale and hardening. 35 sends, a retention digest, a locked prompt against a 10-thread regression set, a 7-day expiring $99 offer, permissioned proof assets, and spend caps plus a manual review queue for low-confidence briefs.

Week 5 (days 29-30) is reconciliation and the next plan: Stripe reconciled to TrustMRR, every warm lead contacted, a one-page next-30-days plan based on observed rates.

7. Revenue and profit scenarios

These are projections with no verified basis. Conservative: 4 customers at a blended $99, $396 gross, $13 processing, $30 operating, zero ad spend. Base: 14 customers at $112 blended, $1,568 gross, $50 processing, $99 refunds, $110 operating. Upside: 45 customers at $134 blended, $6,030 gross, $190 processing, $199 refunds, $150 paid marketing, $420 operating.

Hackathon profit is gross revenue minus refunds, chargebacks, processing and paid marketing; hosting and inference are not deducted there, so base shows roughly $1,309. Business profit subtracts operating costs and lands near $1,199. Upside hackathon profit is about $5,491 and business profit about $5,071. Conservative is about $383 and $353. Processing assumes Stripe at 2.9% plus $0.30 per charge.

None of these approach $100K. The goal is proving paid demand and a repeatable channel inside the window.

8. Risks and validation experiments

Confidentiality objection is the killer. Test it by asking three leads to forward a redacted thread before the privacy note is finished, and change positioning if nobody will forward within 48 hours of a live handover.

Wrong owners and dates destroy trust faster than no brief. Run a 5-thread accuracy check on day 4 and day 24; if item-level accuracy stays under 80 percent, stop selling subscriptions and sell reviewed Single Briefs only.

Commodity chatbot pressure is real. The counter is the delta and the citation, validated by asking every brief recipient whether they would pay $49 for the next one.

Churn after the trigger ends is expected. Test the digest email in week 4; if fewer than a third of paying users forward again within 14 days, monthly pricing is wrong and the model should move to per-brief credits.

Outreach conversion may never arrive. If 150 sends produce fewer than 5 replies by day 18, change the segment from general agencies to consulting firms with named account managers, not the product.

9. First 24 hours

Hours 0-2: Stripe account, TrustMRR connection, domain, Supabase project. Hours 2-6: Postmark inbound webhook and the normalizer, verified by forwarding one real thread. Hours 6-10: extraction prompt with mandatory citations against three synthetic threads. Hours 10-14: ledger, diff and the HTML brief. Hours 14-18: PDF, share link and checkout in test mode. Hours 18-24: build the first 60-lead list and send the first 10 messages, including the free-brief offer.

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 →