DriftZero — scope drift engine for agencies

Evaluation note: this is a submitted business plan, not a Rui-originated idea. Sections 1–9 evaluate the venture on its merits. Section 10 scores fit against founder-profile.md; if the submitter is someone else, read that section as "what this demands of whoever builds it."

1. The idea

An account manager at a mid-sized agency has a signed SOW covering two rounds of homepage revisions. The client asks for a third. Raising a change order means an awkward money conversation mid-relationship, a delay while finance prices it, and a real chance the client gets annoyed. Delivering the third round quietly costs nothing that shows up on anyone's dashboard that week. So it gets delivered, and absorbed. Ignition's 2025 survey of 273 US agency managers puts the aggregate at 57% of agencies losing $1,000–$5,000 a month to unbilled work, and 30% losing more than $5,000.

DriftZero proposes to close that leak with machinery rather than discipline: ingest signed SOWs from watched cloud folders to establish a labor and financial baseline; capture off-book requests through passive surfaces (Slack emoji reactions, BCC email aliases, meeting transcripts, weekly PM-tool polls); reconcile the two in a weekly batch job; and deliver a Monday-morning variance brief with one-click change orders. Priced $299 / $699 / $1,299 per month by contracts monitored. Validation runs through a landing page, a scope leakage calculator, and a paid ($150–250) manual post-mortem audit of a closed project — deliberately sidestepping the NDA problem of touching live client comms.

2. Fact strip

3. The numbers

4. Why now

There isn't a dated forcing function, and that is the finding. The plan asserts "agencies are under immense margin pressure" and that passive ingestion "finally makes automated scope tracking viable." Neither is dated. Scope creep has been a chronic agency condition for decades; the anchor statistic is from a report published 22 May 2025, not a 2026 event. Under the scoring rubric, an idea without a dated external trigger caps at 5 on timing.

Two things are genuinely new, and both cut in more than one direction:

• LLM document extraction got cheap enough to parse unstructured SOWs at unit economics that work. True — but it is equally true for every competitor, and it is the same "AI is cheap now" tailwind under thousands of 2026 startups. It lowers the barrier for the builder and for whoever copies them.
• Purpose-built entrants appeared in the last twelve months. ScopeShield launched February 2026 at $20/month; ScopeAuditor is live positioning itself as "AI-Powered Scope Creep Protection"; Alliansis shipped Scope Optimizer with AI anomaly detection (competitor scan, §8). That validates the problem — and means the window is being entered, not opening.

5. The receipts

The pain is real and people are actively engineering around it:

"Is it a big issue with creative agencies or is it just me that's tired of their clients chewing up their profit margins over the course of the project?" — r/marketingagency · willsamadi · Feb 2026 · 77 comments · thread

"there are so many reasons we allow this sort of thing — we think it will buy us loyalty or goodwill, we think we have to over-serve or we will lose the client... But here is the deal. it buys you ZERO. You might as well pay the clients rent because that's what you are doing. But the Fear of the Change Order is real." — r/marketingagency · ms_cannoteven · Feb 2026 · comment

"make much more detailed scoping at the beginning of each project, and give 10-20% out-of-scope maximum to maintain client relationship. If they want more than that without revising the contract, just leave them." — r/marketingagency · i-am-one · Feb 2026 · comment

"When they ask for someone that is out of scope, we put it in our pm tool as a change request. We make it clear that changes requests are chargeable. We have this in our contracts and we have this caught very early, so that its never a problem conversation that is uncomfortable." — r/marketingagency · NHRADeuce · Feb 2026 · comment

"It is so exhausting dealing with clients who expect one person to be a strategist, designer, video grapher, and ad manager all for the price of one role." — r/SocialMediaManagers · RevolutionNo962 · Aug 2026 · 24↑, 30 comments · thread

Corroborating: a 7-figure agency owner running an AMA in r/agency (316↑, 499 comments) lists "How do you deal with bad clients or scope creep?" among the five questions he is asked most (thread).

Read the receipts carefully and they say something the plan does not. Every practitioner above already knows when scope is crossed. Their fixes are about policy and nerve — tighter SOWs, a 10–20% allowance, naming the freebie out loud, making change requests chargeable up front. Not one of them describes failing to notice.

6. Whitespace

The gap the plan claims: "Traditional project management tools track tasks, but they don't know what was actually promised in the signed contract."

Partly false as stated. Scoro markets that it "ties project phases, budgets, and time tracking together so firms can monitor scope creep and protect fee-based project margins in real time," and runs retainers as mini-projects with per-cycle scope and budget visibility. Productive.io sells budget control across "hourly, fixed, retainer, or hybrid." Neither parses the PDF, but both maintain a scope baseline and alert on burn against it — which is the job the buyer thinks they're buying.

The gap that is real: nobody in the agency-side lane combines (a) contract-PDF parsing into a machine-readable baseline with (b) passive capture from the channels where scope actually gets granted — Slack, email, calls. The closest thing found is Turnstile, whose own positioning is exactly this mechanism ("reads the signed contract at intake and encodes the scope boundary as data the system checks against, so a delivery that exceeds it becomes a flagged billing event"), priced $100/mo + 0.6% of billing volume — but it is a quote-to-cash platform sold to SaaS finance teams, not an agency product.

The wedge, honestly stated: zero-behavior-change capture. That is a real differentiator against every tool that requires someone to log something. It is also the hardest part to build and the easiest part to be wrong about.

7. Proof & signals

• The anchor statistic is solid and citable: 273 US agency managers and executives, published 22 May 2025 — 57% lose $1–5K/mo, 30% lose $5K+/mo, 78% "rarely or only sometimes" charge for out-of-scope work (Ignition).
• Agencies already pay for adjacent software: Productive.io from ~$9–24 per user/month, Scoro ~$19.90–49.90 per user/month (2026 pricing comparison). A 30-seat agency on Scoro Performance is already spending ~$1,500/month on agency ops.
• A competitor prices the identical mechanism at $100/mo + 0.6% of billing volume (Turnstile) — evidence the value is real, and a ceiling on what DriftZero can charge for detection alone.
• The freelancer tier of this market is already contested: ScopeShield launched February 2026 at $20/month; ScopeAuditor is live (MicroGaps gap analysis, Feb 2026).

8. Who you're up against

• The account manager's judgment + a spreadsheet — INCUMBENT. Free, universal, and — per §5 — already aware of the overage. This is the real thing to beat, and it doesn't lose because it can't see.
• Scoro (~$19.90–49.90/user/mo) — explicitly markets scope-creep monitoring and retainer-cycle budget visibility. Owns the buyer's mental slot for "agency financial control."
• Productive.io (~$9–24/user/mo) — budget control across retainer/fixed/ hybrid; the default PSA for mid-size agencies.
• Turnstile ($100/mo + 0.6% of billing volume) — contract extraction → machine-readable scope boundary → flagged billing event. Adjacent (SaaS quote-to-cash) but actively marketing this exact agency narrative.
• ScopeAuditor / ScopeShield — purpose-built AI scope-creep detection, currently aimed at freelancers, $20/mo tier. Upmarket drift is the obvious next move for them.
• Alliansis Scope Optimizer — SOW creation, approval workflows, budget reconciliation, "AI that finds patterns you won't." Sold to the buy side (marketing procurement managing agency spend) — the mirror image of DriftZero, and a sign the category is being built from both ends.
• US Tech Automations "Retainer Health Alerts" — a productized workflow that tracks cumulative scope requests against retainer value and alerts at a 10% threshold. Consultancy-delivered, not SaaS, but it is the same feature sold today.

9. The verdict

Reasons to build

• The pain is quantified by a real survey with a stated sample (n=273) and corroborated by practitioners in their own words — this is a better-evidenced problem than most ideas ever get.
• The buyer already spends on this category: agencies pay Scoro/Productive per-seat today, so a $299–699/month line item competes for an existing budget rather than creating one.
• Price-to-value is legible in a way most SaaS isn't: an agency losing $5,000/month to leakage can be shown a $699 subscription as a 7x return, and the leakage number comes from their own data rather than a case study.
• The zero-behavior-change thesis is correctly identified. Time-tracking fatigue is real, and every competing approach depends on someone remembering to log something.
• The validation plan (§5 of the plan) is unusually disciplined for a business-plan document: charging $150–250 for a manual post-mortem before building software is exactly the right first test.

Reasons to not build

• The core thesis targets the wrong constraint. 78% of agencies rarely or only sometimes bill for out-of-scope work, and only 1% bill for all of it (Ignition). They are not failing to detect the overage; they are declining to ask. A detection engine sold into that population produces a more precise inventory of money its buyers have already decided not to request — and "the Fear of the Change Order" is the thing standing between the brief and the invoice. Every receipt in §5 supports this reading; none describes a discovery problem.
• The whitespace claim is overstated. "PM tools don't know what was promised" is contradicted by Scoro's and Productive's own marketing, and four purpose-built scope-detection products already exist (ScopeAuditor, ScopeShield, Alliansis, Turnstile). The lane is narrower than the plan assumes and is being entered from three directions at once.
• The integration surface is enormous and mostly gated. Module 1–3 as specified requires multi-tenant OAuth with Google Drive, Dropbox and OneDrive; Slack and Teams apps; inbound email infrastructure; webhook integrations with three transcription vendors; and REST polling against four PM tools. Google Drive alone is a restricted scope, which requires an annual third-party CASA security assessment — roughly $540/year at the cheapest authorized assessor and repeated every 12 months (restricted-scope verification; cost account, Jul 2026). That is recurring compliance cost and review latency before the first dollar, on top of Slack and Microsoft app review.
• Weekly batch reconciliation may be the wrong cadence for the job. The moment leverage exists is when the request arrives, before the work is done — a Friday-midnight cron that surfaces the overage on Monday reports labor already spent. It converts unbilled work into an awkward retroactive ask, which is precisely the conversation the data says agencies avoid.
• Emoji-reaction capture is behavior change wearing a costume. Reacting 🚩 to a client request still requires an account manager to notice, decide it is out of scope, and act — the same judgment call that already fails today, minus the excuse of effort. The genuinely passive surfaces (transcripts, PM polls) are the noisy ones.
• Pricing sits above the anchors it will be compared to. $299–$1,299/month competes against a $100/mo + 0.6% competitor, $20/mo point tools, and per-seat PSA suites a small agency already pays for. Defensible only if the brief demonstrably converts to recovered revenue — which returns to the willingness-to-bill problem.

10. Founder fit

The idea demands: distribution 7/10 · domain 7/10 · sales 7/10 · technical 8/10 · capital 6/10

Best for: an operator who has personally run agency finance — someone who can sell the change-order conversation, not the dashboard — paired with the engineering time to hold a dozen brittle integrations together.

Wrong for: a part-time solo builder on a sub-$1K budget, which is exactly the profile on file.

The Rui check. Technical is the only comfortable axis (9 against a demand of 8). The other three collide with the stated constraints:

• Capital 2/10 vs. demand 6. Under $1K per bet does not survive first contact with this architecture: CASA at ~$540/year recurring for Drive alone, plus Slack/Microsoft app review, plus LLM inference over contract PDFs, plus email infrastructure — all before revenue.
• Time 5–10 hrs/week vs. a four-module build. Modules 1–4 as specified are a multi-quarter effort for a full-time team. At 8 hours a week this does not reach a demoable state inside the 12-month goal window.
• Distribution 5 vs. demand 7, with one genuine asset: the AgentForge pipeline already talks to agency founders weekly. That is the single strongest reason this idea is in front of him at all — and it is an asset for a service, which needs ten conversations, far more than for a SaaS, which needs hundreds.
• Goal check: $5K MRR by month 12 via $299–699 subscriptions means 8–17 paying agencies on a product that cannot be built at 8 hrs/week. Via the pivot below it means ~25 clients on a monthly review retainer — hard, but arithmetically reachable.

11. Value ladder

12. The plan

The plan's own §5 is the right first move and should simply be executed before any code: landing page, calculator, and the paid $150–250 post-mortem. Two amendments the research argues for.

First, sell the ask, not the alert. Every post-mortem should end not with "you leaked $18,400" but with a drafted change-order email, a price, and the sentence to say when the client pushes back. The evidence says the money is lost at the conversation, not the discovery — so the deliverable that gets paid for is the one that survives the conversation.

Second, run it manually, on Rui's own pipeline. Twenty post-mortems for agency founders already in the AgentForge outreach list is a fortnight of evenings and costs nothing but time. It produces the two numbers the plan cannot assert today: what fraction of agencies pay $250 to look backwards, and — the one that decides everything — what fraction actually send the change order afterwards. Under 30% and the software should never be built.

Hardest part: post-mortems don't compound into software automatically. Each one must be run against a fixed extraction schema so that twenty audits become the labelled training set for Module 1, rather than twenty bespoke PDFs.

13. Napkin math — year one

Modelled on the pivot (manual audit → review retainer), not the SaaS.

Weakest assumption: not the conversion rates — the send rate. The model assumes agencies that buy a post-mortem will act on it. If they read the number, wince, and still don't invoice the client, every downstream row is worth zero and the whole category is a vitamin. That is testable for $0 in the first three audits.

Goal gap, stated plainly: ~$1.7K MRR at month 12 against a $5K target. Closing it needs ~25 retainers, which means roughly 60 paid post-mortems — triple the modelled volume, and the reason distribution (not engineering) is the binding constraint on this idea.

14. The ceiling

$1M–$3M ARR as an agency-vertical product (roughly 150–400 accounts at $500–700/month). Two things would raise it: expanding past agencies into the same mechanism elsewhere — construction change orders, fintech implementation, media licensing all share the structure — or moving from detecting the overage to executing the billing, where Turnstile already sits and where the money actually changes hands. Both are second-decision problems, not year-one ones.

15. Playbook prompts

• Build plan: "Read reports/2026-09-01-driftzero.md. Scope only the manual post-mortem instrument from §12: the fixed extraction schema, the audit deliverable template including the change-order script, and how twenty completed audits become labelled training data for Module 1."
• Roast: "Read reports/2026-09-01-driftzero.md and roast it as (a) an agency COO who already pays for Scoro, (b) Turnstile's founder, (c) an account manager who will be asked to react 🚩 in Slack. No mercy."
• Money model: "Read reports/2026-09-01-driftzero.md. Pressure-test the $299/$699/$1,299 tiers against a $100/mo + 0.6% competitor and per-seat PSA pricing, and model the review-retainer path to $5K MRR."

16. Verdict & next move

PIVOT · medium confidence

The pivot: sell the change-order conversation, not the detection engine — and sell it as a service before writing a line of Module 1.

The problem is real, quantified, and expensive; the plan's diagnosis of why it persists is where it goes wrong. Agencies are not losing 15–20% of margin because they can't see the overage. They see it and decline to bill — 78% rarely or never charge, only 1% charge for everything. A weekly brief that reports what they already knew, arriving after the labour is spent, solves a problem they don't have, at a price above three cheaper competitors, on top of an integration surface requiring recurring paid security certification. Built as specified, by this founder, at 5–10 hours a week and under $1K, it does not ship.

Built as the plan's own §5 already suggests — calculator, $250 post-mortem, manual review retainer, with the deliverable reframed around the ask rather than the alert — it fits the constraints, uses the one distribution asset on hand, and answers the single question that determines whether the software is worth building at all.

Next move: three free post-mortems for agency founders already in the AgentForge pipeline, run against a fixed schema, with a drafted change order as the deliverable. Then count how many actually send it. Cost: ~3 evenings, $0. If the send rate clears 50%, charge $250 for the next twenty. If it doesn't, the category is dead and $0 was spent finding out.