Handover Dossier
Generates a client-ready codebase handover dossier for dev agencies closing out a project, turning repository history into a branded PDF in about 15 minutes instead of two days.
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 lead developer at a 3-15 person web or mobile development agency in the US, UK, Canada or Australia, at the moment a client engagement closes out or the final invoice waits on documentation.
Market demand 3.8/10
Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.
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; 6 sales at $199 clears $1,000 of collected revenue; strongest signal is solo build feasibility at 7.4/10.
Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.
Your first 24 hours
10 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Owner or lead developer at a 3-15 person web or mobile development agency in the US, UK, Canada or Australia, at the moment a client engagement closes out or the final invoice waits on documentation.
Why now
Small agencies are shipping faster with AI assistance while closeout documentation stays manual, and the local-collector design removes the client-code objection that blocked earlier hosted tools.
Problem
At closeout the agency owes the client documentation of what was built, and reconstructing architecture, env vars, risky files, dependency debt and known gaps takes a senior developer one to two days of unbillable work.
Solution
A local collector CLI (npx handover-collector) emits a metrics-only JSON from git history, lockfiles, CI config and env templates; uploading it produces a six-section branded HTML/PDF dossier with an executive summary, module map, hotspot ranking, landmine list, dependency/CVE table with upgrade order, onboarding runbook and open questions.
1. Product opportunity and positioning
Handover Dossier sells one document: the client-ready handover pack a small dev agency owes at project closeout. Today that document costs one to two senior developer days, is the least billable work in the project, and sits between the agency and its final invoice. The buyer is the owner or lead developer of a 3-15 person web or mobile agency in the US, UK, Canada or Australia, reached in the week a client engagement closes.
The wedge is narrow on purpose. JEV scored this exact concept 59.7/100 (band C), with speed to first revenue (7.08) and solo build feasibility (7.4) as the strongest criteria and market demand (3.84) as the weakest. This plan attacks that weakness directly: it does not wait for inbound demand, it manufactures urgency by putting a finished, agency-branded dossier in front of an owner who already has a closeout on the calendar. Monetization (4.97) is answered by a $199 single dossier plus a $499 five-pack that turns episodic closeouts into a repeat purchase.
Differentiation is the delivery mechanism, not the AI. The collector runs on the buyer's own machine and uploads metrics only: file paths, churn counts, dependency names and versions, environment variable names. No source lines leave the laptop. That one design choice removes the security objection that kills most agency tool sales, and it makes the deliverable producible in roughly 15 minutes, on the same call where it is sold.
The trigger is dated and the price sits under an owner's approval threshold. That combination, not market size, is the bet: a $199 charge approved without a second signature, on a project that is already invoicing, for a document the client is already expecting. The report is sold as a deliverable, never as a subscription or a platform.
2. Smallest sellable MVP
Four things must exist for money to change hands: the collector CLI on npm, the upload plus dossier renderer, the branded PDF export, and a Stripe Payment Link that unlocks both. The six fixed sections are executive summary, module map, hotspot ranking, landmine list, dependency and CVE table with a suggested upgrade order, and onboarding runbook with open questions. A free watermarked preview of the first two sections is the sales artifact. Explicitly not built: PR bot, GitHub Action, code fixes, monitoring, IDE plugin, team accounts, source upload, procurement support.
3. Technical implementation plan
Build order: CLI skeleton and metrics JSON schema on day 1, git history and dependency extraction on day 2, hotspot scoring, landmine flags and OSV.dev lookups on day 3, the Next.js upload and render path on day 4, Playwright PDF, Stripe gate and Resend email on day 5. The LLM writes only the narrative sections and is constrained to the uploaded metrics JSON; file names and dependency versions are injected verbatim from the file, never generated. The hardest technical risk is thin or squashed git history producing an empty-feeling dossier, mitigated by falling back to lockfile and CI-config evidence and by showing an explicit data-coverage note.
4. Pricing and monetization
Single Dossier at $199 one time, Agency Pack at $499 for five dossiers over 12 months, watermarked preview at $0. Expected blended revenue per buyer sits between $199 and $244 depending on pack mix. The only upsell is the pack, offered to any buyer who mentions more than one open closeout.
5. First-customer acquisition
One channel: direct X and LinkedIn DMs to agency owners, each carrying a free watermarked dossier the founder generated from that agency's own public repository. Build a 150-200 prospect list by day 7, send in waves of 30 from day 9, follow up once after four days, and post anonymized samples in agency and Indie Hackers communities. Projected conversion is roughly 10 percent of the reached list inside 30 days, which is the base case below.
6. 30-day execution roadmap
Days 1-5 build the MVP with a sellable artifact at the end of day 5. Day 6 is QA against five real public repositories. Day 7 builds the prospect list; days 8-10 generate samples and send the first 60 DMs plus one community post. Day 11 is the first-sale target, delivered by walking a warm prospect through the CLI live. Days 12-20 run a second and third outreach wave, ship the Agency Pack, publish a free closeout checklist page, and patch the top quality complaints. Days 21-28 run the final waves, publish a case-study thread, ship a client sign-off checklist, and tally collected revenue. Days 29-30 close the warm pipeline with a referral ask to every buyer.
7. Revenue and profit scenarios
All figures are projections, not verified revenue. Conservative: 3 buyers at $199, $597 revenue, $55 costs, $542 profit. Base: 9 buyers at $232 blended, $2,088 revenue, $120 costs, $1,968 profit. Upside: 20 buyers at $244 blended with three pack upgrades, $4,880 revenue, $240 costs, $4,640 profit. Costs are Stripe fees, npm and hosting, LLM tokens and email. Nothing here is a customer, a commitment or a signed contract.
8. Main risks and validation experiments
First, closeouts are episodic, so the reached segment may not contain enough of them in 30 days: test by asking 20 prospects whether a closeout lands inside 30 days; kill the channel if fewer than 5 say yes. Second, owners may decide the client does not need documentation: test with 15 DMs that lead with the closeout checklist rather than the product; kill the checklist angle if it produces zero replies in four days. Third, free-sample outreach may read as unsolicited use of a public repo: test two message variants, one asking permission first, and adopt whichever produces fewer negatives. Fourth, dossier quality is history-dependent: instrument every generated dossier for data coverage and refund any report below the coverage floor.
9. First 24-hour action plan
Hours 1-2: scaffold the npm package, install simple-git and fast-glob, and commit the metrics JSON schema. Hours 3-5: implement per-file commit counts, author spread, lines changed and file age, and print metrics for the founder's own repository. Hours 6-7: add package.json and lockfile parsing into the same JSON. Hours 8-9: draft the six dossier section templates and the DM message, and register the domain and Stripe account so the $199 link can exist by day 5.
Smallest sellable MVP
An npm collector that emits metrics-only JSON plus a web app that turns that JSON into a branded six-section PDF unlocked by a $199 Stripe Payment Link.
Must-have features
- npm CLI handover-collector that parses git log for per-file commits, authors, lines changed and file age
- Dependency and version extraction from package.json and lockfiles with OSV.dev CVE lookup
- Hotspot ranking by churn, size and recency with untested-file landmine flags
- Auto-drafted onboarding runbook and env variable inventory from CI config, scripts, .env.example and README
- Web upload, job record and HTML dossier viewer with six fixed sections
- LLM-written narrative grounded only in the uploaded metrics JSON
- Playwright branded PDF export with agency name, logo and accent color
- Stripe Payment Link unlock plus emailed 7-day download link
- Watermarked free preview of the first two sections
Explicitly out of scope
- PR bot, GitHub Action or auto-approval
- Automated code fixes, refactors or migrations
- Continuous monitoring or repository watch
- IDE plugin, team accounts or permissions
- Source code upload or hosted cloning
- SOC 2 or security questionnaire support
Demo flow (what the buyer sees)
- Founder runs npx handover-collector in the agency's private repo
- CLI writes handover-metrics.json with paths, churn, dependencies and env names only
- Owner uploads the JSON to the web app
- App renders the six-section dossier with a watermarked preview
- Owner pays $199 via Stripe Payment Link
- PDF renders with the agency's logo and accent color
- Emailed 7-day download link delivers the branded PDF in about 15 minutes total
Technical implementation plan
Stack
Architecture
The collector is a stateless local process with no network calls: it reads .git, lockfiles, CI config, .env.example and README, and writes a single metrics JSON. That file is uploaded to a Next.js API route that stores the metrics and a job record in Supabase, computes scoring deterministically in application code, and calls the LLM once per section group with the metrics JSON as the only allowed input. The rendered HTML is turned into a PDF by Playwright on demand, stored behind a signed token with a 7-day expiry, and the Stripe webhook flips the job to paid and triggers the Resend email. Nothing persists source code because nothing receives source code.
Build steps
- Scaffold the npm package and define metrics JSON schema v1
- Implement git log parsing for commits, authors, lines changed and file age
- Add package.json and lockfile dependency extraction
- Implement hotspot scoring, landmine flags and OSV.dev CVE lookups
- Build Next.js upload endpoint, Supabase job table and signed tokens
- Render the six fixed dossier sections in HTML with a watermarked preview mode
- Add the LLM narrative call with a metrics-only prompt
- Add Playwright PDF export with agency branding fields
- Wire Stripe Payment Link webhook to unlock PDF and email
- Wire Resend delivery with a 7-day expiring link
- Test on five public repositories and harden thin-history fallbacks
- Deploy to Vercel and publish the CLI to npm
AI components
- LLM writes the executive summary, module narrative and open-questions framing
- Prompt is constrained to the uploaded metrics JSON; file paths and dependency versions are injected verbatim
- A second pass checks that no file name or package appears in the narrative that is absent from the metrics
Pricing and monetization
Single Dossier
Entry offerFor Agency owner with one client closeout this month
- One branded PDF and HTML dossier
- Six sections with client-facing executive summary
- Dependency and CVE table with upgrade order
- Onboarding runbook and open-questions list
- 7-day download link
Agency Pack
For Agency with several closeouts per year
- Five dossiers valid for 12 months
- Saved branding preset
- Reusable closeout checklist template
Watermarked Preview
For Prospect evaluating before paying
- First two sections only
- No PDF export
- No branding
Model: One-time per-deliverable pricing with a five-pack for agencies with repeated closeouts.
First revenue offer: I ran your public repo through Handover Dossier. Here is the watermarked version. If you have a closeout this month, your private repo takes about 15 minutes and costs $199 for the branded PDF.
Expected ACV: $232
Upsell path: Offer the $499 five-dossier pack to any buyer who names a second closeout in the same conversation, and to every past buyer in week 3.
First-customer acquisition
Direct X and LinkedIn DMs to agency owners, each carrying a free watermarked dossier generated from that agency's own public repository.
Where to find them
- Public agency directories and clutch-style listings filtered to 3-15 person shops
- LinkedIn search for 'founder' or 'owner' at agencies with 2-10 employees in US, UK, CA, AU
- GitHub organisations linked from agency websites with a last commit inside 12 months
- Agency owners posting about client handovers, retainer endings or final invoices on X
- Freelance and agency communities on Indie Hackers and niche Slack groups
Exact outreach motions
- Day 9 wave: send 30 DMs, each with a pre-generated watermarked sample branded to that agency.
- Day 12 wave: send 30 more using wording harvested from the first replies.
- Day 11 follow-up: send a one-page closeout checklist to the day-9 batch with no pitch attached.
- Day 10 community post: publish an anonymized sample dossier in two agency communities with the free sample as the call to action.
- Day 21 case study thread: post the before and after of one dossier on X, no customer names.
- Day 29 nudge: message every non-reply once with a price-holds-through-day-30 line.
Message template
Hi [name] — I ran a handover dossier on your public repo [repo] and it is here: [link]. It maps hotspots, dependency risk and env vars into a client-ready PDF. If you have a closeout this month, your private repo takes ~15 min and is $199. Want me to walk you through it live?
30-day execution roadmap
Week 1 · Build & validate · 7 days
Collector skeleton
- Scaffold the npm package with TypeScript, simple-git and fast-glob.
- Write the metrics JSON schema v1.
Deliverable: CLI that prints a metrics JSON for a local repo.
Git and dependency metrics
- Implement per-file commits, author spread, lines changed and file age.
- Parse package.json and lockfiles into the same JSON.
Deliverable: Complete metrics file on three test repos.
Scoring and risk table
- Score hotspots as churn times size times recency.
- Flag untested files as landmines and query OSV.dev for CVEs.
- Emit a suggested upgrade order.
Deliverable: Hotspot and CVE sections present in the metrics JSON.
Web app and dossier
- Build the Next.js upload route with a Supabase job record.
- Render the six dossier sections in HTML.
- Add the metrics-only LLM narrative call.
Deliverable: End-to-end upload to HTML dossier.
Pay, PDF and ship
- Add Playwright PDF with agency logo and accent color.
- Wire the Stripe Payment Link unlock and Resend email.
- Ship the watermarked two-section preview.
Deliverable: Live MVP with a working $199 checkout, MVP deadline.
QA on real repos
- Run the collector on five public agency repos.
- Fix thin-history output and hallucinated file names.
Deliverable: Five clean sample dossiers.
Prospect list
- Build a 150-row agency list with repo URL and owner contact.
- Filter to shops with a public GitHub org and an active owner.
Deliverable: 150-row prospect spreadsheet.
Week 2 · Launch & first sale · 7 days
Sample generation
- Generate 30 watermarked dossiers branded per agency.
- Set up a reply and sale tracking sheet.
Deliverable: 30 ready-to-send samples.
First outreach wave
- Send 30 X and LinkedIn DMs with the sample attached.
- Log every reply in the tracking sheet.
Deliverable: 30 DMs sent, replies logged.
Second wave and community post
- Send 30 more DMs with a sharper first line.
- Post an anonymized sample in two agency communities.
Deliverable: 60 DMs sent, two community posts live.
First sale
- Follow up the day-9 batch with the closeout checklist.
- Walk one warm prospect through the CLI live and unlock the PDF on the call.
Deliverable: First paying customer, first-sale target day.
Convert and learn
- Send 30 DMs reusing language from the first buyer.
- Ask the buyer for a one-line quote.
Deliverable: 90 DMs sent, one quote collected.
Third wave
- Send 30 DMs.
- Offer the Agency Pack to any buyer with a second closeout.
Deliverable: 120 DMs sent, pack offered at least three times.
Week-2 funnel review
- Compute reply, call and paid rates per wave.
- Rewrite or retire the weakest message.
Deliverable: Revised script and updated funnel numbers.
Week 3 · Repeat & systematize · 7 days
Agency Pack
- Ship the $499 checkout with credit tracking.
- Add a saved branding preset.
Deliverable: Agency Pack live and purchasable.
Outreach wave four
- Send 30 DMs.
- Pitch the pack in every call.
Deliverable: 150 DMs sent.
Follow-up and calls
- Follow up all unanswered DMs once.
- Run two demo calls.
Deliverable: Five warm prospects in pipeline.
Free checklist page
- Publish a one-page closeout checklist on the site.
- Post it in two communities with the sample as the CTA.
Deliverable: Checklist page live and posted.
Outreach wave five
- Send 30 DMs leading with the checklist.
- Log which opener converts.
Deliverable: 180 DMs sent, opener comparison logged.
Quality patch
- Fix the three most common dossier complaints.
- Add a data-coverage note to every report.
Deliverable: v1.1 dossier quality patch shipped.
Week-3 review and upsell
- Tally collected revenue and costs.
- Upsell every single-dossier buyer to the pack.
Deliverable: Revenue statement and at least one pack attempt per buyer.
Week 4 · Scale what works · 7 days
Invoice-blocked angle
- Send 30 DMs framed around the final invoice waiting on documentation.
- Log objection types.
Deliverable: 210 DMs sent, objection log started.
Case study thread
- Publish a before-and-after dossier thread on X, anonymized.
- Reply to every comment with the free sample offer.
Deliverable: Case study thread live.
Contract-objection handling
- Send 30 DMs with a one-line local-collector security note.
- Update the site FAQ with the same sentence.
Deliverable: 240 DMs sent, FAQ updated.
Demand capture
- Follow up all warm threads.
- Book three calls for days 26-28.
Deliverable: Three calls booked.
Client sign-off checklist
- Ship a client sign-off checklist section inside the PDF.
- Re-render two past dossiers for free.
Deliverable: Sign-off feature shipped, retention gesture made.
Outreach wave six
- Send 30 DMs.
- Post the checklist in a third community.
Deliverable: 270 DMs sent across the 30 days.
Revenue accounting
- Reconcile Stripe payouts against costs.
- Rank channels by paid conversions and keep the top one.
Deliverable: Verified collected-revenue and profit statement.
Days 29-30 · Consolidate · 2 days
Pipeline close
- Message every non-reply once with a day-30 price hold.
- Close the warm pipeline on calls.
Deliverable: Remaining warm deals closed or marked dead.
Wrap and referrals
- Ask every buyer for one agency referral by name.
- Publish final 30-day numbers and freeze the roadmap.
Deliverable: Final revenue report and referral asks sent.
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
- Blended revenue per buyer is $199 for single dossiers and $244 when three in twenty upgrade to the $499 pack.
- DMs to 150-200 agency owners convert at roughly 10 percent to paid within 30 days in the base case.
- Average cost per dossier is under $12 including LLM tokens and PDF rendering.
- Stripe fees are about 3 percent of collected revenue.
- Fixed monthly cost is under $45 for hosting, database and email.
- No paid ads, no contractors and no inventory are used.
- All figures are projections produced before launch, not verified revenue.
Conservative
3 customers- Refunds
- n/a
- Chargebacks
- n/a
- Payment fees
- n/a
- Paid marketing
- n/a
- Hackathon profit
- n/a
- Operating costs
- n/a
- Business profit
- n/a
Pre-breakdown estimate. This report was generated before costs were itemised, so refunds, fees, ad spend and operating costs cannot be separated without inventing them. Nothing is estimated here. Original modelled profit (all costs included): $542.
Base case
9 customers- Refunds
- n/a
- Chargebacks
- n/a
- Payment fees
- n/a
- Paid marketing
- n/a
- Hackathon profit
- n/a
- Operating costs
- n/a
- Business profit
- n/a
Pre-breakdown estimate. This report was generated before costs were itemised, so refunds, fees, ad spend and operating costs cannot be separated without inventing them. Nothing is estimated here. Original modelled profit (all costs included): $1,968.
Optimistic
20 customers- Refunds
- n/a
- Chargebacks
- n/a
- Payment fees
- n/a
- Paid marketing
- n/a
- Hackathon profit
- n/a
- Operating costs
- n/a
- Business profit
- n/a
Pre-breakdown estimate. This report was generated before costs were itemised, so refunds, fees, ad spend and operating costs cannot be separated without inventing them. Nothing is estimated here. Original modelled profit (all costs included): $4,640.
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $1,791
- Payment fees (3.9%)
- $70
- Paid marketing
- $0
- Hackathon profit
- $1,721
- Business profit
- $1,721
Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.
These are projections, not verified revenue, customers or traction.
Main risks and validation experiments
Risk 1Closeout events are episodic, so 30 days of outreach may not overlap with enough live closeouts.
Ask every prospect whether a closeout lands inside 30 days and prioritise those who say yes.
Ask 20 prospects directly and count how many have a closeout within 30 days.
Fewer than 5 of 20 prospects report a closeout inside 30 days after two waves.
Risk 2Owners decide the client does not actually require documentation and skip the purchase.
Lead with the free closeout checklist so the buyer keeps the value even without buying.
Send 15 DMs leading with the checklist and measure replies over four days.
Zero replies to the checklist opener after 15 sends.
Risk 3Free-sample outreach reads as unsolicited use of a public repository.
Offer a permission-first variant and keep samples to public, permissively licensed repositories only.
Run two message variants, permission-first versus sample-attached, on 30 prospects each and compare negative replies.
More than 3 negative or takedown replies in 60 sends.
Risk 4Dossiers can be thin or embarrassing when git history is squashed or the repo is young.
Detect low data coverage, add fallback evidence and refund any report below the coverage floor.
Generate ten dossiers on repos of varying history depth and score coverage manually.
More than 2 of 10 dossiers judged too thin to show a client.
Risk 5The wrong hotspot or landmine call reaches a client and damages the agency relationship.
Label every finding as a signal with confidence, and require the agency to review before export.
Have two agency owners review a sample and flag any claim they would not send.
Any reviewer says they would not send the report to a client even after editing.
Hour-by-hour: the first 24 hours
Hours 1-2
- Scaffold the npm package with TypeScript, simple-git and fast-glob.
- Write and commit the metrics JSON schema v1.
Output: Repository with package skeleton and schema file.
Hours 3-5
- Implement per-file commit counts, author spread, lines changed and file age.
- Print the metrics JSON for the founder's own repo.
Output: Working git-history collector.
Hours 6-7
- Parse package.json and lockfile dependencies into the same JSON.
- Include env variable names from .env.example.
Output: Dependency and env section in the metrics file.
Hours 8-9
- Draft the six dossier section templates.
- Draft the DM message and the free-sample offer.
Output: Section templates and outreach copy.
Hours 10-12
- Register the domain and Stripe account.
- Create the $199 Payment Link and the $499 pack link.
Output: Live payment links ready for day 5.
Full 30-day launch report
Read the full generated report
Handover Dossier, 30-Day Solo Launch Report
1. Product opportunity and positioning
Handover Dossier sells one document: the client-ready handover pack a small dev agency owes at project closeout. Today that document costs one to two senior developer days, is the least billable work in the project, and sits between the agency and its final invoice. The buyer is the owner or lead developer of a 3-15 person web or mobile agency in the US, UK, Canada or Australia, reached in the week a client engagement closes.
The wedge is narrow on purpose. JEV scored this concept 59.7/100 (band C), with speed to first revenue (7.08) and solo build feasibility (7.4) as its strongest criteria and market demand (3.84) as its weakest. This plan attacks that weakness directly: it does not wait for inbound demand, it manufactures urgency by putting a finished, agency-branded dossier in front of an owner who already has a closeout on the calendar. Monetization (4.97) is answered by a $199 single dossier plus a $499 five-pack that turns episodic closeouts into a repeat purchase.
The differentiation is the delivery mechanism, not the AI. The collector runs on the buyer's own machine and uploads metrics only: file paths, churn counts, dependency names and versions, environment variable names. No source lines leave the laptop. That one choice removes the security objection that kills most agency tool sales, and it makes the deliverable producible in roughly 15 minutes, on the same call where it is sold.
The trigger is dated and the price sits under an owner's approval threshold. That combination, not market size, is the bet: a $199 charge approved without a second signature, on a project that is already invoicing, for a document the client already expects.
2. Smallest sellable MVP
Four things must exist for money to change hands: the collector on npm, the upload and dossier renderer, the branded PDF export, and a Stripe Payment Link that unlocks both. The six fixed sections are executive summary, module map, hotspot ranking, landmine list, dependency and CVE table with suggested upgrade order, and onboarding runbook with open questions. The free watermarked preview of the first two sections is the sales artifact. Explicitly not built: PR bot, GitHub Action, code fixes, monitoring, IDE plugin, team accounts, source upload, procurement support.
3. Technical implementation plan
Build order maps to five days. Day 1 is the CLI skeleton and schema. Day 2 is git history and dependency extraction. Day 3 is hotspot scoring, landmine flags and OSV.dev lookups. Day 4 is the Next.js upload, Supabase job record and HTML render. Day 5 is Playwright PDF, the Stripe webhook and Resend delivery.
The LLM writes only the narrative sections and is constrained to the uploaded metrics JSON. File names and dependency versions are injected verbatim from the file, never generated, and a second pass rejects any mention of a path or package absent from the metrics. The hardest risk is thin or squashed git history producing an empty-feeling dossier; the fix is lockfile, CI-config and directory-evidence fallbacks plus an explicit data-coverage note so the buyer sees what the report could and could not see.
4. Pricing and monetization
Single Dossier at $199 one time, Agency Pack at $499 for five dossiers over 12 months, watermarked preview at zero. Expected blended revenue per buyer lands between $199 and $244 depending on pack mix. The only upsell is the pack, offered to any buyer who names a second closeout in the same conversation and to every past buyer in week 3.
5. First-customer acquisition
One channel: direct X and LinkedIn DMs to agency owners, each carrying a free watermarked dossier generated from that agency's own public repository. Build a 150-row list by day 7, send in waves of 30 from day 9, follow up once after four days, and post anonymized samples in two agency communities. The base case assumes about 10 percent of the reached list converts inside 30 days.
6. 30-day execution roadmap
Days 1-5 build the MVP, ending day 5 with a live $199 checkout. Day 6 is QA on five public repositories. Day 7 builds the list; days 8-10 produce samples and send the first 60 DMs plus two community posts. Day 11 is the first-sale target, closed by walking a warm prospect through the CLI live and unlocking the PDF on the call. Days 12-20 run three further waves, ship the $499 pack, publish a free closeout checklist page and patch the top quality complaints. Days 21-28 tally revenue, run the invoice-blocked angle, publish a case study thread and ship a client sign-off checklist. Days 29-30 close the warm pipeline and ask every buyer for one named referral.
7. Revenue and profit scenarios
All figures are projections, not verified revenue. Conservative: 3 buyers at $199, $597 revenue, $55 costs, $542 profit. Base: 9 buyers at $232 blended, $2,088 revenue, $120 costs, $1,968 profit. Upside: 20 buyers at $244 blended with three pack upgrades, $4,880 revenue, $240 costs, $4,640 profit. Costs cover Stripe fees, hosting, npm, LLM tokens and email. None of this describes existing customers, signed contracts or collected money.
8. Main risks and validation experiments
First, closeouts are episodic: ask 20 prospects whether a closeout lands inside 30 days, and kill the segment if fewer than 5 say yes. Second, owners may decide the client does not need documentation: send 15 checklist-first DMs and abandon that angle on zero replies in four days. Third, free-sample outreach may read as unsolicited use of a public repository: run permission-first versus sample-attached variants on 30 prospects each and stop if more than 3 negatives appear in 60 sends. Fourth, thin repositories produce weak reports: score coverage on ten repos and refund anything below the floor. Fifth, a wrong landmine call could reach a client: label findings as signals and require agency review before export.
9. First 24 hours
Hours 1-2 scaffold the npm package and commit the metrics schema. Hours 3-5 implement git-history metrics and print the JSON for the founder's own repo. Hours 6-7 add dependency and env extraction. Hours 8-9 draft the six section templates and the DM message. Hours 10-12 register the domain, create the Stripe Payment Links and set up Resend so day 5 ships with payments already wired.
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 →Repo Second Opinion
A paid, plain-English code risk report for non-technical founders who paid an agency or freelancer to build their app and now need to know if the code is safe to keep building on.
ReviewReady Packet
Generates a reviewer-ready Meta App Review submission bundle — per-permission justifications, screencast script, test-account steps and deauth code — for solo devs and small agencies stuck at 'rejected'.
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.