At some point, every agency owner starts asking the same question: “Is my team working enough?” It is usually prompted by a margin problem — a quarter where the revenue looked fine but the profit didn’t, where three projects ran over budget, or where the MD realised they’d spent the last month on business development while the delivery team quietly ran out of road.
Utilisation is the metric that should answer that question. In practice, it often doesn’t — either because agencies aren’t tracking it properly, or because they’re applying a single blanket target to everyone from a junior developer to a client strategist, which is roughly as useful as averaging everyone’s height and calling it a dress code. This article sets out a more precise framework: what utilisation actually means, what targets make sense across different roles and agency models, and how to avoid the two failure modes (too low and too high) that quietly kill agency profitability and retention.
What Utilisation Actually Measures (and What It Doesn’t)
Staff utilisation is the percentage of a person’s available working time that is spent on billable activity. The formula is straightforward: billable hours divided by total available hours, expressed as a percentage. If a developer works 37.5 hours in a week and logs 26 hours against client projects, their utilisation rate is 69%.
That definition contains a hidden complexity: what counts as “available hours.” The theoretical ceiling is the contracted working week, typically 37.5 or 40 hours. But available hours in practice are lower. Annual leave, public holidays, training days, sick days, and team meetings all reduce the real number. For planning purposes, most agencies use a net available hours figure calculated annually — for a full-time employee in the UK with 25 days’ holiday and eight bank holidays, you are working with roughly 227 billable days, or 1,702 hours, not 1,950.
Utilisation also does not measure quality, focus, or output. A team member logging eight hours a day is not necessarily more productive than one logging five. This is why utilisation should never be used in isolation as a performance metric for individuals — it is a planning and profitability tool, not a proxy for how hard someone is working.
A useful distinction: some agencies separate billable utilisation (hours billed to clients) from productive utilisation (billable hours plus internal project work, training, and investment time). Both are worth tracking, but they serve different purposes. Billable utilisation tells you about revenue efficiency. Productive utilisation tells you whether non-billable time is being invested meaningfully or just lost.
The Right Utilisation Target by Role
The most common mistake agencies make with utilisation is applying one target universally. In reality, the right number differs substantially depending on what a person’s role requires. A senior developer’s week looks nothing like a client services director’s week, and a utilisation target that makes sense for one will be damaging if applied to the other.
Here is a practical framework for role-based targets in a typical UK digital agency:
These ranges assume a healthy operational structure. An eight-person agency where the owner is still the lead developer will have different dynamics, and that’s fine as a stage — but the targets should reflect the reality of how roles are actually structured, not an aspirational org chart.
The Danger Zones: Too Low and Too High
It is worth being specific about what goes wrong at the extremes, because the failure modes are different and require different fixes.
Below 60% blended utilisation is a margin problem. At that level, you are paying for more capacity than you are converting to revenue. For a ten-person agency with an average fully-loaded cost of £45,000 per person per year (salary plus NI plus benefits), a 55% utilisation rate versus a 70% rate represents roughly £120,000 in lost billable output annually — assuming a blended rate of £90/hour. That is a significant number to carry through a P&L.
Low utilisation typically stems from one of three causes: a pipeline that is not filling the schedule fast enough, retainer clients whose contracted hours are not being consumed (unused retainer capacity), or poor visibility of who has capacity — which means work gets allocated to the same people while others sit lighter. The fix is rarely “work harder.” It is usually a combination of better pipeline management and better resource allocation visibility.
Above 80% blended utilisation, the risks shift entirely. The team is running at near-maximum capacity, which means there is no slack to absorb the normal unpredictability of agency work: an urgent client request, a project that turns out to be more complex than scoped, a person who goes off sick for a week. At 85% or above, those events do not cause minor disruption — they cascade. One person’s absence forces their work onto an already full team, quality degrades, deadlines slip, and the pressure accelerates the very thing you are trying to avoid.
High utilisation also has a talent retention dimension. Sustained periods above 80% are one of the clearest predictors of burnout. In the current UK market, replacing a mid-level developer or designer typically costs £8,000–£15,000 in recruitment fees and lost productivity during onboarding. That cost dwarfs the short-term revenue gained from running the team hot.
The optimal band for most UK digital agencies is 65–75% blended billable utilisation. It delivers strong margins, it is operationally sustainable, and it leaves enough headroom to absorb the unexpected.
How Your Agency Model Affects the Right Target
The 65–75% band is a useful starting point, but the right target for your agency is also shaped by how you generate revenue. A predominantly retainer-based agency and a project-based agency face structurally different utilisation challenges.
Retainer-heavy agencies have more predictable revenue but can develop a particular problem: retained clients who consume fewer hours than contracted. If a client is paying for 20 hours a month but the team only logs 12, you either have scope creep risk on one side (the client asks for more and you have no contractual basis to push back) or wasted capacity on the other (you have committed resource that is not converting to output). Retainer agencies should track “retainer utilisation” separately — the ratio of hours consumed to hours contracted, by client — and flag where there is consistent underconsumption.
Project-based agencies face utilisation variance between projects. The gap between project completion and the next project starting is where utilisation craters. The fix is pipeline discipline: your revenue predictability depends on how well you forecast the pipeline and manage the hand-off from one project to the next. Even a two-week bench period between projects, across three developers, represents 210 hours of lost billable capacity.
Mixed-model agencies — which describes most agencies beyond a certain size — need to use the retainer base as a utilisation floor and manage project work to fill above it, rather than treating them as completely separate scheduling pools. If your retainers are consuming 55% of team capacity reliably, you have roughly 10–15 percentage points of project work to fill to hit your target band. That is a very different planning challenge from an all-retainer or all-project model.
How to Measure Utilisation Correctly
The most important thing to get right before setting targets is the measurement itself. Utilisation data is only useful if it reflects reality, and there are several ways agencies systematically undercount or miscount their hours.
The first problem is incomplete time tracking. If your team only logs hours against active client projects and not against internal work, your utilisation figures will be artificially high — the denominator (total hours) is not being tracked, so the ratio looks better than it is. You need every hour captured: client billable, client non-billable (work done for clients but not invoiced), internal projects, business development, training, and administrative time. This is the only way to understand where time is actually going.
The second problem is retrospective logging. When team members fill in timesheets at the end of the week from memory, the data is unreliable. Studies consistently show that retrospective time logging underestimates billable hours (people forget to claim time) and overestimates focused work time (they do not remember the interruptions). The closer to real-time your tracking is, the more accurate your utilisation data will be.
The third problem is confusing capacity with availability. Booked hours are not the same as available hours. If a developer is nominally available for 30 hours this week but is also the on-call person for a client support retainer, their effective availability for new project work is lower. Utilisation models that do not account for support commitments, buffer time, and planned admin will always overstate real capacity.
Marque CRM’s time tracking and utilisation reporting is designed to surface exactly these distinctions. You can see billable versus non-billable breakdown by person, track retainer hours consumed against contracted, and view team-wide utilisation trends over time — without assembling it manually from separate systems each month.
Setting Targets and Reviewing Them
Once you have reliable data, setting targets is relatively straightforward. Here is a process that works for agencies at most sizes:
- Calculate your current blended utilisation for the last 90 days. This is your baseline. Do not start with a target — start with the reality.
- Break it down by role type using the framework above. The blended number hides more than it reveals. You want to know whether you have a developer utilisation problem or a leadership utilisation problem — they require completely different responses.
- Identify the outliers. Anyone consistently below 55% or above 82% is in a zone that warrants attention. Below, you need to understand why — pipeline gap, poor allocation, or structural role mismatch? Above, you need to understand whether it is temporary (a project sprint) or chronic (a staffing problem).
- Set role-specific targets, not a single agency-wide number. Communicate these to the team — people perform better when they understand what good looks like and why.
- Review monthly, not quarterly. Utilisation is a fast-moving metric. A quarterly review means you are responding to problems that happened two months ago. Monthly reviews let you catch drift early enough to act.
One thing worth being explicit about: targets should not be shared with individuals as performance metrics in isolation. A developer who knows they are being measured on utilisation percentage will game it — logging hours to internal tasks to hit the number rather than actually being productive. Utilisation at the individual level is a planning input and a coaching signal, not a KPI for appraisals.
Connecting Utilisation to Agency Profitability
Utilisation on its own does not tell you whether you are profitable — it tells you whether your capacity is being converted to output. To connect it to profitability, you need to combine it with your effective hourly rate and your cost base.
The key metric here is revenue per available hour (sometimes called RPAH or “shop rate performance”). Take your total revenue in a period, divide it by the total available hours across the team in that period, and you get a revenue-per-hour figure that you can benchmark against your loaded cost per hour. If your team costs you £35/hour on a loaded basis (salary, NI, benefits, overhead allocation) and your revenue per available hour is £42, you have a healthy margin. If your revenue per available hour is £28, you have a problem regardless of what your utilisation looks like in isolation.
For a 10-person agency running at 70% utilisation with a blended rate of £90/hour, the maths look like this: 10 staff × 37.5 hours × 70% × £90 = approximately £23,600/week in billable revenue, or roughly £1.23m annually. That is the revenue ceiling for your current team size before hiring. Knowing this number — and knowing that moving from 65% to 72% utilisation adds around £85,000 in annual revenue without any additional headcount — clarifies why utilisation tracking is worth taking seriously.
The reporting and utilisation modules in Marque CRM connect time tracking directly to invoicing and retainer data, so you can see this picture in one place rather than building it from spreadsheets each month. The metrics that matter most for agency owners all flow from the same underlying time data — which is why getting that foundation right is the first step.
Practical Starting Points
If you are reading this without a clear picture of your current utilisation, the most important step is not setting a target — it is getting the data. You cannot manage what you cannot measure, and in most agencies, the data problem is more urgent than the target problem.
Start here:
- Audit your time tracking coverage. Are all your team members logging time? Are they logging non-billable time as well as billable? If not, you are working with an incomplete picture.
- Calculate your actual blended utilisation for the last quarter, broken down by role. This will reveal where the real constraints are.
- Identify your highest and lowest utilisation individuals and understand why. High outliers may be heading for burnout. Low outliers may have a pipeline or allocation problem that is solvable.
- Set role-specific targets using the framework above as a starting point, adjusted for your agency’s model and growth stage.
- Review monthly and track trends, not just point-in-time snapshots. A utilisation rate that has moved from 68% to 78% over six months is a very different signal to one that has been stable at 78% for two years.
The agencies that manage utilisation well are not the ones chasing the highest billable percentage. They are the ones who understand the relationship between capacity, margin, and sustainability — and who make resourcing decisions based on real data rather than gut instinct. That distinction, more than any individual target number, is what separates the agencies that grow profitably from the ones that grow themselves into trouble.
For more on building the systems that make this kind of management possible, see our guides on agency capacity planning and the metrics every agency owner should be tracking.