Score B · 6.86/10Free to read$100K Hackathon · November 16, 2026 → December 16, 2026Nov 15, 2026

ScopeLock Change Orders

ScopeLock turns a client's "quick extra" email into a priced, client-ready change order PDF, using the studio's saved rate card and original scope document.

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.

Promising6.86/10
MVP build (solo)
5 days
Launch price
$39
Sales to $1,000 revenue
26 customers
First paying customer
Personally generated free change-order PDFs delivered by DM or email to studio owners found complaining about scope creep in agency and freelance communities.
Who pays

Owner-operator of a 1-10 person design, development, video or marketing studio billing on fixed-scope contracts (US/UK/CA/AU), right after a client emails an unplanned addition mid-project.

Biggest execution risk

Operational simplicity 4.7/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 8; 26 sales at $39 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

10 concrete actions. Tick them off as you go — nothing is saved or sent.

0/10
Entry price
$39
Solo build
5 days
30d base revenue
$1,728
30d hackathon profit
$1,611
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operator of a 1-10 person design, development, video or marketing studio billing on fixed-scope contracts (US/UK/CA/AU), right after a client emails an unplanned addition mid-project.

Why now

Structured-output LLM extraction and serverless PDF rendering are now cheap and reliable enough to turn a 30-minute Word task into a 60-second review, at near-zero delivery cost.

Problem

Unbilled scope creep: writing a change order costs 20-40 minutes of admin plus a confrontational message, so owners absorb the extra work or delay delivery and lose hundreds to thousands per project.

Solution

Forward or paste the client thread; ScopeLock extracts requested additions, diffs them against the uploaded scope doc, prices only new items from the saved rate card, and returns a branded change order PDF plus a short client email.

Differentiation · A ChatGPT prompt gives prose with no scope diff, no rate-card arithmetic, no branding and no record of what was billed; ScopeLock returns the signed-ready document and keeps the studio's rate card and scope docs.

Fixed-scope studios lose money in one narrow, repeatable moment. A client emails a friendly addition, and the owner must either write a change order (20-40 minutes of admin plus a mildly confrontational message) or absorb the work. Absorbing usually wins, which is why the loss never appears on any invoice.

ScopeLock Change Orders attacks that moment and nothing else. The owner forwards the thread to a ScopeLock address or pastes it. The product extracts every requested addition, diffs the list against the original scope document uploaded once per client, marks each item in-scope or new, prices only the new items from a saved rate card, and returns a branded change order PDF with line items, subtotal, timeline impact and a signature block, plus a short client-facing email.

Positioning is not "AI for agencies". It is an artifact machine: one input (the client email), one output (a priced PDF the client can approve). The buyer already knows the money at stake because it is their own project, so no ROI argument or procurement cycle is needed. The purchase is a $99 card charge in the middle of a live dispute.

The alternative is a generic ChatGPT prompt. It produces unfenced prose with no scope diff, no rate-card arithmetic, no branding and no audit trail of what was billed. ScopeLock's edge is the classification pass plus the document, and the rate card, scope docs and client history accumulate per studio so month two is faster than month one.

JEV scored this concept 68.6/100 (band B). It is strongest on speed to first revenue (8.59/10) and reachable customers (8.13/10), weakest on operational simplicity (4.69/10). This plan answers that weakness directly: stateless jobs on managed services, no human review queue, no integrations, no team seats, no 24/7 support promise. Delivery cost per document is a few cents of inference plus hosting, so every sale at $39 or above clears its own cost by a wide margin.

Section 2 of 8

Smallest sellable MVP

A paste-or-forward intake that returns a watermarked priced change order PDF and a client email, gated by a Stripe checkout with a saved rate card and one uploaded scope document per client.

Must-have features

  • Paste box plus inbound forwarding address for a client thread and attachments
  • One scope-document upload per client (PDF/DOCX/text) with text extraction and chunking
  • Rate card editor with hour/day/fixed units, price and minimum increment
  • Three-call LLM pipeline with enforced JSON schema: extract, diff in-scope vs new, price
  • React-PDF change order with line items, subtotal, timeline delta and signature block
  • Stripe Checkout with document-count gating and watermark removal
  • Document history list with draft/sent/approved status and one-click email copy

Explicitly out of scope

  • E-signature or payment collection on the change order
  • Invoicing, accounting or the buyer's own Stripe sync
  • Asana, Jira, ClickUp or CRM integrations
  • Team seats, roles or approval chains
  • Mobile app
  • Custom or fine-tuned models
  • Human review queue or done-for-you service

Demo flow (what the buyer sees)

  1. Owner pastes a client email asking for two extra landing pages
  2. Owner selects client workspace with its uploaded scope doc and rate card
  3. Pipeline extracts items, marks one in-scope and two new
  4. Only new items are priced at the saved day rate
  5. Watermarked PDF and client email render for review
  6. Owner pays $39 or subscribes, downloads the clean PDF and sends it
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase (Postgres, storage, auth)Anthropic or OpenAI API with JSON-schema structured outputReact-PDF for document renderingResend for inbound and outbound emailStripe Checkout and Billing Portal

Architecture

A Next.js app on Vercel handles auth, the rate card and scope-doc uploads against Supabase Postgres and storage. Intake arrives two ways: a paste box, or Resend inbound email parsed into the same job record. A queued job runs three sequential model calls with enforced JSON schema (extract additions, classify against retrieved scope chunks, price new items). Pricing arithmetic runs in code from the saved rate card, never inside the model. The priced object renders through React-PDF to storage; unpaid documents carry a watermark and the download endpoint checks Stripe subscription or one-off credit before serving a clean file.

Build steps

  1. Define the extract/diff/price JSON schema and test it in a local script on five messy threads
  2. Stand up Next.js repo, Supabase project, auth and a protected dashboard shell
  3. Build rate card CRUD and scope-document upload with text extraction and chunking
  4. Implement the three-call pipeline endpoint with per-client scope retrieval and deterministic pricing in code
  5. Build the React-PDF template with watermark logic and the client-email generator
  6. Add Stripe Checkout, webhooks and document-count gating per plan
  7. Wire Resend inbound email into the same job pipeline
  8. Run twelve real-shaped threads, fix classification errors, ship edit-before-download
  9. Add document history with status and one-click email copy
  10. Instrument checkout funnel events and harden empty and error states

AI components

  • Extraction call: pull requested additions with verbatim quotes
  • Classification call: compare each item against retrieved scope-doc chunks and label in-scope or new
  • Pricing assist call: map new items to rate-card service items, with all arithmetic done in code
  • Client-email drafting call: short, non-defensive message referencing the attached change order
Hardest technical risk: Classification on threads where the client restates existing scope alongside genuinely new work; a wrong 'new' flag makes the studio look like it is nickel-and-diming its own client.
Section 3 of 8

Pricing and monetization

One-Off

Entry offer
$39 one-time

For Owner with a single live scope dispute right now

  • One branded change order PDF
  • One client-facing email draft
  • No subscription

Solo

$99 / month

For 1-3 person studio billing fixed-scope projects

  • 10 change orders per month
  • Saved rate card and scope documents
  • Watermark-free PDFs

Studio

$249 / month

For 4-10 person studio with multiple client brands

  • Unlimited change orders
  • Client workspaces and stored scope docs
  • Document history export

Model: Three published prices with no free tier: a $39 one-off document to convert live disputes, $99/month for solo studios, $249/month for multi-brand studios.

First revenue offer: Send the prospect their own email turned into a finished change order PDF within two hours, free, then: "If you want to do this yourself next time, it's $39 for this one or $99/mo — link here."

Expected ACV: $99

Upsell path: One-Off buyers are offered Solo on day 3 with the $39 credited; Solo accounts exceeding ten documents a month or managing several client brands are offered Studio at $249.

Target customers
90
Revenue model
$11,610
Costs
$640
Profit model
$10,970
Section 4 of 8

First-customer acquisition

Primary channel

Personally generated free change-order PDFs delivered by DM or email to studio owners found complaining about scope creep in agency and freelance communities.

Where to find them

  • Reddit r/web_design threads about unpaid extras
  • Reddit r/freelance and r/agency scope-creep complaints
  • Indie agency Slack and Discord groups
  • X posts from studio owners about clients adding work
  • Comment sections of design/dev YouTube videos on contracts
  • Local design and dev meetup group channels

Exact outreach motions

  • Reply publicly with a redacted before/after sample, then DM the commenter offering to run their email through the tool free
  • DM with the person's own words quoted, offering a free run with no signup and delivery inside two hours
  • Follow up on day 3 and day 7 with the stored draft and a one-line $39 link
  • Ask every engaged owner for one intro to another studio owner
  • Post a weekly raw-email-vs-priced-PDF teardown in the same two or three communities

Message template

Saw your post about the client adding "just one more page" mid-project. I built a tool that turns that exact email into a priced change order PDF using your rate card and the original scope doc. Want me to run yours through it? Free, no signup, back within two hours.
Week-one goal: 120 qualified prospects logged with links and quotes, 50 personalized DMs sent, 15 free samples delivered, landing page and checkout live.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 5First sale target: day 830 days planned
Week 1 · Build & validate · 7 days
Day 1Foundation

Repo, auth, schema

  • Create Next.js repo on Vercel and Supabase project.
  • Wire magic-link auth and a protected dashboard shell.
  • Register domain; set up Resend domain and Stripe test keys.
  • Commit the extract/diff/price JSON schema.

Deliverable: Deployed app shell with login and schemas committed.

Day 2Rate card and scope docs

Studio inputs

  • Build rate card CRUD with unit types and minimum increments.
  • Add scope-doc upload to storage with text extraction and chunking.
  • Create per-client workspace records.

Deliverable: Saved rate card and chunked scope doc retrievable by API.

Day 3Pipeline

Three-call extraction, diff, price

  • Implement /api/generate with the three sequential calls.
  • Move all pricing arithmetic into code from the rate card.
  • Log token cost per run.

Deliverable: Priced JSON for five messy sample threads.

Day 4Document output

PDF and client email

  • Build React-PDF template with line items, subtotal, timeline delta, signature block.
  • Add watermark for unpaid documents.
  • Generate the short client-facing email.

Deliverable: Change order PDF plus email from a pasted thread.

Day 5Ship MVPMVP shipped

Billing and inbound email

  • Add Stripe Checkout for One-Off, Solo and Studio.
  • Webhook gates documents per month and removes watermark.
  • Wire Resend inbound parsing to the same job pipeline.
  • Run one real paid test transaction.

Deliverable: End-to-end paid flow live; MVP shipped.

Day 6Hardening

Accuracy on real threads

  • Run twelve real-shaped threads through the pipeline.
  • Fix the top five classification errors.
  • Add empty states and upload error handling.

Deliverable: Error log with fixes; landing page live.

Day 7Prospects

First outreach batch

  • Build a 120-thread prospect sheet with links and quotes.
  • Send 25 free-sample DMs.
  • Post one redacted before/after sample.

Deliverable: 120 prospects logged, 25 DMs sent.

Week 2 · Launch & first sale · 7 days
Day 8First salesFirst sale target

Deliver samples fast

  • Deliver 10 free PDFs within two hours each.
  • Attach the $39 One-Off link to every delivery.
  • Follow up day-7 prospects with stored drafts.

Deliverable: 10 samples delivered; first paying customer target.

Day 9Follow-up

Second touch

  • Send 25 new personalized DMs.
  • Publish a teardown post in a second community.
  • Reply to every comment on both posts.

Deliverable: 50 cumulative DMs and two public posts.

Day 10Conversion

Sample to paid

  • Review free-sample to paid drop-off.
  • Add one-click buy from the delivery email.
  • Ship a public sample gallery page.

Deliverable: Sample gallery plus checkout link in every delivery.

Day 11Holiday dip build

Ship while replies are slow

  • Send only 10 DMs around the US holiday.
  • Ship document history list with status.
  • Write three answer-first pages on change orders for studios.

Deliverable: History UI and three pages live.

Day 12Second channel

Communities

  • Post a case study in one agency Slack or Discord.
  • DM 25 studio owners on X.
  • Ask three engaged owners for intros.

Deliverable: Three intro requests sent.

Day 13Studio tier

Test the $249 tier

  • Send 30 DMs targeting 4-10 person studios.
  • Offer Studio with client workspaces.
  • Instrument checkout funnel events.

Deliverable: Funnel events firing end to end.

Day 14Week review

Kill losing message

  • Tally DMs, samples, sales and refunds.
  • Kill the worst message variant.
  • Rewrite the winner and lock it as the template.

Deliverable: Metrics sheet and locked winning message.

Week 3 · Repeat & systematize · 7 days
Day 15Content engine

Inbound trickle

  • Publish a raw-email vs priced-PDF teardown.
  • Send 30 DMs.
  • Reply to 10 public scope-creep threads with the sample.

Deliverable: One teardown published, 30 DMs out.

Day 16Trust

Confidentiality objection

  • Ship a trust page: no training on customer data, one-click delete.
  • Add paste-only mode as an alternative to upload.
  • Send 25 DMs.

Deliverable: Trust page and paste-only mode live.

Day 17Upgrade push

One-Off to Solo

  • Email every One-Off buyer offering Solo with the $39 credited.
  • Send 25 DMs.
  • Add Stripe Billing Portal link to the dashboard.

Deliverable: Upgrade email sent to all one-off buyers.

Day 18Referral loop

Borrow distribution

  • Add a send-a-sample-to-a-studio-friend link.
  • Follow up all day-7 prospects.
  • Send 25 DMs.

Deliverable: Referral link live and tracked.

Day 19Quality bar

Reduce bad pricing

  • Audit ten generated drafts for pricing errors.
  • Tighten rate-card minimums and rounding rules.
  • Ship edit-before-download.

Deliverable: Edit-before-download shipped; audit notes filed.

Day 20Community

Third surface

  • Post a before/after in a third community.
  • Send 25 DMs.
  • Answer every comment within four hours.

Deliverable: Third community post with reply log.

Day 21Week review

Double down

  • Compare conversion by community.
  • Drop the two weakest sources.
  • Plan the final nine-day sprint.

Deliverable: Source-by-source conversion table.

Week 4 · Scale what works · 7 days
Day 22Warm list

Re-contact

  • Re-message 40 warm non-buyers with a new sample.
  • Send 20 fresh DMs.
  • Ship one pricing-error fix from the audit.

Deliverable: 40 warm re-contacts sent.

Day 23Billing hygiene

Retention mechanics

  • Add failed-payment dunning copy.
  • Link the Billing Portal in the nav.
  • Send 30 DMs.

Deliverable: Dunning and portal live.

Day 24Adjacent referrers

Bookkeepers and VAs

  • DM 10 bookkeepers and agency VAs offering free documents.
  • Ask each for one studio intro.
  • Publish a short teardown reply in a finance-for-agencies thread.

Deliverable: 10 referrer conversations opened.

Day 25Answer content

Search-shaped replies

  • Reply to 15 'how do I charge for scope creep' threads.
  • Link the sample gallery, not the pricing page.
  • Send 20 DMs.

Deliverable: 15 answer replies posted.

Day 26Proof

Second case study

  • Write a redacted case study with real numbers from a user's document.
  • Post it where the winning source is.
  • Send 30 DMs.

Deliverable: Case study published.

Day 27Year-end angle

Close scope before the break

  • Message 40 prior contacts with a year-end scope-close angle.
  • Refresh the sample gallery with three new examples.
  • Check refund and watermark edge cases.

Deliverable: 40 year-end messages sent.

Day 28Week review

Clean up

  • Audit refunds and chargebacks.
  • Rewrite pricing copy for the Solo and Studio tiers.
  • Cut any feature that is not in the seven must-haves.

Deliverable: Pricing page rewrite and refund audit.

Days 29-30 · Consolidate · 2 days
Day 29Final burst

Last push

  • Send 50 DMs from the highest-converting source.
  • Ask three users for a written quote.
  • Post the launch recap thread.

Deliverable: 50 DMs sent, quotes collected.

Day 30Close

Reconciliation

  • Reconcile Stripe payouts against document counts.
  • Screenshot verified profit for the submission.
  • Write the next-30-days decision memo.

Deliverable: Reconciled books, submission screenshot, decision memo.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.

Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).

The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.

Stated assumptions

  • Conservative/Base/Upside differ mainly in DM-to-paid conversion, not price.
  • ARPU reflects mix: One-Off $39, Solo $99, Studio $249; early mix skews to One-Off and Solo.
  • Payment fees assume Stripe at roughly 4.5% blended including the fixed per-transaction component.
  • Refunds are assumed under 5% of revenue because samples are delivered before any charge.
  • Chargebacks assume one contested transaction and its fee in the upside case only.
  • Paid marketing is $0 except a small sponsored-post test in the upside case; all outreach is organic.
  • Operating costs cover Vercel, Supabase, domain, Resend and per-document inference at a few cents per run.
  • No customer, revenue or traction exists today; every figure is a projection.
  • Hosting, tooling and inference are excluded from hackathon profit by the contest rules but shown as operating costs for business profit.

Conservative

4 customers
$368
collected revenue · avg payment $92
Refunds
$0
Chargebacks
$0
Payment fees
$17
Paid marketing
$0
Hackathon profit
$351
Operating costs
$22
Business profit
$329

Base case

16 customers
$1,728
collected revenue · avg payment $108
Refunds
$39
Chargebacks
$0
Payment fees
$78
Paid marketing
$0
Hackathon profit
$1,611
Operating costs
$58
Business profit
$1,553

Optimistic

42 customers
$5,082
collected revenue · avg payment $121
Refunds
$138
Chargebacks
$25
Payment fees
$229
Paid marketing
$120
Hackathon profit
$4,570
Operating costs
$155
Business profit
$4,415

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$624
Payment fees (3.9%)
$24
Paid marketing
$0
Hackathon profit
$600
Business profit
$542

Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.

All scenarios are projections built from stated assumptions, not verified revenue, customers or traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Free-sample outreach conversion decays because it depends on founder hours and personalization.

Mitigation

Template the structure, personalize one line per prospect, and cap outreach at 90 minutes a day so quality holds.

Validation experiment

Run two message variants against 50 DMs each in week two and compare reply and paid conversion rates.

Kill criteria

Fewer than 8% reply after 150 DMs and fewer than two sales by day 14: switch channel to direct outreach inside two paid agency communities.

Risk 2A mispriced or wrong scope classification damages the buyer's relationship with their own client.

Mitigation

Ship edit-before-download, a review banner on low-confidence items, and pricing arithmetic in code rather than in the model.

Validation experiment

Audit 20 real generated documents and count items that needed heavy manual edits.

Kill criteria

More than 40% of documents need heavy edits: narrow intake to threads under 400 words and add a confirmation step.

Risk 3Buyers refuse to upload a confidential statement of work to an unknown tool.

Mitigation

Paste-only mode, no training on customer data, one-click deletion, per-client isolation.

Validation experiment

Ask 15 prospects directly whether they would upload a scope doc; count refusals and check paste-only conversion separately.

Kill criteria

More than half refuse even with delete-in-one-click and paste-only does not convert: drop storage from the pitch and sell the single-document flow only.

Risk 4Buyers decide a ChatGPT prompt is good enough, collapsing willingness to pay.

Mitigation

Lead every sample with the scope diff and the branded PDF, not the text generation.

Validation experiment

Show ten studio owners a raw prompt answer and a ScopeLock PDF and ask which they would pay for.

Kill criteria

Seven of ten say the prompt is enough: re-scope the wedge rather than discounting the price.

Risk 5Refunds and chargebacks on a low-price product erase a large share of profit.

Mitigation

Deliver the sample before charging, refund instantly on complaint, keep the watermark until payment clears.

Validation experiment

Track refund reason codes weekly and review any chargeback the same day.

Kill criteria

Chargebacks exceed two transactions in the window: stop selling One-Off and require Solo subscriptions only.

Risk 6Inbound email forwarding is blocked or lands in spam, breaking the primary intake path.

Mitigation

Make the paste box the default experience and treat the forwarding address as a convenience.

Validation experiment

Send test forwards from five providers in week one and log delivery.

Kill criteria

Two or more providers fail consistently: remove the forwarding address from the landing page entirely.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Lock scope to the seven must-have features and write them down.
  • Buy the domain and create Supabase and Vercel projects.

Output: Repo, domain and hosting projects live.

Hours 3-6

  • Write the extract, diff and price prompts with a strict JSON schema.
  • Run them against five real-shaped client threads in a local script.

Output: Priced JSON output for five threads plus a token-cost log.

Hours 7-10

  • Build the Next.js shell with magic-link auth.
  • Ship the rate card editor with unit types and minimum increments.

Output: Deployed shell with one saved rate card.

Hours 11-13

  • Build the React-PDF template with line items, subtotal, timeline delta and signature block.
  • Add the unpaid watermark.

Output: One sample change order PDF.

Hours 14-17

  • Log 40 prospects with links, quotes and community source.
  • Send the first 10 free-sample DMs with the offer to run their email.

Output: Prospect sheet started and 10 DMs sent.

Complete report

Full 30-day launch report

Read the full generated report

ScopeLock Change Orders — 30-Day Launch Report

Solo founder. Window: Mon 16 Nov 2026 13:00 UTC to Wed 16 Dec 2026 13:00 UTC. Every number here is a projection from stated assumptions, not verified revenue.

1. Product opportunity and positioning

Fixed-scope studios leak money in one narrow, repeatable moment: a client emails "can you also just…" and the owner must choose between writing a change order (20-40 minutes of admin plus a mildly confrontational message) or eating the work. Most eat it, which is why the loss never shows on an invoice.

ScopeLock is an artifact machine for that moment. The owner forwards the thread; the product extracts the requested additions, diffs them against the studio's uploaded scope document, prices only genuinely new items from a saved rate card, and returns a branded change order PDF plus a client-ready email. One input, one output.

The buyer is the owner-operator of a 1-10 person design, dev, video or marketing studio on fixed-scope contracts in the US, UK, Canada or Australia — someone who can pay $99 on a company card without asking anyone.

Against the obvious alternative: a ChatGPT prompt gives prose with no scope diff, no rate-card arithmetic, no branding and no record of what was billed. ScopeLock's value is the diff plus the document, and the accumulating rate card and scope docs make month two easier than month one.

JEV scored the concept 68.6/100 (band B): strongest on speed to first revenue (8.59/10) and reachable customers (8.13/10), weakest on operational simplicity (4.69/10). The build plan answers that weakness directly — stateless jobs, managed services, no review queue, no integrations, no team seats.

2. Smallest sellable MVP

Sellable on day five: paste or forward a client thread, upload one scope doc, save a rate card, receive a priced PDF and an email. Everything else is out.

Must exist: intake (paste box plus forwarding address), per-client scope-doc upload with text extraction, rate card editor with hour/day/fixed units and minimum increments, a three-call pipeline with enforced JSON schema, PDF render with a watermark for unpaid documents, Stripe Checkout with document-count gating, and a document history list.

Deliberately not built: e-signature, payment collection on the change order, invoicing, Asana/Jira/ClickUp/CRM integrations, team seats, mobile app, fine-tuned models, any done-for-you queue that would turn this into a service.

3. Technical implementation plan

Next.js on Vercel, Supabase for Postgres, storage and auth, one structured-output model chain (Anthropic or OpenAI), React-PDF for rendering, Resend for inbound and outbound mail, Stripe Checkout plus Billing Portal.

The pipeline is three sequential calls, not one prompt. First, extract requested additions with verbatim quotes. Second, classify each item in-scope or new against retrieved scope-doc chunks. Third, map new items onto rate-card service items. All arithmetic happens in code with deterministic rounding and minimum increments, so a bad token cannot invent a price. Low-confidence items are flagged for review before download; the PDF stays watermarked until payment clears.

Order of work: schema and prompts tested on five messy threads in a local script; then UI shell and auth; then rate card and storage; then PDF; then Stripe and inbound email; then hardening on twelve real-shaped threads.

Hardest risk: classification when a client restates existing scope alongside genuinely new work. Mitigation is the review banner plus edit-before-download, and a hard rule that ambiguous items are shown as "review" rather than silently priced.

4. Pricing and monetization

Three prices, one page. One-Off at $39 for a single PDF with no subscription; Solo at $99/month for ten documents with a saved rate card and no watermark; Studio at $249/month for unlimited documents, client workspaces and export. No free tier — free here only trains people never to pay.

The conversion mechanic is the free sample: the founder runs the prospect's own email through the tool and delivers the PDF in under two hours, then attaches a $39 link. One-Off exists purely to convert while the pain is live; Solo is offered on day three with the $39 credited.

Upsell path: One-Off to Solo, then Studio once a studio exceeds ten documents a month or manages several client brands. No annual contracts and no sales calls.

5. First-customer acquisition

One channel only: personally generated free change orders delivered by DM or email to studio owners found publicly complaining about scope creep on r/web_design, r/freelance, r/agency, indie agency Slacks and Discords, and X. No ads, no SEO bet, no partnerships.

Daily rhythm: 25-30 personalized DMs, each opened with the person's own words, never a blast; every accepted sample delivered within two hours; follow-ups on day three and day seven using the stored draft; one intro request to every engaged owner. Twice a week, post a redacted raw-email-versus-priced-PDF teardown in the same two or three communities.

Week-one goal: 120 qualified prospects logged, 50 DMs sent, 15 free samples delivered, landing page and checkout live.

6. 30-day roadmap

Day one is 16 November; day thirty is 15 December. The day-by-day list is in the structured roadmap, and the shape is: days 1-5 build to a paid end-to-end flow; days 6-7 harden and send the first 25 DMs; days 8-14 first sales, follow-ups, sample gallery and three answer pages; days 15-21 upgrade push, referral loop, trust page and quality audit; days 22-28 warm-list re-contact, case studies, year-end angle; days 29-30 final burst and reconciliation.

Two calendar realities. US Thanksgiving on 26-27 November thins replies, so days 11-12 are build and content heavy. The final ten days sit in pre-holiday agency budgeting, which favours a "close scope before year-end" message over generic outreach.

7. Revenue and profit scenarios (projections)

Conservative: 4 customers at $92 blended ARPU, $368 gross, $0 refunds, $0 chargebacks, $17 fees, $0 paid marketing, $22 operating costs. Hackathon profit $351; business profit $329.

Base: 16 customers at $108, $1,728 gross, $39 refunds, $0 chargebacks, $78 fees, $0 marketing, $58 operating costs. Hackathon profit $1,611; business profit $1,553.

Upside: 42 customers at $121, $5,082 gross, $138 refunds, $25 chargebacks, $229 fees, $120 marketing, $155 operating costs. Hackathon profit $4,570; business profit $4,415.

Conservative assumes the DM channel underperforms and only warm, single-dispute owners convert. Base assumes roughly 16 buyers from 600-800 personalized touches plus community posts. Upside assumes one teardown post travels and a handful of Studio subscriptions land. No customer, revenue or traction exists today.

8. Main risks and validation experiments

Sample conversion decays. Test two openers on 50 DMs each in week two. If reply rate stays under 8% after 150 DMs and two sales, move the channel inside two paid agency communities.

Bad pricing damages the buyer's own client relationship. Ship edit-before-download and a review banner in week one, then audit 20 real outputs. If more than 40% need heavy edits, restrict intake to threads under 400 words.

Trust barrier on confidential SOWs. Offer paste-only mode and ask 15 prospects directly. If more than half refuse to upload even with one-click delete, drop storage from the pitch.

Commodity substitution. Show ten owners both a raw ChatGPT answer and a ScopeLock PDF. If seven say the prompt is enough, re-scope the wedge rather than discount it.

Chargebacks on a $39 product. Deliver within minutes, never charge before the sample is seen, refund instantly on complaint, and watch refund reasons weekly.

9. First 24 hours

Hours 1-2: lock scope to the seven must-haves, buy the domain, create Supabase and Vercel projects. Hours 3-6: write the three prompts and the JSON schema, run them on five real-shaped threads in a local script. Hours 7-10: Next.js shell, magic-link auth, rate card editor. Hours 11-13: React-PDF template with line items, subtotal, timeline delta and signature block. Hours 14-17: log 40 prospects and send the first 10 free-sample DMs.

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 →