Capacity problems in agencies tend to appear in the same two forms. The first is overallocation: the team is stretched across too many projects, delivery slips, quality suffers, and people burn out. The second is bench time: work completes, the next project has not started yet, and billable hours fall off. Both are expensive. Both are largely avoidable with a basic capacity planning process.
Resource capacity planning is the practice of understanding how much work your team can realistically take on, matching that against what is committed or likely to come in, and making decisions about staffing, pacing, and intake before problems surface rather than after. For most agencies, this is less about sophisticated forecasting models and more about having the right information visible at the right time.
This guide covers how to calculate capacity, how to match it against demand, and how to build the weekly rhythm that makes capacity planning a habit rather than a crisis response.
In a professional services context, capacity planning has two sides. Supply is the total productive hours your team can realistically deliver in a given period, after accounting for leave, public holidays, non-billable commitments, and the overhead of meetings and administration. Demand is the hours required to deliver committed projects plus a probability-weighted estimate of work likely to come in from the pipeline.
Capacity planning is the process of keeping supply and demand in alignment. When demand consistently exceeds supply, the agency is overallocated. When supply consistently exceeds demand, you have bench time. Both states cost money, but they cost it differently. Overallocation costs you through delivery failure, client attrition, and staff turnover. Bench time costs you directly through unrecovered staff cost.
According to capacity planning research across professional services firms, 58% of resource managers in 2026 cite aligning capacity with demand as their top operational priority, yet the average utilization rate across organizations sits at 72%, below the 80 to 85% that top-performing professional services firms maintain. That gap represents significant lost revenue across the industry.
For agencies specifically, capacity planning has a few characteristics that make it more complex than for product or internal teams. Project demand is lumpy: new work arrives unevenly and client timelines shift. The team is often split across multiple clients simultaneously. Skill availability matters as much as headcount: having 200 available hours means nothing if none of them belong to the person the project needs.
The starting point is a clean picture of what your team can actually deliver in any given week or month. The formula is:
Available capacity = (Contracted hours per week minus planned leave minus non-billable commitments) multiplied by the number of people in that role
For example: a team of five designers each contracted at 40 hours per week gives you 200 theoretical hours. Subtract planned leave (8 hours across the team), internal meetings (5 hours each, so 25 hours), and non-billable admin time (2 hours each, so 10 hours). Available capacity is 200 minus 43, which equals 157 productive hours available for client work that week.
That 157 hours is your supply. It is not the same as your target billable hours. Most agencies target billable utilization of 70 to 80% of available capacity, which means planning for 110 to 125 billable hours from that team in that week. The remaining hours absorb unplanned client requests, quality review time, and the inevitable surprises that every project throws up.
The relationship between available capacity and actual billable output is your billable utilization rate. Tracking it alongside capacity gives you a complete picture of both how much your team can do and how much of that is generating revenue.
One important detail: capacity should be calculated per person, not just per team. Two developers with 40 hours each is not the same as four developers with 20 hours each if the project requires continuous focused work. Aggregate team capacity is useful for pipeline decisions. Individual capacity is what project scheduling actually runs on.
Once you know your supply, you need a picture of demand. For agencies, demand comes from three sources: active projects with committed timelines and hours, pipeline opportunities that have a reasonable probability of closing, and repeat work from existing clients that has not been formally scoped yet.
Active projects are the most predictable. You know what has been sold, you can see the project plan, and you can calculate the hours required per resource per week to deliver on schedule. This is your committed demand.
Pipeline demand requires a probability weighting. A 200-hour project at 80% likelihood to close contributes 160 hours to your demand forecast. A 400-hour project at 25% likelihood contributes 100 hours. This is a rough approximation, but it prevents the two failure modes of ignoring pipeline entirely (which leads to overcommitting capacity) and treating every prospect as certain (which leads to under-selling and bench time).
Repeat client demand is the hardest to quantify but often the most predictable in practice. Most agencies have clients whose monthly or quarterly spend follows a pattern. Building that baseline into your capacity plan, even at a conservative estimate, produces a more accurate picture than treating every month as if it starts from zero.
When you lay committed plus probability-weighted demand against available supply by role, you can see capacity gaps and bottlenecks before they become problems. A gap at a senior level in week 6 is actionable today. The same gap discovered at the start of week 6 is a crisis.
Most agency capacity failures are not caused by a lack of tools or process sophistication. They are caused by a small set of recurring mistakes.
Planning to 100% utilization: Allocating every available hour to committed work leaves no buffer for unplanned requests, project variance, or the time it takes to hand off and context-switch. The practical result is that even a minor disruption causes a cascade. Planning to 75 to 80% of capacity gives the team room to absorb variance without delivery failure.
Tracking capacity at the team level only: Knowing that your development team has 80 hours free next week is useful. Knowing that those 80 hours belong to two junior developers and none of them are senior is critical. Capacity planning at team-level averages masks skill distribution problems that show up as delivery failures.
Ignoring non-billable time: Internal meetings, business development, training, and administrative work are real time costs. Agencies that do not account for non-billable overhead in their capacity calculations consistently overestimate how much billable work the team can deliver.
Treating the capacity plan as a static document: Capacity changes every week. Leave is booked, projects shift timelines, clients request additional work. A capacity plan reviewed monthly is out of date within days. The cadence needs to match the pace of change, which for most agencies means weekly.
Separating capacity planning from sales: When the sales team commits capacity for projects without checking availability against the current plan, overallocation is not a risk, it is a certainty. Capacity planning only works when sales, delivery, and operations share a single view of availability.
A weekly capacity review does not need to be a long meeting. For most agencies, 30 to 45 minutes with the right people and the right data is enough to stay ahead of problems.
The capacity review needs representation from delivery (project managers or team leads who know what is actually happening on active projects) and from the commercial side (whoever owns the sales pipeline and knows what is likely to close and when). Without both, the review either lacks the pipeline context needed to plan ahead or lacks the ground-level visibility of what delivery actually has bandwidth for.
Current week and next two weeks of committed demand by role, compared against available capacity. Any changes to project timelines that affect resource allocation. Pipeline updates that will affect capacity over the next four to six weeks. Any team members approaching sustained high utilization who need load reduction or timeline adjustment before burnout becomes a risk.
Each review should end with a clear list of decisions or flags: any project whose timeline needs adjustment, any role where a freelancer may be needed in the next two to three weeks, and any pipeline deal where intake timing needs to be coordinated with delivery capacity. These actions should be assigned before the meeting ends.
Capacity planning gives you the lead time to make resourcing decisions well rather than under pressure. The two options for filling a capacity gap are bringing in freelancers or contractors, or making a permanent hire. The decision depends on how long the gap is likely to last and how certain that assessment is.
Freelancers are the right call when the gap is project-specific or short-term, when the skill required is specialised and unlikely to be needed regularly, or when the pipeline gives you confidence about demand for the next six to twelve weeks but not beyond. They are also the right call when a hire would take longer to complete than the gap can wait. A hire that takes three months to close does not solve a capacity problem that arrives in four weeks.
A permanent hire is the right call when you have sustained demand for a role over at least twelve months, when the skill is core to your service delivery and building internal capability has strategic value, or when the volume of freelancer spend on a particular skill has reached a level where a hire would be less expensive. Using a freelancer to cover a structural gap costs you the rate premium plus the management overhead of working with external resources.
The capacity plan gives you the data to make this call with evidence rather than instinct. If you can see that you have needed 80 hours per week of senior copywriting for the past six months and your pipeline suggests that continues, the hire decision practically makes itself.
According to SPI Research, firms that invest in resource management maturity show significantly better performance on on-time delivery, billable utilization, and overall profitability than firms that operate reactively. The differentiator is rarely the tool they use. It is the consistency of the process.
Capacity planning and project profitability are closely linked. Overallocation compresses project margin through senior-on-junior substitution and late rework. Bench time creates unrecovered staff cost. Getting capacity right is one of the most direct levers on profitability available to an agency.
Pike gives agencies a real-time view of team capacity across all active and upcoming projects, so you can see gaps and bottlenecks before they create problems. See how it works.
Capacity planning focuses on the supply side: how many hours does the team have available in a given period, by role and by skill. Resource planning is the allocation side: assigning specific people to specific projects and tasks within that capacity. Capacity planning tells you whether you can take on new work. Resource planning tells you who does it and when. You need both, but capacity planning typically comes first: it is the decision about whether to commit, before resource planning works out how to execute.
Most agencies benefit from a rolling six-week planning horizon as their primary operational view, updated weekly. A secondary view covering the next three to six months is useful for hire decisions and pipeline strategy, though that view will carry more uncertainty. The six-week operational view is where the actionable decisions live: who is allocated where, where gaps are opening, and whether pipeline deals need to be paced or accelerated based on current capacity.
For production roles such as designers, developers, and writers, most agencies target 75 to 80% billable utilization of available working hours. For account and project management roles, 60 to 70% is more realistic given the proportion of time spent on internal coordination and client management that is not directly billable. Sustained utilization above 85 to 90% is a burnout risk and typically signals an underlying capacity problem that needs to be addressed rather than managed around.
Spreadsheets work for very small teams or as a starting point, but they break down quickly as team size and project complexity grow. The core problem is that spreadsheets are a snapshot tool: they show you capacity at the moment the spreadsheet was last updated. As soon as project timelines shift or leave is booked, the data is stale. Resource capacity planning guides consistently point to real-time visibility as the key differentiator between agencies that manage capacity proactively and those that respond to problems after they surface. Once you have more than eight to ten people or more than five concurrent projects, a purpose-built tool pays for itself in avoided delivery failures.
If your team feels stretched one month and underused the next, capacity planning is the fix and it does not need to be complicated to work. Book a demo to see how Pike helps agencies stay ahead of capacity: book a free demo.
02 Jun 25
