Doc Decay Scanner
Crawls a SaaS company's public help center, scores every article for decay, and delivers a prioritized fix queue plus ten ready-to-paste rewritten articles for $199.
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 Support, Docs Lead, or founder-operator at a 20-200 person B2B SaaS with a public help center (Intercom, Zendesk, GitBook, Docusaurus), 50-500 published articles, shipping product changes monthly.
Market demand 3.3/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 12; strongest signal is speed to first revenue at 8.2/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 Support, Docs Lead, or founder-operator at a 20-200 person B2B SaaS with a public help center (Intercom, Zendesk, GitBook, Docusaurus), 50-500 published articles, shipping product changes monthly.
Why now
Solo founders can now crawl headlessly, embed for duplicate detection, and generate rewrites on managed APIs for a few dollars per report, so a $199 fixed-price audit with real margins is deliverable by one person in days.
Problem
The public help center has rotted silently: dead outbound links, screenshots of removed UI, near-duplicate articles, and pages untouched for two years. Nobody has time to audit 300 articles by hand.
Solution
The buyer submits a help center URL, gets a free 0-100 score with three real findings, then pays $199 to unlock the full prioritized fix queue with quoted defects and URLs, plus LLM rewrites of the ten worst articles exported as Markdown or HTML.
JEV scored this concept 58.3/100 (band C, confidence 0.69). Read the sub-scores as a build order, not a verdict. Speed to first revenue (8.21) and reachable customers (7.32) carry the plan: the prospect list is public, the proof point is generated before the buyer pays, and no integration gate stands between a scan and a charge. Market demand (3.26) and operational simplicity (4.87) are the weak points, and the 30 days are shaped to route around them.
Demand scores low because "our docs are stale" is a chronic complaint, not an urgent one. The plan attaches to a trigger the buyer already feels: a ticket queue fed by articles nobody trusts, or a release that just invalidated thirty screenshots. An email that says "your article <title> links to a 404 and still shows the old Settings UI" converts a chronic gripe into a dated, checkable event.
Positioning: Doc Decay Scanner does not ask anyone to adopt a wiki. It audits the help center a company already publishes, at a fixed $199, and returns a prioritized fix queue plus ten rewritten articles. The deliverable exists before the payment clears, so the decision is whether ten fixed articles are worth $199, not whether the team wants to migrate its knowledge base.
Why not the generic alternative (Notion, Confluence, Slite, Guru, Tettra): those are subscriptions that relocate the maintenance tax onto the same person already failing to maintain the docs. This is a one-time, externally verifiable artifact with no login, no seat count, and no security review. The buyer's manager can open the hosted report and click every finding back to the live article, which makes internal justification trivial.
Defensibility is modest (6.27) and that is fine for a 30-day sprint. The moat is not the crawler; it is the prospect graph. Every scan produces a real defect, every defect produces a personalized email subject, and every re-scan produces a reason to follow up on day 3 and day 7. That compounding list, plus the optional $49/mo monitor, is what turns a one-off audit into a repeat purchase and answers JEV's monetization critique (4.58).
The competitive risk is real: help-center platforms could ship native decay reporting. The hedge is price and packaging, not features. A Zendesk add-on will be a dashboard inside a contract; this is a $199 PDF a Docs Lead can expense this week without talking to procurement. Operational simplicity is addressed by keeping the system stateless: no CMS write-back, no accounts, no human review step, magic-link delivery only.
Smallest sellable MVP
A URL intake form that crawls a public help center, computes a 0-100 decay score with a prioritized fix queue, generates ten rewritten articles, and unlocks the full report behind a $199 Stripe Checkout — all hosted, no account.
Must-have features
- Sitemap-first headless crawl storing title, HTML, images, outbound links and last-modified per article
- Decay engine: broken outbound links, missing images, article age, duplicate clusters via embeddings, orphan pages, deprecated-term matches
- Public free-scan page showing the 0-100 score and three real findings before an email gate
- Hosted report with a prioritized queue where every item quotes the offending sentence and links the live URL
- LLM rewrite of the ten highest-impact articles with before/after diff and Markdown/HTML export
- Stripe Checkout that unlocks the report via magic link, no account required
Explicitly out of scope
- CMS write-back into Zendesk, Intercom or GitBook
- Internal wiki, Slack ingestion or SOP capture
- AI chat assistant over the docs
- Multi-seat permissions, SSO or admin console
- Done-for-you human editing
- Net-new SEO article generation
- Non-English decay lexicons in v1
- Bulk multi-domain dashboards for agencies
Demo flow (what the buyer sees)
- Buyer pastes a help center URL on the free-scan page
- Crawler pulls every article from the sitemap and stores structured fields
- Decay engine scores each article and rolls up a 0-100 health score
- Page shows the score plus three findings with live links and asks for an email
- Email delivers a magic link to the gated report and the $199 unlock
- Stripe Checkout returns the buyer to the unlocked queue, rewrites and exports
Technical implementation plan
Stack
Architecture
A single Next.js app on Vercel handles intake, the scan job, the hosted report and Checkout. The crawl runs in a background route with a per-domain timeout that tries sitemap.xml first and falls back to nav-link discovery, writing articles into Supabase. A scoring job then issues HEAD requests for outbound links, checks image URLs, buckets articles by last-modified age, embeds article bodies to cluster duplicates by cosine similarity, and computes inbound-link counts to find orphans. Each finding row stores the quoted sentence, the article URL and a severity. The free page renders the score plus three findings; the paid page renders the full queue and the rewrite diffs. Rewrites are generated lazily only after payment so unpaid scans cost only crawl and embedding tokens. A signed token in the magic link authorizes report access without accounts.
Build steps
- Register domain, deploy Next.js skeleton to Vercel, create Supabase tables (scans, articles, findings, orders)
- Implement sitemap-first crawler with Playwright fallback, per-domain timeout and block detection
- Add broken-link HEAD checker with 8s timeout and one retry, plus missing-image detection
- Implement embedding-based duplicate clustering and orphan-page detection
- Compute the 0-100 score with weighted penalties and persist the ranked findings
- Build /scan/[id] free page with score, three findings and email gate
- Add Stripe Checkout, order webhook, signed magic-link access and the unlocked report page
- Add the rewrite engine with before/after diff and Markdown/HTML/PDF export
- Run 40 real domains through the pipeline, fix the three worst failures, publish a sample report
AI components
- OpenAI embeddings to cluster near-duplicate articles by cosine similarity
- GPT-class rewrite of the ten highest-impact articles with full source text in the prompt
- LLM extraction of the offending sentence span for each finding to make the quote exact
Pricing and monetization
Free Scan
Entry offerFor Anyone with a public help center URL
- 0-100 health score
- Top three findings with live links
- Email-gated full report preview
Decay Report
For Support or docs lead who already saw real defects
- Full prioritized fix queue with quoted defects and URLs
- Ten LLM-rewritten articles with before/after diff
- Markdown and HTML export
- Hosted report link, no account needed
Monitor
For Teams shipping product changes weekly
- Monthly re-crawl
- New-defect email digest
- Refreshed rewrite queue
Model: Free scan to create the proof point, a $199 one-time report as the core sale, and a $49/month re-scan as the recurring path.
First revenue offer: A three-line email to a docs owner quoting one verified defect from their own help center, linking their free scan, and offering the full queue plus ten rewritten articles for $199 delivered within 24 hours of payment.
Expected ACV: $199
Upsell path: Every report buyer gets a $49/month monitor offer in the delivery email, with the first re-scan scheduled free; buyers who decline stay on a quarterly re-scan nudge, and multiple help centers at one company convert to a per-domain bundle.
First-customer acquisition
Personalized cold email to docs and support owners whose help centers have already been scanned, quoting one real defect in the subject line.
Where to find them
- Intercom 'Powered by Intercom' help center footers on B2B SaaS product sites
- Zendesk-hosted subdomains (support.example.com, help.example.com)
- GitBook and Docusaurus public docs sites linked from product nav bars
- Product Hunt and Indie Hackers launches from the last 18 months with a linked help center
- Public API and integration directories of SaaS tools with per-feature documentation pages
- r/technicalwriting and r/CustomerSuccess threads asking about documentation maintenance
Exact outreach motions
- Batch-scan 400 candidate domains and keep only those with 5+ mechanical defects
- Email 1: subject line quotes the literal defect, body links the free scan and states the $199 unlock
- Day-3 follow-up: same thread, one newly detected defect from a fresh crawl
- Day-7 follow-up: offer to hold the report open for 48 hours and name the specific article rewritten first
- Reply handling: if the prospect questions a finding, reply with the exact HTTP status and timestamp
- Referral ask after delivery: one intro to another docs owner, re-scan offered free
Message template
Subject: your article "Set up SSO" links to a 404
Hi {first}, I scanned {domain}'s help center this morning — 34 of 212 articles have at least one broken outbound link or missing image, and "Set up SSO" still shows the pre-2024 Settings UI. Your score is {score}/100 here: {scan_link}. The full queue plus ten rewritten articles is $199, delivered within 24 hours: {checkout_link}. No account needed. — {founder}30-day execution roadmap
Week 1 · Build & validate · 7 days
Domain, database, payments, prospect seed
- Register the domain and deploy the Next.js skeleton to Vercel.
- Create Supabase tables for scans, articles, findings and orders.
- Connect Stripe to TrustMRR and pass a test-mode checkout.
- Start the prospect sheet with the first 60 help center URLs.
Deliverable: Live domain, empty schema, working Stripe test charge, 60 prospects logged.
Sitemap-first headless crawl
- Implement sitemap.xml discovery with nav-link fallback.
- Add Playwright rendering for JS-heavy help centers.
- Store title, HTML, images, outbound links and last-modified per article.
- Run 20 domains and log the block rate.
Deliverable: Crawler extracts 1,000+ articles across 20 domains with a measured block rate.
Mechanical defects and scoring
- Add broken-link HEAD checks with an 8s timeout and one retry.
- Detect missing images and bucket articles by last-modified age.
- Cluster near-duplicates using OpenAI embeddings at cosine 0.92.
- Detect orphan articles via inbound internal link counts.
Deliverable: A 0-100 score and ranked findings for all 20 test domains.
Public score page and email gate
- Build the URL intake form that queues a scan job.
- Render /scan/[id] with the score and three findings.
- Gate the full report behind an email field.
- Send the magic link through Resend.
Deliverable: Public free-scan flow working end to end on a real URL.
Stripe unlock and ten rewritten articles
- Wire Stripe Checkout at $199 with an order webhook.
- Unlock the hosted report through a signed magic link.
- Generate ten rewrites with before/after diff.
- Add Markdown, HTML and PDF export.
Deliverable: MVP is live and sellable: free scan, $199 unlock, full report, exports.
Fix the pipeline before sending anything
- Run 40 real domains through the full pipeline.
- Fix the three highest-frequency failures.
- Publish the landing page with a sample report.
- Write the refund policy: full refund within 24 hours on request.
Deliverable: 40 clean scans, public landing page, published sample report.
First 60 personalized emails
- Send 60 emails quoting a verified defect each.
- Load the day-3 and day-7 follow-up sequence.
- Post the free scan in two documentation communities.
- Log every reply in the prospect sheet.
Deliverable: 60 emails sent, follow-ups queued, first replies logged.
Week 2 · Launch & first sale · 7 days
Volume and fast reply handling
- Send 80 more personalized emails.
- Reply to every inbound message within two hours.
- Fix any finding a prospect disputes.
- Scan 60 new domains from GitBook footers.
Deliverable: 140 total emails sent, median reply time under two hours.
Subject-line iteration
- Send 80 emails using the best-performing defect type as the subject.
- A/B the defect-quote versus score subjects on 40 sends each.
- Add a plain-text checkout link to shorten the path.
- Update the free-scan page copy with the top objection seen.
Deliverable: 220 total emails sent and a chosen subject-line winner.
Day-3 follow-ups with fresh evidence
- Send day-3 follow-ups to all non-openers.
- Re-crawl five domains to surface a genuinely new defect.
- Offer a 15-minute screen share to the five warmest replies.
- Trim the prospect sheet of dead or unlinked domains.
Deliverable: Day-3 wave sent, five calls proposed.
Reach 400 scanned domains
- Add 100 Zendesk-hosted subdomains to the sheet.
- Batch-scan the new domains overnight.
- Send 100 emails to the highest defect-density newcomers.
- Confirm delivery cost per scan stays under $3.
Deliverable: 400 domains scanned, 320 emails sent.
Convert warm replies
- Send a direct $199 offer to the ten warmest leads.
- Run one live screen-share scan with a prospect.
- Offer to start the rewrite on their worst article first.
- Track time from reply to checkout link.
Deliverable: First paid $199 report collected through Stripe.
Deliver fast and ask for proof
- Deliver every purchased report within 24 hours.
- Ask each buyer for a one-line quote and a permission to anonymize.
- Refund immediately if a report is judged wrong.
- Log the exact defect types buyers cared about.
Deliverable: All sold reports delivered, first written feedback captured.
Introduce recurring revenue
- Email every buyer the $49/month monitor offer.
- Schedule the first free re-scan for each buyer.
- Review the week: sends, replies, sales, refunds.
- Double down on the single best-performing email angle.
Deliverable: Monitor offers sent, week-two funnel numbers written down.
Week 3 · Repeat & systematize · 7 days
120 sends at higher density
- Send 120 emails to domains with 10+ defects.
- Segment the sheet by help-center platform.
- Add a one-click sample report link per segment.
- Log block rate per platform to find crawl gaps.
Deliverable: 440 emails cumulative with a platform-level defect map.
Cut refunds at the source
- Add a style guide and full source text to the rewrite prompt.
- Review three sample rewrites line by line.
- Strip invented facts by instructing the model to reuse only source sentences.
- Add a visible 'changed' diff highlight to exports.
Deliverable: Rewrite v2 with a documented prompt and a QA checklist.
Keep delivery under $3
- Cache crawl results per domain for 24 hours.
- Batch embeddings in one call per domain.
- Move rewrites to a lazy post-payment job only.
- Measure median scan duration end to end.
Deliverable: Documented cost per report and median scan time.
Sustain the pipeline
- Send 120 emails with day-3 follow-ups.
- Push the monitor offer to non-buyers who replied.
- Ask two warm prospects what would make them buy today.
- Refresh the prospect sheet to 500 domains.
Deliverable: 560 emails cumulative, 500 scanned domains in the sheet.
Turn buyers into leads
- Ask every buyer for one intro to another docs owner.
- Offer a free re-scan for each completed intro.
- Scan the introduced domains the same day.
- Send the intro email within an hour of the ask.
Deliverable: Referral ask sent to all buyers, introduced domains scanned.
Publish the artifact
- Publish a full sample report for a public open-source docs site with attribution.
- Post it to r/technicalwriting and Indie Hackers.
- Add the sample link to every outbound email footer.
- Track inbound free scans from the post.
Deliverable: Public sample report live and cited in all outreach.
Refund and funnel audit
- Audit every refund and chargeback for a shared cause.
- Compare close rate by email angle and segment.
- Cut the two worst-performing subject lines.
- Recompute cost per acquired customer.
Deliverable: Written funnel audit with the next week's angle chosen.
Week 4 · Scale what works · 7 days
Technical docs buyers
- Build a 100-domain list of developer docs on Docusaurus and GitBook.
- Adapt the email to version-drift defects instead of UI drift.
- Scan all 100 and rank by defect density.
- Send 100 segment-specific emails.
Deliverable: 100 developer-docs emails sent with a version-drift angle.
Recurring revenue
- Email the $49/month monitor to every scanned prospect who never bought.
- Frame it as weekly drift detection, not another audit.
- Offer a two-month trial price of $99.
- Track activation and month-one retention signals.
Deliverable: Monitor campaign sent with a tracked trial-price response rate.
Repeatable sending
- Send 120 emails with refreshed defects.
- Follow up on all day-3 non-responders.
- Reply to every objection with a concrete finding.
- Re-scan the ten most engaged domains.
Deliverable: 680 emails cumulative, engagement list re-scanned.
Fix the top complaint
- Identify the single most common refund reason.
- Ship the narrow fix that removes it.
- Proactively re-send corrected reports to affected buyers.
- Add the fix to the pre-purchase page copy.
Deliverable: Refund cause fixed and disclosed pre-purchase.
Volume peak
- Send 150 emails to fresh high-defect domains.
- Refresh the prospect sheet to 700 scanned domains.
- Prioritize founders and Heads of Support over generic addresses.
- Log reply rate by recipient title.
Deliverable: 830 emails cumulative with reply rate by buyer title.
Show the rewrite quality
- Publish a second sample audit focused on rewritten articles only.
- Add a side-by-side diff view to the public page.
- Link it from the checkout page as pre-purchase proof.
- Measure checkout conversion before and after.
Deliverable: Rewrite-focused sample page live with before/after conversion data.
Raise average order value
- Offer a $249 bundle (report plus three months of monitor) to new prospects.
- Split 50 emails each between $199 and $249.
- Keep the $199 single report available for every buyer.
- Record which price wins on total collected revenue.
Deliverable: Price split run with a documented winner.
Days 29-30 · Consolidate · 2 days
Deadline urgency
- Send 150 emails with a deadline-framed offer.
- Re-offer to every warm lead who never replied.
- Deliver all outstanding reports within 24 hours.
- Confirm every payment landed inside the window.
Deliverable: 980 emails cumulative, all deliverables closed out.
Verified profit and post-mortem
- Match Stripe payouts against TrustMRR records.
- Process any remaining refunds before the window closes.
- Write the post-mortem: close rate by angle, cost per report, refund rate.
- Decide whether the monitor graduates to the next 30 days.
Deliverable: Reconciled revenue figure and a one-page post-mortem.
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 are projections from stated assumptions, not verified revenue.
- Conservative: 3 sales from ~980 cold emails, roughly a 0.3% close rate.
- Base: 8 sales from ~980 cold emails, roughly a 0.8% close rate.
- Upside: 20 sales from ~980 cold emails plus referral and community inbound, roughly a 2% close rate.
- ARPU is held at $199 in every scenario; Monitor subscriptions are excluded from 30-day revenue to keep the model conservative.
- Payment fees assume 4% blended on collected revenue (Stripe 2.9% + $0.30 domestic, higher on international cards).
- Ad spend is $0 because the only channel is organic cold email and community posting.
- Operating costs cover Vercel, Supabase, domain, Resend and crawl plus LLM tokens at roughly $2-$3 per delivered report.
- Refund rate assumes under 10% of sales, concentrated in rewrite-quality complaints.
- No first-30-day buyer requires CMS write-back, a contract, or a security review.
Conservative
3 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $24
- Paid marketing
- $0
- Hackathon profit
- $573
- Operating costs
- $30
- Business profit
- $543
Base case
8 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $64
- Paid marketing
- $0
- Hackathon profit
- $1,528
- Operating costs
- $60
- Business profit
- $1,468
Optimistic
20 customers- Refunds
- $199
- Chargebacks
- $0
- Payment fees
- $159
- Paid marketing
- $0
- Hackathon profit
- $3,622
- Operating costs
- $150
- Business profit
- $3,472
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $392
- Payment fees (3.9%)
- $15
- Paid marketing
- $0
- Hackathon profit
- $377
- Business profit
- $317
Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.
All scenarios are projections derived from stated assumptions. They are not verified revenue, not existing customers, and not a forecast. Actual results may be zero.
Main risks and validation experiments
Risk 1Cold email deliverability collapses because a brand-new domain sends ~980 emails in 30 days.
Warm the domain for 5 days, cap at 40 sends per day per mailbox, use plain text with one link, and keep a secondary mailbox ready.
Send 30 emails on day 7 and measure delivered-versus-bounced and any open signal within 48 hours.
If open signal is under 10% after 150 sends and the domain is not blacklisted, switch to community posting and direct replies to public docs-complaint threads.
Risk 2Bot protection blocks crawling on a large share of help centers, shrinking the usable prospect list.
Sitemap-first with a nav fallback, an 8s timeout, and an automatic refusal to sell a report on a domain that failed to crawl cleanly.
Crawl 40 domains on day 6 and log the percentage returning fewer than 20 articles.
If more than 50% of targets fail to crawl, re-target Docusaurus and GitBook static docs where crawling is reliable.
Risk 3Buyers treat the $199 report as a one-off and never take the $49/month monitor, capping revenue per customer.
Include the first re-scan free in the delivery email and frame the monitor as weekly drift detection tied to their release cadence.
Offer the monitor to the first three buyers and measure acceptance within 7 days.
If zero of the first five buyers accept the monitor, drop recurring positioning and push the $249 report-plus-monitor bundle instead.
Risk 4Rewrite quality complaints drive refunds and chargebacks that reduce verified profit directly.
Supply full source text in the prompt, instruct the model to reuse only source sentences, QA three samples manually, and refund within 24 hours on request.
Have three peers review ten rewrites for factual drift before the first paid delivery.
If more than 20% of delivered reports draw a factual-accuracy complaint, ship report-only at $99 and remove the rewrite promise.
Risk 5A realistic low close rate yields only a handful of sales and the sprint misses its revenue target.
Keep the free scan as a compounding asset, run day-3 and day-7 follow-ups with fresh defects, and expand the list to 700 scanned domains by day 26.
Track close rate by email angle after 200 sends and reallocate to the winning angle.
If there are no sales after 400 emails with verified defects, change the price point to $99 or change the buyer to founder-operators at sub-20-person SaaS.
Hour-by-hour: the first 24 hours
Hours 1-2
- Register the domain and deploy the Next.js skeleton to Vercel.
- Create the Supabase project and the scans, articles, findings and orders tables.
Output: Live URL and an empty but queryable schema.
Hours 3-5
- Implement the sitemap-first crawler with an 8s per-domain timeout.
- Run it against five known help centers and inspect the stored article fields.
Output: Crawler that writes article rows for at least five real domains.
Hours 6-9
- Add the broken-link HEAD checker and missing-image detector.
- Compute a first-pass 0-100 score from link and image defects only.
Output: Working score output for the five test domains.
Hours 10-13
- Build the free-scan intake form and /scan/[id] results page.
- Wire the email gate and Resend magic link delivery.
Output: A public scan page a stranger could use.
Hours 14-17
- Connect Stripe to TrustMRR and create the $199 Checkout link.
- Log the first 60 prospect URLs into the sheet and queue their scans.
Output: Test-mode payment path plus 60 queued prospect domains.
Full 30-day launch report
Read the full generated report
Doc Decay Scanner — 30-Day Solo Launch Plan
Window: 16 Nov 2026 13:00 UTC to 16 Dec 2026 13:00 UTC. One founder, one product, one channel, no funding.
1. Product opportunity and positioning
JEV scored this concept 58.3/100 (band C, confidence 0.69). Read the sub-scores as a build order. Speed to first revenue (8.21) and reachable customers (7.32) carry the plan: the prospect list is public, the proof point is generated before the buyer pays, and nothing sits between a scan and a charge. Market demand (3.26) and operational simplicity (4.87) are the weak points, and the 30 days are shaped around them.
Demand scores low because "our docs are stale" is a chronic complaint, not an urgent one. The plan attaches to a trigger the buyer already feels: a ticket queue fed by articles nobody trusts, or a release that just invalidated thirty screenshots. An email saying "your article links to a 404 and still shows the old Settings UI" turns a chronic gripe into a dated, checkable event.
The positioning is deliberately not a wiki. Doc Decay Scanner audits the help center a company already publishes at a fixed $199 and returns a prioritized fix queue plus ten rewritten articles. The deliverable exists before the payment clears. The only decision left is whether ten fixed articles are worth $199. Notion, Confluence, Slite and Guru all relocate the maintenance tax onto the same overloaded docs owner; this removes it for one week at a price nobody needs to approve.
Defensibility is modest at 6.27 and that is acceptable for a sprint. The moat is not the crawler, it is the prospect graph: every scan produces a real defect, every defect produces a personalized subject line, and every re-scan produces a reason to follow up.
2. Smallest sellable MVP
One input, one output, one paywall. A URL form crawls the help center, computes a 0-100 decay score, shows three real findings for free behind an email gate, and unlocks the full prioritized queue plus ten rewrites for $199 via hosted Checkout. No accounts, magic-link access only. Ten rewrites are generated lazily after payment so an unpaid scan costs cents; the target is under $3 per delivered report. Build time is four working days; the roadmap allows five before the first email goes out.
3. Technical implementation plan
One Next.js app on Vercel handles intake, scanning, the hosted report and Checkout. Supabase Postgres stores scans, articles, findings and orders. The crawler tries sitemap.xml first and falls back to navigation discovery, with Playwright only for JS-rendered help centers. Scoring issues HEAD requests for outbound links, checks image URLs, buckets articles by last-modified age, embeds bodies to cluster duplicates at cosine 0.92, and counts inbound internal links to flag orphans. Each finding stores the quoted sentence, the live URL and a severity so the report is clickable rather than assertive.
The hardest technical risk is bot protection producing empty crawls and therefore wrong scores. The product must refuse to sell on a domain it could not crawl cleanly; a refund is cheaper than a bad report.
4. Pricing and monetization
Free scan creates the proof. The $199 one-time Decay Report is the core sale and the number that appears in every email. The $49/month Monitor is the recurring path, offered in the delivery email with the first re-scan free. Average order value in this plan is $199; monitor revenue is excluded from all 30-day scenarios to stay conservative. A $249 bundle is tested on day 28.
5. First-customer acquisition
The only channel is personalized cold email to docs and support owners whose help center has already been scanned. Build 400-700 candidate domains from Intercom and Zendesk footers, GitBook and Docusaurus docs sites, and recent launches with a linked help center. Scan all of them, keep only domains with five or more mechanical defects, and rank by defect density. Send three lines quoting one literal defect, linking their scan, and stating the $199 unlock. Follow up on day 3 and day 7 with a newly detected defect from a fresh crawl. Deliver every paid report within 24 hours and refund on request within the same window.
6. 30-day execution roadmap
Days 1-5 build: foundation, crawler, decay engine, free scan, paywall. MVP is live on day 5. Days 6-7 are QA on 40 real domains plus the first 60 emails. Days 8-13 run three outreach batches, follow-up waves, and a warm-lead close push; the first paid report is targeted for day 12, delivered day 13. Day 14 introduces the monitor and reviews the funnel. Days 15-21 scale to 120 sends per batch, improve rewrite quality, cut delivery cost, launch a public sample report, and audit refunds. Days 22-28 add a developer-docs segment, run a monitor campaign, run a price split, and fix the top refund cause. Days 29-30 push deadline-framed volume, close out delivery, and reconcile Stripe against TrustMRR.
7. Revenue and profit scenarios
All figures are projections, not verified revenue. Conservative: 3 customers at $199, $597 gross, $24 in fees, $30 operating cost. Base: 8 customers, $1,592 gross, $64 in fees, $60 operating cost. Upside: 20 customers, $3,980 gross, one $199 refund, $159 in fees, $150 operating cost. Ad spend is zero in every case because the channel is organic. Hackathon profit subtracts refunds, chargebacks, fees and ad spend; business profit additionally subtracts hosting and API delivery cost. None of these numbers exist today.
8. Main risks and validation experiments
Deliverability: new domain, ~980 emails. Mitigation is a five-day warm-up and capped daily volume; validate with a 30-email test on day 7. Crawling: bot protection shrinks the list; validate by crawling 40 domains on day 6 and refusing to sell on failures. Recurring conversion: monitor may not sell; validate with the first three buyers before repositioning. Rewrite quality: factual drift causes refunds; peer-review ten rewrites before the first paid delivery and downgrade to a report-only $99 offer if complaints exceed 20%. Close rate: if 400 verified-defect emails produce zero sales, cut the price or narrow the buyer to founder-operators at sub-20-person SaaS.
9. First 24 hours
Hours 1-2: domain, Vercel deploy, Supabase schema. Hours 3-5: sitemap crawler running against five real help centers. Hours 6-9: broken-link and missing-image detection with a first-pass score. Hours 10-13: public scan page, email gate, magic link. Hours 14-17: Stripe test checkout and the first 60 prospect domains queued. The day ends with a working scanner and a filled pipeline, not a design document.
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.
ScopeLock Change Orders
Turns a client's out-of-scope request into a priced, signable change order PDF with a payment link in under two minutes, for solo freelancers and 2-10 person studios.