Cleanup Scope Report
Upload a prospect's QuickBooks exports and get a white-labeled PDF that lists every books issue, its dollar exposure, estimated cleanup hours and a defensible fixed fee — in under five 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.
Owner/principal of a 1-10 person bookkeeping or fractional-CFO firm in the US/Canada managing 20-80 QuickBooks Online client files, at the moment they must send a cleanup scope and fixed fee within 48 hours.
Operational simplicity 5.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 11; 13 sales at $79 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.0/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
9 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Owner/principal of a 1-10 person bookkeeping or fractional-CFO firm in the US/Canada managing 20-80 QuickBooks Online client files, at the moment they must send a cleanup scope and fixed fee within 48 hours.
Why now
Year-end and January cleanup quoting forces every firm into a 48-hour scoping window, and file-upload-only delivery removes the QuickBooks OAuth and Intuit app review that would push launch past the contest.
Problem
Quoting a cleanup honestly requires 2-4 senior hours skimming twelve months of an unfamiliar QuickBooks file; most firms skip it, underquote, absorb the overrun, or send a vague letter that becomes a dispute.
Solution
Upload seven standard QuickBooks exports; a deterministic rule engine runs 40-60 checks, values each finding in dollars, maps it to cleanup hours and a fixed-fee band, writes a grounded paragraph per finding, and renders a white-labeled PDF with an evidence appendix, shareable link and client email draft.
1. Product opportunity and positioning
The buying moment is a deadline, not an abstraction. A bookkeeping firm's principal signs a new client in January and owes them a cleanup scope and a fixed fee within 48 hours. Producing that honestly means skimming twelve months of an unfamiliar QuickBooks file for uncategorized transactions, duplicate vendors, unreconciled accounts, negative A/P, opening-balance-equity residue and stale A/R — two to four senior hours per prospect. Most firms skip it, and one of three things happens: they underquote and eat the overrun, they quote high and lose the deal, or they send a vague letter that becomes an argument in month three.
The product turns seven standard exports — Trial Balance, Chart of Accounts, Transaction List by Date, A/R Aging, A/P Aging, Balance Sheet, P&L — into a 6-8 page white-labeled PDF: severity heatmap, dollar exposure per finding, cleanup-hour ranges, a fixed-fee band computed from the firm's own hourly rate, an evidence appendix citing the exact flagged transactions, plus a shareable link and a client email draft.
It is a yes because it is a pre-sale cost of winning revenue, not a new software line item, so it never competes with the firm's existing stack. No QuickBooks OAuth, no Intuit app review, no migration, no ledger writes — the firm uploads files it already downloaded. It demos in 45 seconds on a synthetic file, and the buyer is a named individual in a public directory.
Alternatives are weak in the specific way that matters: an Excel checklist still needs the same judgment; a chat model cannot be trusted with a client file and leaves no evidence trail; incumbent suites sell bookkeeping work, not the diagnosis that precedes it. The moat is narrow and real — the priced scope plus the appendix converts "your books look messy" into a number the client accepts in the room.
JEV scores this concept 6.52 weighted (65.2/100, band B). Its strongest criteria are the two that decide a 30-day contest — speed to first revenue and reachable customers, both 8.02. Its flagged weakness is operational simplicity, 4.97. Treat that as the build constraint: stateless rendering, managed services, delete-on-render, no human review step, no custom infrastructure.
Smallest sellable MVP
One branded PDF, generated from uploaded QuickBooks exports in under five minutes, that a firm can forward to its own client without editing.
Must-have features
- Parse Trial Balance, Chart of Accounts, Transaction List by Date, A/R Aging, A/P Aging, Balance Sheet and P&L from xlsx/csv
- Manual column-mapping fallback that saves a mapping per export type
- Deterministic rule engine with 40-60 named checks carrying severity and dollar valuation
- Hour-and-fee estimator producing a fixed-fee band from the firm's configured hourly rate
- One grounded LLM paragraph per computed finding, restricted to engine fields
- White-label PDF renderer with logo, colors, footer, scope/fee page and evidence appendix
- Shareable report link and a copy-ready client email draft
- Stripe Checkout plus a minimal account page with credits and past reports
Explicitly out of scope
- QuickBooks OAuth, live sync or any write-back to a ledger
- Journal entries, reclassification or reconciliation automation
- Ongoing bookkeeping workflow, close checklists or client document requests
- Dashboards, KPI tracking or multi-month monitoring
- Team seats, roles, permissions or approval flows
- Slack bot, chat assistant or receipt chasing
- Any human review step inside the delivery pipeline
Demo flow (what the buyer sees)
- Founder uploads a deliberately messy synthetic QuickBooks export bundle
- Column mapping auto-detects and shows a confirm screen
- Rule engine runs and displays 40+ findings with dollar exposure
- Fee estimator produces cleanup hours and a fixed-fee band from a sample $150/hr rate
- Founder types a firm name, uploads a logo, picks a color
- PDF renders with heatmap, scope page and evidence appendix
- Shareable link and client email draft appear on screen
Technical implementation plan
Stack
Architecture
Browser parses the uploaded workbooks with SheetJS and posts normalized JSON to one serverless route. That route runs the deterministic rule engine, values each finding, makes one model call per finding for its narrative paragraph, renders HTML to PDF, pushes the file to storage, deletes the source uploads, and returns a signed link plus the email draft. Postgres holds only the derived report, findings and firm branding config so a firm can re-download without re-uploading.
Build steps
- Scaffold Next.js, Vercel, Supabase and Stripe test keys on day 1
- Build the SheetJS readers and per-export-type column mapping with saved mappings
- Implement the check runner interface: id, severity, dollar value, sample transactions
- Write checks 1-25 (uncategorized, duplicates, reconciliation, negative A/P, OBE residue)
- Write checks 26-45 (stale A/R, TB-vs-aging mismatch, wrong signs, missing class)
- Map each check to an hour range and build the fixed-fee band from configured rate
- Add the fenced LLM call: one paragraph per finding, engine fields only
- Render branded HTML and convert to PDF; add scope page and evidence appendix
- Add Stripe Checkout, credits, account page and Resend delivery
- Add delete-on-render, parse-failure logging with header rows, and signed shareable links
AI components
- One grounded narrative paragraph per computed finding
- Scope summary paragraph assembled from finding categories and hour totals
- Client email draft referencing the fee band and top three findings
- Suggested column-header mapping when auto-detection fails
Pricing and monetization
Single Report
Entry offerFor Solo bookkeeper testing it on one prospect file
- One white-labeled PDF report
- Evidence appendix with flagged transactions
- Cleanup hours and fixed-fee estimate
- Shareable link and client email draft
Firm
For 1-10 person bookkeeping or fractional-CFO firm onboarding multiple clients
- Unlimited reports
- Firm logo, colors and footer
- Saved report history and re-download
- Configurable hourly rate and fee bands
Firm Annual
For Firms that know they will scope 20+ cleanups this year
- 12 months of unlimited reports
- White-label branding
- Priority on new checks
Model: Per-report entry price plus a flat monthly firm subscription and an annual prepay, all sold self-serve through Stripe Checkout with no sales call.
First revenue offer: Send any client's QuickBooks export bundle and get a branded Cleanup Scope Report with hours and fee estimate back within 24 hours, free, no login, no access to your QBO file — then $199/month for unlimited reports.
Expected ACV: $199
Upsell path: Single-report buyers convert to the $199/month Firm plan after their second prospect; monthly firms move to the $1,990 annual after they have scoped roughly eight cleanups, which trades two months of revenue for a full-year commitment.
First-customer acquisition
Manual cold outreach to named owners of 1-10 person bookkeeping and fractional-CFO firms sourced from the public QuickBooks ProAdvisor directory and LinkedIn.
Where to find them
- Public QuickBooks ProAdvisor directory, filtered to US/Canada firms
- LinkedIn search: 'bookkeeping' + Owner/Principal, 1-10 employees
- r/Bookkeeping threads asking how to quote a cleanup
- QuickBooks ProAdvisor Facebook groups
- Fractional CFO communities and Slack groups where scoping gets discussed
- Referrals from firms that received a free report
Exact outreach motions
- Send a 90-word message with a 45-second Loom of a synthetic file becoming a branded PDF
- Offer a free branded report on one client file within 24 hours, no login required
- Follow up on day 3 with 'did the file go through okay?'
- Follow up on day 7 with 'what did the client say when you sent it?'
- Post a redacted sample report as a value reply in threads asking how to price a cleanup
- Ask every recipient for one intro to another firm owner after delivery
Message template
Hi {first_name} — you scope cleanups at {firm}. I built a tool that takes the QuickBooks exports you already download and returns a branded PDF with every issue, its dollar exposure, cleanup hours and a fixed fee you can defend. Here's a 45-second demo: {loom}. Send me any client's export bundle and I'll send the report back within 24 hours, free — no login, no access to your QBO. Worth one file?30-day execution roadmap
Week 1 · Build & validate · 7 days
Ship the skeleton and start the list
- Create the Next.js app, Vercel project, Supabase database and storage bucket.
- Connect Stripe test keys and a $79 test product.
- Build the 60-firm target list from the ProAdvisor directory and LinkedIn.
Deliverable: Deployed skeleton on a custom domain plus a 60-row outreach sheet.
Turn exports into normalized JSON
- Implement SheetJS readers for xlsx and csv.
- Build the manual column-mapping screen with saved mappings per export type.
- Seed the Chart of Accounts parser and account-type classifier.
Deliverable: Seven export types parsed into a normalized transaction and balance model.
First 25 named checks
- Write the check runner with severity and dollar valuation per check.
- Implement uncategorized balance, duplicate vendor, duplicate transaction and unreconciled-account checks.
- Add opening-balance-equity residue and negative A/P checks.
Deliverable: 25 checks producing structured findings with dollar exposure.
Reach 45 checks and estimate hours
- Add stale A/R, TB-vs-aging mismatch, wrong-sign and missing-class checks.
- Map each check to a cleanup-hour range and build the fixed-fee band from a configured rate.
- Add the fenced LLM narrative call, one paragraph per finding.
Deliverable: 45 deterministic checks plus a working hours and fee estimator.
PDF and payment
- Render the branded HTML report to PDF with logo, colors and footer.
- Add the scope and fee page, evidence appendix, shareable link and email draft.
- Wire Stripe Checkout and a minimal account page with credits.
Deliverable: End-to-end MVP: upload to paid, branded PDF.
Make it showable
- Hand-build one deliberately messy synthetic QuickBooks bundle.
- Run it end to end and fix the three worst rendering defects.
- Record a 45-second Loom and publish a sample report page.
Deliverable: Public sample report page and demo video.
First 25 messages
- Send the offer to 25 firms with the Loom link.
- Log every send, reply and file received in one sheet.
Deliverable: 25 outreach messages sent with a tracked status column.
Week 2 · Launch & first sale · 7 days
First real files
- Ingest the first inbound files and log every parse failure with its header row.
- Deliver the first two free branded reports within 24 hours.
- Fix the top two parser breakages.
Deliverable: Two branded reports delivered and one parser patch shipped.
Second batch and community
- Send 25 more messages to new firms.
- Post a value reply with a redacted sample in two r/Bookkeeping threads.
Deliverable: 50 cumulative messages sent and two community replies posted.
Volume of free reports
- Deliver three more free reports.
- Ask each recipient 'what did the client say when you sent it?'
- Put a Stripe link in the footer of every delivered PDF.
Deliverable: Five cumulative free reports delivered with Stripe links.
Convert a warm recipient
- Send a direct checkout link to the three most engaged recipients.
- Offer the $79 single report to anyone unwilling to commit monthly.
Deliverable: First paid invoice inside the contest window.
Firm branding
- Ship logo upload, color picker and footer config.
- Ship the hourly-rate and fee-band settings page.
Deliverable: Firms can generate reports in their own brand.
Non-responders
- Follow up on day 7 with every non-responder.
- Ask each delivered firm for one intro to another owner.
Deliverable: Full follow-up wave sent plus referral requests logged.
Which message produced files
- Compare replies-to-files by message variant and rewrite the loser.
- Ship ten more checks based on real-file gaps.
Deliverable: One rewritten message variant and 55 checks in production.
Week 3 · Repeat & systematize · 7 days
ProAdvisor groups
- Answer five threads in QuickBooks ProAdvisor groups with a redacted sample.
- Add a no-retention, delete-on-render policy page and link it everywhere.
Deliverable: Five group replies posted and an indexed data policy page.
Third batch
- Send 30 messages to a new segment of fractional CFOs.
- Track time-to-file for each segment.
Deliverable: 80 cumulative messages with segment-level response rates.
Annual plan
- Ship the $1,990 annual checkout.
- Add a credits page showing remaining reports and re-download links.
Deliverable: Three live price points and a working credits page.
Reliability
- Deliver all pending free reports within 24 hours each.
- Ask two recent recipients for a one-line quote usable on the site.
Deliverable: Zero reports older than 24 hours; quote requests out.
Public writing
- Post the cleanup-quoting math publicly on LinkedIn and X.
- Link the sample report and the free-report offer in the post.
Deliverable: Two public posts published with sample report links.
Warm pipeline
- Follow up on every delivered report with the client-response question.
- Send checkout links to anyone who replied positively.
Deliverable: Every delivered firm contacted at least twice.
Parse coverage
- Fix the top three remaining parse failures.
- Cut median render time and report generation errors.
Deliverable: Parser handling every file received so far without manual mapping.
Week 4 · Scale what works · 7 days
Fourth batch
- Send 40 messages, prioritizing firms with visible January onboarding activity.
- Re-test the rewritten message variant against the original.
Deliverable: 120 cumulative messages with a winning variant identified.
Warm calls
- Offer a 10-minute call to every warm reply.
- Close monthly plans on the call with a Stripe link sent live.
Deliverable: Three or more live conversations booked.
Proof of use
- Add view and download counts to the shareable report link.
- Show that count on the account page as evidence the report was sent.
Deliverable: Report-view analytics visible to the firm.
Second push
- Answer five more threads across Reddit and Facebook groups.
- Attach one redacted sample report per reply.
Deliverable: Ten cumulative community replies with samples.
Monthly to annual
- Offer annual prepay to every active monthly firm.
- Add a one-click upgrade path in the account page.
Deliverable: Annual offers sent to all monthly accounts.
Nothing pending breaks
- Clear the bug list and reduce report latency.
- Re-run every delivered file through the current engine to confirm consistency.
Deliverable: Clean bug list and a consistent re-render across past reports.
Final push
- Send the last 40 messages of the month.
- Ask every paying firm for one referral by name.
Deliverable: 300 cumulative messages and referral asks logged.
Days 29-30 · Consolidate · 2 days
Money in
- Reconcile Stripe charges against the TrustMRR-connected account.
- Issue any refunds voluntarily and record chargeback exposure as zero where true.
Deliverable: A reconciled payment ledger for the contest window.
Document the motion
- Write the exact message, list source and delivery steps that produced revenue.
- Decide the post-contest price and the first feature to build in January.
Deliverable: A one-page repeatable acquisition playbook.
Revenue and profit scenarios
How the numbers are defined
Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.
Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).
The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.
Stated assumptions
- Conservative/Base/Upside: blended ARPU mixes $79 single reports with $199 monthly Firm plans taken in the window; only the first month of any subscription counts.
- Conservative/Base/Upside: ad_spend_usd is 0 in all cases because acquisition is manual outreach and organic community posts only.
- Conservative/Base/Upside: payment processing assumed at roughly 4-4.5% blended on Stripe Checkout including international cards.
- Conservative/Base/Upside: refunds stay near zero because a free report precedes any payment; the upside case carries one $79 refund.
- Conservative/Base/Upside: operating_costs_usd covers domain, Vercel, Supabase, storage, email and inference at under $1 per report plus a fixed monthly floor.
- Conservative: 5 paying accounts from 150 messages.
- Base: 14 paying accounts from roughly 250 messages, implying about 8% of messages produce a file and 10-15% of files convert.
- Upside: 30 paying accounts at a $199 blended ARPU, which is the concept's own target and the least likely number to hit.
Conservative
5 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $28
- Paid marketing
- $0
- Hackathon profit
- $672
- Operating costs
- $45
- Business profit
- $627
Base case
14 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $104
- Paid marketing
- $0
- Hackathon profit
- $2,206
- Operating costs
- $85
- Business profit
- $2,121
Optimistic
30 customers- Refunds
- $79
- Chargebacks
- $0
- Payment fees
- $269
- Paid marketing
- $0
- Hackathon profit
- $5,622
- Operating costs
- $160
- Business profit
- $5,462
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $1,106
- Payment fees (3.9%)
- $43
- Paid marketing
- $0
- Hackathon profit
- $1,063
- Business profit
- $978
Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.
All scenarios are projections built from the stated assumptions. They are not verified revenue, existing customers or real traction.
Main risks and validation experiments
Risk 1QuickBooks export formats vary by version and region, so the parser fails on a real file at the delivery moment.
Manual column-mapping fallback built on day 2, plus parse-failure logging that records the header row of every failed file.
Ingest five real files from five different firms by day 9 and count how many parse without manual mapping.
If fewer than four of five parse automatically and the fallback takes more than five minutes, the 24-hour delivery promise is false and the concept needs rescoping.
Risk 2Firms take the free branded report and never pay, turning the offer into unpaid consulting.
Cap free reports at twelve, require one question in exchange, and put a Stripe link in every PDF footer.
Track free reports delivered versus priced conversations opened within seven days of delivery.
If ten free reports produce zero priced conversations, the offer is a service rather than a product and must be repackaged.
Risk 3Buyers treat it as a one-off and never subscribe, so revenue does not repeat.
Offer the $79 single report deliberately and upsell to monthly after the second prospect; add credits and saved history to create switching cost.
Measure the share of early buyers choosing $79 versus $199/month and count upgrades within fourteen days.
If two-thirds take the single report and none upgrade in two weeks, reprice around a per-report credit pack instead of a monthly plan.
Risk 4The narrative layer invents a finding, destroying trust with the first firm.
Fence the model to computed engine fields only, with no open-ended discovery prompt, and review every generated paragraph manually in the first twenty reports.
Diff each narrative paragraph against its source finding on the first twenty reports and log any ungrounded claim.
Any repeated invented claim after one prompt fix means the narrative layer ships off by default and the PDF goes out with templated text only.
Risk 5Firms refuse to send client financial exports to an unknown solo founder.
Publish a one-page no-retention, delete-on-render policy before day 7, state it in the outreach message, and never request QBO login access.
Track how many of the first 50 messages receive a file versus a question about data handling.
If data-handling objections exceed half of all replies by day 15, add a self-hosted local parse option or abandon the upload model.
Hour-by-hour: the first 24 hours
Hours 0-2
- Register the domain and create Vercel and Supabase projects.
- Push the Next.js skeleton and wire Stripe test keys.
Output: Deployed skeleton reachable on a custom domain.
Hours 2-5
- Build the 60-firm list from the ProAdvisor directory and LinkedIn: owner name, firm, city, email.
Output: A 60-row outreach sheet with named owners and firm sizes.
Hours 5-8
- Hand-build one deliberately messy synthetic QuickBooks export bundle covering all seven report types.
Output: A synthetic messy dataset that produces at least eight material findings.
Hours 8-11
- Build SheetJS readers and the manual column-mapping screen.
Output: Working upload-to-normalized-JSON path with a mapping fallback.
Hours 11-14
- Implement ten rule checks end to end and a plain HTML report page listing findings with dollar exposure.
Output: A readable HTML report generated from the synthetic file.
Hours 14-18
- Write the outreach message and the Loom script, then record a rough 45-second cut against the HTML report.
Output: A demo Loom and a final outreach message.
Hours 18-24
- Send the first ten messages to the warmest names on the list.
- Log every send in the outreach sheet.
Output: Ten live outreach messages with replies tracked.
Full 30-day launch report
Read the full generated report
Cleanup Scope Report — 30-Day Operator Brief
1. Product opportunity and positioning
The buying moment is a deadline, not an abstraction. A bookkeeping firm's principal signs a new client in January and owes them a cleanup scope and a fixed fee within 48 hours. Producing that honestly means skimming twelve months of an unfamiliar QuickBooks file for uncategorized transactions, duplicate vendors, unreconciled accounts, negative A/P, opening-balance-equity residue and stale A/R — two to four senior hours per prospect. Most firms skip it, and one of three things happens: they underquote and eat the overrun, they quote high and lose the deal, or they send a vague letter that becomes an argument in month three.
The product turns seven standard exports — Trial Balance, Chart of Accounts, Transaction List by Date, A/R Aging, A/P Aging, Balance Sheet, P&L — into a 6-8 page white-labeled PDF: severity heatmap, dollar exposure per finding, cleanup-hour ranges, a fixed-fee band computed from the firm's own hourly rate, an evidence appendix citing the exact flagged transactions, plus a shareable link and a client email draft.
It is a yes because it is a pre-sale cost of winning revenue, not a new software line item, so it never competes with the firm's existing stack. No QuickBooks OAuth, no Intuit app review, no migration, no ledger writes — the firm uploads files it already downloaded. It demos in 45 seconds on a synthetic file, and the buyer is a named individual in a public directory.
Alternatives are weak in the way that matters: an Excel checklist still needs the same judgment; a chat model cannot be trusted with a client file and leaves no evidence trail; incumbent suites sell bookkeeping work, not the diagnosis that precedes it. The moat is narrow and real — the priced scope plus the appendix converts "your books look messy" into a number the client accepts.
JEV scores this 6.52 weighted (65.2/100, band B). Its strongest criteria are the two that decide a 30-day contest — speed to first revenue and reachable customers, both 8.02. Its flagged weakness is operational simplicity at 4.97. Treat that as the build constraint: stateless rendering, managed services, delete-on-render, no human review step, no custom infrastructure.
2. Smallest sellable MVP
Ship the whole loop, not a feature. The sellable unit is one PDF a firm can put its own logo on and forward to its own client without editing. Anything that does not move that PDF out the door in under five minutes is cut.
Must ship: parsing for the seven exports with a manual mapping fallback; 40-60 named deterministic checks; a severity-weighted hour and fee estimator; one grounded paragraph per finding; the white-label PDF with scope page and evidence appendix; Stripe Checkout; a minimal account page. Cut: OAuth, live sync, write-back, reconciliation automation, dashboards, seats, Slack, and any human review inside delivery.
Five days is deliberate. Day 1 skeleton and domain, days 2-4 parser and engine, day 5 renderer and checkout. Forty checks shipped beats fifty-five planned.
3. Technical implementation plan
Next.js on Vercel, one Postgres database, one storage bucket, one model call per finding. Upload parses in the browser with SheetJS and posts normalized JSON to a single serverless route that runs the engine, values findings, calls the model once per finding, renders HTML to PDF, stores the file and returns a signed link. Source files are deleted immediately after render.
The model is fenced. It receives only computed fields — account, check name, dollar amount, count, sample transactions — and returns one plain-English paragraph for a non-accountant. Never an open-ended discovery prompt. A hallucinated finding destroys the trust the product runs on.
The hardest risk is export variance: QuickBooks Online changes header rows, appends footer metadata and renames columns by region. Build the mapping fallback on day 2, not day 12, and log every parse failure with its header row so the first ten real files compound into a tolerant parser.
4. Pricing and monetization
Three prices, one job each. $79 single report removes the "is this worth trying" objection for a solo bookkeeper with one messy prospect. $199/month Firm is the product: unlimited reports, firm branding, saved history, configurable rate and fee bands. $1,990 annual is cash and commitment from firms already scoping twenty-plus cleanups a year.
Economics are clean because the report is the deliverable: inference and rendering land under $1 per report, so every sale covers its own cost — required, since selling below delivery cost disqualifies. There is no free tier; the free report is outreach, capped near twelve files and only for firms on the named list. Do not discount the monthly plan to win a logo. Discount the single report to zero only as the outreach report.
5. First-customer acquisition
One channel: manual cold outreach to named owners of 1-10 person firms from the public QuickBooks ProAdvisor directory and LinkedIn filters, 60 firms on day 1 and 300 by day 28. Zero ad spend.
The offer: send any client's QuickBooks export bundle, get a branded Cleanup Scope Report with hours and fee estimate back within 24 hours, free, no login, no access to the QBO file. Lead with a 45-second Loom of a synthetic messy file going in and a finished branded PDF coming out.
Then do the work. Deliver the first twelve personally, ask each recipient one question — "what did the client say when you sent it?" — and put a Stripe link in every PDF footer. Follow up on day 3 and day 7. Post the same offer with one redacted sample in r/Bookkeeping and ProAdvisor threads about quoting cleanups.
Week-one target: 60 firms listed, 50 messages sent, 5 free reports delivered.
6. 30-day execution roadmap
Days 1-5 build, with a hard MVP gate on day 5: skeleton, parser, engine, estimator, PDF, checkout. Days 6-11 are the trust sprint: synthetic file, Loom, sample report page, first 50 messages, first five free reports delivered, first paid conversion targeted for day 11. Days 12-21 add volume and fit: firm branding, rate configuration, outreach batches three and four, community threads, annual checkout, and a retro on which message produced files rather than polite replies. Days 22-30 convert and close: follow-ups on every delivered report, referrals, annual upsells, triage of the top parse failures, and a day-29 reconciliation of Stripe against the TrustMRR-connected account before the window shuts.
Two rules: no day after day 6 passes without ten outreach messages, and no feature ships unless it sits in the path of a report being delivered or paid for.
7. Revenue and profit scenarios
All figures are projections from stated assumptions, not verified revenue.
Conservative — 5 accounts at a blended $140: $700 gross, no refunds, no chargebacks, roughly 4% processing, no ad spend, about $45 operating. Base — 14 accounts at $165 blended: $2,310 gross, about $104 processing, about $85 operating. Upside — 30 accounts at $199 blended: $5,970 gross, one $79 refund, about $269 processing, about $160 operating.
Hackathon profit — gross minus refunds, chargebacks, processing and paid marketing, the figure the contest ranks — lands near $2,200 in the base case, because ad spend is zero. Business profit subtracts operating costs and lands near $2,100. The upside needs roughly 8% of 300 messages to produce a live file and 10-15% of those files to convert; that is the assumption most likely to break, which is why the base case is the plan and the upside is a ceiling.
8. Risks and validation experiments
Export variance breaks the parser. Test five files from five firms by day 9; if fewer than four parse without manual mapping, the delivery promise is false and the fallback becomes the priority.
Free reports become unpaid consulting. Cap at twelve and require one question in exchange. If ten free reports produce zero priced conversations, the offer is a service, not a product.
One-off usage instead of subscription. If two-thirds of early buyers take the $79 report and none upgrade within two weeks, reprice around a per-report credit pack rather than pretending the monthly plan works.
The narrative invents a finding. Review the first twenty reports against engine output; any repeated invented claim halts sending until the prompt is fixed.
Data-handling objection kills deals. Publish a no-retention, delete-on-render page before day 7 and lead with it. Kill criteria: if by day 20 fewer than eight firms have sent a file, or no report has produced a paid invoice, stop building and re-cut the offer around the $79 report delivered done-for-you.
9. First 24-hour action plan
Hours 0-2 — register the domain, create Vercel and Supabase projects, push the skeleton, wire Stripe test keys.
Hours 2-5 — build the 60-firm list: owner, firm, city, email, from the ProAdvisor directory and LinkedIn.
Hours 5-8 — hand-build one deliberately messy synthetic export bundle so there is something to demo.
Hours 8-11 — SheetJS parser skeleton plus the manual column-mapping screen.
Hours 11-14 — ten checks end to end and a plain HTML report page.
Hours 14-18 — write the outreach message and Loom script, record a rough 45-second cut.
Hours 18-24 — send the first ten messages to the warmest names. Ten real conversations beat a prettier PDF.
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 →Zéro Écart
A fixed-price catch-up service for French small businesses that are months behind on bookkeeping: upload a bank export plus a pile of receipts, and receive a finished, importable accounting journal, renamed receipts, and an itemised list of exactly what could not be matched.
Bridge Brief
Turns a founder's own LinkedIn connections export into a ranked warm-intro map against a specific target list, with a ready-to-send ask for every path.
AnswerProof Audit Kit
A white-label audit generator that lets small SEO and content agencies produce a client-ready PDF showing how ChatGPT, Perplexity, and Gemini describe a client's brand versus its competitors, complete with a 30-day fix list.