ScopeBack — change-order closer for solo creatives

1. One-liner

Reads the client’s “just one small tweak” email, checks it against your SOW, and hands you a send-ready paid change order.

2. Trend signal — why now?

Scope creep is the single most-repeated complaint in freelance and small-agency communities, and 2024–2026 produced hard numbers behind the whining:

• 57% of agencies lose $1,000–$5,000/month to unbilled scope creep; only 1% bill for all out-of-scope work — meaning 99% are leaking. (dev.to / Valynx, 2026)
• 67% of freelancers report doing unpaid work because of scope creep; solo freelancers lose ~$7,800–$15,600/year (Freelancers Union 2026 figure, repeated across the category). (MicroGaps, 2026-02-18)
• Real voice: an r/freelance UI designer estimated losing “probably $10k in a year just from forgotten scope creep”; a recurring anecdote — “Just one small change to the header—should take five minutes” — turned into five unbilled hours of nav rework. (aceshowbiz summary of r/freelance, 2025)
• Tooling is moving in: incumbents (Bonsai $15–59/user/mo, Moxie, Plutio) and PM tools (PSOhub, Productive, LiteFlows) added scope-creep dashboards in 2026; a dedicated MVP (ScopeShield, $20/mo) launched Feb 2026; Revisio ($19/mo) sells a revision-round counter. The category is being validated by money and product launches right now.

The “right now” is the LLM unlock: as of 2025 a model can ingest a messy client email thread plus the original one-page SOW and reliably reason “this is out of scope, here’s the diff, here’s the price, here’s the script” — for cents. That reasoning step did not work two years ago.

Provenance:

• Signal 1 (demand): 57% agencies lose $1K–5K/mo, 99% under-bill out-of-scope; 67% freelancers do unpaid scope work; r/freelance “$10k/year” — dev.to, aceshowbiz — 2025–2026
• Signal 2 (feasibility): cheap LLM inference can parse free-form client comms vs SOW and draft a diplomatic change order — MicroGaps — 2026-02-18
• Signal 3 (economic): Bonsai/Moxie/PSOhub adding scope features; ScopeShield ($20/mo) + Revisio ($19/mo) launched/selling — thedigitalprojectmanager, getrevisio — 2026 Category: Workflow automation

3. The opportunity

Every incumbent treats scope creep as a detection/measurement problem: Revisio counts revision rounds, Bonsai gives you a better contract template, PSOhub puts a “margin at risk” badge on an agency dashboard. None of them solve the actual moment of pain.

The pain is not “I didn’t notice the scope grew.” Freelancers notice. The pain is the 20 seconds of dread before sending the email that says “this costs extra.” They eat the work because writing that message — politely, with the right scope reference, without sounding petty, fast enough to matter — is socially expensive and they’re busy delivering.

ScopeBack attacks that exact moment. It doesn’t ask the client to use a portal (Revisio’s fatal friction — the client never logs in). It sits on the freelancer’s side, watches where work actually arrives (email/Slack/WhatsApp forward), and the instant a request crosses the SOW line it produces a ready-to-send change order: the scope diff in plain language, a defensible price, and a warm, non-confrontational script the freelancer approves in one tap. It converts dread into a button.

10× better than the incumbents because it removes the human bottleneck (the awkward write-up) instead of just instrumenting it.

4. Target market

• Primary customer: Solo freelance designers, web devs, video editors, and 2–8 person creative micro-agencies running fixed-bid projects ($2K–$30K typical), billing clients directly (not just Upwork-escrow). English-first markets: US, UK, EU, AU, plus India/PH/LatAm freelancers serving Western clients.
• Why they buy (their words): “I lost probably $10k in a year just from forgotten scope creep.” “It was ‘just one small change to the header’ and it ate five hours I couldn’t bill.” They know they’re bleeding; they hate the conversation more than they hate the loss — until the loss is quantified for them.
• Rough TAM reasoning: Don’t anchor on the 1.5B “global freelancers” vanity number. Realistic serviceable wedge: low-millions of professional fixed-bid creative freelancers + micro-agencies in English markets. Capturing 5,000 paying users at ~$20/mo = $1.2M ARR — comfortably inside a bootstrap target without needing a large share.
• Why now for them: Payment cycles stretched, budgets tightened 2024–2026, AI commoditized the base creative work — so margin now comes from not giving away the extras. The thing they used to absorb to “keep the client happy” is now the thing standing between them and rent.

5. Product sketch (MVP)

• Drop your SOW once: paste the proposal/contract/scope email; ScopeBack extracts the deliverables, revision allowance, and exclusions into a structured scope baseline.
• Forward the request: freelancer forwards (or connects Gmail/Slack) the client message. ScopeBack returns a verdict in seconds: in scope / borderline / out of scope, with the specific clause it deviates from.
• One-tap change order: for out-of-scope, it drafts (a) a plain-language scope diff, (b) a suggested price from the freelancer’s own rate, (c) a polished, non-confrontational client message offering “add to this project / next phase / skip” options.
• Tone dial: warm ↔ firm slider so the message sounds like the freelancer, not a lawyer.
• Recovery tracker: running tally of ”$ recaptured this month / this year” — the retention hook and the proof-of-value the freelancer screenshots.
• Scope ledger per client: a timestamped log of every accepted/declined change — ammunition if the relationship sours.
• Vertical script packs: pre-tuned phrasings for design, dev, video, copywriting (the awkwardness is domain-specific).

6. AI angle — what’s load-bearing

Remove the AI and this is a Notion template — i.e., it doesn’t exist. The load-bearing work is: (1) parsing an unstructured, often vague SOW into a usable scope baseline; (2) judging whether a free-form, hedged client request (“tiny tweak, whenever you get a sec”) materially exceeds that scope — a fuzzy reasoning task, not a keyword match; (3) generating a price-justified, emotionally calibrated message the freelancer will actually send without editing. All three are LLM-native and were not reliably doable pre-2025. The product is the model’s judgment plus a send button.

7. Localization angle (if any)

N/A as a wedge — this is a global English-first play. The buyer is the freelancer (English-comfortable, serving Western clients), not the end client, so payment-rail/language localization isn’t the moat. A later India/LatAm tier at local pricing (₹399/mo) is a plausible expansion, not the entry wedge.

8. Business model — path to $1M–$5M ARR

• Pricing: $20/month solo (benchmarked to ScopeShield $20, Revisio $19); $49/mo micro-agency (up to 5 seats + shared scope ledger). Annual discount to fight freelancer churn.
• ACV: ~$240 solo, ~$590 agency. Blended ~$280.
• To $1M ARR: ~3,600 paying accounts at blended $280 (e.g., 4,000 solo + 400 agency). Achievable within the serviceable niche.
• To $5M ARR: ~17,000 accounts — requires winning the category against ScopeShield/incumbents and an agency tier doing real expansion (per-seat + recovered-revenue success pricing).
• Expansion path: seats as agencies grow; optional success fee (small % of recovered scope) once the recovery tracker proves trustworthy; later: e-sign change orders, deposit collection, contract generation — moving up into the Bonsai footprint.

9. Go-to-market wedge — first 100 customers

• r/freelance, r/graphic_design, r/webdev, r/editors: these threads are full of scope-creep horror stories. Reply (genuinely, not spam) on 50–100 recent posts with a free “forward me the email, I’ll send back the change order” manual concierge — convert the strongest into paid. The complaint is self-identifying the buyer.
• The ”$ you left on the table” calculator: a free tool — paste 3 past projects, get an estimated annual scope-creep loss. Loss-quantification is what flips “annoying” into “I’ll pay $20.” Distribute via the subreddits + freelance newsletters (Peak Freelance, Millo, ContractKilla audiences).
• Creator-economy micro-influencers: Chris Do / The Futur–adjacent design-business YouTubers and the contract-lawyer creators (Selene the Lawyer, The Legal Paige) already preach this exact problem to the exact audience — affiliate/sponsored slots.
• Freelance marketplace forums (Upwork/Contra communities): the scope-creep threads there are evergreen and searchable; seed a genuinely useful answer + tool.

If the subreddit concierge play doesn’t convert at ≥5%, the idea is in trouble — that’s the kill test.

10. Build complexity — justification

Low. Off-the-shelf LLM API for scope parsing/judgement/drafting, standard web stack, Gmail/Slack OAuth (well-trodden), Stripe billing. No custom models, no proprietary data, minimal state (scope baselines + a recovery log). A solo builder ships a credible v1 (paste-SOW + forward-email + draft change order) in 5–7 weeks; inbox/Slack auto-ingest is a fast-follow, not a v1 blocker.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Drafting assistive text; freelancer sends it. No regulated activity.
Ethical — no harm / dark patterns	✅	Helps the underdog get paid for work done; nothing deceptive to the client.
Market exists (evidence above)	✅	Hard stats + competitor launches + verbatim complaints.
1–5 person team can build this	✅	Solo, ~6 weeks to v1.
Launchable with <$50K / ₹40L	✅	API + hosting + a landing page. Low four figures.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	15/20	Real, frequent (every project), quantified loss — but it’s a slow leak they’ve tolerated for years, not a hair-on-fire daily emergency. Behavior change required.
Demand evidence	15	12/20→12/15	Multiple independent hard signals + verbatim complaints + competitors charging money. Strong, just short of “skeptic-proof” because nobody’s at scale yet.
Build feasibility	15	13/15	Pure off-the-shelf LLM + web stack; solo in ~6 weeks.
Distribution clarity	15	9/15	Self-identifying buyers in named subreddits is good, but converting “annoyed” to “paying $20” is unproven and the channel saturates fast.
Revenue mechanics	15	9/15	Pricing benchmarked and sane, but $20/mo prosumer churn is brutal and the recovery-tracker value-proof is an assumption.
Time to first revenue	10	7/10	Concierge MVP can charge within 2–4 weeks; trial-to-paid funnel realistic.
Defensibility	10	3/10	Thin moat. Copyable in weeks; ScopeShield/Revisio already moving; incumbents (Bonsai/Moxie) could bolt this on. Wins only on focus + brand in-niche.
Total	100	68/100	Honest VALIDATE. Real pain, fresh unlock, but crowded race + weak moat + churn risk cap it.

13. Qualitative modifiers

Founder-fit tags

technical-heavy (LLM prompt/judgement quality is the product) · content-heavy (distribution is community presence + the loss-calculator content engine).

Key assumptions to validate (3–5)

1. Assumption: Freelancers will send an AI-drafted change order they wouldn’t have written themselves. How to test: Concierge with 30 freelancers — measure how many actually send the drafted message vs. chicken out.
2. Assumption: “Annoyed about scope creep” converts to paying $20/mo. How to test: Loss-calculator → trial → paid funnel; need ≥5% subreddit-concierge close.
3. Assumption: The model’s in/out-of-scope judgement is trustworthy enough that freelancers don’t second-guess every verdict. How to test: Blind-grade 100 real request/SOW pairs against freelancer ground truth; target ≥85% agreement.
4. Assumption: $20/mo prosumer churn stays survivable (<6%/mo) because the recovery tracker proves ongoing value. How to test: 90-day cohort retention on the first 100 paying users.

Risk flags

1. Competitive race: ScopeShield (Feb 2026, $20/mo) and Revisio ($19/mo) are already in-market; Bonsai/Moxie can add a feature. First-mover window is months, not years.
2. Behavior-change risk: the blocker is psychological (fear of the conversation). A tool can lower friction but may not overcome a freelancer’s people-pleasing — the deepest unvalidated risk.
3. Platform dependency: Gmail/Slack API access + LLM provider pricing/policy shifts.
4. Prosumer churn: $20/mo solo tools historically churn hard once the acute pain passes; success-fee pricing may be the only durable model.

14. Structured verdict

Score:                  68/100
Verdict:                VALIDATE
Confidence:             Medium
Best-fit builder:       Technical solo founder who is also active/credible in a freelance community
Time to revenue:        2–4 weeks (concierge) / 6–8 weeks (self-serve)
Capital to launch:      $3–6K (₹3–5L) — API, hosting, landing page
Top 3 assumptions to validate first:
  1. Freelancers actually SEND the drafted change order — concierge with 30 users, measure send rate
  2. "Annoyed" converts to "paying $20" — subreddit concierge ≥5% close
  3. Model scope-judgement ≥85% agreement with freelancer ground truth on 100 real pairs
Kill criteria:
  - Abandon if <5% of subreddit-concierge prospects convert to paid after the loss number is shown
  - Abandon if <40% of concierge users actually send the drafted change order (it's a confidence problem a tool can't fix)
  - Abandon if a funded incumbent (Bonsai/Moxie) ships an equivalent before self-serve v1

15. Next step — 1-week validation sprint

• Day 1–2: Build the manual concierge — a form: paste your SOW + paste the client request. You (the founder) run it through an LLM by hand and email back a polished change order within 2 hours. No product yet.
• Day 3–4: Drop genuinely helpful “send me your scope-creep email, I’ll write the change order free” replies in 40–60 recent r/freelance / r/graphic_design / r/webdev threads. Track requests in.
• Day 5: Of everyone who got a drafted change order back, how many (a) say they’ll send it and (b) say they’d pay $20/mo for this on tap? Go if ≥10 qualified requests and ≥30% express willingness to pay; no-go otherwise.

Falsifiable: a real send-rate and a real willingness-to-pay count from real freelancers — not “people seemed to like it.”