StaleDoc Audit
StaleDoc Audit scans a company's existing Google Drive in about ten minutes and delivers a ranked PDF report of outdated, duplicated and orphaned documents, so an ops lead knows exactly which pages to fix or kill first.
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.
Head of Operations, Chief of Staff or People Ops lead at a 20-200 person remote-first software company in the US, UK or Canada, triggered by a new-hire cohort, a Series A raise, or SOC 2 / ISO audit prep.
Monetization potential 4.1/10
Tie the price to a measurable money or time outcome and add a recurring or repeat-purchase path instead of a single low-value charge.
Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 10; 6 sales at $199 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
10 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Head of Operations, Chief of Staff or People Ops lead at a 20-200 person remote-first software company in the US, UK or Canada, triggered by a new-hire cohort, a Series A raise, or SOC 2 / ISO audit prep.
Why now
Hiring cohorts, funding rounds and audit kickoffs create a dated, already-budgeted moment where one named person must answer which documents are current, and no existing tool answers it without a migration project.
Problem
The shared drive holds hundreds of documents written by people who have left, several near-identical versions of the same policy, no owner labels, and no signal about which page is safe to trust.
Solution
Read-only Drive connection or ZIP upload, up to five top-level folders, and a Documentation Debt Report PDF with a 0-100 Rot Score, 25 ranked high-risk documents, duplicate clusters with a recommended survivor, an orphan list, per-owner nudge messages, and a CSV fix list.
The gap StaleDoc Audit fills
The buyer is a Head of Operations, Chief of Staff or People Ops lead at a 20-200 person remote-first software company in the US, UK or Canada. The trigger is dated and specific: a new-hire cohort starts, a Series A closes, or SOC 2 / ISO audit preparation kicks off. At that moment one named person must answer a question nobody has priced: which of these several hundred documents can the team actually trust?
The honest answer today is to read them all, or to guess. Notion, Confluence, Slite and Guru all solve this by asking the company to adopt a new home and maintain it. That is a migration project with ownership assignment, team buy-in and a monthly seat bill, and it does not tell the ops lead anything useful about the drive that already exists this quarter.
What is actually being sold
A diagnosis, not a platform. The buyer connects Google Drive with read-only access, picks up to five top-level folders, and receives a Documentation Debt Report PDF containing:
- a 0-100 Rot Score for the drive;
- the 25 highest-risk documents ranked, each with owner, last-edit date and a one-line reason;
- clusters of near-duplicate titles with the recommended survivor;
- orphaned documents nobody links to;
- copy-ready nudge messages addressed to each owner;
- a CSV fix list, plus a per-owner summary page added in week four.
The free partial scan returns the Rot Score, the document count and three sample rows. The full artifact unlocks at 199 USD. A 399 USD Consultant Pack covers three client drives for fractional COOs and ops consultants.
Why this wedge and not the platform
The deliverable is a document, so it is sellable before it is polished. The buyer is a single person who can spend 199 USD without procurement. There is no migration, no seat count, no integration with the rest of the stack, and no ongoing maintenance promise the founder has to staff. Revenue arrives on the same day the value is demonstrated, which is the only shape that fits a 30-day solo window.
Where the concept is weak
The JEV score of 58.1 (band C) is honest about the soft spots: market demand (4.44 normalized) and monetization potential (4.09) are the lowest axes, because a one-time 199 USD charge has no renewal path and documentation hygiene is a nagging pain rather than a burning one. The plan below addresses both without changing the product: the trigger event is used to create urgency in outreach, the Consultant Pack and a 90-day rescan referral create repeat purchase, and every report carries a per-owner summary that makes the value legible to the person who approves budget.
Smallest sellable MVP
A live page where an ops lead connects a Google Drive folder set or uploads a ZIP, sees a Rot Score and three sample rows for free, pays 199 USD via Stripe, and receives a PDF plus CSV naming the 25 documents to fix first.
Must-have features
- Google OAuth read-only Drive connection limited to five top-level folders, capped at 5,000 files
- ZIP-upload fallback that parses an exported folder without any OAuth grant
- Rule-based risk scoring engine weighting folder context, days since last edit, owner account inactivity and missing owner
- Near-duplicate clustering on normalized titles plus first-paragraph similarity, with one recommended survivor per cluster
- Orphan detection for documents with no inbound links in the export body
- AI pass over the top 40 flagged documents producing one reason line and one nudge message each
- React-PDF report renderer with cover, Rot Score gauge, ranked risk table, clusters, orphan list and executive summary, plus CSV export
- Free-scan paywall showing score, count and three rows, unlocked by Stripe Checkout at 199 USD and delivered by email
Explicitly out of scope
- No document editing, rewriting or auto-fixing
- No Slack or Teams bot and no employee Q&A
- No Notion, Confluence or SharePoint connectors
- No scheduled rescans, monitoring or alerting
- No multi-seat roles, SSO, admin console or security review package
- No compliance certification claims
- No free tier beyond the one partial scan
Demo flow (what the buyer sees)
- Buyer opens the landing page and clicks scan a drive
- Buyer grants read-only Drive access or uploads a ZIP export
- Buyer selects up to five top-level folders
- Scan job syncs metadata and computes the Rot Score
- Free screen shows the score, document count and three sample rows
- Buyer pays 199 USD through Stripe Checkout
- Full PDF and CSV render server-side and are emailed within minutes
- Buyer forwards the report and nudge messages to document owners
Technical implementation plan
Stack
Architecture
A scan is a durable record in Postgres. The ingest layer writes metadata rows first (name, owner, last-modified, folder path, sharing, size), so scoring never depends on file bodies. The scoring engine is pure functions over those rows and produces a JSON report payload. One batched Claude call reads only the top 40 flagged documents and returns reason lines and nudge drafts, which are merged into the payload. The renderer turns the payload into a PDF and CSV, uploads both to Supabase Storage, and the Stripe webhook flips the scan to paid and triggers the Resend delivery email. The free screen renders from the same payload with the detail rows stripped.
Build steps
- Scaffold Next.js, deploy to Vercel, attach domain and environment secrets
- Create Supabase tables: scans, files, reports, payments
- Build Google OAuth flow with read-only scopes and a five-folder picker
- Write the metadata sync worker with pagination and a 5,000-file cap
- Build the ZIP parser that reconstructs folder paths and owner fields from an export
- Implement the scoring engine and Rot Score formula as pure functions with unit tests
- Add duplicate clustering and orphan detection over normalized titles and body links
- Add the batched Claude call for the top 40 documents with strict JSON output and a timeout fallback
- Render the PDF and CSV, store both, and gate the paid version behind the payments table
- Wire Stripe Checkout, webhook, and the Resend delivery email; test with a live 1 USD purchase
AI components
- Claude generating one plain-language reason line per flagged document
- Claude drafting a short nudge message addressed to each document owner
- Claude adjudicating duplicate clusters where title similarity alone is ambiguous
Pricing and monetization
Rot Report
Entry offerFor A single ops or people lead auditing one company drive
- Full Documentation Debt Report PDF with Rot Score and 25 ranked documents
- Duplicate clusters with recommended survivor
- Orphan document list
- CSV fix list
- Copy-ready nudge messages per owner
- Per-owner summary page
Consultant Pack
For Fractional COOs and ops consultants auditing several client drives
- Three full Rot Reports for three separate drives
- Client-ready white-labelled cover page
- CSV fix list per drive
- Priority scan queue
Model: One-time fixed-fee diagnostic reports, with a multi-drive pack for consultants.
First revenue offer: A free ten-minute scan of their onboarding or policy folder that returns the Rot Score, the count of documents untouched for over 12 months, and three sample rows, followed by the full report for 199 USD.
Expected ACV: $199
Upsell path: Every buyer is offered a free 90-day rescan in exchange for one referral to another ops lead, and consultants are moved to the 399 USD three-drive pack after their first single report.
First-customer acquisition
Direct cold outreach to Heads of Operations and People Ops leads at 20-200 person remote-first software companies found in the public YC company directory and on LinkedIn.
Where to find them
- Public YC company directory filtered to remote-friendly B2B software
- Company public team pages for the ops or people lead name
- LinkedIn search for Head of Operations and Chief of Staff titles at 20-200 person software companies
- Companies posting SOC 2 or ISO 27001 preparation signals on their careers pages
- Two or three operator and startup-ops communities where onboarding documentation is already discussed
Exact outreach motions
- Day 8: 40 first-touch emails naming a specific trigger such as a new-hire cohort or audit prep and offering a free scan of one folder
- Day 9: run the free scan within 24 hours of any reply and send the teaser with the Rot Score, the stale-document count and three rows
- Day 10: reply to the teaser with the 199 USD Stripe link and a one-line fix order for the top three documents
- Day 11: post the redacted sample report in two operator communities with the free-scan call to action
- Day 15 onward: two follow-ups at day 3 and day 7, each a single line about the highest-risk document found
- Day 20: ask every buyer for one referral to another ops lead in exchange for a free 90-day rescan
Message template
Hi [name] - you are hiring [n] people this quarter, which usually means new hires land on onboarding docs nobody has touched since 2023. I run a ten-minute read-only scan of one Drive folder and send back a Rot Score plus the three most stale documents, free. Want me to run it on your onboarding folder? No drive-wide access needed, and a ZIP export works too.
30-day execution roadmap
Week 1 · Build & validate · 7 days
Payment rails and app shell
- Create the Next.js repo, deploy to Vercel and attach the domain.
- Provision Supabase and the scans, files, reports and payments tables.
- Create Stripe products at 199 and 399 on the TrustMRR-connected account.
- Write the data-handling note: read-only scope, delete on request.
Deliverable: Live app shell with a working Stripe test-mode checkout.
Read-only OAuth and folder picker
- Add Google OAuth with read-only Drive scopes.
- Build a folder picker limited to five top-level folders.
- Sync file metadata capped at 5,000 files into Supabase.
Deliverable: A scan job that stores name, owner, last-modified, path and sharing for a real drive.
ZIP path plus risk engine
- Build the ZIP parser that maps folder paths to metadata rows.
- Implement scoring on folder context, days since edit, owner inactivity and missing owner.
- Compute the Rot Score from weighted flags.
Deliverable: Rot Score produced on two of the founder's own drives.
Analysis depth
- Cluster near-duplicates on normalized titles plus first-paragraph similarity.
- Detect orphans as documents with no inbound links in the export body.
- Call Claude for one reason line and one nudge draft on the top 40 flagged documents.
Deliverable: A complete JSON report payload for a real drive.
Paid end-to-end
- Render the PDF: cover, gauge, risk table, clusters, orphans, executive summary.
- Generate the CSV fix list from the same payload.
- Gate full output behind Stripe; free view shows score, count and three rows.
- Wire the Stripe webhook to the Resend delivery email.
Deliverable: A paid report produced and emailed end to end on the founder's own drive.
Proof and speed
- Publish the landing page with a redacted sample PDF embedded and one CTA.
- Put the ten-minute promise and security FAQ above the fold.
- Time a 2,000-file scan and fix the slowest step.
Deliverable: Live site with sample report and a measured scan duration.
300 companies
- Pull 300 remote-friendly B2B companies from the public YC directory.
- Find the ops or people lead name on each public team page.
- Verify 40 email addresses and stage the first batch.
Deliverable: A 300-row outreach sheet with 40 verified contacts.
Week 2 · Launch & first sale · 7 days
40 sends
- Send 40 first-touch messages naming a specific trigger.
- Track sends, opens and replies in one sheet.
- Draft the teaser email template with score, count and three rows.
Deliverable: 40 sends logged and a teaser template ready.
Deliver proof fast
- Run free scans for every reply within 24 hours.
- Send the teaser with the score and three rows, no ask yet.
- Log which trigger each prospect named.
Deliverable: Three to six teasers delivered.
Convert a teaser
- Follow up each teaser with the 199 USD Stripe link and a one-line fix order.
- Offer ZIP upload to anyone who objects to OAuth.
- Confirm the delivery email lands in the inbox, not spam.
Deliverable: First paid Rot Report (target day).
Sends and community
- Send 40 new first-touch messages.
- Post the redacted sample in two operator communities.
- Add a reply line that captures warm intros.
Deliverable: 80 total sends and 2 community posts live.
Security trust
- Publish a security page: read-only scope, storage location, deletion on request.
- Add a one-click delete-my-data link after delivery.
- Log the top three objections verbatim.
Deliverable: Security page live and an objection log started.
Remove founder from delivery
- Add scan status emails and retries on transient Drive errors.
- Publish refund and 14-day terms pages.
- Test the full flow with a stranger's ZIP upload.
Deliverable: A flow that completes with zero founder involvement.
Measure and rewrite
- Compute reply rate, free-scan rate and teaser-to-paid rate.
- Rewrite the opener around the best-performing trigger.
- Cut any step costing more than five founder minutes per sale.
Deliverable: A v2 outreach template and updated tracking formulas.
Week 3 · Repeat & systematize · 7 days
50 sends plus follow-ups
- Send 50 messages using the v2 opener.
- Start the two-touch follow-up at day 3 and day 7.
Deliverable: 50 sends and follow-up sequence running.
SOC 2 and ISO segment
- Send 50 messages to companies showing audit-prep signals.
- Write a variant opener for post-funding companies.
Deliverable: 50 sends and two opener variants under test.
Three-drive buyers
- Identify 15 fractional COO and ops consultant profiles.
- Send a pack-specific message about auditing three client drives.
- Add a white-label cover field to the 399 checkout.
Deliverable: Pack checkout variant live and 15 messages sent.
Permissioned case
- Ask each buyer for permission to publish an anonymized before and after.
- Publish one redacted before and after page.
Deliverable: One permissioned case page on the landing site.
Distribution
- Send 50 messages.
- Post the case page in one new operator community.
- Answer documentation threads there with the free-scan CTA.
Deliverable: 50 sends, 1 post, 5 thread replies.
Repeat purchase
- Ask every buyer for one ops-lead referral.
- Offer a free 90-day rescan in exchange.
Deliverable: Referral asks sent to all buyers.
Kill the weaker channel
- Compare channels on paid conversions per 100 contacts.
- Kill the weaker one and reallocate all outreach time.
Deliverable: A written channel decision with numbers attached.
Week 4 · Scale what works · 7 days
- Send 60 messages plus LinkedIn notes to email non-openers.
- Keep every message under 60 words.
Deliverable: 60 sends and 30 LinkedIn touches.
Hold the ten-minute promise
- Move duplicate clustering into a cheap pre-pass so the AI call stays under 40 documents.
- Cache folder trees per scan to cut rerun time.
Deliverable: Scan time under ten minutes on a 5,000-file drive.
Legibility to leadership
- Add a per-owner summary page listing documents each person owns.
- Group the fix list by folder.
Deliverable: Report v1.2 shipped.
Week one non-responders
- Send 60 messages to week-one non-responders with a new angle.
- Name the likely onboarding folder problem in line one.
Deliverable: 60 re-engagement sends.
Batch three drives
- Build a three-scan batch flow with one white-label PDF per drive.
- Write a one-page consultant handover note.
Deliverable: A Consultant Pack delivered without manual assembly.
Close older teasers
- Collect two short written testimonials with permission.
- Follow up every teaser older than five days.
Deliverable: Two permissioned quotes on the landing page.
Books reconcile
- Reconcile Stripe payouts against TrustMRR records.
- Confirm every sale falls inside the contest window.
Deliverable: A reconciliation sheet with zero unexplained rows.
Days 29-30 · Consolidate · 2 days
Last sends
- Send 60 final messages with a same-week delivery promise.
- Reply to every outstanding thread within two hours.
Deliverable: 60 sends and zero unanswered threads.
Delivery and retro
- Deliver every outstanding report.
- Publish a 30-day retro with the real collected numbers.
- Freeze scope and archive the outreach sheet.
Deliverable: All reports delivered, retro published, books closed.
Revenue and profit scenarios
How the numbers are defined
Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.
Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).
The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.
Stated assumptions
- All scenarios price the Rot Report at 199 USD; the 399 USD Consultant Pack appears only in the upside blend (Conservative/Base/Upside).
- Upside arpu of 214 USD reflects roughly 4 of 30 sales being 399 USD packs (Conservative/Base/Upside).
- Payment fees assume Stripe at 2.9% plus 0.30 per transaction with international card mix, modelled as 4.5% of collected revenue (all scenarios).
- Refunds assume 14-day terms and 0 to 2 refunds across the window (Conservative 0, Base 1, Upside 2).
- No chargebacks are modelled in any scenario because delivery is digital and immediate (all scenarios).
- Ad spend is organic outreach at zero in Conservative and Base; Upside includes 300 USD of sponsored community placement (Base/Upside).
- Operating costs cover Vercel, Supabase, domain, Resend and Claude tokens at under 1 USD per report served (all scenarios).
- Roughly 600 targeted first-touch messages plus community posts are assumed to produce the base case of 15 paid audits (Base).
- These are projections built from stated assumptions, not verified revenue, customers or traction.
Conservative
4 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $36
- Paid marketing
- $0
- Hackathon profit
- $760
- Operating costs
- $40
- Business profit
- $720
Base case
15 customers- Refunds
- $199
- Chargebacks
- $0
- Payment fees
- $134
- Paid marketing
- $0
- Hackathon profit
- $2,652
- Operating costs
- $120
- Business profit
- $2,532
Optimistic
30 customers- Refunds
- $398
- Chargebacks
- $0
- Payment fees
- $289
- Paid marketing
- $300
- Hackathon profit
- $5,433
- Operating costs
- $260
- Business profit
- $5,173
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $2,985
- Payment fees (3.9%)
- $116
- Paid marketing
- $0
- Hackathon profit
- $2,869
- Business profit
- $2,749
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 three scenarios are projections derived from the assumptions above. They are not verified revenue, existing customers or real traction, and outcomes inside a 30-day window are highly sensitive to outreach reply rates.
Main risks and validation experiments
Risk 1Google restricts read-only Drive scopes to verified apps, so external buyers cannot complete OAuth inside the contest window.
Ship the ZIP-upload path as a full production path with identical output, and lead with it when a buyer hesitates on OAuth.
Have three testers produce a report from a ZIP export on day 3 and time each run end to end.
If fewer than 1 in 5 free-scan starters completes either ingest path by day 12, replace ingest with a guided manual upload and re-scope the report to the uploaded subset.
Risk 2Cold outreach from an unknown solo founder converts far below the projected rate.
Send 600 messages across 30 days with two opener variants, and keep every message under 90 words.
Send a 40-message batch on day 8 and measure reply rate before scaling volume.
If reply rate stays under 5% after 200 messages, change trigger and channel emphasis rather than the product; if paid conversion stays at zero after 400 messages, stop outbound and re-price.
Risk 3Buyers do not consider a one-off report worth 199 USD compared with doing a rough pass themselves.
Lead with the free Rot Score and three real rows, and add the per-owner summary that makes the value visible to leadership.
Offer 199 USD to one 20-prospect half and 149 USD to another between day 10 and day 17, and compare teaser-to-paid rates.
If fewer than 1 in 20 completed free scans converts at 149 USD, drop to 99 USD and re-price the pack at 249 USD for three drives.
Risk 4A stranger requesting access to a company drive triggers a security objection the founder cannot clear.
Publish a security page stating read-only scope, storage location, deletion on request, and offer ZIP upload as the zero-access route.
Publish the security page on day 12 and log the first three objections verbatim to see which line actually converts.
If more than half of all replies are security objections after the security page ships, switch the default offer to ZIP upload and remove OAuth from the primary CTA.
Risk 5AI duplicate and staleness calls are wrong on unusual folder structures, producing a report the buyer distrusts and refunds.
Keep scoring deterministic and rule-based; use the model only to write reason lines and nudge drafts, and show last-edit dates the buyer can verify.
Show ten flagged rows to three blind testers and ask whether the fix recommendation is correct.
If fewer than 7 of 10 flagged rows are judged correct, remove AI from scoring entirely and ship rule-only output with raw dates.
Hour-by-hour: the first 24 hours
Hours 1-2
- Create the Next.js repo, buy the domain, deploy the shell to Vercel.
Output: A live URL with a placeholder headline.
Hours 3-5
- Create Stripe products at 199 and 399 on the TrustMRR-connected account.
- Run a live 1 USD test purchase and confirm the webhook fires.
Output: A working payment link and a verified webhook log.
Hours 6-10
- Implement Google OAuth with read-only Drive scopes.
- Pull metadata for one folder into Supabase.
Output: A 200-row metadata dump from the founder's own drive.
Hours 11-15
- Write the scoring function and compute a Rot Score on that metadata.
- Print the top ten ranked documents to the console.
Output: A working score on a real drive, however ugly the output.
Hours 16-19
- Draft the landing copy, the ten-minute promise and the security FAQ.
- Sketch the redacted sample report structure.
Output: Landing page text and a report outline ready to build against.
Hours 20-24
- Build the first 50 rows of the YC target list with company, lead name and profile URL.
Output: A 50-row outreach sheet, ready to extend to 300 on day 7.
Full 30-day launch report
Read the full generated report
StaleDoc Audit — 30-Day Launch Report
1. Product opportunity and positioning
The buyer is one named person: Head of Operations, Chief of Staff or People Ops lead at a 20-200 person remote-first software company in the US, UK or Canada. The trigger is a date on a calendar — a new-hire cohort starting, a Series A closing, or SOC 2 / ISO preparation kicking off. That person must answer which documents the team can trust, and today the only options are reading them all or guessing.
StaleDoc Audit sells the diagnosis, not a knowledge base. Read-only Google Drive access (or a ZIP export), up to five top-level folders, ten minutes of scanning, and a Documentation Debt Report PDF: Rot Score, 25 ranked high-risk documents with owner and last-edit date, duplicate clusters with a recommended survivor, an orphan list, per-owner nudge messages, and a CSV fix list. The free scan shows the score, the document count and three rows. The full artifact unlocks at 199 USD.
Wikis ask for migration, ownership assignment and months of upkeep. This returns a finished decision artifact the same day from the drive that already exists, priced below four hours of the buyer's loaded time, with no procurement cycle. That is the entire wedge, and it is why a solo founder can sell it in week two rather than after a platform adoption curve.
2. Smallest sellable MVP
One flow must work unbroken: connect a drive or upload a ZIP, get a Rot Score, pay 199 USD, receive a PDF naming 25 documents to fix first plus a CSV. Everything else is decoration.
The build is deliberately rule-first. Metadata sync writes name, owner, last-modified, folder path and sharing into Postgres. The scoring engine is deterministic — folder context weight (onboarding, HR, policy, security score higher), days since last edit, owner account inactivity, missing owner. Duplicate clustering runs on normalized titles and first-paragraph similarity. Orphans are documents with no inbound links in the export body. Only after those exist does the model touch anything: one batched call over the top 40 flagged documents writes a single reason line and a nudge draft each.
Explicitly not built in 30 days: editing, auto-fix, Slack bot, Notion or Confluence connectors, scheduled rescans, multi-seat roles, SSO, or any compliance attestation language.
3. Technical implementation plan
Next.js on Vercel, Supabase Postgres for scans, files, reports and payments, Google Drive API with read-only scopes, JSZip for the fallback, Claude for reason lines and nudge drafts, React-PDF for rendering, Stripe Checkout on the TrustMRR-connected account, Resend for delivery.
The scan is a durable record, not a session. Ingest writes metadata rows first and never holds file bodies beyond the top 40. Scoring is pure functions over rows, unit-tested. The renderer turns one JSON payload into both the PDF and the CSV so they can never disagree. The Stripe webhook flips the scan to paid and triggers the email. The free screen renders from the same payload with detail rows stripped, which means no second code path to maintain.
The hardest risk is Google's app verification for read-only Drive scopes. Assume OAuth reaches only a handful of test users during the window and build the ZIP parser as a first-class route on day 3, not day 25.
4. Pricing and monetization
Two one-time tiers. Rot Report at 199 USD for one company drive. Consultant Pack at 399 USD for three drives with a white-labelled cover, aimed at fractional COOs and ops consultants. No subscription, because a recurring fee on a diagnostic nobody runs monthly invites churn and refunds.
The repeat path is explicit: every buyer is offered a free 90-day rescan in exchange for one referral, and consultants graduate from a single report to the three-drive pack. The 199 USD price is defensible against the alternative — an ops lead manually reading several hundred documents — and it clears the cost of delivery by a wide margin since inference stays under one dollar per report.
5. First-customer acquisition
One channel: direct cold outreach to ops and people leads at remote-first 20-200 person software companies, sourced from the public YC directory and LinkedIn, with the lead name taken from public team pages. No ads, no SEO ramp, no partnerships.
The sequence is fixed. Build 300 companies by day 7 and verify 40 addresses. Send 40 first-touch messages on day 8, each naming a specific trigger. Run any free scan within 24 hours and reply with the Rot Score, the count of documents untouched for over 12 months, and three rows. Only then send the 199 USD link. Follow up twice, at day 3 and day 7, each time with a single line about the highest-risk document found. Supplement with the redacted sample report in two or three operator communities where the same buyer already asks about onboarding documentation.
Week-one goal: 300-row list, 40 verified sends, at least 4 replies, at least 2 completed free scans.
6. 30-day execution roadmap
Days 1-5 build the product and the payment rail, ending with a paid report emailed end to end on the founder's own drive (MVP deadline, day 5). Day 6 publishes the landing page with a redacted sample and a measured scan duration. Day 7 builds the 300-company list.
Days 8-14 are the first sales sprint: 80 sends, teasers delivered within 24 hours of any reply, first paid report targeted for day 10, security page published day 12, and the flow hardened on day 13 so delivery needs zero founder involvement. Day 14 measures reply rate, free-scan rate and teaser-to-paid rate and rewrites the opener.
Days 15-21 scale the winning message: 150 more sends, a SOC 2 / ISO trigger variant, 15 consultant-pack messages, one permissioned case page, and referral asks to every buyer. Day 21 kills the weaker channel using paid conversions per 100 contacts, not vibes.
Days 22-28 add a LinkedIn secondary touch, hold scan time under ten minutes on 5,000 files, ship the per-owner summary page, build the three-drive batch flow, collect two testimonials, and reconcile Stripe payouts against TrustMRR records on day 28. Days 29-30 are the final 60 sends, full delivery, and a published retro with real collected numbers.
7. Revenue and profit scenarios
All three lines below are projections from stated assumptions, not verified revenue.
Conservative — 4 reports at 199 USD. Gross 796 USD. Refunds 0, chargebacks 0, payment fees 36 USD, ad spend 0. Hackathon profit 760 USD. Operating costs 40 USD leaves 720 USD business profit.
Base — 15 reports at 199 USD. Gross 2,985 USD. One refund at 199 USD, payment fees 134 USD, no ad spend. Hackathon profit 2,652 USD. Operating costs 120 USD leaves 2,532 USD business profit.
Upside — 30 sales, blended 214 USD (four are 399 USD packs). Gross 6,420 USD. Refunds 398 USD, payment fees 289 USD, 300 USD of sponsored community placement. Hackathon profit 5,433 USD. Operating costs 260 USD leaves 5,173 USD business profit.
Fees assume Stripe at roughly 4.5% blended with international card mix. Upside is included to show what happens if the consultant pack lands, not as an expectation.
8. Main risks and validation experiments
OAuth verification. Google restricts read-only Drive scopes. Mitigation: ZIP upload ships as a full path on day 3. Test: three testers complete a ZIP report and are timed. If fewer than 1 in 5 starters complete either ingest path by day 12, replace ingest with a guided manual upload.
Cold outreach underperforms. Test: 40-message batch on day 8, reply rate measured before scaling. If under 5% after 200 messages, change the trigger, not the product.
Price resistance. Test: 199 USD to one 20-prospect half, 149 USD to the other, between day 10 and day 17. If under 1 in 20 completed free scans converts at 149 USD, drop to 99 USD and re-price the pack at 249 USD.
Security objection. Publish the security page on day 12 and log objections verbatim. If more than half of replies are security objections after that page ships, make ZIP upload the default CTA.
Wrong AI calls. Keep scoring deterministic and let the model write only reason lines. Test ten flagged rows with three blind testers. If under 7 of 10 are judged correct, ship rule-only output with raw last-edit dates.
9. First 24-hour action plan
Hours 1-2: repo, domain, deploy the shell. Hours 3-5: Stripe products at 199 and 399 on the TrustMRR-connected account, plus a live 1 USD test purchase and a verified webhook. Hours 6-10: OAuth with read-only scopes and a 200-row metadata dump from the founder's own drive. Hours 11-15: scoring function and top-ten ranked output, however rough. Hours 16-19: landing copy, ten-minute promise, security FAQ, report outline. Hours 20-24: first 50 rows of the YC target list with lead names and profile URLs.
At the end of day one the founder should have a live URL, a working payment link, real metadata from a real drive, and a target list already started. Everything after that is repetition and repair.
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 →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.
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.
SpecAnswer Blocks
Generates paste-in pre-purchase answer blocks — spec-grounded FAQs with FAQPage schema — for Shopify stores whose buyers keep asking 'will this fit my car / printer / lens?', so the answer exists on the product page before checkout.