Resource Allocation for Billable Teams: A Simple System

Here's a pattern almost every services firm recognizes. The team's overall utilization looks fine — say 72 percent. But your senior developer hasn't had a free hour in six weeks, your designer is quietly refreshing job boards out of boredom, and a project just slipped because the one person who could do the work was triple-booked.

That's not a capacity problem. It's a resource allocation problem — and the difference matters, because the fixes cost wildly different amounts. Capacity problems are fixed with hiring or selling. Allocation problems are fixed with a whiteboard.

The team average is lying to you

Averages blend the extremes into a comfortable middle. A six-person team can post a healthy average while carrying both burnout and bench:

The numbers above are an illustration, not client data — but the shape is the point. Run utilization per person before you trust any team-level read (the formula lives in our utilization rate guide). The spread between your most- and least-loaded person is often the single most actionable number in the business.

Capacity versus demand: the forward look

Per-person load is the snapshot. Allocation also needs the movie: what does booked work look like next month, against next month's capacity? This is where most small firms fly blind — they know today's chaos in detail and next month's not at all.

The forward comparison sorts into three cases, each with different moves:

• Demand exceeds capacity. Your levers, cheapest first: rebalance, subcontract the spike, raise rates to shape demand, hire if it's sustained, or decline work honestly. (The hire branch has its own math — run it before posting the job.)
• Capacity exceeds demand. You have a bench. Sell it first — outreach to past clients, expanded scopes, productized offers — and put the remainder into chosen productive work. Don't let it silently become "everyone seems busy anyway."
• Roughly matched. Healthy — protect it by checking every new engagement before it lands, which is the next section.

The check before every yes

Allocation falls apart one enthusiastic yes at a time. The fix is a standing habit: no new engagement gets accepted until it's been checked against real capacity. The check takes five minutes:

1. Size the engagement — weekly hours and rate, roughly.
2. Lay it against current load — whose hours would it consume, and what are those people running at now?
3. Read the verdict — it fits inside target; it fits only by running hot (fine for a sprint, not a lifestyle); or it doesn't fit, and the yes requires subcontracting, hiring, or a start-date shift.
4. Decide out loud — take it, stage it, staff it, or decline it. Any of these beats the silent yes that overloads your best person again.

This is exactly what the Planner's New Work Check automates: enter the prospective client's hours and rate, and it shows whether the team absorbs it within target, only above target, or not at all — plus the added revenue and the extra capacity (in FTE) a yes would need.

Make it a cadence, not a crisis

Resource allocation works as a monthly rhythm, not a fire drill: update per-person numbers, glance at the spread, compare next month's demand to capacity, and pre-check anything in the pipeline that might close. Twenty minutes a month keeps the two expensive surprises — a burnout resignation and a panic hire — off your calendar.

If you run an agency, the Agency Operators Skills Pack ($89) picks up where the math ends — installable Claude skills for the status reports, scope-creep pushback, and renewal comms that allocation decisions turn into. And if you do this professionally across client companies, the Fractional Executive & Consultant Skills Pack ($99) packages the operator playbook for running someone else's capacity honestly.