Where your agency's margin actually goes
Retainers rarely become unprofitable in one dramatic moment. They erode through requests nobody thought were worth escalating, absorbed by people who are not the ones measured on margin. This page is about making that leak visible while you can still bill for it.
Why agency scope creep hides
At an agency, the person who absorbs the request is almost never the person who owns the account's profitability. A designer takes the extra round because the client is happy and the deadline is fine. An account manager says yes because the relationship matters more than an hour.
Both decisions are locally reasonable. The hours land in a timesheet, not in a conversation about scope, and nobody connects them to the retainer until someone reviews margin a quarter later - long past the point where the work could have been billed.
This is why agency scope creep is not a discipline problem. It is a visibility problem: the information needed to raise a change order exists, but never reaches the person who would raise it, in time.
What the leak looks like at scale
Take an agency running ten concurrent retainers with a blended rate of $120 an hour. On each account, the team absorbs six unbilled hours a month - roughly one small request a week, none of them worth an argument.
That is 60 unbilled hours a month, or $7,200 a month and $86,400 a year, delivered for free. No single instance of it would ever survive scrutiny as a line item, which is exactly why it never gets one.
Substitute your own retainer count and blended rate in the scope creep calculator to see the figure for your book of business. The numbers above are illustrative, not a benchmark.
What Ersilia gives an agency
Scope defined per project, visible per account
Each project carries its own deliverables, budget, quoted hours and rate. Workspaces group those projects and let you invite team members, so scope lives with the work rather than in one account manager's memory.
Alerts land in a shared channel
Route detections into a shared Slack, Discord or Microsoft Teams channel. An out-of-scope request becomes a visible team decision instead of a private favour someone quietly absorbs.
The change order is already drafted
Every alert carries why the request falls outside scope, how significant it is, a suggested amount, and a client-ready response your account manager can edit and send.
Recovery is measured, not assumed
Revenue analytics and financial reports track what was flagged against what was actually billed, so you can see which accounts leak and which team members are absorbing the most.
Requests are analysed when they are logged against a project, or when they arrive through the WhatsApp Business integration. Ersilia does not connect to your team's inboxes.
Raising scope early protects the relationship
The common objection is that flagging out-of-scope work makes an agency look difficult. In practice the opposite is true. Silent absorption builds quiet resentment on your side and an expectation on theirs that the next request is also free.
What damages client relationships is the late correction: the awkward invoice, the renegotiation, or the quality drop when a team finally runs out of goodwill. A change order raised the same week, with a clear reason and a specific number, is what a mature supplier does.
Agency questions
Why is scope creep harder to see at an agency?
Because the person absorbing the request is rarely the person who owns the margin. A designer or account manager says yes to keep the relationship smooth, the extra hours disappear into a timesheet, and nobody connects them to the retainer's profitability until a quarterly review. The leak is distributed, so it never looks urgent to any one person.
How does Ersilia work across a team?
Workspaces let you group projects and invite team members, so scope is defined per project but visible across the account. Alerts can be routed into a shared Slack, Discord or Microsoft Teams channel, which means an out-of-scope request becomes a visible team decision rather than a private favour someone quietly absorbs.
Does this replace our project management or time tracking tools?
No. Those tools record work your team has already committed to. Ersilia sits at the point where a client asks for something, judging whether it falls outside the agreed scope and what it should be billed at. It complements time tracking by telling you which hours should have been a change order rather than absorbed cost.
What does the alert actually contain?
The request that triggered it, why it falls outside the agreed scope, how significant it is, a suggested amount to charge, and a drafted client response your account manager can edit and send. Revenue analytics then track what was flagged against what was actually recovered.
How does this affect client relationships?
It usually improves them. Scope creep damages relationships when it is absorbed silently and resentment builds, or when it surfaces late as an awkward invoice dispute. Raising it early with a clear, professional change order is what mature suppliers do, and clients generally respect it more than quiet over-delivery.
Test it on a request your team absorbed last week
Paste a real client message and see how Ersilia judges it against an agreed scope, what it suggests charging, and the response it drafts. No signup required.
Or work out what it has already cost you with the scope creep calculator.