SEO agency capacity planning is the practice of converting what you have sold into hours of delivery work, comparing that to the hours your team can supply, and deciding in advance when to hire. The number that makes it work is hours per unit of work, and that number has to come from your own time records. Nobody else's average describes your team.
Utilization is the related metric, and I cover how to read it in what a good utilization rate looks like. Capacity planning is the forward-looking version: instead of asking how busy people were last month, it asks whether you can take on the next client.
Units of work in SEO agency capacity planning
The unit is the smallest repeatable piece of delivery that you can count and time. SEO has a natural set:
- Technical fix tickets, from a one-line redirect rule to a template change.
- Content pieces, including brief, draft, edit and on-page optimization.
- Link or outreach batches.
- Reports and review calls.
- Onboarding audits, which happen once per client.
Add a unit for account management and communication, because it is real time and it is the first thing left out of a plan. Many agencies undercount this and then wonder why a client who needs only a few tickets a month still fills a week.
Finding hours per unit
You measure it. Pull a few months of time entries, group them by unit type, and take the typical hours for a completed unit, using the median and noting the spread. A content piece that takes anywhere from 4 to 12 hours needs to be split into types, not averaged into one muddy figure.
Two cautions. First, time data is only as honest as the logging behind it. If people log to the billing code that is easiest instead of the one that matches the work, your units will be wrong, and the problem is the same one described in why utilization can look fine while margin drops. Second, remeasure after any process change. Templates, checklists and automation shift hours per unit, and a plan built on old figures will overstate your need for people.
Available hours and the buffer
Start with the hours a person has for delivery after leave, internal meetings and admin. In my own working assumption that is closer to 32-35 hours a week than 40, and you should replace that with your calendar. Then hold back a buffer for the things a plan cannot predict: urgent client requests, rework from failed QA, a sick day, a site migration that arrives without notice.
The size of the buffer is a decision you make from your own history. A team with stable, standardized accounts needs less than a team that handles a lot of ad hoc requests. Review it each quarter by comparing planned hours with actual hours for the same units.
A worked example (invented numbers)
The numbers below are invented for illustration. They are not benchmarks, and your hours per unit will differ. Only the method carries over.
Assumed hours per unit (example): content piece 6 hours, technical fix ticket 2 hours, outreach batch 5 hours, monthly report 3 hours. A standard account in this example needs, each month: 4 content pieces (24 hours), 6 tickets (12), 2 outreach batches (10), 1 report (3) and 5 hours of account communication, for 54 hours.
Supply (example): one specialist with 34 available hours a week works about 136 hours over four weeks. Holding back a 20% buffer leaves 108.8 plannable hours.
| Item | Hours (example) |
|---|---|
| Available hours, 4 weeks | 136.0 |
| Buffer at 20% | 27.2 |
| Plannable hours | 108.8 |
| One standard account | 54.0 |
| Two standard accounts | 108.0 |
| Remaining after two | 0.8 |
In this example one specialist can carry two standard accounts and nothing else, which means the third account needs a hire or a change in the workload per account. The conclusion would change if the buffer were 10% or if reporting were automated. That sensitivity is the useful part. Run the plan with a few assumptions and see how much each one moves the answer.
When to hire
Hire on triggers you set before you need them, so the decision is not made under pressure. Examples of triggers an agency might choose:
- Signed and expected work would push planned load above your plannable hours for the next quarter.
- Actual hours exceed planned hours on the same units for several months running, after you have checked it is not a logging problem.
- Client-side blockers are rising because account communication is crowding out production.
Allow for lead time. If recruiting and onboarding takes a few months, the trigger has to fire that far ahead of the load. A trigger tied to today's utilization always arrives too late.
Before hiring, check whether process is the cheaper lever. Sakas & Company's agency research puts it at 4-8 clients per manager when accounts are high-touch and 15-20 when the process is standardized. It is a rough guide, and it is why I check the workflow first, as set out in SEO delivery management.
AEO and GEO use the same method
The method is the same and the units are different. AEO plans around target questions and repeated citation checks, and GEO plans around entities and third-party sources with long lead times. See AEO agency capacity planning and GEO agency capacity planning.
Agency utilization consulting is where I check these numbers with agency owners: audit where the hours go, then size the team to the work that was sold.
FAQ
What is SEO agency capacity planning?
SEO agency capacity planning is the process of converting sold client scope into hours of delivery work, comparing it to the hours your team can supply after a buffer, and setting hiring triggers. It depends on hours per unit of work measured from your own time records.
How many hours does an SEO task take?
It depends on your team, your process and the task type, so no universal figure is reliable. Measure it from your own time entries by grouping completed work into unit types and taking the median hours for each. Remeasure after process changes such as new templates or automation.
How big should the capacity buffer be?
Set the buffer from your own history, not from a rule of thumb. Compare planned hours with actual hours on the same units to see how much unplanned work, rework and absence you absorb. Standardized accounts usually need less buffer than teams handling many ad hoc requests. Review it every quarter.
When should an SEO agency hire another person?
Hire when a trigger you defined in advance fires, such as planned load for the next quarter exceeding plannable hours, or actuals running above plan for several months. Set the trigger early enough to cover your recruiting and onboarding lead time.