Retainer Utilization Tracker: See Which Clients Are Eating the Month

A retainer is a promise to deliver a certain amount of work for a fixed fee. The tracker answers whether that promise is being kept, exceeded or under-delivered, and it needs to answer in the middle of the cycle rather than after it, because that is the only point at which anyone can act.

How it is done today

The most common method is a shared sense of which clients are demanding. Everyone in the studio knows, nobody has a number, and the account is repriced only when someone finally loses patience. It is remarkably accurate about which client and remarkably vague about how much.

The next version is timesheets filled in on Friday for the whole week. Those produce a number, but the scope tag is guesswork by then, and the report arrives after the month has already been over-serviced. Late data describes a problem; timely data prevents one.

Client and agreement

• Client, account manager and agreement start date.
• Retainer value and billing cycle.
• Included hours or deliverable units per cycle.
• Scope statement — what is explicitly included and excluded.
• Rollover rule and any cap.
• Target effective rate for this tier of account.
• Renewal date and notice period.

Time and work entries

• Date, person and role, with the role's cost and charge rate.
• Client and project or workstream.
• Task and deliverable it contributes to.
• Hours, logged the same day.
• Scope tag — in scope, out of scope, or internal.
• Billable flag, which is not the same as in scope.
• Change request reference where out-of-scope work has been approved.

An illustrative example using indexed values rather than real fees, to show how the same utilisation figure can mean opposite things. Assume each client is billed the same retainer value of 100 units per month.

Four accounts, four different actions. Client A is healthy and needs nothing. Client B is the obvious over-servicing case and needs a repricing conversation backed by three months of this data. Client C looks profitable and is actually the riskiest account on the list, because a client receiving 60 per cent of what they pay for is a client questioning the retainer at renewal. Client D sits near its allocation but carries fourteen out-of-scope hours, which is a change request that was never raised.

Scope becomes a field rather than an opinion

Tagging at the point of logging means the out-of-scope total is real. Weekly, it is small enough to raise politely; quarterly, it is a confrontation.

Alerts replace month-end discovery

A threshold alert at, say, 70 per cent utilisation halfway through the cycle gives an account manager a decision to make while the month can still be shaped.

Renewals get evidence

Renewal reminders arriving with utilisation history and effective rate turn a conversation about feelings into a conversation about a shared record.

Counting hours without rates

Ten senior hours and ten junior hours are the same row and very different money.

Only reviewing at month-end

By then the work is delivered and the only options left are absorbing it or an awkward retrospective invoice.

Treating under-utilisation as good news

A consistently under-served client is a churn risk, not a margin win.

Never raising change requests

An agency that has never raised one is not scoping perfectly. It is absorbing everything and calling it service.

Continue with CRM for small business, sales automation, CRM vs Excel, product features, the tools library, and use cases.