Renewal Diff Brief
For independent employee-benefits brokers, Renewal Diff Brief turns a client's current plan PDF and carrier renewal packet into a cited employer change brief and employee explainer deck 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.
Independent employee-benefits broker or small-group benefits consultant at a 1-20 person US agency, managing 2-50 small employer clients, triggered when a carrier renewal packet arrives before open enrollment.
Monetization potential 4.9/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 12; 5 sales at $249 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
8 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Independent employee-benefits broker or small-group benefits consultant at a 1-20 person US agency, managing 2-50 small employer clients, triggered when a carrier renewal packet arrives before open enrollment.
Why now
Q4 renewal packets are already in brokers' inboxes and open-enrollment deadlines are fixed, so the buyer has the PDFs today and can judge the output on one free sample before paying.
Problem
The broker must hand-compare dense SPD/SBC and renewal PDFs, catch every material change in copays, deductibles, networks, Rx tiers and eligibility, and explain it without misstating plan terms.
Solution
Upload two PDFs; the product extracts a fixed benefits schema, diffs the plans field by field, attaches a page citation to every flag, and exports a branded 2-page Employer Change Brief, a 5-slide Employee Explainer and a one-page FAQ.
1. Product opportunity and positioning
Employee-benefits brokers at 1-20 person agencies carry a Q4 bottleneck that has nothing to do with selling. A carrier renewal packet lands, and someone must read 60-150 pages of the current SPD/SBC against the renewal PDF, catch every change in deductible, out-of-pocket max, copays, coinsurance, Rx tiers, network and eligibility, then explain it to an office manager without misstating a plan term. Most do it with two PDFs open and memory. Missed changes surface in January as angry employees and lost accounts.
Renewal Diff Brief turns that into a diff. The broker uploads two PDFs; the product extracts a fixed benefits schema, aligns the plans, flags each field as unchanged, changed, added, removed or unclear, and attaches a page citation to every flag. It exports a broker-branded two-page Employer Change Brief, a five-slide Employee Explainer and a one-page FAQ.
The positioning is deliberately narrow: a diff tool, not benefits advice, not benefits administration, not claims or appeals. That framing keeps the founder out of PHI (employer-level plan documents only, member names and rates redacted), keeps the buyer out of procurement (the output is inspectable in 30 seconds), and keeps the build inside a week (no integration surface).
Why now: renewal and open-enrollment cycles are running, so the buyer already has the PDFs and a deadline. Value is provable on one free sample against a real packet before payment. JEV scored speed-to-first-revenue at 8.18 and solo build feasibility at 7.07, which is the shape of this wedge. The two weak criteria are constraints, not inconveniences: monetization (4.9) requires an explicit repeat-purchase path, and operational simplicity (4.94) requires that low-confidence extractions never become a permanent human desk. Sections 3 and 4 handle both.
The generic alternative is a comparison spreadsheet or a producer's memory. Incumbent broker tech exists but lives inside agency management systems nobody switches mid-season. This product does not ask for a switch. It asks for two PDFs.
Smallest sellable MVP
One renewal kit: two PDFs in, a branded 2-page change brief, 5-slide explainer and FAQ out, delivered inside 24 hours.
Must-have features
- Two-PDF upload with a page cap and per-page text map
- Fixed benefits schema: deductible, OOP max, copays, coinsurance, Rx tiers, network, eligibility, telehealth, HSA/HRA
- Field-level diff classifier with per-field confidence score
- Citation mapper showing the page and excerpt beside every flagged change
- Branded export: 2-page brief PDF, 5-slide PPTX/PDF explainer, 1-page FAQ
- Stripe Checkout for one-time kit purchase connected to TrustMRR
- Magic-link job status page with downloads
- Founder-only review queue that holds low-confidence jobs
Explicitly out of scope
- No claims, EOB or appeal-letter processing
- No PHI or member-level data
- No carrier, EHR, payroll or benefits-administration integrations
- No employee login portal or ongoing navigation
- No automated benefits or legal advice
- No SSO, procurement workflow or 24/7 support promise
Demo flow (what the buyer sees)
- Broker uploads current plan PDF and renewal PDF (redacted)
- System extracts per-page text and builds a page map
- LLM populates the fixed benefits schema with page references
- Diff engine classifies each field and scores confidence
- Citation mapper links each flag to its excerpt
- Artifacts render with broker logo and color
- Broker pays via Stripe and receives all three files by email and job page
Technical implementation plan
Stack
Architecture
One job record per upload drives everything: files sit in a private Supabase bucket, extraction and diff JSON sit in Postgres, artifacts sit in storage, and a status column renders the magic-link job page. Rendering is synchronous serverless work; there is no queue service and no worker fleet. Payment and delivery are decoupled so a job can be produced before Stripe is touched.
Build steps
- Create Next.js + TypeScript repo and deploy an empty shell to Vercel
- Write and version the fixed benefits schema as a JSON file
- Provision Supabase project with a private bucket and magic-link auth
- Implement two-PDF upload with page cap and unpdf page mapping
- Write and test the structured extraction prompt against public SBC/SPD samples
- Build the diff classifier with unchanged/changed/added/removed/unclear states
- Add the citation mapper and force unclear when the value is absent from the excerpt
- Render the 2-page brief PDF, 5-slide deck and FAQ
- Add Stripe Checkout with the two products and the magic-link job page
- Send delivery email with attachments via Resend
- Add the founder-only low-confidence review queue and disclaimer footer
- Generate two synthetic renewal pairs as public sample kits
AI components
- Structured extraction of the benefits schema from each PDF with page references
- Natural-language change narrative for the employer brief
- Employee Explainer slide copy and one-page FAQ generation
- Confidence estimation that routes low-certainty fields to manual review
Pricing and monetization
Single Renewal Kit
Entry offerFor Independent broker with one employer renewal due
- One current-vs-renewal diff
- 2-page Employer Change Brief
- 5-slide Employee Explainer
- Citation appendix
- Broker branding
Agency Pack
For Small agency with multiple Q4 renewals
- Three renewal kits
- Reusable broker-branded template
- Priority 24-hour turnaround
- One FAQ page per employer
Model: Two one-time products tied to a renewal event, with repeat purchases each renewal cycle rather than a subscription.
First revenue offer: I will turn one current-vs-renewal packet into a client-ready change brief, free, no call, no PHI. If it is useful, the full kit with the deck and FAQ is $249, sent the same day.
Expected ACV: $249
Upsell path: Single-kit buyers with 3+ renewals move to the $499 Agency Pack; every delivered kit carries the broker logo so the next renewal cycle is a re-order, and renewal dates are captured to build a dated repeat pipeline.
First-customer acquisition
Direct LinkedIn outreach to independent employee-benefits brokers posting about Q4 renewals or open enrollment.
Where to find them
- LinkedIn search for employee benefits broker plus renewal or open enrollment posts
- NABIP chapter member directories
- State insurance department producer-license lookups for small agencies
- Small-group benefits broker Facebook and Slack communities
- Commenters on carrier and benefits-compliance posts in November
- Referrals from each free-sample recipient
Exact outreach motions
- Send a 3-line message offering a free diff on one anonymized renewal packet, no call required
- Comment publicly on a renewal or open-enrollment post before the DM
- Follow up once after four days with the same offer and a sample artifact link
- Deliver the free sample within 24 hours with the single biggest change called out
- Send the $249 checkout link the same day the sample is delivered
- Ask each recipient for one broker introduction and forward a 3-line template
Message template
Saw your post about Q4 renewals. I built a tool that turns a current plan PDF plus the carrier renewal packet into a 2-page employer change brief and 5-slide employee explainer, every change cited to a page. I will run one packet free, redact names and rates, 24-hour turnaround, no call. Want me to do yours?
30-day execution roadmap
Week 1 · Build & validate · 7 days
Repo, schema, storage
- Create the Next.js repo on Vercel and deploy the empty shell.
- Write the fixed benefits schema as a versioned JSON file.
- Create the Supabase project with a private storage bucket.
Deliverable: Live empty app, schema v1 committed, storage ready.
PDF to structured JSON
- Wire unpdf extraction with a 200-page cap and per-page text map.
- Write the extraction prompt returning the schema with a page reference per field.
- Run it on three public SBC or SPD samples and log failures.
Deliverable: Extraction JSON with page refs on three documents.
Field alignment and citations
- Classify every field as unchanged, changed, added, removed or unclear.
- Store a confidence score and the cited page excerpt per field.
- Force unclear whenever the excerpt does not contain the value.
Deliverable: Diff JSON with per-field citations and confidence.
Brief, deck, FAQ
- Render the 2-page Employer Change Brief to PDF with broker logo and color.
- Generate the 5-slide explainer with pptxgenjs plus a PDF fallback.
- Emit the one-page FAQ from changed fields only.
Deliverable: Three branded downloadable artifacts per job.
Checkout to delivery
- Add Stripe Checkout with $249 and $499 products linked to TrustMRR.
- Build the magic-link job page with status and downloads.
- Send the delivery email with all three attachments via Resend.
Deliverable: End-to-end paid upload-to-delivery flow live, MVP deadline met.
Fail safe, not fast
- Add the admin queue that holds any job with a low-confidence field.
- Add the disclaimer that the artifact is a document diff, not advice.
- Add redaction instructions and 24-hour turnaround copy on upload.
Deliverable: Production-safe v1 with a review queue.
Samples and site
- Build two synthetic renewal pairs and generate anonymized sample kits.
- Publish the landing page with an embedded sample brief and both prices.
- Instrument events for upload, checkout and download.
Deliverable: Public site with two viewable sample kits.
Week 2 · Launch & first sale · 7 days
60 brokerages
- Search LinkedIn for employee benefits brokers posting about renewals.
- Log 60 agencies with name, city, contact and post URL.
- Rank by recency of a Q4 renewal or open-enrollment post.
Deliverable: 60-row outreach sheet with 20 A-priority contacts.
20 first touches
- Send 20 LinkedIn messages using the free-diff offer.
- Send connect requests to the same recipients with no pitch.
- Log every send and reply in the sheet.
Deliverable: 20 first touches sent and logged.
20 more plus follow-up
- Send 20 first touches to B-priority contacts.
- Follow up once on day-9 sends with a one-line nudge.
- Open an intake folder for incoming redacted packets.
Deliverable: 40 total sends, one follow-up per contact.
24-hour turnaround
- Process the first three anonymized packets through the live product.
- Manually resolve any low-confidence field and rebuild artifacts.
- Return each kit with a note on the single biggest change found.
Deliverable: Three broker-ready kits delivered inside 24 hours.
Convert samples to paid
- Send the $249 checkout link to every sample recipient.
- Offer the $499 Agency Pack to anyone with 3+ Q4 renewals.
- Post an anonymized before-and-after in one broker community that permits it.
Deliverable: First paid kit collected through Stripe.
One intro each
- Ask each sample recipient for one broker introduction.
- Send a 3-line forwardable intro template.
- Contact every new intro the same day.
Deliverable: Referral asks sent to every recipient.
Fix the top failure
- Review every low-confidence field from week 2 jobs.
- Patch the extraction prompt for the top recurring failure.
- Regenerate the public sample kit if artifacts improved.
Deliverable: Prompt v2 deployed, failure log closed.
Week 3 · Repeat & systematize · 7 days
40 new contacts
- Add 40 brokerages from NABIP chapters and producer-license lookups.
- Send 20 first touches to the new list.
- Re-follow-up silent day-9 and day-10 contacts once.
Deliverable: 100 contacts listed, 60 total first touches.
One post
- Publish a LinkedIn post showing a redacted changed-deductible diff.
- Reply to every comment with the free-diff offer.
- Message the five most engaged brokers directly.
Deliverable: One post live with tracked replies.
Multi-renewal buyers
- Identify every contact holding 3+ renewal packets.
- Send a specific Agency Pack message naming their renewal count.
- Record objections verbatim in the sheet.
Deliverable: Agency Pack pitch sent to eight contacts.
Numbers
- Tally sends, replies, packets, kits delivered and dollars collected.
- Kill any message variant with zero replies after 25 sends.
- Double down on the working variant.
Deliverable: Midpoint scorecard with one decision made.
Turnaround
- Time every job end to end.
- Cut any manual step costing more than 10 minutes.
- Add a canned status email for jobs older than 12 hours.
Deliverable: Median turnaround under six hours.
Warm intros
- Ask every past buyer for one introduction.
- Offer a free kit to each introduced broker.
- Move referrals to the top of the outreach sheet.
Deliverable: Five warm intros requested.
Refund risk
- Re-read every delivered artifact for a misstated term.
- Correct and resend anything wrong before the client notices.
- Log any refund request and its stated reason.
Deliverable: Quality audit log with zero unresolved errors.
Week 4 · Scale what works · 7 days
Daily rhythm
- Send 15 first touches every weekday from here.
- Follow up all prior sends on a three-day cadence.
- Keep the sheet current within an hour of each send.
Deliverable: Daily outreach rhythm running.
Trust block
- Write a one-page no-PHI data-handling note.
- Link it in the message and on the upload page.
- Test it against the top two stated objections.
Deliverable: Public data-handling page live.
Second post
- Post the three most common renewal changes seen in delivered kits.
- Pin the sample kit link in the post.
- Reply to each comment within two hours.
Deliverable: Second post live with sample link.
Checkout friction
- Run the full purchase on a phone in incognito.
- Remove any step requiring an account before payment.
- Add a clear Stripe receipt line item describing the kit.
Deliverable: Mobile checkout completing end to end.
Next cycle
- Email every past buyer about their next renewal date.
- Offer the Agency Pack to anyone with a January renewal.
- Record renewal dates in the sheet.
Deliverable: Repeat-purchase list with dates.
Sample distribution
- Share the sample kit in two broker groups that permit it.
- Answer questions as the builder, not as a vendor.
- Capture every inbound request in the sheet.
Deliverable: Two community posts plus an inbound log.
Pipeline
- Count open packets, unpaid samples and silent contacts.
- Send a final-call message to every unpaid sample recipient.
- Publish the December delivery cutoff date on the site.
Deliverable: Final-call wave sent.
Days 29-30 · Consolidate · 2 days
Finish every kit
- Deliver every outstanding kit before the cutoff.
- Send receipts and download links for all paid jobs.
- Reconcile Stripe payouts against TrustMRR.
Deliverable: Zero undelivered paid kits.
Record and hand off
- Export a revenue, refund and fee ledger for the 30 days.
- Archive every artifact and job record.
- Write the January renewal plan for the next cycle.
Deliverable: Final ledger, archive and January plan.
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
- All three scenarios are projections from stated assumptions; no customers, revenue or traction exist.
- Conservative/Base/Upside: one-time kit sales only; blended ARPU rises with Agency Pack mix.
- Payment fees modeled at 3.5-4.0% of collected revenue through Stripe, including card mix.
- Conservative and Base use zero paid marketing; Upside includes $150 of sponsored community posts.
- Refunds modeled only in Upside (one $249 kit); chargebacks modeled at zero throughout.
- Operating costs cover Vercel, Supabase, LLM tokens, PDF rendering and email; founder time is not counted.
- Every sale must cover its delivery cost; no kit is sold below cost.
Conservative
4 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $35
- Paid marketing
- $0
- Hackathon profit
- $961
- Operating costs
- $45
- Business profit
- $916
Base case
14 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $139
- Paid marketing
- $0
- Hackathon profit
- $3,347
- Operating costs
- $110
- Business profit
- $3,237
Optimistic
36 customers- Refunds
- $249
- Chargebacks
- $0
- Payment fees
- $403
- Paid marketing
- $150
- Hackathon profit
- $9,278
- Operating costs
- $320
- Business profit
- $8,958
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $3,486
- Payment fees (3.9%)
- $136
- Paid marketing
- $0
- Hackathon profit
- $3,350
- Business profit
- $3,240
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 derived from stated assumptions. These are projections, not verified revenue, customers or traction.
Main risks and validation experiments
Risk 1A generated brief misstates a material plan term, destroying trust and triggering a refund.
Force the unclear state whenever the cited excerpt does not contain the value, and hold those jobs in the founder review queue before delivery.
Run ten synthetic renewal pairs and count material errors that shipped unflagged.
More than one unflagged material error across ten pairs.
Risk 2Brokers refuse to upload client plan documents to a new solo-founder tool.
Ask for redacted employer-level PDFs only, publish a no-PHI data-handling note, delete files after delivery, and show a sample artifact first.
Track how many of 40 first touches agree to send a redacted packet.
Under 5% packet conversion after 60 first touches.
Risk 3Renewal season may already be past peak for many employers during the contest window.
Shift targeting to brokers with January and Q1 renewals from day 22 and capture next-renewal dates on every conversation.
Ask every reply for their next renewal date and count how many fall in Q1.
Fewer than three packets received from 60 first touches.
Risk 4Manual review and free samples consume the founder's month and stall paid conversions.
Cap free samples at two per day, hold any job needing more than 20 minutes of manual work, and prioritise paying jobs.
Time every job and log manual minutes against delivery hour.
Median turnaround above 24 hours for a full week.
Risk 5The artifact is perceived as benefits or legal advice, creating liability concerns.
Label every output as a document diff, include a footer disclaimer, and never recommend a plan choice or an enrollment decision.
Ask five brokers whether the disclaimer changes their willingness to use it with a client.
Three or more of five say the framing still reads as advice.
Hour-by-hour: the first 24 hours
Hours 1-2
- Write the fixed benefits schema covering all nine benefit categories.
- Freeze it as schema v1 with a version field.
Output: schema-v1.json committed to the repo.
Hours 3-5
- Create the Next.js repo and deploy the shell to Vercel.
- Provision Supabase with a private bucket and magic-link auth.
Output: Live URL and a working private upload bucket.
Hours 6-8
- Wire unpdf per-page text extraction on one public SBC sample.
- Run the structured extraction prompt and inspect page references.
Output: First extraction JSON with page-level citations.
Hours 9-11
- Search LinkedIn for brokers posting about Q4 renewals.
- Log 20 brokerages with contact and post URL.
Output: 20-row outreach sheet ready for day-9 sends.
Full 30-day launch report
Read the full generated report
Renewal Diff Brief - 30-Day Launch Report
Contest window 16 Nov 2026 13:00 UTC to 16 Dec 2026 13:00 UTC. Every number below is a projection, not verified revenue or traction.
1. Product opportunity and positioning
Employee-benefits brokers at 1-20 person agencies carry a Q4 bottleneck that has nothing to do with selling. A carrier renewal packet lands, and someone must read 60-150 pages of the current SPD/SBC against the renewal PDF, catch every change in deductible, out-of-pocket max, copays, coinsurance, Rx tiers, network and eligibility, then explain it to an office manager without misstating a plan term. Most do it with two PDFs open and memory. Missed changes surface in January as angry employees and lost accounts.
Renewal Diff Brief turns that into a diff. The broker uploads two PDFs; the product extracts a fixed benefits schema, aligns the plans, flags each field as unchanged, changed, added, removed or unclear, and attaches a page citation to every flag. It exports a broker-branded two-page Employer Change Brief, a five-slide Employee Explainer and a one-page FAQ.
The positioning is deliberately narrow: a diff tool, not benefits advice, not benefits administration, not claims or appeals. That framing keeps the founder out of PHI (employer-level plan documents only, member names and rates redacted), keeps the buyer out of procurement (the output is inspectable in 30 seconds), and keeps the build inside a week because there is no integration surface.
Why now: renewal and open-enrollment cycles are running, so the buyer already has the PDFs and a deadline. Value is provable on one free sample against a real packet before payment. JEV scored speed-to-first-revenue at 8.18 and solo build feasibility at 7.07, which is the shape of this wedge. The two weak criteria are constraints, not inconveniences: monetization (4.9) demands an explicit repeat-purchase path, and operational simplicity (4.94) demands that low-confidence extractions never become a permanent human desk. Sections 3 and 4 handle both.
The generic alternative is a comparison spreadsheet or a producer's memory. Incumbent broker tech exists but lives inside agency management systems nobody switches mid-season. This product does not ask for a switch. It asks for two PDFs.
2. Smallest sellable MVP
One renewal kit. Two PDFs in, three branded artifacts out, inside 24 hours. That is the whole sellable unit, and it is deliberately not a platform.
Built by day 5: two-PDF upload with a page cap and page map; a fixed benefits schema covering deductible, out-of-pocket max, copays, coinsurance, Rx tiers, network, eligibility, telehealth and HSA/HRA; a diff classifier with per-field confidence; a citation mapper showing the page excerpt beside every flag; branded export to a two-page brief PDF, five-slide explainer and one-page FAQ; Stripe Checkout plus a magic-link job page; a founder-only queue holding low-confidence jobs.
Out of scope: claims, EOBs, appeal letters, member-level or PHI data, carrier integrations, EHR or payroll, employee logins, automated benefits advice, SSO, procurement and 24/7 support.
The launch gate is not that it compiles. It is that three synthetic renewal pairs produce artifacts a working broker would put their logo on.
3. Technical implementation plan
Next.js on Vercel serves the upload, job page and site. Supabase provides Postgres, a private bucket and magic-link auth. unpdf extracts per-page text and builds a page map. One structured LLM call per document returns the schema with a page reference on every field; a second pass writes the change narrative and the FAQ. pptxgenjs renders slides, a headless renderer builds the brief PDF, Resend delivers files, and Stripe Checkout collects payment with products connected to TrustMRR from the first dollar.
One job record per upload drives everything: files in storage, extraction and diff JSON in Postgres, artifacts in storage, a status column rendering the magic-link page. No queue service, no worker fleet, no custom infrastructure.
Build order runs repo, schema, storage, extraction, prompt, diff engine, citation mapper, renderers, checkout, delivery email, review queue, sample kits.
The hardest technical risk is dirty PDFs: scanned packets, multi-column layouts and repeated headers that make the model attribute a dollar figure to the wrong field. The mitigation is structural rather than clever. Any field whose value cannot be found in its cited excerpt is forced to unclear and held for review. The product never guesses quietly.
4. Pricing and monetization
Two one-time products. Single Renewal Kit at $249 for one employer renewal. Agency Pack at $499 for three kits, a reusable branded template, priority turnaround and a per-employer FAQ. One-time billing fits how brokers buy: a renewal is an event, and $249 clears a card without procurement.
The monetization weakness is real, so the repeat path is explicit rather than hoped for. A broker with 20 small-group clients does not buy one kit; they buy an Agency Pack, use it, and return in the next cycle. Every delivered kit carries the broker logo, which makes the next purchase a re-order rather than a re-evaluation. Day 26 exists specifically to capture next-renewal dates and convert a one-off sale into a dated pipeline.
5. First-customer acquisition
One channel: direct LinkedIn outreach to independent employee-benefits brokers posting about Q4 renewals or open enrollment. No ads, no SEO, no partnerships.
The motion is a free diff on one anonymized packet. The ask is short, requires no call and makes the trade explicit: send two redacted PDFs, get a client-ready artifact in 24 hours, keep it whether or not you pay. Replies become packets; packets become a $249 link the same day the sample lands.
Weekly geometry: 60-100 brokerages listed, 60 first touches, roughly a quarter replying, five to eight packets, three to five free kits, one to three paid conversions in week two, then referrals. Every sample recipient is asked for one intro; every buyer is asked for one intro on delivery. Community posts use a real redacted artifact, only where brokers already gather.
6. Thirty-day roadmap
Days 1-5 are build: schema, extraction, diff, citations, artifacts, checkout, delivery. Day 5 is the MVP deadline and day 12 is the first-sale target.
Days 6-7 harden the product with a review queue, disclaimers and redaction copy, then publish two synthetic sample kits on the landing page.
Days 8-14 are the first revenue push: a 60-brokerage list, 40 first touches, free samples delivered inside 24 hours, $249 links sent the day of delivery, referrals requested, then a prompt fix for the top extraction failure.
Days 15-21 widen the list to 100, add proof content, pitch Agency Packs to multi-renewal contacts, run a midpoint scorecard that kills losing message variants, and audit every delivered artifact for misstated terms.
Days 22-28 run a daily 15-message rhythm, publish a no-PHI data-handling note, fix mobile checkout friction, capture next-renewal dates, and send a final-call wave.
Days 29-30 finish every outstanding kit, reconcile Stripe against TrustMRR, and archive the ledger.
7. Revenue and profit scenarios
| Scenario | Kits | Blended ARPU | Gross revenue | Paid ads | Operating |
|---|---|---|---|---|---|
| Conservative | 4 | $249 | $996 | $0 | $45 |
| Base | 14 | $249 | $3,486 | $0 | $110 |
| Upside | 36 | $280 | $10,080 | $150 | $320 |
Conservative assumes the list converts poorly and renewal timing runs late. Base assumes the free-sample motion works at roughly one paid kit per two samples. Upside assumes Agency Pack mix, referrals and $150 of sponsored community posts.
Fees are modeled at 3.5-4% of collected revenue through Stripe. Refunds appear only in the upside case (one $249 kit); chargebacks are modeled at zero. Hackathon profit excludes operating costs by rule; business profit does not. Both are derived from the inputs above rather than asserted here.
8. Main risks and validation
Misstated plan term. The artifact is the product, so one wrong deductible destroys the sale. Mitigation: force unclear when the excerpt lacks the value and hold those jobs for review. Test: ten synthetic pairs, count unflagged material errors. Kill: more than one.
Upload trust. Brokers may refuse to send client documents to a solo-founder tool. Mitigation: redacted employer-level PDFs only, a published data-handling note, deletion after delivery. Test: track packet conversion from 40 first touches. Kill: under 5% after 60 touches.
Seasonal timing. Volume peaks before the window opens. Mitigation: shift targeting to January and Q1 renewals from day 22. Test: ask every reply for their next renewal date. Kill: fewer than three packets from 60 touches.
Free-sample time sink. Manual review could eat the month. Mitigation: cap free samples at two per day and hold any job needing more than 20 manual minutes. Test: time every job. Kill: median turnaround above 24 hours for a week.
Advice perception. A brief that reads like a recommendation invites liability. Mitigation: label every output a document diff, footer disclaimer, no plan recommendations. Test: ask five brokers whether the framing changes their willingness to use it with a client.
9. First 24 hours
Hours 1-2: write and freeze the benefits schema. Output: schema v1 file.
Hours 3-5: repo, Vercel deploy, Supabase with a private bucket. Output: live URL and storage.
Hours 6-8: per-page PDF extraction plus the structured prompt on one public sample. Output: extraction JSON with page references.
Hours 9-11: 20-row broker list from LinkedIn renewal posts. Output: sheet ready for day-9 outreach.
This brief was generated from public data about established startups, then narrowed and scored for a solo 30-day launch. Revenue and profit figures are scenario models, not verified results, guarantees or evidence of existing customers. Validate demand yourself before you spend a month on it — and check the contest rules for what counts toward your score.
Related ideas
All ideas →Chargeback Evidence Forge
Turns a disputed order's support messages and tracking into a reason-code-matched evidence PDF for Stripe chargeback responses.
BriefToBoard Compiler
Turns a signed client brief into an importable project board, a one-page scope memo, and a missing-inputs checklist for small web-design and branding agencies.
MissedCall Quote Card
Turns a missed call plus a customer photo into a ready-to-send SMS quote card for solo home-service pros.