How do I know if we can take on a new client without burning out the team?

What is agency capacity planning?

Capacity planning is the process of comparing how many billable hours your team actually has available against how many hours your current and prospective client work needs, so you can tell whether taking on new work is safe or whether it will burn people out. Most agencies that skip this run on instinct: the team says they're "pretty stretched" or "could probably fit it in," and that answer is usually optimistic because nobody wants to be the person who says no to new revenue. A number fixes that, because a number doesn't care about anyone's optimism.

The capacity formula

For each person on the team, for a given month:

Available hours = working days × hours per day, minus planned time off, minus recurring internal time (team meetings, admin, training). A typical agency employee working 5 days a week at 8 hours a day, with 10% carved out for internal meetings and admin, nets out to roughly 29 to 30 billable hours a week, not 40.

Committed hours = the sum of estimated hours needed across every active client account that person works on, for that same period.

Free capacity = available hours minus committed hours.

Once you have free capacity per person, roll it up by role or team, since a content writer being at 100% capacity doesn't tell you anything about whether your designer has room. A new client's workload needs to fit inside the specific roles it actually requires, not inside your team's capacity in the aggregate.

A worked example

Say your agency has three account managers, each with roughly 30 available billable hours a week after internal time is subtracted. Their current client commitments: AM1 at 26 hours, AM2 at 29 hours, AM3 at 22 hours. A new client needs an estimated 8 hours a week of account management time. Only AM3 has that much free capacity (8 hours free against an 8-hour need), so the new client goes to AM3, or the work gets redistributed first if AM3 isn't the right fit for that account. If all three AMs were already above 85% committed, the honest answer is that nobody has room, and taking the client on without changing something (hiring, trimming scope on an existing account, or raising a price to compensate for the strain) means someone's either working unpaid overtime or an existing client's quality slips.

A month-long cycle at a 12-person agency

A single snapshot is a start, but the real value shows up when you run the same check across a full month. Take a 12-person agency: three account managers, four designers, three developers, a strategist and a project manager. At the start of November, the design team's available hours come out to 480 for the month (4 designers × 30 billable hours a week × 4 weeks). Against that, active client contracts have 410 hours of design work allocated, which leaves a planned buffer of 70 hours, roughly 15% headroom, comfortably under the 85% utilization line.

By the third week, the project manager runs a mid-month check rather than waiting until month-end, and the picture has shifted: design has already logged 365 hours against that 410-hour allocation, with ten working days still left in the month. At the current pace, the team is on track to log close to 520 hours by month-end, 110 hours over what was planned. The cause, once traced back through the project management tool, is a single client whose scope quietly grew from two rounds of revisions per deliverable to four, a change nobody formally approved or re-quoted. Catching that in week three, instead of discovering it in the November wrap-up report, gives the agency three options while there's still time to act: pause and re-scope that one account, pull a developer with slack capacity into light design-adjacent work temporarily, or bring on a freelance designer for the rest of the month. The agency goes with the first option, has the account manager re-scope the client's remaining deliverables back to two revision rounds, and closes November at 438 design hours, 28 over plan instead of 110, with the overage billed back to the client as a scope change rather than absorbed as free work. That's the actual payoff of capacity planning: not a tidier spreadsheet, but a decision made with three weeks of runway instead of zero.

A simple capacity planning template

Person	Available hours/week	Committed hours/week	Free capacity	% utilized
AM1	30	26	4	87%
AM2	30	29	1	97%
AM3	30	22	8	73%

Build this as a live spreadsheet or table that updates as client workloads change, not a one-time exercise you do before a big pitch and then forget about. A spreadsheet version of this works fine at a small agency; the limit shows up once you're pulling committed hours from several project tools by hand each week, which is where the manual version starts costing more time than it saves. My Excel to web app guide covers the point where a spreadsheet like this is worth turning into something that updates itself.

Common capacity planning mistakes

• Using scheduled hours instead of actual historical hours: If a task is supposed to take 5 hours but historically takes 7, your estimates need the real number, pulled from past time tracking, not the optimistic original quote.
• Ignoring internal, non-billable time: Team meetings, internal reviews and admin eat a real chunk of the week. Leaving that out of "available hours" overstates capacity by 10 to 20% on most teams.
• Planning at the team level, not the role level: An agency "at 70% capacity" overall can still have zero free hours in the one role (often design or a senior strategist) that a new client actually needs most.
• Not revisiting the number regularly: Capacity shifts every time a client scope changes, someone leaves, or a project runs long. A monthly or biweekly check catches the drift before it becomes a crisis.

How do you estimate committed hours for a client you haven't started yet?

For an existing client, committed hours come from real time-tracking history, which is the most reliable number you have. For a prospective new client, you don't have that history yet, so the estimate has to come from a comparable existing account: find a current client of similar size and service scope, use their actual logged hours as the stand-in estimate, and adjust up if the new client's scope is genuinely broader. Estimating from a quoted scope of work alone, without anchoring it to a real comparable account's actual hours, is one of the most common reasons capacity plans turn out optimistic once the new client actually starts.

When is it time to hire instead of squeezing more in?

A few honest signs: your team is consistently above 85 to 90% utilization across more than one role for more than a month or two, you're turning down qualified new business specifically because of capacity rather than fit, or overtime has become the normal way projects get finished rather than the exception. Hiring ahead of 100% utilization, not after, is what keeps quality steady; waiting until the team is already drowning to post a job means several more months of strain before the new hire is even up to speed.

How would Blur Studio approach this for your agency?

A spreadsheet is the right starting point, and I'd tell you to stick with one if it's working. Where I come in is when that spreadsheet needs to be fed by real data instead of manual updates: a live view that pulls actual logged hours from your time tracking tool and current workload from your project management tool, rolled up by role, so the capacity number on the screen is always current instead of a snapshot from two weeks ago that's already wrong. My KPI dashboard guide covers the thinking behind building a live view like that, and my staff scheduling software guide covers tools built specifically for the scheduling side of this problem.