Agency Capacity Planning Guide: Workload and Hiring Triggers

A new project lands in the inbox and the honest answer to whether you can take it is not sitting in anyone’s head. It is sitting in a spreadsheet nobody built. Capacity planning is the discipline of knowing that answer before you say yes, not scrambling to build it after the contract is signed.

My basis for this: twelve years running delivery operations for marketing agencies and 92 completed engagements. One flag before you read on: there is no benchmark percentage anywhere in this piece. Nobody has published a credible number for what agency capacity should look like, and inventing one so this article feels more authoritative would make it less useful. The honest comparison is your own trend, not an industry average that does not exist.

What is agency capacity planning, and how is it different from utilization?

Utilization tells you what already happened. It is a rearview number, billable hours over available hours, measured after the fact, one of the metrics I set out in the piece on the KPIs that actually run agency delivery and unpacked in full in the utilization deep-dive. I am not going to repeat the formula here. What I want to cover is the question utilization cannot answer: not what happened last month, but what you can commit to next month.

Capacity planning is forward and aggregate. Forward, because it gets asked before you sign the contract, not after. Aggregate, because at this stage the question is whether the agency as a whole has room, not which specific person picks up which task in week three of the project. That second question is a real discipline with its own piece and its own rhythm, and I am deliberately not covering it here. This one stays at the level of the whole agency: what can we take on, do we have room to sell it, and when does the answer mean hire.

Is headcount capacity the same as delivery capacity?

No, and the gap between the two is where most overselling starts. Headcount capacity is a multiplication: number of people times hours in the working week. It is the number a spreadsheet produces in about four seconds, and it is almost never the number that matters.

Delivery capacity is that headcount number after you subtract everything headcount does not account for. The non-billable work the agency needs just to keep functioning. The ramp time a new hire needs before they produce at full rate. The ceiling I wrote about in the utilization piece, the point past which more booked hours produce more rework rather than more delivered work. Delivery capacity is always smaller than headcount capacity. How much smaller is specific to your agency, and it will not show up in a formula copied from somewhere else. It shows up when you track your own forward view for a quarter and compare what you sold against what actually shipped on time.

How do I build a forward capacity view from what I already have?

You do not need new software for this. If the agency runs on ClickUp, Asana, Monday.com, Airtable or Notion, the raw material is already sitting in it. Four steps, run at whatever cadence matches your sales cycle, monthly for most agencies, weekly if the pipeline moves fast:

  1. List every live contract and its hours run rate for the period ahead. This is committed load, not a forecast.
  2. List the pipeline, weighted by how likely each deal is to close. A deal you would call a coin flip contributes half its hours to the forward number, not all of it and not none of it.
  3. Total delivery capacity for the same period, the discounted number from the section above, not the headcount multiplication.
  4. Subtract committed load plus weighted pipeline from delivery capacity. What is left over is headroom. What is missing is a deficit, and a deficit is information, not a crisis, provided you see it before you have already sold into it.

Run this before every sales conversation of any size, not once a quarter in a planning meeting. A forward view built once a quarter is stale by the second month of it.

Do I actually have room to sell this?

This is the question capacity planning exists to answer, and most agencies answer it by feel. Feel runs in both directions, and both are expensive. An owner who feels busy turns down work the forward view would have shown room for, and pipeline that could have funded a hire quietly goes to a competitor instead. An owner who feels fine signs a contract the forward view would have flagged as a deficit, and the agency delivers it by borrowing capacity from the next thing already promised to someone else.

The fix is not more confidence. It is checking the number built above before the proposal goes out, not after the client signs. If a new deal would push committed load plus weighted pipeline past delivery capacity, there are three honest options before saying yes: negotiate the timeline, bring in subcontracted capacity for the peak, or say no to something else on the list to make room. Saying yes and hoping the gap closes itself is the fourth option, and it is the one that shows up as missed dates two months later.

When does a capacity gap mean it is time to hire?

Not the first time the forward view shows a deficit. A single tight quarter is normal, and the answer to it is usually one of the cheaper levers: reprice a service line that consumes disproportionate hours for its fee, bring in subcontracted capacity for the peak, or fix whatever is generating unbilled rework in the first place. I go through options like these in more depth when I work with an agency as an operations consultant, and none of them require adding permanent payroll.

Hire when the deficit is structural rather than transient. It shows up period after period. It shows up regardless of which service line is driving it that month. And the cheaper levers have already been pulled without closing the gap. That pattern says the agency has sold past its permanent capacity, not that one month ran hot. The trigger is the pattern, not the number on any single forward view. One tight quarter proves nothing. Three in a row, built the same way each time, is a hiring decision wearing a scheduling problem’s clothes.

What should I check before I act on a hiring signal?

Rule out three things first. One, confirm the numbers were built the same way each period, the same definition of delivery capacity, the same pipeline weighting, because a deficit that only appears when you change your own methodology is not a deficit, it is noise. Two, confirm it is not a pricing problem wearing a capacity costume. An underpriced service line can make the whole agency look short-handed when the real fix is the rate card, not the roster. Three, confirm the shortage is genuinely aggregate and not simply a reflection of how the work currently sits across the people already on the team. That is a real problem, and it deserves its own piece and its own fix rather than being folded into a hiring decision it did not actually cause.

Once those three are ruled out and the deficit still holds, hire. Not because a formula said so, because the aggregate forward view, built the same way for three periods running, says the agency has sold more than its permanent capacity can carry, and every lever short of adding headcount has already been tried.

So what is my capacity planning verdict?

Build the forward view before you need it, not while a client is on hold waiting for an answer. Keep it aggregate, not per person. Use delivery capacity, discounted from headcount, never headcount itself. Check it before every proposal of any size, not once a quarter. Treat a single tight period as normal and a repeating one as a signal. Hire on the pattern, after the cheaper levers have been tried and the deficit still holds, not on the strength of one loud month. That is the whole of my position, and like the utilization number it feeds into, it only works if it is built the same way every time and trusted over how the week felt.

Where to start

If you want an outside read on whether the agency’s forward capacity actually matches what the pipeline is asking of it, that is one of the things the Agency Ops Audit is built to answer. It is a $1,500 fixed-fee review, two weeks, ending in a written 90-day roadmap and a 60-minute readout call. If the honest answer is that there is room and the real issue is pricing or intake, I would rather say so in the readout than sell a hiring plan that is not needed.

Monis Ahmed Khan

Monis Ahmed Khan

Project & Operations Manager for Digital Marketing Agencies

Monis Ahmed Khan manages day-to-day delivery for digital marketing agencies and uses AI automation to reduce repetitive work. Twelve years and 92 completed engagements.

Free weekly dispatch

Field notes from agency delivery.

Notes on agency operations, delivery, and the AI that runs it — from the work, not the theory.

Similar Posts