I wrote the standard for making websites AI-operable. Learn More

78% of Agencies Aren't Charging for Work They're Already Doing

October 28, 2026

scope creep, agency retainer pricing, managed services, project close

Most agencies think they have a pricing problem. They're wrong — and a single data point from Ignition's 2025 Agency and Cash Flow Report makes that case more clearly than any consultant pitch deck could.

What The Data Shows

According to the Ignition 2025 Agency and Cash Flow Report, 78% of agencies rarely or only sometimes charge for work done outside the agreed scope of a project or retainer (cited via taskip.net). That's not a rounding error. That's the operating norm across the industry.

Pair that with the commonly observed reality that agencies routinely deliver 20–30% more work than their retainers contractually cover, and a clear picture emerges: the revenue problem most agencies are trying to solve through new client acquisition is already sitting inside their current book of business, unbilled.

The Ignition report also found that cash flow is the top operational stressor for agencies — yet the primary response is to chase new revenue rather than recover what's already been earned. Agencies are running a leaky bucket and responding by pouring in more water.

Why This Keeps Happening

Scope creep isn't dramatic. That's why it persists.

It arrives as a Slack message asking for one more revision. A strategy call that wasn't scoped. A "quick" deck for a client presentation. Each individual instance feels too minor to escalate — flagging a 45-minute task as billable feels more awkward than just absorbing it.

So nothing gets flagged. And nothing gets documented.

The deeper structural issue is that most agencies have no system between the work and the invoice. Deliverables live in project management tools. Time (when tracked at all) lives in a separate platform. The SOW lives in a signed PDF that nobody opens again after kickoff. There's no mechanism that surfaces the gap between what was agreed and what was delivered — so the gap never becomes a conversation.

There's also a relationship dynamic at play. Account managers are incentivized to keep clients happy, not to enforce contracts. Raising a scope question mid-project feels like it introduces friction into a relationship the agency depends on. The irony is that this silence compounds the problem: clients get trained to expect extras for free, and the agency gets locked into a margin structure that gets worse over time, not better.

What The Top 10% Do Differently

Agencies that consistently enforce scope don't do it through willpower or uncomfortable confrontations. They do it through systems that make scope visible before it becomes a dispute.

Specifically:

They document scope at the deliverable level, not the project level. Instead of "social media management," the SOW reads: "12 posts per month, two rounds of revisions per post, one strategy call per quarter." Specificity removes ambiguity — and ambiguity is where scope creep lives.

They conduct a scope audit at 30-day intervals on every active retainer. This isn't a client-facing process — it's internal. Someone on the team is responsible for comparing what was delivered against what was scoped. If there's a gap, it becomes a line item in the next month's conversation, not a silent write-off.

They produce a client-facing value summary at the end of every engagement period. This document lists everything delivered, maps it to the client's stated goals, and quantifies the output wherever possible. This serves two functions: it makes the agency's value undeniable, and it creates a natural opening to discuss any work delivered beyond the original scope — framed as value, not as a complaint.

They have a standard process for out-of-scope requests. Not a policy document. A process. When a client makes an out-of-scope request, the response is immediate, warm, and clear: "That's outside our current scope — I can get you a quick add-on estimate by end of day." No friction. No accusation. Just a system.

How To Build The System

The infrastructure for this doesn't need to be complex, but it does need to be automatic — because anything that depends on someone remembering to do it will fail during a busy month.

The minimum viable version:

  1. A scope baseline document created at project kickoff that itemizes every deliverable, revision round, and touchpoint. This lives somewhere accessible — not buried in email.
  2. A monthly delivery log — even a simple spreadsheet — that tracks what was actually completed. If you're using a project management tool, this is likely already being captured; it just needs to be compared against the scope doc.
  3. A project close document that compiles everything delivered, maps it to client outcomes, and flags anything outside the original scope. This becomes both a value-justification tool and a reference point for renewal or upsell conversations.

The more sophisticated version automates the close document entirely: triggered at project completion, it pulls deliverables, formats them into a client-facing summary, and generates a cost-justification doc that quantifies what was delivered against what was contracted.

If you want that system running without building it yourself, Project Close Kit handles exactly this — triggered at project completion, it auto-generates a client cost-justification document alongside a full suite of sales assets, so finished work converts into institutional memory instead of disappearing into the archive.

The margin problem most agencies are trying to solve isn't upstream. It's already inside the relationships they have. The fix is a documentation system, not a bigger pipeline.

Start Here

Get Expert Help Without the Overhead

One expert. No middlemen. Let's fix what's not working and build something better.

I respond personally within 1 business day. No sales pitch - just a real conversation.