Repo Dossier
Repo Dossier turns any codebase into a fixed-structure onboarding dossier, covering the architecture map, a where-things-live index, verified run commands and a landmine list, so the next developer is productive on day one instead of week three.
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 or tech lead of a 3-15 person software agency, or a senior freelance developer in US/EU/India, at the moment they inherit an unfamiliar client repo or hand one off.
Operational simplicity 4.2/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 10; 7 sales at $149 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.6/10.
Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.
Your first 24 hours
8 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Owner or tech lead of a 3-15 person software agency, or a senior freelance developer in US/EU/India, at the moment they inherit an unfamiliar client repo or hand one off.
Why now
Agencies are absorbing more inherited client codebases and running thinner benches, and repo-aware AI assistants have made people expect a synthesized answer—but not a citable, client-facing deliverable they can bill.
Problem
The first 1-3 weeks of every inherited codebase go into reverse-engineering which files matter, how it deploys, which env vars exist and what is load-bearing, because the author is gone and the README is stale.
Solution
Upload a zip or paste a public git URL; a deterministic analyzer extracts structure, routes, env var names, CI config and git churn, an AI layer writes only from those facts with citations, and the buyer receives a hosted page, a PDF and a DOSSIER.md with secrets stripped.
Repo Dossier — 30-Day Launch Report
1. Product opportunity and positioning
Repo Dossier sells one artifact: a fixed-structure onboarding dossier for a codebase. The buyer is the owner or tech lead of a 3-15 person software agency, or a senior freelancer, at the exact moment they inherit an unfamiliar client repo or hand one off to someone else. Today that transition costs one to three weeks of reverse engineering that agencies absorb unbilled, and it depends on a departing developer who is expensive, in another timezone, or already gone.
The dossier has a fixed shape: architecture map, where-things-live index, verified run commands, environment-variable names, CI and deploy summary, a landmine list ranked by git churn and revert history, and an explicit list of what the analyzer could not determine. Every AI-written paragraph cites the file, commit or config it came from. That citation trail is the product. A general-purpose coding assistant will summarize a repo for free, but it will not tell the buyer which sentence to trust or which module is load-bearing.
JEV scored this concept 64/100 (band C). Its strengths are speed to first revenue (8.56) and reachable customers (7.92); its weakest criterion is operational simplicity (4.22), because delivery touches a customer's source code. The 30 days are therefore built around founder-delivered dossiers first and automation second, with redaction treated as a stop-ship gate.
Positioning: not a tool, a deliverable. Agencies already sell onboarding and handover as billable work, so $149 is a line item a client pays for, not a new subscription budget. The product is demonstrable before it is bought — generate a dossier on the prospect's own public repo and send the link as the opening message. That removes the need for brand trust, an audience or ad budget, which is the only realistic distribution a solo founder has in 30 days.
2. Smallest sellable MVP
Four build days produce the sellable unit: an ingest path (zip upload or public URL clone into an ephemeral workspace), a deterministic analyzer (file tree, languages, entry points, routes, models, jobs, cron, env var names, CI and deploy config, dependency list), a git history pass (churn ranking, revert and hotfix commits, TODO/FIXME clusters, no personal attribution), a secret scanner that strips values before rendering, and a renderer producing a hosted page at an unguessable URL plus a PDF and a DOSSIER.md.
Explicitly excluded: no IDE plugin, no live session sync or replay, no GitHub App, no continuous monitoring, no seats, no SSO, no refactoring or pull requests. The MVP is one dossier per payment. Turnaround is quoted as 48 hours and delivered by the founder, not by a queue.
3. Technical implementation plan
Next.js on Vercel serves checkout, the delivery gate and hosted dossiers. Supabase Postgres holds job metadata and license records. Repo ingest uses isomorphic-git with tree-sitter WASM parsers; analysis runs as a background job with a hard runtime cap. The AI layer is called once per section with a strict facts-only prompt, and any paragraph lacking a citation is rejected before rendering. Artifacts land in Cloudflare R2, delivery email goes through Resend, and Stripe Checkout issues the license key that unlocks the page.
The hardest technical risk is parser coverage, not the AI: messy monorepos, minified bundles and polyglot trees produce thin facts, and a thin facts file produces a visibly empty dossier. Mitigation is a completeness check that blocks delivery and forces a partial dossier with an honest scope note rather than a confident empty one. Second risk is redaction; the scanner fails closed and a manual spot check runs on every private-repo order.
4. Pricing and monetization
Three one-time tiers: Single Dossier $149, Rush Dossier $249 (12-hour delivery, priority queue), Agency Pack $399 (three dossiers, white-label cover page, editable Markdown). No subscription, because the buying trigger is episodic and a monthly charge would fight the moment of purchase. The upsell path is volume and speed: single buyers who mention a second or third repo are pitched the agency pack, and anyone with a start date inside 48 hours is pitched Rush.
5. First-customer acquisition
One channel: direct 1:1 outreach with a free dossier attached, generated on the prospect's own public repo. The day-7 seed list is 150 agency owners and senior freelancers who publicly write about taking over client codebases; it is extended by 10-15 names daily from LinkedIn search, GitHub profiles of contract developers and agency directories, reaching roughly 350-400 sends by day 28. At a 4-5% send-to-paid rate that is 15-20 sales in the base case.
The opener is the dossier itself. The follow-up after three days asks one question — which module would your new dev hit first — because the answer is also the sales qualification. Reply rate is measured per segment weekly, and any message under 10% reply after 50 sends is rewritten or killed.
6. 30-day execution roadmap
Days 1-5: build. Ingest, deterministic analyzer, git history, redaction, renderer, PDF and license gate. Day 5 is the MVP deadline and the first end-to-end dossier must run on the founder's own repos.
Days 6-10: proof and first money. Twenty free dossiers on prospect repos expose real failure modes; day 7 ships the 150-name list and two message templates; days 8-10 send 75 dossiers and flip Stripe to live. First sale target is day 10.
Days 11-14: delivery discipline and higher ticket. A delivery checklist, the white-label cover page and the 12-hour rush queue ship by day 13. Day 14 is a hard review: compute reply rate, close rate and refunds, and kill or rewrite anything under threshold.
Days 15-21: top of funnel and reliability. The free watermarked public-repo generator goes live as the only self-serve surface, job retries and runtime caps land, and outreach continues at 25-30 per day.
Days 22-30: volume, objections and settlement. Objection handling for "an assistant already does this" and "we cannot upload client code", agency-pack upsells to existing buyers, referrals requested from every replier, a final push toward Rush pricing for anyone with a start date, and day 30 reconciliation of every payment received inside the window.
7. Revenue and profit scenarios
All figures are projections from stated assumptions, not verified revenue. Fees assume a 5% blended processing cost on international cards.
| Scenario | Customers | ARPU | Gross | Refunds | Fees | Ad | Operating | Hackathon profit | Business profit |
|---|---|---|---|---|---|---|---|---|---|
| Conservative | 6 | $149 | $894 | $0 | $45 | $0 | $60 | $849 | $789 |
| Base | 18 | $149 | $2,682 | $149 | $134 | $0 | $150 | $2,399 | $2,249 |
| Upside | 42 | $160 | $6,720 | $298 | $336 | $100 | $320 | $5,986 | $5,666 |
Operating cost is Vercel, Supabase, R2, Resend and roughly $0.60 of AI spend per dossier. The conservative case assumes outreach underperforms and only warm prospects convert; the upside assumes 550 sends, a Rush/Agency mix lifting ARPU to $160, and one refunded order per twenty.
8. Risks and validation experiments
Quality collapse on messy repos. Test: run the generator on 20 real prospect repos and score section completeness. Kill if more than 30% of dossiers have an empty core section after two fix rounds.
"An AI assistant already summarizes this." Test: split 40 sends between a "billable deliverable" angle and a "repo summary" angle. Kill the summary angle if the deliverable angle does not outperform it.
Reply rate far below 25%. Test: 50 sends in days 8-10 with a logged reply sheet. Kill the message if reply is under 8% after two rewrites.
Secret leak. Any single leak into a hosted page, PDF or email is a stop-ship event: pause sales, patch the scanner, spot-check every prior artifact.
Founder hours. Test: time five consecutive deliveries. If median exceeds 90 minutes, cap daily intake and raise the Rush price rather than promise more capacity.
Refusal to upload client code. Test: count this objection across the first 100 replies. If it exceeds half, shift the offer toward public-repo and low-sensitivity work.
9. First 24-hour action plan
Hours 1-2: re-read the official rules page, confirm the November 16 to December 16 window, create the Stripe account and connect it to TrustMRR before any customer exists.
Hours 3-5: scaffold the Next.js app on Vercel, create the Supabase job and license tables, register the domain, deploy a hello-world checkout.
Hours 6-9: implement zip upload and public URL clone into an ephemeral workspace, with a hard size cap and cleanup after the run.
Hours 10-12: build the file-tree and language parser, run it against three known public repos, and start the 150-name prospect list with one public repo captured per prospect.
Smallest sellable MVP
A paid, founder-delivered dossier for one repo: zip or public URL in, hosted page plus PDF plus DOSSIER.md out, with every AI paragraph citing a real file or commit and secrets stripped.
Must-have features
- Repo ingest via public git URL clone or zip upload with a size cap and ephemeral workspace cleanup
- Deterministic analyzer for file tree, languages, entry points, routes, models, jobs, cron, env var names, CI and deploy config
- Git history pass: churn ranking, revert and hotfix commits, TODO/FIXME clusters, no personal attribution
- Secret scanner that strips env values, keys and tokens and fails closed
- Fact-citation layer rejecting any AI paragraph without a file, commit or config reference
- Fixed-structure renderer producing a hosted page at an unguessable URL and a DOSSIER.md
- PDF export plus emailed delivery
- Stripe Checkout with a license key gating the hosted dossier
Explicitly out of scope
- No IDE plugin, editor extension or real-time cursor sync
- No session recording, replay player or narrative diff
- No GitHub App install or continuous repo monitoring
- No subscription seats, team management or SSO
- No automated refactoring or pull requests into the client repo
- No deep semantic correctness analysis beyond parser and git evidence
Demo flow (what the buyer sees)
- Founder clones a prospect's public repo into an ephemeral workspace
- Analyzer extracts structure, entry points, routes, env var names, CI config and dependency list
- Git history pass ranks churn and flags reverts, hotfix commits and TODO clusters
- Secret scanner strips values before any rendering
- AI layer writes each section from the facts file only, with citations attached
- Renderer produces the hosted page, PDF and DOSSIER.md
- Founder spot-checks completeness and sends the hosted link as the opener
Technical implementation plan
Stack
Architecture
A Next.js app handles checkout, the license gate and hosted dossier pages. An uploaded zip or cloned URL lands in an ephemeral workspace; a background job runs the deterministic analyzer and git history pass, writes a facts.json, runs the secret scanner, then makes one constrained AI call per section. Anything without a citation is discarded before rendering. The renderer emits an HTML page in Supabase-backed storage, a PDF and a DOSSIER.md in R2, and Resend emails the link to the paying buyer. Stripe issues a license key that unlocks private pages.
Build steps
- Scaffold Next.js on Vercel and create Supabase tables for jobs, licenses and dossiers
- Implement zip upload and public git URL clone into an ephemeral workspace with size cap
- Parse file tree, languages and package manifests with tree-sitter WASM
- Detect entry points, routes, models, jobs and cron from framework conventions
- Extract env var names and CI/deploy config without values
- Run isomorphic-git churn ranking, revert/hotfix detection and TODO clustering
- Ship the secret scanner with fail-closed behaviour
- Build the constrained per-section AI prompt with mandatory citation extraction
- Render the hosted page at an unguessable URL and generate DOSSIER.md
- Add PDF export to R2 and Resend delivery
- Add Stripe Checkout products, license keys and page gating
- Add a completeness check that blocks delivery on thin facts and forces an honest scope note
AI components
- Per-section narrative generation constrained to a facts file, with mandatory file/commit citations
- Facts-backed section summarization for the architecture map and landmine explanations
- No autonomous code analysis beyond what parsers and git history have already extracted
Pricing and monetization
Single Dossier
Entry offerFor Freelance devs and small agencies onboarding one inherited or handed-off repo
- Hosted dossier page
- PDF export
- DOSSIER.md written back to the repo
- Secret-redacted run commands and env var index
Rush Dossier
For Agencies with a new developer starting within 48 hours
- Everything in Single Dossier
- 12-hour delivery window
- Priority queue placement
Agency Pack
For Agencies that onboard client codebases repeatedly
- Three repo dossiers
- White-label cover page with agency name
- Editable Markdown source
- Priority queue placement
Model: Three one-time prices per repo, no subscription, white-label and rush speed as paid upgrades.
First revenue offer: Send a free dossier generated on the prospect's own public repo, then offer $149 for the private client repo with 48-hour turnaround and a refund if a module their new developer cares about is missing.
Expected ACV: $149
Upsell path: Single buyers who mention a second or third repo move to the $399 Agency Pack; anyone with a start date inside 48 hours moves to the $249 Rush tier.
First-customer acquisition
Direct 1:1 outreach with a free dossier generated on the prospect's own public repo attached as the opener.
Where to find them
- LinkedIn agency owners with headlines describing client software delivery
- LinkedIn senior freelancers who post about inheriting legacy codebases
- GitHub profiles of contract developers with many client forks and recent activity
- Agency directories listing 3-15 person shops
- Indie Hackers and r/freelance threads about taking over someone else's code
- X accounts posting about onboarding into unfamiliar repos
- Fractional CTO networks that audit multiple codebases per quarter
Exact outreach motions
- Generate a dossier on one public repo per prospect and send the hosted link with a one-line explanation
- Follow up after three days with a single question: which module would your new dev hit first
- Test a short opener against a long opener on alternating halves of the list
- Segment replies into agency vs freelancer and track reply rate separately
- Ask every replier for one referral to another agency owner
- Publish two sample dossiers on public open-source repos with a free watermarked generator link
Message template
Hi {name} — I generated a 9-page dossier on your {repo} repo in about 12 minutes: {link}. Architecture map, where things live, run commands, and the files that churn most. Want one for the client repo your next dev starts on? $149, 48 hours, refund if a module you care about is missing.30-day execution roadmap
Week 1 · Build & validate · 7 days
Ingest skeleton and payment setup
- Scaffold Next.js on Vercel and create Supabase tables for jobs, licenses and dossiers.
- Add zip upload and public URL clone with a 200MB cap into an ephemeral workspace.
- Create Stripe Checkout products at $149, $249 and $399 in test mode.
Deliverable: Deployed app that accepts a repo and creates a queued job row.
Structure facts
- Parse file tree, languages and package manifests with tree-sitter WASM.
- Detect entry points, routes, models, jobs and cron from framework conventions.
- Extract env var names and CI/deploy config without any values.
Deliverable: facts.json produced for a 50k-LOC repo in under three minutes.
Churn and secrets
- Rank files by churn and flag revert and hotfix commits with isomorphic-git.
- Cluster TODO and FIXME comments by directory.
- Ship the secret scanner that drops key-shaped strings and env values, failing closed.
Deliverable: history.json plus a redaction pass that blocks rendering on any hit.
Dossier output
- Constrain the model to write each section only from the facts file, with citations.
- Render the fixed-structure hosted page at an unguessable URL.
- Generate DOSSIER.md for write-back into the repo.
Deliverable: End-to-end dossier from a public URL on the founder's own repos.
Sellable MVP
- Add PDF export to R2 and emailed delivery via Resend.
- Gate dossier pages behind a Stripe license key.
- Run five real repos and fix the two worst output failures.
Deliverable: Paid-ready product; MVP deadline hit.
Real-world repos
- Generate 20 free dossiers on prospect public repos.
- Log failure modes: monorepos, minified bundles, polyglot trees.
- Fix the top three failure modes found.
Deliverable: 20 shareable dossiers and a written failure log.
Outreach prep
- Build the 150-prospect list with one public repo captured per prospect.
- Write a free-dossier opener and a three-day follow-up question.
- Publish two sample dossiers on public open-source repos.
Deliverable: 150-row list, two message templates, two public samples.
Week 2 · Launch & first sale · 7 days
First 25 sends
- Send 25 personalised dossiers on prospects' own repos.
- Switch Stripe live and run one real $149 purchase end to end.
- Log replies and objections in a tracking sheet.
Deliverable: 25 sends and a verified live payment path.
Second 25 sends
- Send 25 more dossiers.
- Reply to every response within two hours.
- Draft the private-repo intake form with a data-handling note.
Deliverable: 50 total sends and a live intake form.
Convert replies
- Send 25 more dossiers.
- Follow up once with day-8 non-repliers.
- Push engaged repliers to a $149 checkout link.
Deliverable: First paying customer; target day 10.
Fulfilment quality
- Turn paid orders around in under 24 hours.
- Add a delivery checklist that catches empty sections before sending.
- Ask each buyer which module their new dev hits first.
Deliverable: Delivery checklist and first buyer feedback notes.
Message test
- Send 25 more dossiers.
- Run a shorter opener against half the list.
- Record reply rate by segment: agency versus freelancer.
Deliverable: Reply-rate readout per message and segment.
Agency Pack and Rush
- Ship the white-label agency cover page.
- Ship the 12-hour rush queue and priority placement.
- Pitch the $399 pack to anyone naming two or more repos.
Deliverable: Agency Pack and Rush Dossier buyable in production.
Kill criteria
- Compute reply rate, close rate and refunds to date.
- Rewrite or kill any message under 10% reply after 50 sends.
- Decide explicitly: continue the wedge or change the angle.
Deliverable: Week 2 metrics memo with a written go/no-go.
Week 3 · Repeat & systematize · 7 days
Self-serve public repos
- Ship the free watermarked public-repo generator page.
- Add a 'buy the clean version' button to every free dossier.
- Post the generator in two developer communities.
Deliverable: Free-tier generator live with a paid upgrade path.
Volume and second touch
- Send 30 dossiers, adding fractional CTOs to the list.
- Add a second follow-up carrying one specific dossier finding.
- Expand the list outward by 15 new names.
Deliverable: 80 cumulative sends and an expanded list.
Job robustness
- Add job retries, a hard runtime cap and error reporting.
- Handle repos over 150k LOC with a partial dossier and a scope note.
- Wire the completeness check to block thin deliveries.
Deliverable: Jobs that fail visibly instead of shipping empty sections.
Fractional CTOs
- Write an opener aimed at people who audit several codebases per quarter.
- Send 20 segmented dossiers to that list.
- Compare close rate against the agency segment.
Deliverable: Segment comparison table with a decision on where to spend days.
Delivery time
- Measure median time from payment to delivery.
- Template the manual QA pass into a five-point checklist.
- Cut the slowest manual step.
Deliverable: Median turnaround under 24 hours, documented.
Buyer quotes
- Ask every buyer for one line about a specific dossier section.
- Request permission to publish it without naming the client repo.
- Add the strongest line to the offer page.
Deliverable: Permission-cleared quotes or an explicit note that none were granted.
Pipeline math
- Compute how many sends are needed for the remaining window.
- Cut the lowest-converting segment.
- Set the daily send quota for days 22-29.
Deliverable: Send quota and segment cut, written down.
Week 4 · Scale what works · 7 days
Rush push
- Send 30 dossiers.
- Offer Rush pricing to anyone with a start date inside 48 hours.
- Log every refusal reason verbatim.
Deliverable: 30 sends and a refusal-reason tally.
Trust blockers
- Publish a data-handling page covering ephemeral workspaces and deletion.
- Write the answer to 'an assistant already does this' and use it in replies.
- Add an NDA note to the private-repo intake form.
Deliverable: Trust page live and objection scripts in use.
Existing buyers
- Pitch the $399 pack to every single-dossier buyer.
- Offer a discounted second dossier in the same thread.
- Track upsell revenue separately.
Deliverable: Upsell attempt logged for 100% of prior buyers.
Third public sample
- Publish a third sample dossier on a public open-source repo.
- Post it in two freelance and agency communities.
- Point every post at the free watermarked generator.
Deliverable: Third public sample live with community posts made.
Referrals
- Send 30 dossiers.
- Ask every replier for one referral by name.
- Send the single-question follow-up to day-22 non-repliers.
Deliverable: Referral asks made and follow-ups sent.
Cost per dossier
- Remove two manual steps from the delivery path.
- Confirm AI spend stays under $0.60 per dossier.
- Review operating cost against the scenario assumptions.
Deliverable: Cost-per-dossier measurement logged.
Final pipeline
- List everyone who has not yet paid and rank by likelihood.
- Send a dated close offer to the top twenty.
- Confirm every payment collected so far sits inside the window.
Deliverable: Ranked close list and a payment-window audit.
Days 29-30 · Consolidate · 2 days
Last conversions
- Send final follow-ups before the window closes.
- Push Rush pricing where immediate payment is plausible.
- Deliver every outstanding order.
Deliverable: Zero undelivered paid orders.
Verify and report
- Export all Stripe payments received inside the window.
- Reconcile refunds, chargebacks and processing fees.
- Publish a public ship log with customers, revenue and lessons.
Deliverable: Reconciled revenue record and a published ship log.
Revenue and profit scenarios
How the numbers are defined
Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.
Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).
The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.
Stated assumptions
- Base: 350-400 personalised outreach sends across the window at a 4-5% send-to-paid rate.
- Conservative: outreach underperforms and only warm prospects convert, roughly 6 sales from 150 sends.
- Upside: 550 sends plus a Rush/Agency mix lifting ARPU to $160.
- Payment fees assume a 5% blended processing cost (Stripe plus international cards).
- Refunds assume one refund per twenty collected orders because the buyer sees a sample first.
- Operating cost covers Vercel, Supabase, R2, Resend and about $0.60 of AI spend per dossier.
- Ad spend is zero in conservative and base because the channel is organic 1:1 outreach; upside includes a $100 sponsored community post test.
- All figures are projections from stated assumptions, not verified revenue or existing customers.
Conservative
6 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $45
- Paid marketing
- $0
- Hackathon profit
- $849
- Operating costs
- $60
- Business profit
- $789
Base case
18 customers- Refunds
- $149
- Chargebacks
- $0
- Payment fees
- $134
- Paid marketing
- $0
- Hackathon profit
- $2,399
- Operating costs
- $150
- Business profit
- $2,249
Optimistic
42 customers- Refunds
- $298
- Chargebacks
- $0
- Payment fees
- $336
- Paid marketing
- $100
- Hackathon profit
- $5,986
- Operating costs
- $320
- Business profit
- $5,666
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $2,682
- Payment fees (3.9%)
- $105
- Paid marketing
- $0
- Hackathon profit
- $2,577
- Business profit
- $2,427
Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.
Scenario models from stated assumptions, not verified revenue. Hackathon profit excludes hosting, tooling and AI/API delivery cost; business profit deducts them.
Main risks and validation experiments
Risk 1Output quality collapses on messy monorepos, minified bundles or polyglot repos, producing refunds and bad word of mouth.
Completeness check blocks delivery on thin facts and forces a partial dossier with an honest scope note instead of confident filler.
Run the generator on 20 real prospect public repos in week one and score section completeness per dossier.
More than 30% of dossiers have an empty core section after two fix rounds.
Risk 2Prospects decide a general-purpose AI coding assistant already summarizes the repo well enough for free.
Lead with the billable-deliverable angle and the citation trail: every paragraph points at a file or commit, so the buyer can hand it to a client.
Split 40 outreach sends between a 'billable deliverable' opener and a 'repo summary' opener and compare replies.
The deliverable angle does not beat the summary angle on reply rate after 40 sends.
Risk 3Cold outreach reply rates land far below the assumed 25-30%, leaving the target unreachable.
Daily send quota of 25-30, weekly message rewrites and explicit segment tracking on agency versus freelancer.
50 sends in days 8-10 with replies logged and attributed to the exact message variant.
Reply rate under 8% after two message rewrites, or fewer than 2 paid orders from 100 sends by day 21.
Risk 4Any secret leaked into a hosted page, PDF or email destroys trust for agencies handling client code.
Fail-closed secret scanner before rendering plus a manual spot check on every private-repo order.
Deliberately seed a test repo with fake keys and tokens and confirm none survive into any artifact.
A single leak into a delivered artifact pauses sales until the scanner is patched and prior artifacts re-checked.
Risk 5A solo founder doing 40 deliveries plus outreach and support runs out of hours.
Cap daily intake, quote 48-hour turnaround, and price Rush high enough that queue pressure is paid for.
Time five consecutive deliveries in week two and record the median.
Median delivery time above 90 minutes once daily sends reach 25.
Risk 6Some prospects refuse to upload client code at all, capping the addressable list to public or low-sensitivity repos.
Ephemeral-workspace deletion policy, a public-repo free tier, and a written data-handling page.
Count this objection verbatim across the first 100 replies.
More than half of objections are upload refusal and the public-repo tier produces no paid upgrade in two weeks.
Hour-by-hour: the first 24 hours
Hours 1-2
- Re-read the official rules page and confirm the November 16 to December 16 window and the profit definition.
- Create the Stripe account and connect it to TrustMRR before any customer exists.
Output: Confirmed date window, live payment account, zero customers so far.
Hours 3-5
- Scaffold the Next.js app on Vercel and create Supabase job, license and dossier tables.
- Register the domain and deploy a hello-world checkout page.
Output: Deployed skeleton with a public URL and database tables.
Hours 6-9
- Implement zip upload and public git URL clone into an ephemeral workspace with a size cap.
- Add cleanup that deletes the workspace after the analysis run.
Output: Working ingest path with cleanup, tested on one public repo.
Hours 10-12
- Build the file-tree and language parser and run it on three known public repos.
- Start the 150-name prospect list and capture one public repo per prospect.
Output: First facts.json output plus the first 30 rows of the prospect list.
Full 30-day launch report
Read the full generated report
Repo Dossier — 30-Day Launch Report
1. Product opportunity and positioning
Repo Dossier sells one artifact: a fixed-structure onboarding dossier for a codebase. The buyer is the owner or tech lead of a 3-15 person software agency, or a senior freelancer, at the exact moment they inherit an unfamiliar client repo or hand one off to someone else. Today that transition costs one to three weeks of reverse engineering that agencies absorb unbilled, and it depends on a departing developer who is expensive, in another timezone, or already gone.
The dossier has a fixed shape: architecture map, where-things-live index, verified run commands, environment-variable names, CI and deploy summary, a landmine list ranked by git churn and revert history, and an explicit list of what the analyzer could not determine. Every AI-written paragraph cites the file, commit or config it came from. That citation trail is the product. A general-purpose coding assistant will summarize a repo for free, but it will not tell the buyer which sentence to trust or which module is load-bearing.
JEV scored this concept 64/100 (band C). Its strengths are speed to first revenue (8.56) and reachable customers (7.92); its weakest criterion is operational simplicity (4.22), because delivery touches a customer's source code. The 30 days are therefore built around founder-delivered dossiers first and automation second, with redaction treated as a stop-ship gate.
Positioning: not a tool, a deliverable. Agencies already sell onboarding and handover as billable work, so $149 is a line item a client pays for, not a new subscription budget. The product is demonstrable before it is bought — generate a dossier on the prospect's own public repo and send the link as the opening message. That removes the need for brand trust, an audience or ad budget, which is the only realistic distribution a solo founder has in 30 days.
2. Smallest sellable MVP
Four build days produce the sellable unit: an ingest path (zip upload or public URL clone into an ephemeral workspace), a deterministic analyzer (file tree, languages, entry points, routes, models, jobs, cron, env var names, CI and deploy config, dependency list), a git history pass (churn ranking, revert and hotfix commits, TODO/FIXME clusters, no personal attribution), a secret scanner that strips values before rendering, and a renderer producing a hosted page at an unguessable URL plus a PDF and a DOSSIER.md.
The MVP is one dossier per payment. Turnaround is quoted at 48 hours and delivered by the founder, not by a queue. Explicitly excluded: no IDE plugin, no live session sync or replay, no GitHub App, no continuous monitoring, no seats, no SSO, no refactoring or pull requests.
3. Technical implementation plan
Next.js on Vercel serves checkout, the license gate and hosted dossiers. Supabase Postgres holds job metadata and license records. Repo ingest uses isomorphic-git with tree-sitter WASM parsers, and analysis runs as a background job with a hard runtime cap. The AI layer is called once per section with a strict facts-only prompt, and any paragraph lacking a citation is rejected before rendering. Artifacts land in Cloudflare R2, email goes through Resend, and Stripe Checkout issues the license that unlocks the page.
The hardest technical risk is parser coverage, not the model: messy monorepos, minified bundles and polyglot trees produce thin facts, and thin facts produce a visibly empty dossier. Mitigation is a completeness check that blocks delivery and forces a partial dossier with an honest scope note rather than a confident empty one. The second risk is redaction; the scanner fails closed and a manual spot check runs on every private-repo order.
4. Pricing and monetization
Three one-time tiers: Single Dossier $149, Rush Dossier $249 with a 12-hour window, Agency Pack $399 with three dossiers and a white-label cover page. No subscription, because the buying trigger is episodic and a monthly charge would fight the moment of purchase. The upsell path is volume and speed: single buyers who name a second or third repo get pitched the pack, and anyone with a start date inside 48 hours gets pitched Rush.
5. First-customer acquisition
One channel: direct 1:1 outreach with a free dossier generated on the prospect's own public repo. The day-7 seed list is 150 agency owners and senior freelancers who publicly write about taking over client codebases, extended by 10-15 names daily from LinkedIn search, GitHub profiles of contract developers and agency directories, reaching roughly 350-400 sends by day 28. At a 4-5% send-to-paid rate that is 15-20 sales in the base case.
The opener is the dossier itself. The follow-up after three days asks one question — which module would your new dev hit first — because the answer is also the qualification. Reply rate is measured per segment weekly, and any message under 10% reply after 50 sends is rewritten or killed.
6. 30-day execution roadmap
Days 1-5 are build: ingest, deterministic analyzer, git history, redaction, renderer, PDF and license gate. Day 5 is the MVP deadline, and the requirement is one end-to-end dossier from a real public URL.
Days 6-10 are proof and first money. Twenty free dossiers on prospect repos expose real failure modes; day 7 ships the 150-name list and two templates; days 8-10 send 75 dossiers and flip Stripe live. First sale target is day 10.
Days 11-14 are delivery discipline and higher ticket: a delivery checklist, the white-label cover page and the 12-hour rush queue land by day 13, and day 14 is a hard review with an explicit continue-or-change decision.
Days 15-21 add top of funnel and reliability. The free watermarked public-repo generator goes live as the only self-serve surface, job retries and runtime caps land, and outreach continues at 25-30 per day.
Days 22-30 are volume, objections and settlement: scripts for "an assistant already does this" and "we cannot upload client code", agency-pack upsells to existing buyers, referrals requested from every replier, a Rush push for anyone with a start date, and day 30 reconciliation of every payment inside the window.
7. Revenue and profit scenarios
All figures are projections from stated assumptions, not verified revenue. Payment fees assume a 5% blended processing cost across Stripe and international cards.
| Scenario | Customers | ARPU | Gross | Refunds | Fees | Ad | Operating | Hackathon profit | Business profit |
|---|---|---|---|---|---|---|---|---|---|
| Conservative | 6 | $149 | $894 | $0 | $45 | $0 | $60 | $849 | $789 |
| Base | 18 | $149 | $2,682 | $149 | $134 | $0 | $150 | $2,399 | $2,249 |
| Upside | 42 | $160 | $6,720 | $298 | $336 | $100 | $320 | $5,986 | $5,666 |
Operating cost is Vercel, Supabase, R2, Resend and about $0.60 of AI spend per dossier. The conservative case assumes outreach underperforms and only warm prospects convert; upside assumes 550 sends and a Rush/Agency mix lifting ARPU to $160.
8. Risks and validation experiments
Quality collapse on messy repos. Test by scoring section completeness across 20 real prospect repos in week one; kill if more than 30% of dossiers have an empty core section after two fix rounds.
"An AI assistant already summarizes this." Test with 40 split sends comparing a billable-deliverable angle against a repo-summary angle; kill the angle that loses.
Reply rate below 25%. Test with 50 logged sends in days 8-10; kill the message at under 8% reply after two rewrites, and kill the wedge at fewer than 2 paid orders from 100 sends by day 21.
Secret leak. Deliberately seed a test repo with fake keys; a single leak into any delivered artifact pauses sales until the scanner is patched and prior artifacts are re-checked.
Founder hours. Time five deliveries in week two; if the median exceeds 90 minutes, cap daily intake and raise the Rush price rather than promise capacity.
Upload refusal. Count the objection verbatim across the first 100 replies; if it exceeds half and the free public tier produces no paid upgrade in two weeks, narrow the offer.
9. First 24-hour action plan
Hours 1-2: re-read the official rules, confirm the November 16 to December 16 window, create the Stripe account and connect it to TrustMRR before any customer exists.
Hours 3-5: scaffold Next.js on Vercel, create the Supabase job and license tables, register the domain, deploy a hello-world checkout.
Hours 6-9: implement zip upload and public URL clone into an ephemeral workspace with a hard size cap and post-run cleanup.
Hours 10-12: build the file-tree and language parser, run it against three known public repos, and start the 150-name prospect list with one public repo captured per prospect.
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.
BriefToBoard Compiler
Turns a signed client brief into an importable project board, a one-page scope memo, and a missing-inputs checklist for small web-design and branding agencies.
Repo Handoff Dossier
A fixed 14-section PDF dossier generated from any GitHub repo in under 10 minutes, so a developer taking over an inherited codebase can hand the client a professional assessment instead of a two-day write-up.