Capacity Planning for Professional Services: Matching People to Pipeline Before It Hurts

Hiring a good permanent consultant or engineer takes roughly a quarter, while pipeline rarely gives that much warning, so capacity planning in professional services works best as a rolling twelve week model that sets weighted pipeline against named team availability, role by role, and is reviewed every week. The model will not predict the future, but it tells you early enough whether to hire, bring in contractors or hold your nerve, which is the decision that actually matters.

Why capacity planning hurts in a scaling services firm

The tension is structural rather than a failure of anyone's judgement, because sales operates on a horizon of weeks while hiring operates on a horizon of months, and in a business of somewhere between 20 and 60 people there is rarely enough slack to absorb the difference. When a large deal closes unexpectedly, delivery is stretched across people who are already allocated, quality slips and the founder steps back into projects to hold them together. When two deals slip in the same month, the opposite happens, and a bench appears that quietly erodes margin while everyone waits for sales to catch up.

Most firms in this position are not short of data, since they have a CRM full of opportunities and a resourcing sheet full of names, but the two live in different places, owned by different people, and are only joined together in someone's head, usually the founder's. The rolling model described here does nothing more sophisticated than put those two sources side by side so that the gap between them becomes visible before it becomes painful.

Building a twelve week capacity view in a spreadsheet

You need three tabs, and the discipline lies less in the formulas than in keeping each tab honest.

Tab one: supply, meaning who is actually available

List every delivery person by name and by role, with one column per week for the next twelve weeks. In each cell, enter the days that person can realistically deliver, which means contracted days minus known holiday, training, internal work and a sensible allowance for the unplanned, rather than the five days the contract implies. Then subtract days already committed to signed work, so that what remains is genuinely free capacity. If your realistic delivery days look suspiciously high, the guidance on measuring utilisation properly is worth reading before you trust the totals.

Tab two: demand, meaning weighted pipeline

List each open opportunity with its stage, a probability for that stage, an expected start week, its duration and the roles and days per week it would need. Multiply the days by the probability to get weighted demand, and spread it across the weeks the work would run. The probabilities should come from your own history of how often deals at each stage actually close, and where you have no history you should set conservative figures and correct them each quarter, because a weighting borrowed from optimism is worse than none.

Tab three: the capacity view

For each role and each week, take free supply from tab one and subtract weighted demand from tab two. A positive number is spare capacity, a negative number is a shortfall, and conditional formatting that turns shortfalls red and large surpluses amber is enough to make the sheet readable in a meeting. Keep it at role level rather than individual level for the leadership view, because the question leadership is answering is whether you have enough senior developers in week seven, not whether a particular person is free on a Tuesday.

Contractors, permanent hires or a bench

Once the capacity view shows a gap, the harder question is how to close it, and the answer depends on how long the gap lasts and how confident you are in it.

• Contractors suit shortfalls that are short, specialist or uncertain, because they cost more per day but can be released when the work ends, which turns a fixed cost into a variable one.
• Permanent hires suit shortfalls that appear across most of the twelve weeks and survive a deal or two slipping, since a gap that only exists if every opportunity closes is not a reason to add salary.
• A deliberate bench, meaning a small amount of planned spare capacity in roles that are hard to recruit, suits firms whose pipeline reliably contains work for those roles, provided it is sized on purpose and costed rather than left to accumulate by accident after one lumpy quarter.

A useful test is to strip out every opportunity below your most reliable stage and look again: if the gap survives on signed and near-certain work alone, start the permanent hire now, because it will take a quarter to land; if it disappears, cover it with contractors and revisit next month. Firms with more predictable income find this decision far easier, which is one reason the work on building recurring revenue pays off in delivery as well as finance.

The governance cadence that keeps the model honest

A capacity model decays quickly when nobody owns it, because probabilities drift upwards, start dates slide without anyone updating them and the sheet becomes a document people agree with rather than one they act on.

1. Weekly, for around thirty minutes: delivery and sales leads update start dates, stages and allocations together, so that the person who knows the deal and the person who knows the team are looking at the same numbers.
2. Monthly, at the leadership meeting: review the role-level view, agree any hire, contractor or bench decision with a named owner and a date, and record what was decided so the next review can test it.
3. Quarterly: compare forecast against what actually happened, correct the stage probabilities and the realistic delivery days, and ask whether persistent shortfalls point to a pricing or sales mix problem rather than a capacity one.

This sits naturally within a wider rhythm of governance for a growing SME, and the point of it is that capacity decisions are made by the leadership team on shared evidence rather than by the founder on instinct late on a Thursday.

Where Vitori fits

Everything above can be built and run in-house, and many firms do it well with nothing more than a spreadsheet and a weekly habit, whether with Vitori or anyone else. Where it tends to stall is the joining of sales and delivery into one conversation, which is an operating model problem more than a spreadsheet problem. Capacity sits within the Delivery and Operations pillars of Vitori's Operational Scale Framework, and through the Operator model Vitori can embed to build the cadence and stay until it holds. If that would help, you can get in touch with Vitori to talk it through, with the aim being a business that runs, and scales, without the founder in every decision.

Common questions about capacity planning

How far ahead should a professional services capacity plan look?

A professional services capacity plan should look at least as far ahead as your hiring lead time, which for permanent roles is often around a quarter, so a rolling twelve week view is a practical minimum. Some firms add a lighter six month view at role level for strategic hiring, but the twelve week view is where weekly decisions are made.

What tool should I use for capacity planning instead of a spreadsheet?

A spreadsheet is enough for most firms of 20 to 60 people, and building one first teaches you which inputs you trust. Professional services automation tools become worth considering once the weekly update takes too long or the data lives in too many places, but a dedicated tool will not fix stage probabilities or start dates that nobody keeps honest.

Who should own the capacity model?

The capacity model works best with a single owner in delivery or operations who maintains the sheet, while sales owns the accuracy of pipeline data and delivery leads own allocations. Making the founder the owner tends to recreate the original problem, because capacity decisions then depend on one person's availability rather than on a shared process the leadership team runs.