A new project can look manageable in a proposal and still overwhelm the team. The problem is often not the total number of hours; it is when those hours are needed, which skills are required, and how much time is already spoken for.
To calculate agency capacity, estimate the work your team can realistically deliver during the project period, then compare it with existing and proposed demand by role and week. This is more useful than treating every employee as a block of 40 available hours.
The method below is designed for small and midsize agencies. It works whether you use a spreadsheet, project-management software, or a simple calendar—as long as estimates reflect actual commitments rather than ideal conditions.
What agency capacity means
Capacity is the amount of work a team can take on without relying on persistent overtime, missed commitments, or quality compromises. It is not the same as paid hours, billable targets, or the maximum number of tasks people could squeeze into a week.
For project decisions, think of capacity in three dimensions:
- Time: How many hours are genuinely available?
- Timing: In which weeks are those hours available?
- Skills: Which roles or specialist capabilities are needed?
A team may have 100 open hours overall and still lack the senior designer needed for a critical launch week. Capacity should therefore be checked by role and time period, not only as one agency-wide total.
Step 1: Calculate usable hours, not contracted hours
Start with each person’s working hours during the period you are planning. Then subtract time that is not available for client delivery: holidays, known leave, internal meetings, sales work, administration, training, and management responsibilities.
Usable project capacity = scheduled working hours − non-project commitments
For example, a full-time strategist has 40 scheduled hours in a week. They have 5 hours of internal meetings, 4 hours for sales and proposals, and 3 hours for management and administration. Their starting project capacity is 28 hours—not 40.
Do not subtract every break or routine interruption as a separate precise adjustment if that creates false accuracy. Instead, review how much time the role has actually delivered to projects over recent weeks. Use that pattern to set a reasonable planning allowance, and revise it when the role or workload changes.
There is no universal billable-hours percentage that fits every agency. A founder who sells and manages people will have less delivery time than a specialist, while a team with heavy client-service demands may lose more time to coordination. Use your own calendar and time records where available.
Step 2: Map current demand by role and week
List active client work, recurring retainers, internal initiatives, and work already sold but not yet started. Estimate the hours each role needs in each week—not just the total project estimate.
A simple table might include:
- Project or commitment
- Role required (for example, strategist, designer, developer, account lead)
- Hours by week
- Confidence in the estimate
- Deadline or dependency
Suppose your developer has 24 usable project hours next week. Existing work needs 16 hours, and support for a retainer needs another 5. That leaves 3 hours of uncommitted capacity. A proposed 12-hour development task does not fit next week, even if the agency has spare capacity in other roles or later in the month.
Use delivery estimates that include the work around the work: reviews, client calls, handoffs, QA, and revisions within the agreed scope. For a website build, estimating only the time spent coding can understate the demand on design, project management, and client service. A work-breakdown estimate for a website project can help make those responsibilities visible.
Step 3: Estimate the new project in stages
Break the proposed project into phases or deliverables, and assign hours by role and week. A 120-hour project is not automatically a 120-hour problem: if most work lands after a current project ends, it may fit. But a 30-hour discovery and design sprint scheduled during your busiest fortnight may not.
Include the likely pattern of client feedback. If the project depends on a client supplying content or approvals, do not assume every phase will proceed on the ideal date. Mark assumptions and dependencies, then check what happens if a review takes longer or a key person is unavailable.
When scope is still unclear, give the estimate a range rather than pretending it is settled. For instance, “about 45–60 hours, depending on the number of review rounds” is more useful for a capacity decision than a precise but unsupported 52-hour figure. Your proposal should state the assumptions that support the estimate; see this guide to what to include in an agency proposal beyond price and timeline.
Step 4: Add a buffer for uncertainty
Do not plan every available hour. Client questions, revisions, production issues, and internal coordination rarely arrive in neat, predictable blocks. A buffer gives the team room to absorb normal variation without immediately disrupting other work.
The right buffer depends on the work. A repeatable monthly deliverable with stable inputs may need less contingency than a new service, unclear brief, or project involving several decision-makers. Rather than applying one percentage to every project, identify the risks and reserve time where they are most likely to affect delivery.
For example, if your designer has 10 uncommitted hours in a launch week, committing all 10 to a new project leaves no room for a delayed approval or an urgent correction. You might offer a later start, reduce the initial scope, or reserve part of that time for contingency.
Planning capacity is also a workload decision, not just a scheduling exercise. The UK Health and Safety Executive’s guidance on workplace demands includes workload, work patterns, and the working environment among the factors employers should manage. Treat routine overtime as a warning that your plan may depend on capacity the team does not sustainably have.
Step 5: Check the bottleneck and the calendar
Compare demand and usable capacity for each role in each week. Flag any period where demand exceeds capacity, then ask whether the gap can be solved without moving risk elsewhere.
- Can the start date move?
- Can the client approve a phased delivery?
- Can a qualified teammate take part of the work?
- Would a freelancer add the right skill at the right time?
- Can an existing commitment be rescheduled with agreement?
Be cautious about solving a bottleneck by assuming another person can absorb specialist work. A project manager cannot simply replace a developer, and a junior designer may need review time from the senior designer whose capacity is already constrained. Include supervision and handoff hours in the plan.
It can help to test two versions: the expected schedule and a realistic disruption scenario. If a one-week slip in client feedback causes three projects to collide, the proposed start date may be too tight even if the original plan balances exactly.
Step 6: Make the acceptance decision explicit
Capacity should inform the commercial decision, not make it automatically. Once you know where the pressure falls, choose a response and explain it clearly to the prospect.
- Accept as proposed when the required roles have room and the schedule includes reasonable contingency.
- Accept with a later start when the team can deliver, but not on the requested date.
- Phase or reduce the scope when the first outcome can be delivered without committing to every later stage.
- Bring in temporary support when the margin, onboarding time, and quality controls make that practical.
- Decline when the work depends on chronic overtime or creates unacceptable risk to current clients.
Record the decision and its assumptions. If the client’s requests later expand, compare the change with the original capacity plan. Our guide to recognizing scope creep and resetting expectations covers the signs that an agreed project is becoming a different workload.
For an evidence-based planning habit, review planned versus actual hours after each project or delivery cycle. The Scrum Guide describes planning as an activity informed by the team’s capacity and past performance. You do not need to adopt Scrum to use that principle: update future estimates with what your own work actually required.
A quick capacity check before you say yes
- Calculate usable hours for each relevant role, allowing for meetings, sales, leave, and management.
- Map existing sold work and recurring commitments by role and week.
- Estimate the new project by phase, role, and week, including reviews and delivery overhead.
- Identify uncertain assumptions, dependencies, and a suitable buffer.
- Check bottlenecks and test a likely disruption, such as delayed feedback or staff absence.
- Choose an acceptance option: proceed, change the start date, phase the work, add support, or decline.
A capacity check does not need to predict every interruption. Its purpose is to make the trade-offs visible before the promise is made. When the plan only works if everyone is continuously available and nothing changes, the project does not fit yet. Adjust the terms—or protect the commitments your team has already made.
Frequently asked questions
How often should an agency recalculate capacity?
Review it at least when a new project is being considered and whenever a major commitment, staffing change, or deadline shift occurs. Teams with changing weekly work may also benefit from a short weekly review.
Should capacity be calculated in hours or days?
Use whichever unit helps your team compare work consistently. Hours are useful for role-level estimates and smaller tasks; days can be easier for broad phases. Avoid mixing units without defining what a “day” includes.
How much buffer should an agency leave?
There is no universal percentage. Reserve more room when scope, approvals, dependencies, or delivery methods are uncertain. Use past project experience to refine the allowance rather than treating a generic figure as a guarantee.
What if a client needs the project sooner than capacity allows?
Offer a realistic start date, a smaller first phase, or a clearly priced staffing option if one is feasible. Do not promise the requested date on the assumption that the team will work unsustainable hours.
Can a team have spare hours but still lack capacity?
Yes. Spare hours in one role or week do not solve a shortage of a specific skill at a critical point in the schedule. Compare demand and availability by role and timing, including the supervision needed for delegated work.