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

ScopeSnap Change Order

ScopeSnap turns a client's extra-request email into a priced, branded change-order PDF and send-ready approval email for fixed-fee web studios.

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.

Speculative6.31/10
MVP build (solo)
5 days
Launch price
$149
Sales to $1,000 revenue
7 customers
First paying customer
Direct DMs and emails to studio owners who publicly post about scope creep or unpaid revisions, offering one free sample change order from their own client email.
Who pays

Owner/operator of a 1-5 person fixed-fee web design or development studio in the US, UK or Canada, triggered when a client emails an extra request mid-project.

Biggest execution risk

Market demand 4.9/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; 7 sales at $149 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.7/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
$149
Solo build
5 days
30d base revenue
$2,190
30d hackathon profit
$1,953
Section 1 of 8

Product opportunity and positioning

Target customer

Owner/operator of a 1-5 person fixed-fee web design or development studio in the US, UK or Canada, triggered when a client emails an extra request mid-project.

Why now

The change order is a document studios already understand and can send today, so the only blocker is writing time, which one forwarded email now removes.

Problem

Extra client requests arrive as friendly emails, so the owner either absorbs the work or burns 30-60 minutes drafting a change order, and unbilled scope leaks revenue.

Solution

Forward the client email to a unique workspace address; ScopeSnap extracts the requested items, prices them against a saved rate card, and returns a branded PDF change order plus an approval link with status tracking.

Differentiation · Generic AI email assistants summarise and remind; ScopeSnap prices the request against studio-specific rate cards and outputs a sendable approval artefact.

1. Product opportunity and positioning

The buyer is the owner of a 1-5 person fixed-fee web studio in the US, UK or Canada. The trigger is a client email that quietly adds work mid-project. The owner then either absorbs the work unbilled or spends 30-60 minutes writing a change order they are not confident pricing, which also makes the client relationship feel adversarial.

ScopeSnap Change Order does one thing. The owner forwards that email to their workspace address; the product extracts the requested deliverables, matches them to a saved rate card, and returns a branded PDF change order plus a send-ready approval email with a tokenised link. The owner edits a line or two, sends, and sees approval status on a dashboard. No app install, no inbox connection, no integration.

It is not a generic AI email assistant. It does not summarise, remind or draft pleasantries. It produces a priced commercial document the studio already knows how to send. That is the whole wedge: no behaviour change, no procurement, no brand equity needed, and the deliverable itself is the product demo.

JEV scored this concept 63.1/100 (band C). Speed to first revenue is the strongest dimension at 8.68 normalised; market demand is the weakest at 4.88. The plan respects that gap: build in five days, then spend days 6-30 proving demand through direct outreach instead of assuming it. Positioning is deliberately narrow. Every extra feature (invoicing, project management, CRM) would dilute the one sentence that makes the sale: forward the email, get a priced change order you can send in ten minutes.

Commercial logic is simple. Delivery costs a few cents of model tokens plus a PDF render, so $149 is far above marginal cost and the contest does not deduct hosting anyway. Defensibility comes from accumulated studio data: the saved rate card, the SOW-clause library and the approval history are specific to that studio and take minutes to recreate elsewhere, which is why the second order is cheaper to win than the first.

Section 2 of 8

Smallest sellable MVP

A paid, self-serve workspace where a studio owner forwards one client email, reviews extracted line items priced from a saved rate card, and downloads a branded PDF change order with an approval link.

Must-have features

  • Unique inbound email address per workspace via Postmark inbound
  • LLM extraction of requested deliverables, implied deadline and out-of-scope signals
  • Editable saved rate card (service name, unit, price, lead time)
  • Branded PDF change order with line items, total, timeline impact and approval link
  • Approval tracking status page (pending, approved, declined)
  • Stripe Checkout credit packs with metered generation
  • Reply-to approval address and simple stop command

Explicitly out of scope

  • Client invoicing or payment collection
  • Project management, task tracking or time tracking
  • CRM, Slack or calendar integrations
  • Client portal or multi-user permissions
  • Legal advice or automated contract enforcement
  • Subscription billing
  • Mobile app

Demo flow (what the buyer sees)

  1. Founder creates a workspace and enters five rate-card lines
  2. Owner forwards a real client extra-request email to the workspace address
  3. System extracts three deliverables and one implied deadline
  4. Owner edits one line item price and confirms
  5. PDF change order renders with studio logo and total
  6. Approval email with tokenised link is generated and sent
  7. Dashboard shows the order as pending, then approved
Build plan

Technical implementation plan

Stack

Next.js on VercelPostmark inbound and outboundSupabase PostgresOpenAI API for extractionReact-PDF in a Node serverless functionStripe Checkout and webhooks

Architecture

Postmark inbound posts each forwarded email to a Vercel route that resolves the workspace from the recipient address, strips quoted history, and stores the thread. A single OpenAI call returns structured JSON of requested items, implied deadline and out-of-scope flags. A matching pass scores those items against the workspace rate card rows in Supabase. The owner reviews on a Next.js page, and confirmation renders a React-PDF document stored in Supabase Storage. A tokenised approval URL and a reply-to address are created in the same transaction, and inbound replies flip order status. Stripe webhooks top up a credits integer on the workspace; generation is blocked at zero credits.

Build steps

  1. Register domain, deploy a Next.js skeleton to Vercel, create Supabase project
  2. Schema: workspaces, rate_items, change_orders, order_items, approvals, credits
  3. Rate-card settings form with add, edit, delete rows and default units
  4. Postmark inbound webhook; parse recipient address into workspace, store raw thread
  5. Extraction prompt returning strict JSON; validate with a schema before storing
  6. Matching pass that prices extracted items against rate_items and flags unmatched lines
  7. Review screen with editable line items, quantities and prices
  8. React-PDF template with logo, line items, total, timeline impact, terms
  9. Tokenised approval link plus reply-to address and status transitions
  10. Credits gating, Stripe Checkout for $149 and $499 packs, webhook credit top-up
  11. Deliverability: SPF, DKIM, DMARC, bounce handling, malformed-forward error email
  12. End-to-end test: one live $1 purchase, one forwarded email, one approved order

AI components

  • Extraction of requested deliverables and implied deadlines from the forwarded thread
  • Out-of-scope classification against the saved rate card categories
  • Draft of the approval email body and the timeline-impact sentence
  • Confidence flagging when an item cannot be matched to a rate-card row
Hardest technical risk: Inbound forwarded threads arrive mangled: quoted history, HTML-only bodies and attachments can hide the actual request, so the extraction misses a line item and the studio sends an underpriced change order. Mitigation: strip quoted text, run extraction on the top reply only, show a low-confidence badge, and provide a paste-the-text fallback box.
Section 3 of 8

Pricing and monetization

Single Change Order Pack

Entry offer
$149 one-time

For Solo web designers or studios testing ScopeSnap on one live project

  • 10 change-order credits
  • Branded PDF output
  • Send-ready approval email
  • Rate-card setup

Studio Pack

$499 one-time

For Small fixed-fee web studios with recurring client scope creep

  • 50 change-order credits
  • Branded PDF output
  • Send-ready approval email
  • Rate-card and SOW-clause library
  • Approval tracking dashboard

Model: One-time credit packs, no subscription, so a studio can buy the moment a client email lands.

First revenue offer: Forward me one client email that added work and I will send back a priced, branded change order within 10 minutes, free. If you send it to your client, the $149 pack covers the next ten.

Expected ACV: $149

Upsell path: Single Pack buyers who generate more than two orders in a week are offered Studio Pack upgrade credit equal to what they already paid, then referral codes worth $50 to both sides.

Target customers
200
Revenue model
$99,800
Costs
$3,200
Profit model
$96,600
Section 4 of 8

First-customer acquisition

Primary channel

Direct DMs and emails to studio owners who publicly post about scope creep or unpaid revisions, offering one free sample change order from their own client email.

Where to find them

  • r/web_design and r/freelance posts mentioning scope creep or extra revisions
  • Indie Hackers and design community threads about fixed-fee projects
  • Freelance web Slack and Discord communities (design and agency channels)
  • X/Twitter posts about unpaid revisions or client requests
  • Public portfolio and directory listings of 1-5 person web studios

Exact outreach motions

  • Reply to a public scope-creep thread with a concrete answer and no link, then DM the poster
  • DM studio owners with the sample offer, one sentence, no attachment
  • Email five small agency or freelance newsletters offering a free pack for their readers
  • Post a redacted sample change order as a value post where rules allow
  • Ask every buyer for one intro to another studio owner with fixed-fee work

Message template

Saw your post about the client who added two extra pages for free. I built ScopeSnap: forward that email to an address, get back a priced change order PDF you can send in ten minutes. Want me to do one from your real email, free, today? No signup needed for the sample.
Week-one goal: 40 outreach sends, 8 sample change orders delivered, 1 paid pack sold by day 12.
Section 5 of 8

30-day execution roadmap

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

Payment rail and inbound address

  • Register the domain and create Vercel and Supabase projects.
  • Connect Stripe and the TrustMRR-linked payment account before any sale.
  • Provision the Postmark inbound domain and a test workspace address.
  • Deploy an empty Next.js page so the domain resolves.

Deliverable: Live domain, live payment account, working inbound test address.

Day 2Data model

Rate card and workspace schema

  • Create tables for workspaces, rate items, change orders, approvals and credits.
  • Build one settings form for rate-card rows: name, unit, price, lead time.
  • Seed a demo workspace with five generic service lines.

Deliverable: A workspace can save and reload a rate card.

Day 3Ingestion

Inbound email to structured line items

  • Parse the Postmark inbound webhook into a change-order record.
  • Run the extraction prompt and store validated JSON output.
  • Add a review screen where the owner edits items and prices.

Deliverable: A forwarded email becomes editable line items in under 60 seconds.

Day 4Output

PDF, approval link, tracking

  • Render the change-order PDF with logo, line items and timeline impact.
  • Generate a tokenised approval link and a reply-to approval address.
  • Add a status page listing pending, approved and declined orders.

Deliverable: Email in, branded PDF and approval link out.

Day 5PaywallMVP shipped

Credits and checkout

  • Gate generation behind a credits counter in Supabase.
  • Wire Stripe Checkout for the $149 and $499 packs with webhook top-up.
  • Run three test-mode purchases and one live low-value transaction.
  • Freeze scope: no new features before day 15.

Deliverable: MVP live and paid; a stranger can buy without the founder.

Day 6Warm-up

Samples and list building

  • Produce three sample change orders from founder-written test client emails.
  • Build a 40-name list of studio owners from public scope-creep posts.
  • Write the outreach message and the sample delivery email.

Deliverable: Three sample PDFs and a 40-name outreach list.

Day 7Outreach wave 1

20 direct messages

  • Send 20 personalised DMs offering a free sample from one forwarded email.
  • Reply to five public scope-creep threads with no link.
  • Log every send with date, channel and reply status.

Deliverable: 20 sends logged and first sample requests in flight.

Week 2 · Launch & first sale · 7 days
Day 8Follow-up and landing

Convert sample requests

  • Deliver requested samples within ten minutes and ask if they want the pack.
  • Ship the landing page with the sample PDF and a $149 checkout button.
  • Follow up every day-7 non-responder once.

Deliverable: Landing page live; all samples delivered.

Day 9First sale push

Ask for money

  • Send the checkout link to everyone who received a sample.
  • Offer a day-only $99 first-purchase price to the three warmest leads.
  • Record the exact objection each lead raises.

Deliverable: First paid pack attempted and objections logged.

Day 10Quality loop

Extraction accuracy

  • Diff extracted items against the owner's edits on every real order so far.
  • Tighten the prompt and add a low-confidence warning badge.
  • Fix the top three pricing misses.

Deliverable: Extraction prompt v2 with a written error log.

Day 11Outreach wave 2

20 new targets

  • Send 20 DMs to a second community segment.
  • Ask each sample recipient for one intro to another studio owner.
  • Post one redacted sample change order where community rules allow.

Deliverable: 20 new sends and three referral asks.

Day 12UpsellFirst sale target

Studio Pack

  • Offer the $499 Studio Pack to anyone generating more than two orders.
  • Add the SOW-clause library to Studio Pack settings.
  • Follow up all wave-1 and wave-2 leads a second time.

Deliverable: At least one Studio Pack conversation open.

Day 13Proof

Public artefact

  • Publish a post on what a scope-creep email costs a fixed-fee studio.
  • Add two PDF branding templates from buyer feedback.
  • Collect consenting buyer quotes.

Deliverable: One public post plus a template update shipped.

Day 14Week 2 review

Numbers and message

  • Count sends, replies, samples and sales; compute reply rate.
  • Rewrite the opener around the best-performing angle.
  • Cut any feature nobody used.

Deliverable: Written funnel numbers and a revised opener.

Week 3 · Repeat & systematize · 7 days
Day 15Outreach wave 3

25 sends

  • Send 25 DMs using the revised opener.
  • Email five small agency newsletters offering a free pack for readers.
  • Reply to ten fresh scope-creep threads.

Deliverable: 25 sends and five newsletter pitches.

Day 16Reliability

Deliverability

  • Add SPF, DKIM and DMARC to inbound and outbound domains.
  • Handle bounces and malformed forwards with a friendly error email.
  • Load-test 50 concurrent inbound emails.

Deliverable: Deliverability checks passing; error path tested.

Day 17Retention

Second order

  • Prompt buyers to reuse the saved rate card on the next order.
  • Send a day-7 credits-remaining email to every buyer.
  • Add one-click duplication of a previous change order.

Deliverable: Repeat-order prompt live.

Day 18Higher tier

Studio Pack sales

  • Offer upgrade credit to every Single Pack buyer.
  • Publish a one-page comparison of the two packs.
  • Close open Studio Pack conversations with a date.

Deliverable: One upgrade attempt per buyer logged.

Day 19Distribution partners

Free community mentions

  • Pitch five Slack or Discord moderators with a free pack for their community.
  • Offer a 20% affiliate code to any moderator who agrees.
  • Build a shareable sample pack link.

Deliverable: Five partner pitches sent.

Day 20Outreach wave 4

20 sends and follow-ups

  • Send 20 DMs to studios found via portfolio sites and directories.
  • Follow up every unanswered sample request once.
  • Take any offered call and keep it under 15 minutes.

Deliverable: 20 sends with all follow-ups cleared.

Day 21Week 3 review

Refunds and quality

  • Review every order for pricing errors and refund requests.
  • Refund without argument anything badly mispriced and log the cause.
  • Update rate-card defaults to prevent recurrence.

Deliverable: Refund log and updated defaults.

Week 4 · Scale what works · 7 days
Day 22Conversion asset

Demo video

  • Record a 90-second capture: forward email, PDF appears, approval link.
  • Embed the video above the fold on the landing page.
  • Add a see-a-real-sample link that captures an email address.

Deliverable: Demo video live on the landing page.

Day 23Outreach wave 5

25 warm lookalikes

  • Send 25 DMs to people who engaged with the public post.
  • Second touch to all newsletter and community partners.
  • Post the demo video in two communities that allow promotion.

Deliverable: 25 sends and two community posts.

Day 24Referral engine

Word of mouth

  • Add referral codes worth $50 to both the buyer and the friend.
  • Email every buyer their code with one sentence on who to send it to.
  • Track referral-attributed sales separately.

Deliverable: Referral codes issued to all buyers.

Day 25Objection handling

Price and trust

  • Add an FAQ on what happens if the client disputes the price.
  • Add a promise: an unapproved change order refunds that credit.
  • Test a $199 mid-tier price on the checkout page.

Deliverable: FAQ and refund promise live; price test running.

Day 26Outreach wave 6

20 final-wave sends

  • Send 20 DMs leading with the refund promise.
  • Ask all buyers for a one-line quote.
  • Follow up every open Studio Pack conversation.

Deliverable: 20 sends and buyer quotes collected.

Day 27Margin check

Delivery cost

  • Measure model tokens and PDF render cost per order.
  • Trim prompt size and cache rate-card lookups if cost exceeds $0.15 per order.
  • Confirm every price covers delivery cost by a wide margin.

Deliverable: Documented cost per order.

Day 28Final push

Pipeline close

  • Send a deadline email to every warm lead.
  • Offer the last-call $149 pack with same-day sample turnaround.
  • Ringfence two hours for live sample delivery.

Deliverable: Every warm lead contacted with a close date.

Days 29-30 · Consolidate · 2 days
Day 29Close and settle

Money in before the deadline

  • Chase every unpaid checkout link before Wednesday 13:00 UTC.
  • Reconcile Stripe payouts against credits issued.
  • Freeze discounts and confirm no sale lands outside the window.

Deliverable: All payments reconciled inside the contest window.

Day 30Report

Verified profit

  • Export gross revenue, refunds, chargebacks and processing fees.
  • Compute hackathon profit and business profit separately.
  • Write a one-page post-mortem with what actually happened.

Deliverable: Submitted profit figures and post-mortem.

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: 3 buyers, all Single Change Order Packs at $149, so ARPU is $149.
  • Base: 10 buyers, a mix of eight $149 packs and two $499 Studio Packs, blended ARPU $219.
  • Upside: 28 buyers, twenty $149 packs and eight $499 Studio Packs, blended ARPU $249. All three are projections, not evidence.
  • Payment processing assumed at Stripe 2.9% plus $0.30, modelled as roughly 4% of gross revenue.
  • Ad spend is $0 in every scenario: acquisition is direct outreach and organic community replies, no paid marketing.
  • Operating costs cover Postmark inbound, Vercel, Supabase, model tokens and PDF rendering at roughly $10 per active workspace-month.
  • Refunds: one $149 refund in conservative and base; one $499 refund plus one $499 chargeback in upside.
  • Founder time is not deducted, per contest rules; hosting and delivery costs are excluded from hackathon profit but deducted from business profit.
  • Prices of $149 and $499 are one-time charges a small studio owner can approve without procurement.

Conservative

3 customers
$447
collected revenue · avg payment $149
Refunds
$149
Chargebacks
$0
Payment fees
$18
Paid marketing
$0
Hackathon profit
$280
Operating costs
$30
Business profit
$250

Base case

10 customers
$2,190
collected revenue · avg payment $219
Refunds
$149
Chargebacks
$0
Payment fees
$88
Paid marketing
$0
Hackathon profit
$1,953
Operating costs
$90
Business profit
$1,863

Optimistic

28 customers
$6,972
collected revenue · avg payment $249
Refunds
$499
Chargebacks
$499
Payment fees
$279
Paid marketing
$0
Hackathon profit
$5,695
Operating costs
$260
Business profit
$5,435

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,490
Payment fees (3.9%)
$58
Paid marketing
$0
Hackathon profit
$1,432
Business profit
$1,342

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 the stated assumptions. They are not verified revenue, existing customers or real traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Volume risk: outreach does not produce enough replies, so sales land far below the base case.

Mitigation

Run six outreach waves of 20-25 personalised sends and track reply rate daily; rewrite the opener every week using the best performer.

Validation experiment

Send 20 DMs on day 7 and count replies and sample requests within 72 hours.

Kill criteria

If 60 total sends produce fewer than 6 replies by day 14, change the segment or the offer before sending more.

Risk 2Sample-to-paid conversion fails: buyers take the free change order and never pay.

Mitigation

Deliver the sample as a watermarked draft, then release the clean PDF and approval link only after purchase.

Validation experiment

Offer 8 samples in week 1 and record how many send the checkout link onwards.

Kill criteria

If fewer than 1 in 8 sample recipients pays by day 16, move to a pay-first $49 single-order entry price.

Risk 3Inbound forwarding breaks or the extraction misprices an item, damaging trust and creating refunds.

Mitigation

Review screen before any PDF is final, low-confidence badge on unmatched items, paste-text fallback, refund any credit where the output was wrong.

Validation experiment

Forward 15 deliberately messy real-world emails and diff extracted line items against manual pricing.

Kill criteria

If more than 2 of 15 forwards need full manual rewrite, add a structured intake form as the primary path.

Risk 4The buyer treats ScopeSnap as a one-off document generator rather than a tool worth a pack.

Mitigation

Frame every pack as credits, push reuse of the saved rate card, and sell Studio Pack upgrade credit to repeat users.

Validation experiment

Track orders per buyer in week 2 and 3; anyone above two orders gets an upgrade offer.

Kill criteria

If zero buyers generate a second order by day 21, the repeat value hypothesis is wrong and the studio-pack tier should be dropped.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register the domain and create the Vercel and Supabase projects.
  • Deploy a one-page Next.js skeleton so the domain resolves.

Output: Resolving domain and deployed skeleton.

Hours 3-4

  • Create the Stripe account and connect it to TrustMRR as required.
  • Create the $149 and $499 products with checkout links.

Output: Live payment links and a connected payout account.

Hours 5-7

  • Provision the Postmark inbound domain and add DNS records.
  • Forward a test email to the workspace address and confirm the webhook fires.

Output: Working inbound address with captured payload.

Hours 8-11

  • Create the Supabase schema and the rate-card settings form.
  • Seed one demo workspace with five generic service lines.

Output: Saved and reloadable rate card.

Hours 12-14

  • Draft the outreach message and the sample delivery email.
  • Build a 40-name list of studio owners from public scope-creep posts.

Output: 40-name outreach list and two ready-to-send messages.

Complete report

Full 30-day launch report

Read the full generated report

ScopeSnap Change Order — 30-Day Launch Report

One solo founder, 30 days, ranked on verified profit. Every figure below is a projection from stated assumptions. No customers, sales or partnerships exist yet.

1. Product opportunity and positioning

The buyer is the owner of a 1-5 person fixed-fee web studio in the US, UK or Canada. The trigger is a client email that quietly adds work mid-project. The owner then either absorbs the work unbilled or spends 30-60 minutes writing a change order they are not confident pricing, which also makes the relationship feel adversarial.

ScopeSnap Change Order does one thing. The owner forwards that email to their workspace address; the product extracts the requested deliverables, matches them to a saved rate card, and returns a branded PDF change order plus a send-ready approval email with a tokenised link. The owner edits a line or two, sends, and sees approval status on a dashboard.

It is not a generic AI email assistant. It does not summarise, remind or draft pleasantries. It produces a priced commercial document the studio already knows how to send. That is the whole wedge: no behaviour change, no integration, no brand needed, and the deliverable is the demo.

JEV scored this concept 63.1/100 (band C), with speed to first revenue as the strongest dimension (8.68 normalised) and market demand the weakest (4.88). The plan respects that gap: build in five days, then spend days 6-30 proving demand through direct outreach instead of assuming it.

2. Smallest sellable MVP

A paid workspace where the owner forwards one client email, reviews extracted line items priced from a saved rate card, and downloads a branded PDF change order with an approval link. Must-haves: a unique inbound address per workspace, LLM extraction of deliverables and implied deadlines, an editable rate card, the PDF, a tokenised approval link, a status page, and Stripe credit packs that gate generation. Explicitly out of scope: invoicing, project management, CRM or calendar integrations, client portals, team permissions and legal advice. Four build days, frozen on day 5.

3. Technical implementation plan

Next.js on Vercel, Postmark inbound and outbound, Supabase Postgres, OpenAI for extraction, React-PDF in a serverless function, Stripe Checkout with webhooks. The inbound route resolves the workspace from the recipient address, strips quoted history, stores the thread, and makes one structured extraction call. A matching pass scores items against rate-card rows and flags unmatched lines. The owner reviews and edits, confirmation renders the PDF, and the approval link plus reply-to address are written in the same transaction. Credits decrement on generation and top up on Stripe webhook.

The hardest risk is forwarding fidelity: HTML-only bodies and quoted history can hide the real request, causing an underpriced order. Mitigation is top-reply-only extraction, a low-confidence badge and a paste-the-text fallback.

4. Pricing and monetization

Two one-time packs. Single Change Order Pack at $149 for 10 credits, aimed at a studio testing on one live project. Studio Pack at $499 for 50 credits plus the SOW-clause library and approval dashboard, aimed at studios with recurring creep. No subscription, because the purchase moment is a specific email, not a monthly renewal decision. Credits make repeat use natural and make the upsell arithmetic obvious: buyers who exceed two orders get upgrade credit equal to what they already paid. Referral codes worth $50 to both sides start compounding after day 24.

5. First-customer acquisition

One channel: direct DMs and emails to studio owners who publicly post about scope creep or unpaid revisions. The opener is a free sample built from their own client email, delivered within ten minutes. Sources are r/web_design and r/freelance threads, Indie Hackers, freelance design Slack and Discord channels, X posts about unpaid revisions, and public portfolio listings of small studios. Six outreach waves of 20-25 sends run between days 7 and 26, each followed by a 48-hour follow-up that attaches the sample PDF and names the unpriced work. Week-one target: 40 sends, 8 samples delivered.

6. Detailed 30-day execution roadmap

Days 1-5 build the MVP: payment rail and inbound address, schema and rate card, extraction to editable line items, PDF plus approval link, then credits and Stripe checkout. Day 5 is the hard freeze.

Days 6-14 run the first two outreach waves, deliver samples within ten minutes, ship the landing page, ask for the money on day 9, then tighten the extraction prompt against real edits. Day 12 opens the Studio Pack conversation; day 13 ships one public artefact and two branding templates; day 14 computes reply rate and rewrites the opener.

Days 15-21 add deliverability hardening and repeat-order prompts, push upgrades, pitch five community moderators for free mentions, and run waves 3 and 4. Day 21 is a refund and quality review: any badly mispriced order is refunded without argument and the rate-card defaults are corrected.

Days 22-28 ship the 90-second demo video, run waves 5 and 6, introduce referral codes, publish the refund promise, test a $199 mid-tier price, verify cost per order stays under $0.15, and close the pipeline with a deadline email.

Days 29-30 reconcile payments before Wednesday 13:00 UTC, export gross revenue, refunds, chargebacks and fees, compute hackathon profit and business profit separately, and write the post-mortem.

7. Revenue and profit scenarios

Projections only, from the assumptions in the JSON. Conservative: 3 buyers at $149, $447 gross, $149 refunds, $18 fees, hackathon profit $280, business profit $250. Base: 10 buyers at blended $219, $2,190 gross, $149 refunds, $88 fees, hackathon profit $1,953, business profit $1,863. Upside: 28 buyers at blended $249, $6,972 gross, $499 refunds, $499 chargebacks, $279 fees, hackathon profit $5,695, business profit $5,435. Ad spend is zero in all three because the channel is organic outreach. Operating costs ($30 / $90 / $260) cover Postmark, Vercel, Supabase, tokens and PDF rendering and are deducted only from business profit.

The concept's own $99,800 target for 200 Studio Packs requires seven sales a day and is treated here as a ceiling, not a plan.

8. Main risks and validation experiments

The dominant risk is volume, not product. Validation: 20 sends on day 7, measure replies within 72 hours; if 60 total sends yield fewer than 6 replies by day 14, change segment or offer. Second risk is sample-to-paid conversion, tested across 8 samples in week 1; if fewer than 1 in 8 pays by day 16, move to a pay-first $49 entry price. Third is extraction quality, tested on 15 deliberately messy forwards; if more than 2 need full manual rewrite, structured intake becomes primary. Fourth is repeat use; if no buyer generates a second order by day 21, the Studio Pack premise fails and the tier is dropped.

9. First 24-hour action plan

Hours 1-2: domain, Vercel and Supabase projects, deployed skeleton. Hours 3-4: Stripe account connected to TrustMRR, $149 and $499 products live. Hours 5-7: Postmark inbound domain, DNS, and one forwarded test email captured. Hours 8-11: schema plus rate-card form with a seeded demo workspace. Hours 12-14: outreach message, sample delivery email and a 40-name list. End state: a working inbound address, live payment links and 40 names ready for day 7.

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 →