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

ClientBrief Weekly

Turns a 60-second async check-in from each teammate into a branded, client-ready weekly status page and email draft for agency retainers, without anyone retyping last week's update.

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.

Promising6.98/10
MVP build (solo)
5 days
Launch price
$49 · monthly
Sales to $1,000 revenue
21 customers
First paying customer
Cold DM plus a free first report fulfilled by the founder using the product.
Who pays

Owner, account manager or project manager at a 3-25 person digital marketing, design or dev agency billing 5-30 clients on monthly retainers, who still owes clients this week's status update on Thursday or Friday.

Biggest execution risk

Operational simplicity 4.9/10

Remove regulated data, human review steps and custom infrastructure; keep the product self-serve and stateless on managed services.

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.4/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

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

0/17
Entry price
$49
Solo build
5 days
30d base revenue
$1,782
30d hackathon profit
$1,626
Section 1 of 8

Product opportunity and positioning

Target customer

Owner, account manager or project manager at a 3-25 person digital marketing, design or dev agency billing 5-30 clients on monthly retainers, who still owes clients this week's status update on Thursday or Friday.

Why now

The buyer already holds a reporting budget line and a hard Friday deadline, $99 clears a card without procurement, and no chat-platform install is required, so value lands in the first session.

Problem

The Friday client status update is hand-assembled from Slack scrollback, a task board and memory, taking 45-90 minutes per client, with shipped work retyped and blocked work silently dropped.

Solution

A persistent per-client item ledger fed by magic-link check-ins or pasted notes, diffed every Friday into Shipped / In progress / Waiting on you / Blocked, published as a branded page at /r/{slug} with a paste-ready email draft and PDF.

Differentiation · A Google Doc or chat model summarises what you paste today and forgets it tomorrow; ClientBrief keeps a durable ledger where open items carry forward and each report is a diff, so week five takes four minutes instead of an hour.

1. Product opportunity and positioning

Agencies billing monthly retainers owe every client a status update on a fixed cadence, usually Thursday night or Friday morning. That artifact is client-facing, so it cannot be skipped, and it is rebuilt by hand each week from Slack scrollback, a task board and memory. The cost is 45-90 minutes per client; the worse cost is drift: shipped work gets retyped, blocked work silently disappears, and the client reads a wall of text nobody proofreads.

ClientBrief sells the artifact, not the habit. The positioning that matters is persistent ledger, weekly diff. A shared doc plus a chat model produces prose but forgets state. ClientBrief's durable asset is the per-client item ledger: open items carry forward, ship with one click, and each Friday's report is a diff against the previous snapshot, so week five takes four minutes instead of an hour. The output is a branded page at /r/{slug} plus a paste-ready email draft and a PDF, something an account manager forwards without editing.

Why this is sellable now: the buyer already has a budget line and a Friday deadline, $99 clears a card without procurement, and no Slack or Teams install is needed, so one person at the agency gets value in the first ten minutes. That is the whole wedge. Magic-link check-ins and paste-in ingestion mean the buyer does not need teammate adoption before the product pays for itself, which removes the single biggest reason agency tools die in week two.

Scope discipline matters more than ambition. The competition ranks verified profit inside 30 days, and every hour spent on integrations is an hour not spent on sends and fulfilled free reports. The product stays a reporting state machine: ingest items, keep a ledger, diff, publish, email. Chat-platform apps, two-way task sync and a client login portal are deliberately deferred.

Section 2 of 8

Smallest sellable MVP

One client ledger that produces one branded public report page plus a paste-ready email draft and PDF, billed through Stripe Checkout with a client-count limit.

Must-have features

  • Magic-link contributor check-in page with one text box and shipped / in progress / blocked tagging
  • Persistent per-client item ledger with one-click ship, carry-forward and archive
  • Friday diff generator producing Shipped this week, In progress, Waiting on you and Blocked
  • Branded public report page at /r/{slug} with agency logo and colour, plus copy-to-clipboard email draft and PDF export
  • Paste-in ingestion of a Slack thread or rough notes into editable ledger items
  • Resend Thursday contributor reminder and Friday owner notification via Vercel Cron
  • Stripe Checkout with Solo/Studio/Agency plans, webhook gating on client count and seats

Explicitly out of scope

  • No Slack, Teams, Google Chat or Discord app or bot directory listing
  • No two-way Jira, Asana, Linear or Trello sync
  • No client-side login, comments or approval portal
  • No time tracking, invoicing or profitability features
  • No mobile app and no general-purpose AI chat assistant

Demo flow (what the buyer sees)

  1. Founder pastes a prospect's real Slack thread or rough notes into the ingestion box
  2. Extraction returns tagged items in an editable review table
  3. Founder confirms rows into the client ledger, one click per shipped item
  4. Generator diffs the ledger against the previous snapshot
  5. Branded page is published at /r/{slug} and the link is copied
  6. Email draft and PDF are generated and sent back to the prospect within 24 hours
Build plan

Technical implementation plan

Stack

Next.js on VercelPostgres via SupabaseStripe Checkout and webhooksResend for transactional and reminder emailAnthropic or OpenAI API for paste-in extraction onlyTailwind CSS for the branded report templateVercel Cron for Thursday and Friday jobs

Architecture

The ledger is the source of truth. Check-ins and paste-ins append tagged items to a client ledger; the generator diffs live items against the last immutable report snapshot and renders four read-only sections; the public page is cached and expires for free reports; Stripe webhooks set plan limits on client count and seats; Vercel Cron fires Thursday reminders and Friday owner notifications per agency timezone.

Build steps

  1. Create the Next.js app on Vercel with Supabase Postgres and Tailwind, deploy on day 1
  2. Schema: agencies, users, clients, contributors, magic_tokens, items, report_snapshots, subscriptions
  3. Magic-link contributor auth via signed 30-day token at /c/{token}, no password
  4. Check-in page writes tagged items with source = checkin
  5. Ledger table per client with ship, carry-forward, archive and inline edit
  6. Paste-in ingestion: model call returns a normalised item array rendered as an editable review table, committed only on confirm
  7. Report generator: diff live items vs last snapshot, build four sections, store immutable snapshot with week number
  8. Public report page /r/{slug}: logo, hex colour, read-only, OG image, expiry flag for free reports
  9. Email draft text from the snapshot, headless PDF route, copy-to-clipboard button
  10. Resend plus Vercel Cron for Thursday reminders and Friday owner notifications
  11. Stripe Checkout and webhook writing plan, ledger limit and seat limit; billing portal link
  12. Internal ops page listing free reports, expiry dates and delivery status

AI components

  • Paste-in extraction: notes or Slack thread to tagged item array, always shown in an editable review table before commit
  • Optional rewrite call that converts raw item text into a client-safe one-line phrasing, labelled as generated and editable
Hardest technical risk: Extraction quality on messy pasted notes: a wrong item sent to a client embarrasses the buyer, so extraction must never auto-publish.
Section 3 of 8

Pricing and monetization

Solo

Entry offer
$49 / month

For Freelancer or one-person shop with up to 3 retainer clients

  • 3 client ledgers
  • 1 seat
  • Branded report pages and email drafts
  • Weekly reminder emails

Studio

$99 / month

For 3-25 person agency with up to 15 retainer clients

  • 15 client ledgers
  • 5 contributor seats
  • Logo and colour branding
  • PDF export
  • Paste-in ingestion

Agency

$199 / month

For Agency over 15 retainer clients or with multiple account managers

  • Unlimited client ledgers
  • 15 contributor seats
  • Custom report subdomain
  • ClientBrief footer removed

Model: Monthly subscription gated by client-ledger count and contributor seats, sold on a card with a written 7-day refund policy.

First revenue offer: Send one client's rough notes this week and I will send back a live branded status page plus a ready-to-send email draft free, no signup, delivered within 24 hours.

Expected ACV: $99

Upsell path: Studio to Agency when the client count passes 15 or a second account manager needs a seat; Agency to a second seat block per additional account manager.

Target customers
30
Revenue model
$2,970
Costs
$150
Profit model
$2,820
Section 4 of 8

First-customer acquisition

Primary channel

Cold DM plus a free first report fulfilled by the founder using the product.

Where to find them

  • r/agency threads about client reporting, status updates or Friday admin
  • r/marketingagency and r/PPC posts about retainers and account management
  • Two agency-focused Slack or Discord communities joined via public invite links
  • X accounts that posted about client reporting or agency admin in the last 60 days
  • Account managers listed on small agency team pages with public contact links

Exact outreach motions

  • Send a three-sentence DM with a before/after screenshot and the free-report offer
  • Post one value-only comment in r/agency answering a reporting question, no link
  • Fulfil accepted offers within 24 hours with a watermarked link expiring in 7 days
  • Follow up 48 hours later with week two pre-built in the ledger and a Studio Stripe link
  • Post one build-in-public thread per week with an anonymised before/after report
  • Log every send, reply and objection, and rewrite the DM after each 25 sends

Message template

Hey {name} - you posted about rebuilding client status updates every Friday. I built a tool that turns one client's rough notes into a branded status page plus a ready-to-send email in about four minutes. Want me to build this week's report for one client free? No signup, just paste your notes.
Week-one goal: 100 named prospects, 55 DMs sent, 5+ replies, 3 free reports delivered live.
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

Schema and deploy

  • Create Next.js app on Vercel and connect Supabase Postgres.
  • Write schema: agencies, users, clients, contributors, magic_tokens, items, report_snapshots.
  • Wire signed magic-link contributor tokens.
  • Seed one demo agency with three clients.

Deliverable: Deployed app with schema and a seeded demo agency.

Day 2Check-in

Ingest and ledger

  • Build /c/{token} check-in page: one textarea plus shipped / in progress / blocked tags.
  • Write items into the client ledger with status and first-seen week.
  • Build ledger table with one-click ship, carry-forward and archive.
  • Add inline edit for item text.

Deliverable: Contributor can post items; owner sees the ledger.

Day 3Report generator

Diff and public page

  • Diff live ledger items against the previous snapshot.
  • Render Shipped, In progress, Waiting on you, Blocked.
  • Publish branded /r/{slug} page with logo and hex colour.
  • Store an immutable snapshot per week.

Deliverable: Live branded report link for the demo client.

Day 4Delivery

Email, PDF, reminders

  • Generate copy-to-clipboard email draft from the snapshot.
  • Add PDF export via a headless render route.
  • Send Thursday contributor reminder and Friday owner email via Resend.
  • Schedule both with Vercel Cron in the agency timezone.

Deliverable: Full Friday output: page, draft, PDF, both emails.

Day 5BillingMVP shipped

Charge and gate

  • Create Solo, Studio and Agency monthly prices in Stripe.
  • Write webhook to set plan, ledger limit and seat limit.
  • Build clients and seats screen plus billing portal link.
  • Run one real card test end to end, then refund it.

Deliverable: MVP frozen; a stranger can pay and produce a report.

Day 6Paste-in

Ingestion with review gate

  • Add paste box that extracts tagged items in one model call.
  • Render results as an editable review table, committed only on confirm.
  • Label output generated from your notes, review before sending.
  • Run 10 messy real threads and log every failure.

Deliverable: Paste-in path validated on 10 messy inputs.

Day 7Demo and list

Landing page and prospects

  • Ship landing page with a 90-second Loom and one CTA.
  • Build 100-name list from subreddits, communities and X.
  • Write DM v1 and the free-report offer.
  • Set up the outreach tracking sheet.

Deliverable: Live landing page, 100 names, DM v1.

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

First 25 sends

  • Send 25 DMs with the before/after screenshot.
  • Post one value-only comment in r/agency.
  • Log replies and objections as they arrive.

Deliverable: 25 sends with first replies logged.

Day 9Fulfilment

Deliver free reports

  • Fulfil up to 3 free reports from real notes.
  • Send watermarked links expiring in seven days.
  • Time each report to confirm under 20 minutes.

Deliverable: Three live free reports delivered.

Day 10Outreach

Second wave

  • Send 30 more DMs to names 26-75.
  • Follow up the first wave with the free-report offer.
  • Rewrite the opening line if reply rate is under 10 percent.

Deliverable: 55 cumulative sends, DM v2 written.

Day 11First saleFirst sale target

Convert free reports

  • Send Studio Stripe links to every free-report recipient with week two pre-built.
  • Ask each for one named agency referral.
  • Offer written 7-day refund on every link.

Deliverable: First paying customer (target).

Day 12Outreach

Push to 100

  • Send 30 DMs to names 76-100.
  • Reply to every open thread within two hours.
  • Log objections into the sheet.

Deliverable: 100 sends complete.

Day 13Public proof

Build in public

  • Post one build-in-public thread with an anonymised before/after.
  • Answer five agency reporting questions in comments.
  • DM every commenter who asks a question.

Deliverable: Inbound replies logged.

Day 14Review

Read the numbers

  • Measure reply rate, free-report acceptance and paid conversion.
  • Decide whether the DM or the offer is the weak link.
  • Update the revenue sheet with actuals.

Deliverable: Written week-2 decision note.

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

Names 101-200

  • Send 40 DMs to names 101-200.
  • Run the second-week hook as the opening line.
  • Log objections into the sheet.

Deliverable: 150 cumulative sends.

Day 16Onboarding

Remove founder

  • Add self-serve onboarding email with three setup steps.
  • Write three canned support replies.
  • Publish a four-step first-report guide.

Deliverable: New buyer can go live without the founder.

Day 17Community

Inbound

  • Post a second build-in-public thread in a different community.
  • Answer questions without linking.
  • DM anyone who asks for the tool.

Deliverable: Second public post live.

Day 18Referrals

Free reports

  • Fulfil up to 4 free reports.
  • Ask each recipient for one named agency referral.
  • Send a two-line intro to each referral.

Deliverable: Referral names added to the list.

Day 19Retention

Week-two reports

  • Email every free account with week two already pre-built.
  • Attach a Studio Stripe link to the same email.
  • Track opens and clicks.

Deliverable: Second-week emails sent to all free accounts.

Day 20Objections

Fix the top two

  • Fix the two most common objections from the sheet.
  • Add a no-teammate-adoption-needed block to the landing page.
  • Shorten the check-in page to a single screen.

Deliverable: Two objection fixes shipped.

Day 21Review

Channel decision

  • Compare reply rate and free-to-paid conversion.
  • Kill or double the channel.
  • Update actuals in the revenue sheet.

Deliverable: Written channel decision.

Week 4 · Scale what works · 7 days
Day 22Referral push

Named intros

  • Ask every paying customer for one named referral.
  • Send three-line intro requests.
  • Follow up intros twice, no more.

Deliverable: Three live referral conversations.

Day 23Upsell

Agency tier

  • Pitch Agency at $199 to any customer above 12 client ledgers.
  • Ship custom subdomain and footer removal.
  • Verify seat and ledger gating.

Deliverable: Agency tier sellable.

Day 24Refund guard

Churn check

  • Check day-7 logins for every paying customer.
  • Email dormant accounts their own last report.
  • Honour refunds immediately, no negotiation.

Deliverable: Churn list with actions.

Day 25Public proof

Third post

  • Post a third thread showing a full anonymised report.
  • Repeat the free-report offer as the CTA.
  • Reply to every comment same day.

Deliverable: Third public post live.

Day 26Outreach

Names 201-300

  • Send 40 DMs to names 201-300.
  • Rewrite the DM from the best-performing line.
  • Book no calls.

Deliverable: 300 cumulative sends.

Day 27Ops

Runbook

  • Write a one-page runbook: refunds, one-business-day support SLA, incident notes.
  • Enable Stripe Radar rules.
  • Confirm database backups.

Deliverable: One-page ops runbook.

Day 28Review

Actuals

  • Compare verified revenue to each projection.
  • Cut any feature with zero usage.
  • Update the pricing note in onboarding.

Deliverable: Actuals sheet updated.

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

Books

  • Match every Stripe charge against TrustMRR.
  • Confirm no pre-launch payments exist.
  • Export invoices and refund receipts.

Deliverable: Reconciled payment ledger.

Day 30Close

Window end

  • Answer every open support thread.
  • Ship no new features.
  • Send each paying customer the December report calendar.

Deliverable: Window closed with clean books.

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: blended ARPU $99 assumes 70% Studio at $99, 20% Solo at $49 and 10% Agency at $199.
  • Conservative: blended ARPU $89 assumes 30% Solo, 65% Studio and 5% Agency.
  • Upside: blended ARPU $104 assumes a stronger Agency mix plus a few buyers paying a second monthly cycle before December 16.
  • Payment fees assume Stripe at 2.9% plus $0.30 per charge, applied to gross revenue.
  • Ad spend is zero in all scenarios: the plan is organic cold DM, community posts and referrals.
  • Operating costs cover Vercel, Supabase, Resend, the domain and paste-in model calls only; founder time is not costed.
  • Free reports are delivered by the founder as automated software output, not as consulting.
  • Customer counts are projections from a funnel of roughly 300 sends, 45 replies and 15 fulfilled free reports; they are not verified traction.

Conservative

6 customers
$534
collected revenue · avg payment $89
Refunds
$0
Chargebacks
$0
Payment fees
$17
Paid marketing
$0
Hackathon profit
$517
Operating costs
$45
Business profit
$472

Base case

18 customers
$1,782
collected revenue · avg payment $99
Refunds
$99
Chargebacks
$0
Payment fees
$57
Paid marketing
$0
Hackathon profit
$1,626
Operating costs
$75
Business profit
$1,551

Optimistic

32 customers
$3,328
collected revenue · avg payment $104
Refunds
$198
Chargebacks
$0
Payment fees
$106
Paid marketing
$0
Hackathon profit
$3,024
Operating costs
$120
Business profit
$2,904

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$882
Payment fees (3.9%)
$34
Paid marketing
$0
Hackathon profit
$848
Business profit
$773

Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.

Scenario models from stated assumptions, not verified revenue, customers or traction. All figures are projections.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold DM reply rate falls well below the assumed 15 percent, leaving the customer target unreached.

Mitigation

Two-channel plan with community posts and referrals, plus a DM rewritten every 25 sends.

Validation experiment

Send 25 DMs on day 8 and 25 on day 9; measure reply rate on 50 sends.

Kill criteria

Below 5 replies from 50 sends means rewrite the DM around the free Friday report and target account managers instead of owners.

Risk 2Agencies keep their Google Doc or Notion template out of inertia even after agreeing the report is better.

Mitigation

Paste-in ingestion plus a pre-built week-two report so the buyer never has to change anyone's behaviour.

Validation experiment

Ask five free-report recipients whether they would have paid $99 before seeing the output.

Kill criteria

Zero of five saying yes after two weeks means the pain is real but unbudgeted; reposition to per-report credit packs.

Risk 3An extraction error from paste-in notes becomes the buyer's client-facing embarrassment and a refund request.

Mitigation

Extraction never auto-publishes; every item passes through an editable review table with a review-before-sending label.

Validation experiment

Run ten real messy threads through paste-in and score each output as sendable or not.

Kill criteria

More than three of ten producing an unsendable item means drop paste-in from the pitch and lead with check-in links.

Risk 4Founder-manual fulfilment caps at three to four free reports per day and support load exceeds a solo operator.

Mitigation

Canned replies, self-serve onboarding email, a one-business-day support SLA, permanent cap on new accounts per week.

Validation experiment

Track minutes per free report and per support thread for two weeks.

Kill criteria

Above 45 minutes per customer per week means cut the Agency tier and stop selling until onboarding is automated.

Risk 5Monthly subscriptions bought late in the window are refunded or churn before December 16, lowering verified profit.

Mitigation

Immediate refunds with no friction, day-7 login check, and a week-two report already waiting in every account.

Validation experiment

Measure day-7 return logins for every paying customer.

Kill criteria

Fewer than half returning in week two means the product is a one-off purchase, so move to credit packs rather than subscriptions.

Risk 6Community self-promotion rules block the public thread channel, removing the inbound half of the plan.

Mitigation

Read each community's rules before posting, lead with answers rather than links, and keep DM volume as the primary channel.

Validation experiment

Post once in each of two communities and record removals versus replies.

Kill criteria

Both posts removed means shift entirely to DM plus referrals and add a paid sponsorship test only if profit allows.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the repo, Vercel project and Supabase database.
  • Sketch the schema on paper before writing SQL.

Output: Empty deployed app with a written schema.

Hours 2-6

  • Create the tables and indexes.
  • Implement signed magic-link tokens.
  • Seed the demo agency with three clients.

Output: Working schema with seeded demo data.

Hours 6-11

  • Build the /c/{token} check-in page.
  • Add one textarea and the three status tags.
  • Write items into the ledger.

Output: A contributor can post a tagged item.

Hours 11-16

  • Build the ledger table per client.
  • Add ship, carry-forward and archive actions.
  • Add inline edit.

Output: Owner-facing ledger with carry-forward.

Hours 16-20

  • Draft the public report template.
  • Write the diff query against the previous snapshot.
  • Render the four sections.

Output: A draft report page rendering real ledger items.

Hours 20-24

  • Write landing page copy and the free-report offer.
  • Add the first 30 names to the prospect list.
  • Write DM v1 and the tracking sheet.

Output: Landing copy, 30 names, DM v1 ready to send.

Complete report

Full 30-day launch report

Read the full generated report

ClientBrief Weekly - Operator Report, 30 Days

Concept: ClientBrief Weekly v1. JEV weighted score: 6.98 (69.8/100, band B, confidence 0.68). The highest sub-score is speed to first revenue (8.36); the lowest is operational simplicity (4.90). Every decision below therefore optimises for a card charge inside the window while removing human steps from delivery.

1. Product opportunity and positioning

Agencies billing monthly retainers owe every client a status update on a fixed cadence, usually Thursday night or Friday morning. That artifact is client-facing, so it cannot be skipped, and it is rebuilt by hand each week from Slack scrollback, a task board and memory. The cost is 45-90 minutes per client; the worse cost is drift: shipped work gets retyped, blocked work silently disappears, and the client reads a wall of text nobody proofreads.

ClientBrief sells the artifact, not the habit. The positioning that matters is persistent ledger, weekly diff. A shared doc plus a chat model produces prose but forgets state. The durable asset here is the per-client item ledger: open items carry forward, ship with one click, and each Friday's report is a diff against the previous snapshot. The output is a branded page at /r/{slug} plus a paste-ready email draft and PDF - something an account manager forwards without editing.

Why it is sellable now: the buyer already holds a budget line and a Friday deadline, $99 clears a card without procurement, and no Slack or Teams install is required. Magic-link check-ins and paste-in ingestion mean the buyer does not need teammate adoption before the product pays for itself, which removes the usual reason agency tools die in week two.

2. Smallest sellable MVP

The sellable unit is one client ledger producing one branded report page plus an email draft. Five things must exist: the magic-link check-in page with shipped / in-progress / blocked tagging; the ledger with one-click ship and carry-forward; the Friday diff generator with four sections; the branded public page, draft and PDF; and Stripe Checkout gating ledger count and seats. Paste-in ingestion is the sixth piece and the one that closes deals, because it lets the buyer get a result alone. Out of scope for 30 days: any chat-platform app, two-way task sync, a client login or comments, time tracking, invoicing, mobile. Pass test: take a real Slack thread and return a live branded link in under four minutes.

3. Technical implementation plan

Next.js on Vercel, Postgres on Supabase, Stripe Checkout plus webhooks, Resend, Tailwind for the report template, Vercel Cron for Thursday and Friday jobs, and a single model call path used only for paste-in extraction. The ledger is the source of truth: check-ins and paste-ins append tagged items; the generator diffs live items against the last immutable snapshot and renders four sections; the public page is read-only and cached; billing webhooks set plan limits. The hardest risk is extraction quality. Mitigation is structural: extraction never publishes, it returns an editable review table, and every generated line is labelled as generated and reviewable. A wrong item must cost the buyer ten seconds, not a client relationship.

4. Pricing and monetization

Monthly only: Solo $49 for 3 ledgers and 1 seat, Studio $99 for 15 ledgers and 5 seats with branding, PDF and paste-in, Agency $199 for unlimited ledgers, 15 seats, custom subdomain and footer removal. Studio is the default pitch because most agencies carry more than three retainers and the $49 gap is trivially approved. Gate on ledger count and seats, not features, so upgrades are caused by growth rather than curiosity. Offer a written 7-day refund, which converts better than a trial and caps damage. No annual plans inside the window: cash inside the 30 days is what gets ranked. Upsell from Studio to Agency when a second account manager needs a seat.

5. First-customer acquisition

One channel: cold DM plus a free first report. Build 100 names from r/agency, r/marketingagency, two agency Slack or Discord communities, and X accounts posting about client reporting in the last 60 days. Send a three-sentence DM with a before/after screenshot and the offer: send one client's notes, get a branded status page free, no signup. Fulfil within 24 hours with a watermarked link expiring in seven days, then follow up 48 hours later with week two pre-built and a Studio Stripe link. Planned funnel as a projection, not a promise: roughly 300 sends, about 45 replies, 15 fulfilled free reports, 5 paying customers - so the upside case depends on referrals from fulfilled reports, not on DMs alone. Rewrite the DM after every 25 sends and never exceed the fulfilment capacity of three to four reports a day.

6. 30-day execution roadmap

Days 1-5 are build-only, ending with an MVP a stranger can pay for: schema and magic links, check-in page and ledger, diff generator and branded page, email draft and PDF with both reminders, then Stripe Checkout, webhook gating and a real end-to-end card test. Day 6 adds paste-in extraction behind the review gate; day 7 ships the landing page, the Loom and the first 100 names. Days 8-14 are outreach and fulfilment: 25 sends, three free reports delivered, 30 more sends, with the first paid conversion targeted at day 11. Days 15-21 double the list through a second community and referral asks, and add self-serve onboarding so buyers never wait on the founder. Days 22-28 push second-week reports into every free account, ask for named referrals, and convert large retainers to Agency. Days 29-30 reconcile Stripe against TrustMRR and ship nothing new.

7. Revenue and profit scenarios

All figures are projections from the stated assumptions, not verified revenue. Conservative: 6 customers at an $89 Solo-heavy blend, $534 collected, no refunds, $17 in Stripe fees, $45 operating. Base: 18 customers at $99, $1,782 collected, one $99 refund, $57 in fees, $75 operating. Upside: 32 customers at $104, $3,328 collected, two refunds at $198, $106 in fees, $120 operating. The contest ranks collected revenue minus refunds, chargebacks, processing fees and paid marketing; hosting, domains and model costs sit in business profit only. Base case: about $1,626 ranked profit and $1,551 business profit. Fees assume Stripe at 2.9% plus $0.30 per charge; ad spend is zero in every scenario because the plan is organic.

8. Main risks and validation experiments

Reply rate collapse. Send 25 DMs on day 8 and 25 on day 9. Fewer than 5 replies from 50 sends means rewrite the DM around the free Friday report and target account managers, not owners.

Template inertia. Ask five free-report recipients whether they would have paid $99 before seeing the output. Zero yes answers means reposition to per-report credit packs.

Extraction embarrassment. Run ten real messy threads through paste-in. More than three unsendable outputs means drop paste-in from the pitch and lead with check-in links.

Fulfilment ceiling. Track minutes per free report and per support thread. Above 45 minutes per customer per week, cut the Agency tier and cap new accounts.

Refunds before December 16. Check day-7 logins for every payer. Fewer than half returning in week two means the product is a one-off and subscriptions are the wrong model.

9. First 24-hour action plan

Hours 1-2: repo, Vercel, Supabase, schema on paper. Hours 2-6: tables, magic-link tokens, demo seed. Hours 6-11: check-in page and tagging. Hours 11-16: ledger with ship and carry-forward. Hours 16-20: public report template and diff query. Hours 20-24: landing copy, the offer text, first 30 prospect names and DM v1. Nothing in those 24 hours is research - it is code or names.

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 →