Guide
Updated 2026-07-08 · For delivery managers and founders at 5–200-person IT services teams
If you sell people's time — agency, dev shop, outsourcing, consultancy — capacity planning answers three questions, every week:
Most 5–50-person teams answer these from a spreadsheet that one delivery manager maintains by hand. It works until the week that person is on vacation — which is, reliably, the week a client asks for two more people.
Utilization numbers lie when they mix people and work that should never be counted. The PSA-standard model uses two independent flags:
One more correction most spreadsheets skip: people on approved leave should leave the denominator for those days. Utilization net of PTO is the number worth managing to; gross-of-PTO utilization punishes teams for taking vacations.
Timesheets record the past in hours; planning works better in percentages. “Olena is 60% on Project A and 40% on Project B” survives a short week, a public holiday, and a sick day — “Olena does 24 hours on A” does not. Percentages also make overallocation instantly visible: the moment someone's assignments sum past 100%, you have a decision to make, not a surprise to discover in next month's retro.
The practical setup: one row per person, one column per week, each cell = total allocated percentage, color-coded. Under ~80% is bench capacity you can sell; 80–100% is healthy; over 100% is a fire.
“Bench” — people allocated under 100% — is where agency margin is won and lost. A visible bench row lets you do three useful things: staff new deals from real availability instead of guesswork, schedule internal work and learning into genuinely free weeks, and spot the roll-off before it happens (an engineer whose project ends in three weeks should already be in a sales conversation today).
Treat it as inventory management. Hiding the bench doesn't shrink it — it just delays the moment you find out about it.
Annual capacity plans in services businesses are fiction — clients extend, cancel, and change scope quarterly. A rolling 12-week forecast is long enough to see roll-offs and hiring needs coming, and short enough to stay true. Review it weekly in the same 15 minutes you review pipeline: capacity and sales are two sides of one decision.
Helia HR is an HR system with delivery operations built in — made for exactly this workflow:
What utilization rate should an agency target?
For billable staff, 70–85% net of PTO is a sustainable band for most services teams. Persistently above ~90% usually means burnout risk and no slack for pre-sales; persistently below ~65% means the bench is quietly eating your margin.
Should founders and managers count as billable?
Only for the share of time they actually bill. Most teams mark them overhead and treat any billed hours as upside — it keeps the utilization number honest.
Is a spreadsheet enough to start?
At 5–10 people, often yes. It breaks when allocations change weekly, when leave stops being visible in the plan, and when the person who owns the sheet becomes a single point of failure — usually somewhere between 10 and 20 people.
Helia HR combines the HR basics with the capacity matrix, bench view, timesheets and client invoicing agencies actually run on — at a fraction of PSA-suite prices. Start free, no card. Privacy-first: GDPR-grade security, role-gated PII, audit-logged access.