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

Retainer Proof

Retainer Proof turns an agency's sent client email into a branded, source-linked monthly recap PDF per retainer client, so the owner can prove the value delivered in minutes instead of an evening of writing.

One product, one founder, thirty days. Everything below is built to be executed inside the contest window — the official rules still decide what counts.

Decide in 20 seconds

The facts that decide whether this is worth thirty days of yours.

Speculative6.35/10
MVP build (solo)
5 days
Launch price
$49
Sales to $1,000 revenue
21 customers
First paying customer
Hand-personalized LinkedIn and X direct messages to 60 boutique agency owners who publicly mention retainers, opening with a free sample recap built from their own sent mail.
Who pays

Owner/operator of a 2-10 person boutique agency (design, dev, SEO, paid media) with roughly 3-15 monthly retainer clients, paying by card, in US/UK/CA/AU.

Biggest execution risk

Operational simplicity 4.0/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 12; 21 sales at $49 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 7.7/10.

Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.

Your first 24 hours

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

0/10
Entry price
$49
Solo build
5 days
30d base revenue
$1,089
30d profit†
$1,019
Section 1 of 8

Product opportunity and positioning

Target customer

Owner/operator of a 2-10 person boutique agency (design, dev, SEO, paid media) with roughly 3-15 monthly retainer clients, paying by card, in US/UK/CA/AU.

Why now

LLM drafting of short bullets from real email is now cheap and accurate enough, and Gmail read-only access takes one click, so the first sample can be delivered on day one.

Problem

The monthly value recap is the document that protects the retainer, and it gets skipped because writing it means digging through a month of sent mail per client.

Solution

Connect Gmail read-only or forward sent mail, map each client to a domain or label, pick a month, review source-linked AI-drafted bullets, and export a branded PDF per client.

Differentiation · Not an email assistant, not a time tracker, not a client portal: every recap bullet links back to the sent message that proves it, and the owner approves before anything reaches a client.

Retainer Proof — 30-Day Solo Founder Report

JEV scored this concept 63.5/100 (band C). Speed to first revenue is the strongest sub-score at 7.71; operational simplicity is the weakest at 4.03. This plan exploits the first and caps the second: the buyer has a monthly deadline and a card in hand, and every human step is limited to what one person can deliver in a day.

1. Product opportunity and positioning

A 2-10 person agency living on retainers has one recurring, high-leverage document: the monthly recap showing what was delivered. It is also the one most often skipped, because producing it means an owner scrolling a month of sent mail per client — an hour each, or nothing. Nothing lands harder at renewal than a client asking what they are paying for.

Retainer Proof builds that document out of work the team already did. Connect Gmail read-only (or forward sent mail to a private address), map a client to an email domain or Gmail label, pick a month, and the engine extracts deliverables, review rounds, meetings and shipped fixes, each carrying a link back to its source message. An LLM drafts four to eight client-ready bullets in the agency's tone; the owner edits and approves item by item; the product renders a branded PDF the owner sends from their own address.

The positioning is deliberately narrow. This is not an email assistant, not a time tracker, not a client portal, not a project-management integration. It does not filter, label, mute or summarize an inbox. It replaces a blank page with a review screen, and it replaces unsourced AI claims with traceable ones. The buyer is the owner, paying by card, with no procurement and no team rollout. The realistic alternatives are a manual evening, a skipped month, or a chat prompt that invents numbers — the source trail plus mandatory approval is the wedge, and the free sample recap is the sales asset.

2. Smallest sellable MVP

Five things and nothing else: Google sign-in with a read-only Gmail connection in Testing mode; a client mapper by domain or label; a month extraction that produces de-duplicated work items with source message IDs; an LLM drafting pass plus a review screen with edit, delete, merge, reorder and per-bullet regenerate; and an HTML-to-PDF renderer with logo and colors, gated by Stripe Checkout. A forward-in fallback address covers the case where OAuth friction stalls a prospect. If an owner cannot go from connect to finished PDF in under ten minutes, the MVP is not done.

3. Technical implementation plan

One Next.js app on Vercel, Supabase Postgres for workspaces, client mappings, source items and approved bullets, Google Identity plus the Gmail API for the primary path, Cloudflare Email Workers for the forward-in address, an LLM API for drafting, a headless PDF renderer, and Stripe Checkout with the Customer Portal. Build order: schema, OAuth, extraction, drafting, review, PDF, billing, fallback. The one thing most likely to break is extraction quality — Gmail threading and calendar dedupe will produce duplicate or empty items for messy clients, so build a manual "add item" escape hatch on day three rather than day twenty. A purge job deletes stored source message bodies after render; that single feature answers the privacy objection in every sales thread.

4. Pricing and monetization

Two prices, both under the owner's approval threshold. A $49 one-time Single Recap removes the commitment objection and converts a hesitant sample conversation into paid proof; the $99 monthly Agency plan is the real product, covering up to ten mapped clients, unlimited recap PDFs, the review screen and a branded template. Expected revenue per paying buyer is $99/month, with the one-time tier as an entry ramp that should convert to monthly after the first delivered PDF. Upsell path: more mapped clients, additional brands, and a second monthly run date per workspace.

5. First-customer acquisition

One channel: hand-personalized direct messages to 60 boutique agency owners whose public profiles mention retainers. The opener offers a finished artifact, not a demo — send one client's name and get back a branded recap of last month's work, free, no signup. Delivery within 24 hours via a five-minute Gmail connection or five forwarded emails. The close is a single sentence with a Stripe link. Follow up on day three and day seven with a forty-second recording of the review screen, ask every buyer for one introduction, and publish one anonymized teardown publicly to catch inbound. Week-one target: 60 names, 35 messages, 4 completed samples.

6. 30-day execution roadmap

Days 1-4 are build: schema, OAuth, extraction, drafting, review screen, PDF, Stripe. Day 5 is MVP live and the first real sample delivered, which is the hard deadline. Days 6-12 are outreach and concierge delivery against a 60-name list, ending with the first paid agency on day 12. Days 13-21 shift from selling to proving: full client sets for buyer one, onboarding time cut under five minutes, a scheduled monthly run date, a published data-handling note, and a second and third close. Days 22-30 are the last outreach wave, month-end closes, a verified revenue and cost reconciliation against Stripe, and a written go-or-narrow decision using pre-committed kill criteria. Daily cap: no more samples than one person can deliver, because sample delivery is the throughput ceiling.

7. Revenue and profit scenarios

Projections only, not verified revenue. Conservative: 4 paying agencies at $99, $396 revenue, $45 costs, $351 profit. Base: 11 agencies, $1,089 revenue, $70 costs, $1,019 profit. Upside: 18 agencies, $1,782 revenue, $130 costs, $1,652 profit. Costs are Stripe fees, LLM usage, PDF/email tooling and a domain; hosting stays on free tiers. The realistic 30-day outcome is roughly $1K-$2K, not $100K. A $100K path requires around 70 agencies retained for twelve months plus per-client upsells, and belongs to a later stage.

8. Main risks and validation experiments

Google restricted-scope verification cannot finish inside 30 days, so the product runs in Testing mode with manually added users plus the forward-in fallback; measure how many prospects abandon at the connection step. Owners may decide a chat prompt or a manual evening is good enough, so ask ten of them what they did last month and how long it took before writing more code. LLM bullets could misstate delivered work, which is reputationally fatal in a client-facing document; mandatory approval and inline source links are the control, and edit rate above 20% means the drafting pass is not ready. A sub-5% reply rate on 60 messages means the channel is wrong, not the product, and the message must be rewritten, not repeated.

9. First 24 hours

Hours 1-2: scaffold the app and register the domain. Hours 3-4: create the Supabase schema and Google OAuth in Testing mode. Hours 5-6: build 25 rows of the agency list with owner names and handles. Hours 7-9: write the extraction query against one real mailbox. Hours 10-12: send the first five messages offering a free sample. By end of day one there must be a deployed skeleton, 25 named prospects, and five messages out.

Section 2 of 8

Smallest sellable MVP

Connect Gmail read-only (or forward sent mail), map one client, pick one month, review AI-drafted source-linked bullets, export one branded PDF and charge for it via Stripe.

Must-have features

  • Google sign-in plus Gmail read-only connection in OAuth Testing mode with manually added test users
  • Client mapper by email domain and/or Gmail label, stored per workspace
  • Month extraction job pulling sent mail plus calendar events, de-duplicated with source message IDs
  • LLM drafting of 4-8 client-ready bullets in the agency's tone, numbers only when present in source
  • Review screen with edit, delete, merge, reorder and per-bullet regenerate plus month approval
  • Branded HTML-to-PDF renderer with agency logo, colors, header and footer
  • Stripe Checkout for $49 single recap and $99 monthly plan with a plan gate
  • Forward-in private per-workspace address as the no-OAuth delivery path
  • Purge job deleting stored source message bodies after render

Explicitly out of scope

  • Inbox triage, filtering, labeling or newsletter summarization
  • Time tracking, timesheets or project-management integrations
  • Client-facing portal, client logins or white-label subdomain
  • Multi-seat team accounts or role permissions
  • Slack, SMS or push alerting
  • Analytics dashboards or delivered-vs-billed reporting

Demo flow (what the buyer sees)

  1. Prospect connects Gmail read-only or forwards five sent emails to their private address
  2. Founder maps one client to an email domain or Gmail label
  3. Extraction pulls the last calendar month of sent mail and calendar events for that client
  4. Engine de-duplicates threads into candidate work items with dates and source message IDs
  5. LLM drafts 4-8 recap bullets with a one-line 'what this means for you' framing each
  6. Owner edits, deletes, merges or regenerates individual bullets and approves the month
  7. Renderer produces a branded PDF with logo, colors and a source trail
  8. Owner downloads the PDF or sends it from their own Gmail address
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres and AuthGoogle Identity + Gmail API (gmail.readonly)Cloudflare Email Workers for the forward-in addressOpenAI or Anthropic API for bullet draftingHeadless Chromium or @react-pdf/renderer for PDF outputStripe Checkout and Customer PortalResend for transactional email

Architecture

A single Next.js app on Vercel serves the landing page, the OAuth callback, the review screen and the PDF endpoint. Supabase holds workspaces, client mappings, extracted source items and approved bullets. A queued extraction job reads Gmail sent mail and calendar events for one client and one month, de-duplicates threads and writes candidate items. An LLM call turns items into bullets stored as draft rows. The owner edits rows in the review screen and approves them, which triggers the renderer to produce a PDF stored in a Supabase bucket for download. Stripe webhooks set the plan flag that unlocks PDF export beyond one sample. The forward-in address writes messages into the same source-item table so both paths converge on one pipeline. A post-render job deletes stored message bodies.

Build steps

  1. Create Supabase tables for workspaces, clients, source_items, bullets and plans
  2. Wire Google OAuth in Testing mode and store refresh tokens per workspace
  3. Build the client mapper (domain list and Gmail label per client)
  4. Write the month extraction job with thread de-duplication and source message IDs
  5. Add a manual 'add item' escape hatch for clients with thin sent mail
  6. Implement the LLM drafting prompt with tone sample and no-invented-numbers instruction
  7. Build the review screen with edit, delete, merge, reorder and regenerate
  8. Build the branded PDF renderer with logo upload and two brand colors
  9. Integrate Stripe Checkout, webhook and plan gate
  10. Ship the forward-in address via Cloudflare Email Workers
  11. Add the purge job that deletes source bodies after render
  12. Publish a landing page with one downloadable sample recap

AI components

  • LLM drafting pass converting extracted work items into 4-8 client-ready recap bullets in the agency's tone
  • LLM tone-matching from a sample of the agency's sent mail
  • LLM regeneration of a single bullet on request
Hardest technical risk: Extraction quality on messy real mailboxes: Gmail threading and calendar overlap will produce duplicates or empty months for some clients, which is why the manual add-item escape hatch ships in the first four days.
Section 3 of 8

Pricing and monetization

Single Recap

Entry offer
$49 one-time

For Agency owner who wants one client recap now with no subscription commitment

  • One branded recap PDF for one client for one month
  • Source-linked bullets with dates and message references
  • One round of regeneration after edits

Agency

$99 / month

For 2-10 person agency carrying 3-10 retainer clients

  • Up to 10 mapped clients
  • Unlimited monthly recap PDFs
  • Review, edit and approve screen with per-bullet regeneration
  • Branded template with agency logo and colors
  • Delivery from the agency's own Gmail address

Model: Two prices: a $49 one-time single recap as the entry ramp and a $99 monthly agency plan for the recurring job.

First revenue offer: Send one client's name and I will send back a branded recap PDF of last month's work I built from your own sent email — free, no signup. If it is useful, it is $49 for this one or $99/month to auto-generate it for every retainer client.

Expected ACV: $99

Upsell path: Single Recap buyers convert to the $99 monthly plan after the first delivered PDF; monthly buyers expand to more mapped clients, a second brand, and a second monthly run date per workspace.

Target customers
15
Revenue model
$1,485
Costs
$95
Profit model
$1,390
Section 4 of 8

First-customer acquisition

Primary channel

Hand-personalized LinkedIn and X direct messages to 60 boutique agency owners who publicly mention retainers, opening with a free sample recap built from their own sent mail.

Where to find them

  • LinkedIn search for 'founder' or 'owner' at 2-10 person design, dev, SEO and paid-media agencies
  • X bios mentioning 'we work on retainer' or 'monthly retainer clients'
  • Public agency directories and Clutch-style listings filtered to small headcount
  • Agency owner communities and small Slack or Discord groups for studio owners
  • Referral names requested from every sample recipient and buyer

Exact outreach motions

  • Build a 60-row sheet with owner name, handle, agency type and one client they publicly mention
  • Send a 60-word first message offering a free one-client recap PDF, no signup
  • Deliver the sample within 24 hours using a five-minute Gmail connection or five forwarded emails
  • Follow up on day 3 and day 7 with a 40-second screen recording of the review screen
  • Send the Stripe link in the same thread that received the sample, never a new thread
  • Ask every buyer for one introduction to another agency owner
  • Publish one anonymized recap teardown publicly to catch inbound

Message template

Hi {name} — I build the monthly recap you owe your retainer clients. Send me one client's name and I'll send back a branded recap PDF of last month's work, pulled from your own sent email. Free, no signup, back within 24 hours.
Week-one goal: 60 named agencies, 35 first-touch messages sent, 4 completed free sample recaps delivered.
Section 5 of 8

30-day execution roadmap

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

Scaffold and prospect list

  • Scaffold Next.js on Vercel with Supabase auth.
  • Create tables for workspaces, clients, source items and bullets.
  • Register and point the domain.
  • Build the first 25 rows of the 60-agency list.

Deliverable: Deployed skeleton and 25 named agency prospects.

Day 2Ingestion

Gmail read-only and extraction

  • Wire Google OAuth in Testing mode with manually added users.
  • Store client mappings by email domain or Gmail label.
  • Pull sent mail and calendar events for a chosen month.
  • De-duplicate threads into candidate work items with message IDs.

Deliverable: Candidate work-item list per client with source links.

Day 3Drafting

LLM bullets and review screen

  • Prompt the LLM for 4-8 bullets in the agency tone, numbers only if in source.
  • Build the review screen with edit, delete, merge and reorder.
  • Add per-bullet regenerate.
  • Add a manual add-item escape hatch.

Deliverable: Editable, source-linked recap bullets.

Day 4Delivery

PDF and payment

  • Render a branded PDF with logo, colors, header and footer.
  • Add Stripe Checkout for $49 single and $99 monthly.
  • Gate PDF download behind an active plan.
  • Send the PDF from the owner's own Gmail address.

Deliverable: End-to-end paid recap PDF.

Day 5MVP liveMVP shipped

Fallback and launch surface

  • Ship the forward-in address per workspace as the no-OAuth path.
  • Publish the landing page with one downloadable sample recap.
  • Run a full recap for a real prospect's month.
  • Send that sample with its source trail.

Deliverable: MVP live and first sample recap delivered.

Day 6Outreach

First message batch

  • Send 20 hand-written messages opening with a free sample.
  • Log every reply in one sheet with a next action.
  • Deliver requested samples within 24 hours.
  • Record the 40-second review-screen video.

Deliverable: 20 contacts touched and samples queued.

Day 7List

Complete 60 names

  • Add 35 more agencies to reach 60.
  • Send 15 more first-touch messages.
  • Post one anonymized recap teardown.
  • Fix the top onboarding friction found this week.

Deliverable: 60-name list complete and 35 messages out.

Week 2 · Launch & first sale · 7 days
Day 8Follow-up

Close attempts

  • Follow up day-3 on every non-replier with the video.
  • Send the $99 offer to everyone who received a sample.
  • Offer a six-month $99 lock to the first three buyers.
  • Answer privacy questions with the delete-after-render policy.

Deliverable: Offer delivered to every sample recipient.

Day 9Friction

Time to first PDF

  • Cut connect-to-first-PDF under five minutes.
  • Add a paste-a-client-domain quick start.
  • Handle empty-month and low-email clients gracefully.
  • Ship the purge job that deletes source mail after render.

Deliverable: Onboarding under five minutes with purge running.

Day 10Validation

Willingness-to-pay calls

  • Book three calls with owners who replied but did not buy.
  • Ask what they do today for recaps and what it costs them.
  • Offer the $49 single recap as the low-commitment entry.
  • Rewrite the offer script from what you hear.

Deliverable: Three discovery calls and a revised offer script.

Day 11Pipeline

Second touch wave

  • Send 20 second-touch messages with a specific client example.
  • Deliver two more free samples.
  • Ask every sample recipient for one referral name.
  • Track reply rate by message variant.

Deliverable: Reply-rate table by message variant.

Day 12First revenueFirst sale target

Close buyer one

  • Push hardest on the warmest sample conversation.
  • Send a Stripe Checkout link in the same thread.
  • Onboard the buyer and generate their first live PDF.
  • Log the exact words that closed the deal.

Deliverable: First paying agency and first paid PDF.

Day 13Retention

Deliver the full client set

  • Map up to ten clients for the first buyer.
  • Generate recaps for every retainer client they have.
  • Ask permission to quote their result, only if granted.
  • Fix anything they had to hand-edit.

Deliverable: Full client set delivered for buyer one.

Day 14Retro

Week two review

  • Compute replies, samples, calls and sales from the log.
  • Cut the worst-performing message variant.
  • Ship the top two fixes from customer edits.
  • Set the week-three sales target.

Deliverable: Week two funnel numbers and week three target.

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

Third message batch

  • Send 20 fresh first-touch messages.
  • Target paid-media and SEO agencies this round.
  • Deliver same-day samples where possible.
  • Post a second public teardown.

Deliverable: 20 new conversations opened.

Day 16Proof

Source trail polish

  • Show the source message snippet under each bullet.
  • Add a verified-against-sent-mail footer line.
  • Flag clients with no sent mail instead of inventing items.
  • Test the PDF on mobile and in print.

Deliverable: Recap PDF with a visible source trail.

Day 17Sales

Close buyers two and three

  • Send checkout links to the two warmest threads.
  • Offer to run month one live on a call.
  • Collect payment before generating the PDF.
  • Ask each buyer for one introduction.

Deliverable: Two checkout links live and introductions requested.

Day 18Ops

Manual throughput

  • Time a full sample delivery end to end.
  • Template the two slowest steps.
  • Cap daily samples at what one person can deliver.
  • Write the delivery checklist.

Deliverable: Repeatable sample delivery checklist.

Day 19Expansion

Second month hook

  • Add a recurring monthly run date per workspace.
  • Email owners on the 1st with a ready recap.
  • Add one-click send-to-client from their own Gmail.
  • Pilot the reminder with existing buyers.

Deliverable: Scheduled monthly recap run.

Day 20Pipeline

Referral push

  • Ask all buyers and sample recipients for one name.
  • Send 15 referral-introduction messages.
  • Publish a before-and-after time comparison from your own log.
  • Follow up on all day-7 non-repliers.

Deliverable: Referral introductions requested.

Day 21Retro

Week three review

  • Review paid versus free sample conversion.
  • Decide whether the $49 single stays.
  • Fix the highest-friction step again.
  • Set the week-four close target.

Deliverable: Week three numbers and a pricing decision.

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

Fourth message batch

  • Send 20 more first-touch messages.
  • Include one line about the $49 single recap.
  • Deliver samples within 24 hours.
  • Reply to every unanswered thread.

Deliverable: 20 new touches with all threads answered.

Day 23Product

Branding controls

  • Add logo upload and two brand colors.
  • Add a client-tone selector.
  • Test the forward-in path with a real mailbox.
  • Fix PDF font and page-break issues.

Deliverable: Branded template usable by any buyer.

Day 24Revenue

Push to five buyers

  • Send checkout links to every warm thread.
  • Offer the founding rate only to new buyers.
  • Onboard each new buyer the same day.
  • Log the close reason for every loss.

Deliverable: Every warm thread at checkout.

Day 25Trust

Privacy answer

  • Publish a one-page data handling note.
  • Ship the delete-source-after-render toggle.
  • Add workspace-level disconnect and purge.
  • Put the note in every sales thread.

Deliverable: Public data handling page.

Day 26Retention

Month two check

  • Check which buyers logged in after their first recap.
  • Call anyone who has not.
  • Ask what would make the recap mandatory.
  • Ship the requested fix if it is under a day.

Deliverable: Churn-risk list with assigned actions.

Day 27Pipeline

Final outreach wave

  • Send 20 final first-touch messages.
  • Rework the opener using the best-performing variant.
  • Deliver outstanding samples.
  • Ask every buyer for a referral again.

Deliverable: Final outreach wave sent.

Day 28Close

Month-end push

  • Call every warm lead before month end.
  • Send checkout links with same-day onboarding.
  • Invoice all monthly plans.
  • Confirm every buyer's next run date.

Deliverable: Month-end closes and renewal dates set.

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

Reconcile numbers

  • Total collected revenue and costs against Stripe.
  • Compute cost per sample delivered.
  • Rank the three best-performing message angles.
  • Write the month-two plan.

Deliverable: Verified revenue, costs and message ranking.

Day 30Decide

Go or narrow

  • Decide continue, narrow or stop using the kill criteria.
  • Keep only channels that produced paying buyers.
  • Set month-two targets from actual conversion.
  • Ship one improvement before day 31.

Deliverable: Go-or-narrow decision with month-two targets.

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

  • Agency owners with three or more retainer clients spend at least an hour per client per month on recaps, or skip them entirely.
  • Owners will connect a read-only mailbox or forward five emails to an unbranded tool in exchange for one finished sample report.
  • 60 hand-written messages produce roughly 8-12 replies and 4-6 completed free samples.
  • About 15-20% of completed sample conversations close at $99 or $49.
  • LLM drafting yields bullets the owner accepts with fewer than 20% edits.
  • $99/month sits under the owner's card-approval threshold with no procurement or finance review.
  • Costs are Stripe fees, LLM usage, PDF/email tooling and a domain; hosting stays on free tiers.
  • A $100K outcome is not claimed for 30 days and would require roughly 70 agencies retained for twelve months plus per-client upsells.

Conservative

4 customers
$396
collected revenue · avg payment $99
Refunds
n/a
Chargebacks
n/a
Payment fees
n/a
Paid marketing
n/a
Hackathon profit
n/a
Operating costs
n/a
Business profit
n/a

Pre-breakdown estimate. This report was generated before costs were itemised, so refunds, fees, ad spend and operating costs cannot be separated without inventing them. Nothing is estimated here. Original modelled profit (all costs included): $351.

Base case

11 customers
$1,089
collected revenue · avg payment $99
Refunds
n/a
Chargebacks
n/a
Payment fees
n/a
Paid marketing
n/a
Hackathon profit
n/a
Operating costs
n/a
Business profit
n/a

Pre-breakdown estimate. This report was generated before costs were itemised, so refunds, fees, ad spend and operating costs cannot be separated without inventing them. Nothing is estimated here. Original modelled profit (all costs included): $1,019.

Optimistic

18 customers
$1,782
collected revenue · avg payment $99
Refunds
n/a
Chargebacks
n/a
Payment fees
n/a
Paid marketing
n/a
Hackathon profit
n/a
Operating costs
n/a
Business profit
n/a

Pre-breakdown estimate. This report was generated before costs were itemised, so refunds, fees, ad spend and operating costs cannot be separated without inventing them. Nothing is estimated here. Original modelled profit (all costs included): $1,652.

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$539
Payment fees (3.9%)
$21
Paid marketing
$0
Hackathon profit
$518
Business profit
$518

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.

These are projections, not verified revenue, existing customers or real traction. No customer, revenue or partnership exists as of writing.

Section 7 of 8

Main risks and validation experiments

Risk 1Google restricted-scope verification cannot complete in 30 days, and Testing-mode OAuth adds friction at signup.

Mitigation

Run OAuth in Testing mode with manually added test users and ship the forward-in inbox address as a parallel path from day five.

Validation experiment

Ask five prospects to connect in a live screen share and count how many finish without help.

Kill criteria

If fewer than three of five prospects can complete either path unaided, rebuild onboarding before any further outreach.

Risk 2Owners decide a manual evening or a generic chat prompt is good enough, so willingness to pay collapses.

Mitigation

Lead every conversation with a delivered artifact and charge $49 for the single recap to test payment without a subscription.

Validation experiment

Ask ten agency owners what they did last month for recaps and how long it took; record verbatim answers.

Kill criteria

If fewer than two of ten say they spend over an hour per client on recaps, the pain is not real and the concept should be narrowed or dropped.

Risk 3LLM bullets misstate delivered work, which is reputationally dangerous in a client-facing document.

Mitigation

Every bullet carries a source message link, numbers appear only when present in the source, and the owner must approve the month before any PDF renders.

Validation experiment

Count edits, deletions and regenerations per recap across the first five samples and report the edit rate.

Kill criteria

If owners edit or delete more than 30% of bullets across five samples, the drafting pass is not sellable.

Risk 4The 60-message outreach list returns under a 5% reply rate, leaving too few conversations to close anything.

Mitigation

Test three message openers in parallel and lead with the free sample artifact rather than a product pitch.

Validation experiment

Send 20 messages per opener variant and compare reply rates by day three.

Kill criteria

If all three variants return under 5% replies after 60 total sends, change channel before writing more code.

Risk 5Free sample delivery becomes a manual service bottleneck that caps throughput well below the projection.

Mitigation

Cap samples at what one person can deliver daily and cut time-to-first-PDF under five minutes with the forward-in path.

Validation experiment

Time three consecutive sample deliveries end to end and record each step.

Kill criteria

If one sample takes more than 30 minutes of founder time, cut the sample offer to pre-qualified owners only.

Risk 6A buyer churns after one month once the renewal pressure passes, making revenue lumpy.

Mitigation

Add a scheduled monthly run date and email owners on the 1st with a ready recap so the product becomes a monthly habit.

Validation experiment

Track login after the first delivered recap across every buyer in week three and four.

Kill criteria

If fewer than half of buyers return for a second recap, the monthly plan is mispriced or mispositioned.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Scaffold the Next.js app on Vercel with Supabase auth.
  • Register the domain and point it at the deployment.

Output: A deployed skeleton behind a real domain.

Hours 3-4

  • Create the workspaces, clients, source_items and bullets tables.
  • Configure Google OAuth in Testing mode and add your own account as a test user.

Output: Working schema and a successful read-only Gmail token.

Hours 5-6

  • Build 25 rows of the agency list with owner name, handle, agency type and one public client mention.
  • Write the 60-word sample offer message.

Output: A 25-row prospect sheet and a tested message variant.

Hours 7-9

  • Write the month extraction query against your own mailbox.
  • Print candidate work items with dates and source message IDs.

Output: A raw extraction output you can inspect by eye.

Hours 10-12

  • Send the first five first-touch messages offering a free sample.
  • Log each send with a follow-up date.

Output: Five live conversations and a follow-up calendar.

Complete report

Full 30-day launch report

Read the full generated report

Retainer Proof — 30-Day Solo Founder Report

JEV scored this concept 63.5/100 (band C). Speed to first revenue is the strongest sub-score at 7.71; operational simplicity is the weakest at 4.03. This plan exploits the first and caps the second: the buyer has a monthly deadline and a card in hand, and every human step is limited to what one person can deliver in a day.

1. Product opportunity and positioning

A 2-10 person agency living on retainers has one recurring, high-leverage document: the monthly recap showing what was delivered. It is also the one most often skipped, because producing it means an owner scrolling a month of sent mail per client — an hour each, or nothing. Nothing lands harder at renewal than a client asking what they are paying for.

Retainer Proof builds that document out of work the team already did. Connect Gmail read-only (or forward sent mail to a private address), map a client to an email domain or Gmail label, pick a month, and the engine extracts deliverables, review rounds, meetings and shipped fixes, each carrying a link back to its source message. An LLM drafts four to eight client-ready bullets in the agency's tone; the owner edits and approves item by item; the product renders a branded PDF the owner sends from their own address.

The positioning is deliberately narrow. This is not an email assistant, not a time tracker, not a client portal, not a project-management integration. It does not filter, label, mute or summarize an inbox. It replaces a blank page with a review screen, and it replaces unsourced AI claims with traceable ones. The buyer is the owner, paying by card, with no procurement and no team rollout. The realistic alternatives are a manual evening, a skipped month, or a chat prompt that invents numbers — the source trail plus mandatory approval is the wedge, and the free sample recap is the sales asset.

2. Smallest sellable MVP

Five things and nothing else: Google sign-in with a read-only Gmail connection in Testing mode; a client mapper by domain or label; a month extraction that produces de-duplicated work items with source message IDs; an LLM drafting pass plus a review screen with edit, delete, merge, reorder and per-bullet regenerate; and an HTML-to-PDF renderer with logo and colors, gated by Stripe Checkout. A forward-in fallback address covers the case where OAuth friction stalls a prospect. If an owner cannot go from connect to finished PDF in under ten minutes, the MVP is not done.

3. Technical implementation plan

One Next.js app on Vercel, Supabase Postgres for workspaces, client mappings, source items and approved bullets, Google Identity plus the Gmail API for the primary path, Cloudflare Email Workers for the forward-in address, an LLM API for drafting, a headless PDF renderer, and Stripe Checkout with the Customer Portal. Build order: schema, OAuth, extraction, drafting, review, PDF, billing, fallback. The one thing most likely to break is extraction quality — Gmail threading and calendar dedupe will produce duplicate or empty items for messy clients, so build a manual add-item escape hatch on day three rather than day twenty. A purge job deletes stored source message bodies after render; that single feature answers the privacy objection in every sales thread.

4. Pricing and monetization

Two prices, both under the owner's approval threshold. A $49 one-time Single Recap removes the commitment objection and converts a hesitant sample conversation into paid proof; the $99 monthly Agency plan is the real product, covering up to ten mapped clients, unlimited recap PDFs, the review screen and a branded template. Expected revenue per paying buyer is $99/month, with the one-time tier as an entry ramp that should convert to monthly after the first delivered PDF. Upsell path: more mapped clients, additional brands, and a second monthly run date per workspace.

5. First-customer acquisition

One channel: hand-personalized direct messages to 60 boutique agency owners whose public profiles mention retainers. The opener offers a finished artifact, not a demo — send one client's name and get back a branded recap of last month's work, free, no signup. Delivery within 24 hours via a five-minute Gmail connection or five forwarded emails. The close is a single sentence with a Stripe link. Follow up on day three and day seven with a forty-second recording of the review screen, ask every buyer for one introduction, and publish one anonymized teardown publicly to catch inbound. Week-one target: 60 names, 35 messages, 4 completed samples.

6. 30-day execution roadmap

Days 1-4 are build: schema, OAuth, extraction, drafting, review screen, PDF, Stripe. Day 5 is MVP live and the first real sample delivered, which is the hard deadline. Days 6-12 are outreach and concierge delivery against a 60-name list, ending with the first paid agency on day 12. Days 13-21 shift from selling to proving: full client sets for buyer one, onboarding cut under five minutes, a scheduled monthly run date, a published data-handling note, and a second and third close. Days 22-30 are the last outreach wave, month-end closes, a verified revenue and cost reconciliation against Stripe, and a written go-or-narrow decision using pre-committed kill criteria. Daily cap: no more samples than one person can deliver, because sample delivery is the throughput ceiling.

7. Revenue and profit scenarios

Projections only, not verified revenue. Conservative: 4 paying agencies at $99, $396 revenue, $45 costs, $351 profit. Base: 11 agencies, $1,089 revenue, $70 costs, $1,019 profit. Upside: 18 agencies, $1,782 revenue, $130 costs, $1,652 profit. Costs are Stripe fees, LLM usage, PDF/email tooling and a domain; hosting stays on free tiers. The realistic 30-day outcome is roughly $1K-$2K, not $100K. A $100K path requires around 70 agencies retained for twelve months plus per-client upsells, and belongs to a later stage.

8. Main risks and validation experiments

Google restricted-scope verification cannot finish inside 30 days, so the product runs in Testing mode with manually added users plus the forward-in fallback; measure how many prospects abandon at the connection step. Owners may decide a chat prompt or a manual evening is good enough, so ask ten of them what they did last month and how long it took before writing more code. LLM bullets could misstate delivered work, which is reputationally fatal in a client-facing document; mandatory approval and inline source links are the control, and an edit rate above 30% means the drafting pass is not ready. A sub-5% reply rate across three message variants means the channel is wrong, not the product, and the response is to change channel rather than send more of the same.

9. First 24 hours

Hours 1-2: scaffold the app and register the domain. Hours 3-4: create the schema and configure Google OAuth in Testing mode. Hours 5-6: build 25 rows of the agency list and write the 60-word offer. Hours 7-9: write the month extraction query against your own mailbox and inspect the output. Hours 10-12: send the first five messages and log follow-up dates. By end of day one there must be a deployed skeleton, working Gmail read-only access, 25 named prospects and five messages out.

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 →