
Agency Resource Planning: Know Your Team’s Real Capacity Before You Say Yes
Your agency has less capacity than you think, and a lot of those missing hours disappear into support work.
A six-person team looks like 240 hours a week on paper. But once you subtract maintenance tickets, client calls, the owner’s sales time, and a buffer for delays, you may be left with closer to 120 hours for new project work.
That gap is exactly why agency resource planning matters.
Agency resource planning is the process of figuring out how many hours your team actually has, then matching projects to the right people before you commit to a start date.
This part of our guide to agency project management shows how a small WordPress agency can calculate that capacity, review it in about 15 minutes a week, and know when the right answer is simply, “not until the 20th.”
Resource Planning vs Capacity Planning for Agencies
Capacity planning answers how many hours your team has. Resource planning answers who does which work in those hours. You need the first number before the second one means anything.
| Capacity planning | Resource planning | |
| Question it answers | How many hours do we have? | Who works on what, and when? |
| Output | One number per person, per week | Assigned tasks with dates |
| How often | Weekly, plus before every new quote | Weekly, plus when work changes |
| Main risk | Counting hours the team doesn’t really have | Giving work to whoever is free, not whoever fits |
Large agencies have a traffic manager and a scheduling tool for this. A 3- to 15-person WordPress agency usually has the owner and a project board, which is enough if the number going in is honest.
Work Out Your Real Weekly Capacity
Real weekly capacity is each person’s working hours, minus time off, internal work, maintenance and support, and a buffer.
Resource Guru’s agency capacity planning guide uses a simpler formula: team members × working hours × utilization rate. That works for big teams, but a small agency needs to see where each hour goes.
Here is a six-person WordPress agency planning next week:
| Person | Working hours | Time off | Internal work | Maintenance and support | Available for projects |
|---|---|---|---|---|---|
| Owner | 40 | 0 | 28 | 0 | 12 |
| Project manager | 40 | 0 | 10 | 2 | 28 |
| Designer | 40 | 8 | 4 | 0 | 28 |
| Developer 1 | 40 | 0 | 4 | 6 | 30 |
| Developer 2 | 40 | 0 | 4 | 6 | 30 |
| Support developer | 40 | 0 | 4 | 24 | 12 |
| Total | 240 | 8 | 54 | 38 | 140 |
Take 15% off the 140 hours as a buffer, and the team has about 119 hours for project work next week. That’s half of what the headcount suggests.
The team isn’t underworked, either. Project hours plus maintenance hours come to 178 of 240, or 74% billable, which sits inside the 70 to 80% range Resource Guru recommends for agencies. A healthy agency can still have only 119 hours for the next project.
1. Take out maintenance and support first
Maintenance and support come off the top because they arrive whether you plan for them or not. Updates, plugin conflicts, “quick changes,” and urgent fixes on live sites all land on the same developers who build new sites.
Use last month’s logged hours, not a guess, and add the hours each retainer promises. If your website maintenance plan includes four hours of changes a month for twelve clients, that’s 48 hours a month, or about 12 a week, before a single ticket comes in.
2. Count the owner honestly
The owner is usually the most overbooked person in a small agency, and the one left out of the plan. Sales calls, quotes, invoicing, hiring, and reviewing work all take real hours.
If you’re the owner, track your own week once and count only what’s left as project time. Twelve hours is common. Planning around 30 is how a design review ends up waiting until Saturday.
3. Leave a buffer for client delays
A buffer covers the work you can’t schedule: late content, a missed feedback deadline that collides with another project, a bug that takes a day instead of an hour. Start at 15% and adjust it from your own numbers. If projects regularly run over, the buffer is too small.
Match Projects to People
Matching projects to people means giving each task an owner, an estimate, and a due date based on who has the hours and the skills, not who replied first. Capacity tells you how much work fits. Matching tells you whether it fits the right people.
Three things make it work:
- An estimate on every task. A rough figure in hours is enough. Without estimates, “Developer 1 has 30 hours” can’t be compared with anything.
- One accountable owner per task. Add others as needed, but one name owns the deadline.
- A short skills note per person. For example, “Developer 2: WooCommerce, custom blocks. Not: server migrations.” It stops the most experienced developer from getting every hard task by default.
When two projects need the same person in the same week, use one priority rule and stick to it. Our guide on how to manage multiple projects covers that rule and the weekly review it feeds.
Run a 15-Minute Weekly Resourcing Check
A weekly resourcing check compares last week’s actual hours with next week’s planned work, so you can fix problems before they reach a client. Do it on Friday afternoon, before anyone commits to new work on Monday.
In FluentBoards, the check uses three screens. The Reports dashboard is free. Time estimates and the Timesheet are part of FluentBoards Pro.
1. Check last week’s actuals in the timesheet
Open the Timesheet report, group it by member, and set the dates to last week. Compare each person’s logged hours with the capacity you planned for them. The Timesheet is only visible to admins and board managers, so whoever runs the check needs that role.
If someone logged 38 project hours when you planned 30, find out why before you plan next week. A pattern of overruns usually means estimates are too low, which our guide to project management time tracking explains how to fix.
2. Read the assignee workload table
Reports Overview shows an Assignee Workload table with each person’s open, completed, and overdue tasks and their estimated time. It shows the eight busiest people, which covers most small agencies.
Read the workload bar carefully. It compares each person with the busiest member of the team, not with their capacity. A full bar means “carrying the most”, not “at 100% of their hours”. You still need your capacity table for that. Reports also count every task touched in the date range, so the estimate column includes finished work. Treat it as a load signal, not remaining hours.
3. Check due dates for next week
Look at the Due Date Distribution on the same page. A spike in “Next 7 Days” or anything in “Overdue” means next week is already under pressure. Open the Calendar view filtered by one person to see exactly which days are crowded.
4. Decide and write it down
Move a date, reassign a task, or tell a client that a start slips. Then write the decision as a comment on the task, so nobody has to remember a Friday conversation. Resource Guru treats anyone above 85% for two consecutive weeks as overallocated, which is a good rule for when to act.
Pro Tip: Put support on the board as a recurring weekly task, like “Support block: 24 hours”, assigned to the support developer with an estimate. Recurring tasks are a Pro feature. Once support is a task, it shows up in the workload numbers instead of hiding behind them.
When to Say No, Push the Start Date or Hire
The weekly check tells you which of three moves to make when new work arrives. Use the numbers, not how busy the team feels.
| What the check shows | What to do |
|---|---|
| The new project fits next month’s capacity, but not next week’s | Push the start date and put it in the statement of work |
| It fits overall, but one person is the bottleneck | Reassign work or bring in a contractor for that skill |
| Someone has been above 85% for two weeks, and the pipeline is still full | Stop selling new builds until it clears, or start hiring |
| Capacity is open for three weeks in a row | Sell, or move internal projects forward |
A later start date is easier to sell than a missed deadline. Clients accept “we can start on the 20th” far more readily than a launch that slips by a month. Write the agreed start date into the statement of work, so both sides plan around the same date.
Hiring is the slowest fix and the easiest one to get wrong. Hire when the check shows the same overload for a month or more, not after one hard week.
The Capacity Planning Worksheet
The capacity planning worksheet is the table from earlier, set up as a reusable weekly form. It has one row per person, with columns for working hours, time off, internal work, maintenance and support, buffer, and available project hours, plus a row for last week’s actual hours next to each plan.
Fill it in on Friday before the resourcing check. After four weeks, you’ll have your agency’s real numbers instead of estimates: how much support really takes, how many hours the owner really has, and how big the buffer needs to be.
Frequently Asked Questions
These are the questions agency owners ask most when they start planning capacity.
How do you calculate agency capacity?
Start with each person’s working hours, then subtract time off, internal work like meetings and admin, and maintenance and support hours. Take a 15% buffer off the result. For a six-person team on 40-hour weeks, that often leaves about 120 project hours out of 240.
What is a good utilization rate for an agency?
Resource Guru recommends that agencies target 70 to 80% billable utilization and treats anyone above 85% for two consecutive weeks as overallocated. Count maintenance and retainer hours as billable, but plan new projects only into the hours left after them.
Do small agencies need resource planning software?
Usually not under about 15 people. Task estimates, logged time, and a workload view in your project management tool, plus a weekly capacity table, cover what a small team needs. Dedicated scheduling tools pay off when you have several teams or a full-time traffic manager.
Run Your First Capacity Check on Friday
You don’t need a new tool or a month of data to start. This Friday, fill in the capacity table for next week, take out maintenance and the owner’s real hours, and compare the result with what’s already promised.
If the number is smaller than you expected, that’s the point. Better to see it on Friday than when two launches land on the same developer. Run the same check every week, and the next time a client asks when you can start, you’ll have a real answer.
That’s all for today. Let’s redefine project management.
Let’s redefine project management with FluentBoards!
Get Tips, Tricks, & Updates
We won’t send you spam.












Add your first comment to this post