Ask an agency owner what scope creep costs them and you'll usually get a shrug and "a few hours here and there." The numbers say otherwise.
The leak, measured
Industry surveys make for uncomfortable reading:
- 78% of agencies say they rarely or only sometimes charge for out-of-scope work.
- 57% lose between $1k and $5k every month to it; another 30% lose over $5k.
- Put together, 87% of agencies are losing $12k to $60k+ per year — quietly, in work nobody invoiced.
(Supernormal's agency scope-creep research has the full breakdown.)
And it's not just agencies: across organizations without tooling for it, nearly half of all projects hit scope creep, budget overruns or missed deadlines.
Why nobody charges for it
It's not that agencies don't know how to invoice. It's that out-of-scope work doesn't announce itself. It arrives as a friendly message — "can we just tweak…" — gets picked up by whichever developer is closest, and ships before anyone with pricing authority ever sees it. By month's end it's indistinguishable from the contracted work around it.
Charging for scope creep after the fact means an awkward conversation. Charging for it at the moment of the request is just… a quote.
Close the gap at the message
The teams that stopped leaking money didn't renegotiate their contracts — they moved the scope check to where requests actually arrive:
- Every incoming client ask is compared against the signed scope, automatically.
- In scope → it flows to the board like normal work.
- Out of scope → it's flagged, priced and pencilled into a future sprint before anyone writes a line of code.
That's what gavril's scope guard does across WhatsApp, Telegram and your tracker. The $12k-a-year leak isn't a discipline problem. It's a visibility problem — and visibility is automatable.
← All posts