Blog

Ask ten agency leaders to explain the difference between resource planning and capacity planning. Half will say they’re the same thing. The other half will describe one of them and call it the other.

Both answers are wrong. Not a vocabulary problem. A planning problem. When you don’t separate the two frameworks, you end up building your schedule without a capacity view, or your capacity view without a scheduling reality check. Both fail, just differently.

Resource planning vs capacity planning: the short answer

Resource planning asks “who is doing which work and when.” Capacity planning asks “does the firm have enough of the right people to take on the work in the pipeline.”

Related. Overlapping. But running on different time horizons and answering different questions. Getting both wrong is common. Getting both right and keeping them connected is where most agencies have a gap.

What is resource planning?

Resource planning is the process of matching specific people to specific work, close enough to execution that the match is real and the schedule is buildable.

It operates at the project and engagement level. When a project manager asks “who’s on the rebrand starting Monday,” they’re doing resource planning. When a COO asks “can we handle the new account if we win it next quarter,” they’re asking something else.

Resource planning lives inside the week-to-week scheduling layer. Decisions at this level cover people, roles, and time blocks. Not whether the firm can sustain that work over the next ninety days. That’s a different conversation.

How this fits into a broader forecasting approach is covered in the cornerstone of this cluster. Short version: resource planning without capacity planning is a schedule that doesn’t know whether it’s sustainable.

What is capacity planning?

Capacity planning asks, at the firm or team level, whether you have enough capacity to handle the work you’re forecasting over a given time window.

It operates at the portfolio and pipeline level. Not “who is on the rebrand” but “if the rebrand plus the retail launch plus three proposals come in, do we have the senior design and strategy capacity to deliver all of them?”

Capacity planning typically looks further out than resource planning. It works with roles, headcount, and skill areas rather than specific names. Naming Maya as capacity in December is planning. Naming her to a specific project in December is scheduling. It’s a meaningful distinction.

Most firm-level decisions belong in the capacity planning conversation. Hiring, subcontracting, sales rate, pricing, vacation blackouts. When those decisions end up in the weekly resourcing meeting, the meeting breaks.

Where they overlap

Both frameworks deal with the same underlying inputs. People, time, available work. Both fail when the data behind them is stale or incomplete. Both need some connection to the pipeline to be useful.

More importantly, they feed each other. Capacity planning sets the guardrails that make resource planning decisions coherent. If capacity planning says the firm is at 85% through next quarter, resource planning can commit to new engagements accordingly. Without that context, resource planning is guessing.

Run them in complete isolation and you end up with a capacity model that doesn’t reflect what’s actually scheduled, and a schedule that regularly blows past what the firm can absorb. That’s the most common version of the gap.

Where they diverge

Time horizon is the clearest difference. Capacity planning is useful eight to sixteen weeks out. Resource planning is useful four to six weeks out. At twelve weeks, naming specific individuals to engagements is fiction. Knowing you’ll need two senior developers and one strategist available is forecastable and actionable.

Granularity is the second difference. Capacity planning works with roles, skills, and percentages. Resource planning works with names, hours, and specific deliverables.

Decision ownership is the third. Capacity planning informs firm-level decisions: whether to hire or hold, whether to submit a proposal, whether to price with or without margin buffer. Resource planning informs project-level decisions: who is on what, when handoffs happen, when someone is overloaded.

Both belong in the same organization. Not the same meeting.

Why agencies treat them as the same thing

Part of this is the tools. Most resource planning software is actually a scheduling tool that calls itself a resource planning tool. Most capacity planning conversations happen in spreadsheets that were built to answer a different question.

So agencies merged them. Weekly resourcing meetings started handling both firm-level capacity questions and project-level scheduling questions in the same ninety minutes. Urgent beats important. Next Tuesday crowds out next quarter.

Resource forecasting sits between the two frameworks. It’s the practice of building a probabilistic view of who you’ll need, far enough out to act but close enough to be useful. Not quite resource planning and not quite capacity planning. Most agencies don’t have a name for it. A few spreadsheets are standing in for it.

When the capacity view and the schedule live in different systems and get updated at different frequencies, the connection between them frays. That’s the planning gap. It shows up as late-stage staffing surprises, pricing decisions made without knowing what the firm can absorb, and resourcing meetings that feel like repeating the same argument every week.

Tools and how they map to each

Scheduling tools, including Float, Runn, and Resource Guru, are primarily resource planning tools. They handle who is on what and when. Some have a capacity view built in, but it’s secondary to the scheduling function.

PSA platforms like Productive and Scoro handle resource planning and some capacity planning within their suite. The trade-off is migration: projects, finance, and time tracking all need to move into one system. That’s not a small lift.

Spreadsheets still drive capacity planning at most agencies. Flexible and fast to set up. The capacity model that was accurate in January is often wrong by March.

Parallax focuses specifically on the forecasting layer that connects the two: pipeline data, capacity assumptions, and actuals in the same view. The goal is to give resource planning a real foundation and capacity planning current data to work from, without requiring you to move your entire stack.

Right question to ask: where in your current setup is the connection between the schedule and the firm-level capacity view breaking? That’s the gap worth addressing first.

How to use both without building two separate processes

They don’t need to be separate processes. They need to be separate conversations with separate frequencies.

Capacity planning runs monthly or quarterly. Inputs: pipeline, headcount, planned leave, known project endings. Output: a confidence level around the firm’s ability to absorb forecasted work. Owner: leadership.

Resource planning runs weekly. Inputs: current projects, team availability, any changes to the capacity baseline from the previous cycle. Output: a schedule that accounts for both. Owner: delivery or operations.

Different rhythms. Different owners. Same data sources.

Connecting them requires a feedback loop. When the scheduled reality diverges significantly from what the capacity model assumed, that has to surface. A key hire fell through. A client engagement doubled in scope. Utilization ran ten points higher than expected. When that happens in the schedule, it should update the capacity view.

Building that connective tissue is harder than either process separately. It’s also where most of the value lives. That’s the part nobody puts in the org chart.

If you have been running the weekly resourcing meeting as both a capacity conversation and a scheduling conversation, the frustration you feel at the end of that meeting is data. We have watched what it looks like when the two are separated correctly and kept in sync. Happy to walk through what that structure could look like for your firm.

Planning is not one meeting. It’s two different conversations that need to stay connected.

There’s a version of this question on nearly every agency leadership team. The project looked profitable at scoping. It looked fine halfway through. And then the numbers came in.

Most agencies have run this experience enough times that they’ve stopped being surprised by it. What they haven’t figured out is why it keeps happening. Not the surface reason (scope creep, difficult client, unclear brief) but the structural reason. Why is project profitability so persistently hard to see before it lands?

It’s not a discipline problem

Start with what this isn’t: primarily a management failure. The agencies that struggle with project profitability visibility aren’t running bad projects or employing careless PMs. They’re running normal agency projects with data stored across systems that were never designed to answer the same question.

This pattern shows up across agency types and sizes. Not in every project, but in enough of them, across enough leadership teams, that it reads as a structural problem, not an individual one.

Data problem: three systems, one question

Project profitability requires three inputs: what did we bill, what did it cost to deliver, and where does the scope stand today?

Those three inputs almost never live in the same system. Revenue and sold price live in the CRM. Actual delivery costs live in the time tracking tool. Scope and status live in the project management platform.

A weekly resourcing meeting might surface who’s over-allocated on scheduling. The financial close might surface that a project ended up underwater. Nobody is running a weekly view that connects pipeline data to delivery costs to scope status, because no single tool was built to answer that question across all three.

Across agencies running over 100 active engagements at any time, a majority describe some version of this disconnect. The data exists. The connection between the data systems is the gap. And because each tool answers a different question perfectly well on its own, there’s no obvious failure signal until the questions are asked together.

Timing problem: visibility arrives too late

Monthly billing cycles are the norm. End-of-project reviews are standard. Both answer the question when it’s too late to change the outcome.

By the time finance runs the month-end numbers, the delivery decisions that drove that month’s profitability were made three to six weeks earlier. By the time the project close report is written, the scope drift that drove the outcome has already happened.

What would change the math isn’t better reporting. It’s earlier reporting. An in-flight project profitability view that surfaces variances in week three, not month three, changes what you can do about them.

Spreadsheets most agencies use for capacity planning and project tracking aren’t built for live variance tracking. Static snapshots. By the time someone updates them, the situation has moved.

Scope problem: agency work resists fixed scope

Software development can have detailed technical specs. Construction has drawings. Agency work has client briefs, discovery conversations, and reference examples.

Briefs are interpreted. Reference examples diverge from what clients actually want once they see options. Discovery conversations surface requirements that weren’t in the brief.

None of this is a problem with how agencies are run. It’s a property of service work where value is co-created with the client. The scope will move. The question is whether the agency has a mechanism to flag when it has moved enough to affect the financial outcome of the project.

Most agencies don’t. The PM is focused on delivery quality and client relationship. The account manager is focused on the client relationship and the renewal. Neither has a clear role in flagging “this project is now doing work that was outside the original estimate” in a way that triggers a financial review.

Change order discipline is the mechanism that handles this when it’s working well. But even in agencies with a change order process, informal scope additions that each feel small end up compounding into something meaningful by project close. “It was just a quick ask” is one of the most expensive phrases in agency work. Five quick asks across a twelve-week project can represent 10-15% of the original estimate.

Trust problem: even available data doesn’t get used

Here’s the part that’s harder to talk about. Even when agencies have access to in-flight profitability data, many leadership teams don’t fully trust it. Double-checking against spreadsheets. Waiting for the finance reconciliation. Treating the tool number as directional, not authoritative.

When financial reporting from the planning tool conflicts with the accounting system’s numbers, people fall back to what they trust. What they trust is usually the finance system, which is always retrospective.

A pattern emerges: the planning layer exists but isn’t driving decisions. Timesheet data gets logged. Resource forecasting tools show utilization numbers. Weekly reports get shared. But the link between those numbers and the decisions that determine project outcomes is weak.

Building trust in the planning layer requires two things: calculation methods that match the accounting system, and enough historical validation that leaders have seen the numbers be right enough times to act on them. That’s not a technology problem. It’s a change management problem. And it’s the one that takes the longest to solve.

What changes the picture

None of the problems above are unsolvable. They’re structural, which means they have structural fixes.

Worth noting what “structural fix” means here. It doesn’t mean buying a new tool and expecting behavior to change. It means establishing a feedback loop (data connection, decision ownership, cadence) that didn’t exist before. The tool is the enabler; the loop is what actually changes the outcome.

Three things, in combination, shift project profitability from something discovered at close to something managed in-flight.

First, a data connection that doesn’t require manual assembly. If someone has to spend ninety minutes on a Friday pulling actuals from the time tracking tool, comparing them to the estimate in the project plan, and reconciling against the sold price in the CRM, that visibility check won’t happen consistently. The connection has to be live and automatic for it to be usable.

Second, an in-flight variance trigger. Not a report. A flag. Something that tells the PM or delivery lead “this project is tracking above estimated hours for this phase by X%.” The flag doesn’t require anyone to already know that something is wrong. It surfaces it.

Third, a decision owner for the financial outcome of the project. When nobody owns the project margin question specifically (when it lives somewhere between PM, account, and finance), it tends not to get addressed until it’s already resolved by time. Assigning someone to act on a variance trigger is the loop that closes.

If your agency has experienced this pattern more than once (strong scoping, confident delivery, and then a close review that doesn’t match expectations), the issue is probably structural rather than individual. The planning gap is where visibility lives. Happy to talk through where it tends to break in practice.

Project profitability isn’t hard to predict because agencies are bad at it. It’s hard to predict because the systems weren’t built to answer the question. Building that connection changes what’s possible. Most of the data you’d need already exists in systems you already own. The work is connecting it and establishing the habit of using it before the project closes.

Most agency leaders know their utilization rate by the time they’re looking at last quarter’s numbers. Some know it by month end. A smaller group knows it weekly.

Almost none of them know what it will be eight weeks from now.

Gap worth closing. Utilization as a measurement tells you what happened. Utilization as a forecast tells you what you can still do something about. Not the same use of the same number.

What is agency utilization rate?

Agency utilization rate is the percentage of available working hours that a team spends on billable client work.

Simple calculation: billable hours divided by total available hours, expressed as a percentage. A team member with 160 available hours in a month who logs 120 billable hours is at 75% utilization.

Standard definition, and it’s only the starting point. Useful utilization analysis requires choosing the right numerator and denominator, understanding what “available” means in your context, and deciding whether you’re tracking utilization as a historical fact or as a forward-looking forecast.

Types of utilization that matter at agencies

Not all agencies use the same definition. Three versions come up often enough to be worth distinguishing.

Billable utilization measures hours charged directly to client projects against total available hours. Most common in agency reporting. Most useful for understanding revenue-generating capacity.

Productive utilization includes both billable work and non-billable productive work (new business, internal projects, business development). Useful for understanding total team output. Can mask genuine capacity issues if non-billable work is growing.

Target utilization is the internal rate the agency is planning against. 75% target utilization means you’re planning for 25% of capacity to be absorbed by overhead, PTO, training, and the inevitable gaps between projects. Comparing actual against target surfaces whether you’re over or under plan.

For most project-level and firm-level decisions, billable utilization is the right metric. Use it consistently and connect it to the decisions it’s meant to inform.

Standard utilization benchmarks for agencies

Directional ranges:

Direct production roles (creative, development, strategy, analytics): 70-80% billable utilization is generally considered healthy. Above 80% runs a burnout risk and leaves little buffer for reactive work. Below 65% suggests overstaffing relative to current pipeline. The 70-80% range also provides the flexibility to absorb an unexpected client request or an internal project without immediately stressing the team.

Project management and account roles tend to run at 60-70%. These roles carry more coordination and overhead by design. A project manager consistently at 85% billable is likely doing work that should be delegated, or the account team is understaffed.

Agency leadership: 40-60% is often realistic and appropriate. Heavy client work at this level limits the management and business development capacity that sustains the firm. Not a problem to fix. A structural reality to plan around.

These are directional. Your own numbers, segmented by role type and tracked consistently, are more useful than any industry average. The trend matters more than the absolute.

Why utilization measurement isn’t enough

Knowing your utilization rate last month is useful. Mostly for explaining what happened. Rarely for changing what happens next.

Here’s where the measurement-only approach breaks down in practice.

Knowing your utilization rate next quarter is useful for making decisions while you still can. That’s a different exercise.

Monthly utilization reports answer: did we bill enough of our capacity last month? The answer usually surfaces after you’ve already made the decisions that drove it.

Utilization forecasting asks: given our pipeline, headcount, and planned capacity, what will our utilization look like in six to eight weeks? And if that number is below target, what are we going to do about it?

Decision lead time is everything. A utilization forecast that says you’ll be at 55% in eight weeks gives you eight weeks to fill the pipeline. The same discovery at month-end billing gives you nothing. The month is already over.

How to forecast utilization

A basic forward utilization model requires four inputs:

Current committed projects. For each active engagement, how many hours per week is the team committed to over the next eight weeks? This is your floor. It’s already sold and staffed.

Incoming pipeline. For deals likely to close in the next eight weeks (weighted by probability and expected start date), what headcount will they consume? A 70% probability deal that’s expected to close in three weeks contributes 70% of its staffing requirement to the forecast.

Planned capacity. Who is available, and at what percentage, over the forecast window? Subtract approved PTO, known commitments, onboarding load for new hires, and any significant internal project work.

Target utilization. What rate are you planning to run at? 75%? 78%? This is the standard against which you’re comparing the forecast.

Bringing these together gives you a forward view: at current pipeline and capacity, where is utilization heading? If it’s heading below target, you have time to act. If it’s heading above 85%, you have time to plan.

Most agencies have this data in multiple systems. Pipeline lives in the CRM. Headcount and PTO live in HR. Project staffing lives in resource planning. Resource forecasting tools exist specifically to connect these inputs without requiring a weekly manual assembly exercise.

What utilization forecasting enables

A utilization forecast changes what decisions you can make and when.

Hiring decisions become earlier. If the forward model says utilization will climb above sustainable levels in ten weeks, you have a data point for starting a hire now rather than after delivery quality suffers. Hiring decisions driven by a utilization forecast tend to land better than those driven by delivery emergencies. Different candidate pool, longer onboarding runway, different outcome.

Pipeline urgency becomes visible. If the forecast shows utilization dropping below target in six weeks, you have a specific trigger for the business development conversation. Not “we should probably be selling more” but “we have a capacity gap forming and we need pipeline to close by a certain date.” That level of specificity changes the energy of the conversation.

Pricing confidence increases. When you know you’ll have senior capacity available at a specific point, you can price and commit to work with more confidence. When you’re guessing at availability, the default is to overprice to hedge against scarcity, or underprice because the capacity appears available until it suddenly isn’t. Both create problems. Forward visibility reduces guessing.

Resource planning conversations change character. When the weekly resourcing meeting has a forward utilization view alongside the assignment schedule, the conversation can shift from “who is available next Tuesday” to “what’s the trend line over the next six weeks and what does it mean.” That shift takes time to build, but it produces fundamentally different decisions.

Common mistakes in utilization tracking

Measuring total hours rather than billable hours. If someone is available for 160 hours but the spreadsheets most agencies use count all hours worked including PTO, admin, and sick time in the denominator, the number is distorted. You end up with a utilization figure that looks fine and masks a real billing gap.

Not distinguishing role types. An overall agency utilization of 72% can obscure that creative is at 88% (overtaxed) while account management is at 58% (under-deployed or understaffed on the wrong end). Role-level visibility changes where you act. Overall-firm utilization is useful for executive reporting. It’s less useful for operational decisions.

Treating planned and actual as the same number. Planned utilization (what you intended) and actual utilization (what was logged) diverge. Both are useful. Confusing them produces a number that nobody can act on confidently.

Using utilization as the only financial health metric. High utilization at below-market rates doesn’t produce good margins. Low utilization on premium-priced retainers might. Utilization is one input to financial health, not a measure of it. Connect it to revenue, rate, and margin data to see the full picture.

Not building a reconciliation habit. A utilization number that gets reviewed once a month at the leadership meeting tends to produce one-month-lagged interventions. Teams that run a weekly utilization check, even briefly, catch small divergences before they compound. Resource forecasting discipline is a habit before it’s a system.

How to read a utilization number

A utilization number doesn’t tell you much in isolation. Here’s what to look for in the context around it.

Stable or volatile? A team running at 74% consistently is in a different position than a team that swings between 55% and 90% over the same period. Volatility suggests structural gaps in how work is pipelined and onboarded. Addressing volatility is a different problem than addressing a low floor.

Is it uniform or concentrated? If one team is at 90% and another at 60%, the average is 75% and looks fine. But one team is at risk of quality problems and the other is at risk of attrition or pipeline problems. Averages mask distribution. Distribution drives decisions.

Trending which direction? Month-over-month direction matters as much as the absolute number. Utilization declining from 78% to 72% to 66% over three months warrants action, even if 66% is still technically in the healthy range. A number that’s declining is a problem forming.

Where is the demand coming from? Utilization driven by over-delivery on existing accounts is different from utilization driven by new pipeline. One is a capacity management issue. The other is a growth signal. Both look the same in an aggregate utilization report, and both require a different response.

If your agency tracks utilization in arrears and wants to move toward a forward-looking view, the planning gap between pipeline and capacity is usually where to start. Most of the data already exists. Pipeline is in the CRM. Headcount and PTO are in HR. Project staffing is in the resourcing tool. Connecting those three data sources consistently is the exercise. We have run this analysis with agencies across size ranges. Happy to compare notes on what a forward utilization model looks like in practice.

Utilization measured is information. Utilization forecasted is leverage. Most agencies have the data to do both. What they’re usually missing is the habit of combining it on a weekly cadence, and the ownership structure that ensures someone acts on what it shows.

Agency profit margin benchmarks are everywhere. “Healthy agencies run at X percent.” Most of those numbers are true at the level of industry average. None of them tell you whether your margin is good, fixable, or structural.

This post covers the benchmarks worth knowing, why they diverge so much by agency type, and what the planning gap has to do with why margins stay chronically lower than they should be. None of it requires new software. It requires understanding what’s driving your specific number.

What “agency profit margin” means (and which number matters)

Agency margin is measured at multiple levels. Which level you’re looking at changes what the number tells you. And what action it implies.

Gross margin is revenue minus cost of revenue (direct labor, subcontractors, direct project expenses), expressed as a percent of revenue. A services agency with $5M revenue and $3M in direct delivery costs has 40% gross margin.

Operating margin is what remains after sales, marketing, and general administrative overhead. An agency with 40% gross margin and $800K in overhead on $5M revenue has 24% operating margin.

Net profit margin is what’s left after everything including taxes, principal pay, and any owner compensation above salary. Healthy service firms often run 10-20% net margin once direct and indirect costs are fully accounted for.

For most operational and strategic decisions, gross margin is the most actionable number. It’s the one you can influence most directly through pricing, delivery efficiency, and utilization. Not next quarter. Right now. Operating and net margin are the measures by which outside investors or buyers would evaluate the business. Useful for a different set of decisions.

Agency profit margin benchmarks by type

These are directional ranges based on industry reporting and common peer comparisons among agencies in the 10-200 employee range.

Creative and brand agencies running primarily retainer work: gross margins in the 45-60% range are achievable. Project-based work at the same firm often runs 35-50%. Media-heavy retainers compress gross margin because a significant portion of revenue passes through at near-cost.

Digital and performance marketing agencies: gross margins of 40-55% on owned-service work. Search and social campaign management at cost-plus often pulls the blended number down. Agencies with strong proprietary analytics or strategy capabilities tend toward the higher end.

Strategy and consulting-style agencies: 55-70% gross margin is achievable at well-managed firms. Lower overhead models and senior-heavy teams billed at appropriate rates drive the upper range. The floor tends to be set by over-delivery to retain client relationships.

Full-service agencies: 35-50% gross margin reflects the blend of service types. Variation within the range usually tracks to how much of the revenue is media pass-through versus owned service.

Technology and development agencies: gross margins of 40-55% are common, with significant variance based on how much senior versus mid-level capacity is in the utilization mix.

None of these ranges is authoritative. They’re directional. Your own trailing four-quarter average, segmented by service type, tells you more about your specific business than any industry average. It’s also the benchmark you can actually improve against. You can’t improve against an industry average that’s calculated differently from how you run your books.

Why margins diverge: the planning gap mechanism

Agency margins are compressed from below, usually by one of three structural causes.

Pricing confidence problems. When an agency doesn’t know what capacity it has available for the next quarter, it prices work conservatively to hedge. Every proposal. Conservative pricing accumulates into meaningful margin compression over a year. Nothing wrong project by project. The aggregate effect is chronic underpricing.

Scope discipline problems. When the planning layer doesn’t connect delivery hours to financial outcomes, informal scope additions get treated as client service decisions rather than margin decisions. A project that absorbs 15% more hours than estimated, without a change order, runs 15% lower margin than planned. Across a firm’s portfolio, this compounds quickly. It’s the source of many “we had a great year but the numbers don’t reflect it” conversations.

Utilization management problems. When the firm doesn’t have a forward utilization view, bench cost gets absorbed as overhead and shows up in compressed operating margin. An agency consistently at 65% billable utilization when 75% is achievable is effectively giving away capacity at cost. Not a small number.

None of these causes has a simple fix. But all three share a root mechanism: the absence of a connected planning layer that shows how pipeline, capacity, and delivery costs interact. That’s the planning gap. Not a technology problem. A visibility problem that produces a margin problem.

How to use benchmarks productively

Benchmarks are most useful when you’re using them to identify variance, not to declare health.

Gross margin 10 points below your type’s range usually has one of a few explanations: pricing structure (rates are systematically below what the market supports), cost structure (loaded labor costs are higher than typical), or delivery efficiency (projects are consistently running over-estimate). Each explanation suggests a different action. Each has a different fix.

Gross margin in range but operating margin compressed: the issue is overhead relative to revenue. Could be the right call at a growth stage (investing ahead of revenue) or a structural problem (overhead that grew with a revenue base that didn’t hold).

Margins volatile, inconsistent across similar project types, or consistently lower than expected: the planning layer is usually where to look. Firms that can see their pipeline-to-capacity picture clearly tend to manage margin better than firms operating in the dark.

Margin benchmarks and the planning gap: what they share

There’s a consistent pattern across the agencies that underperform on margin against their peer group. Not bad work. Not bad clients. Can’t see the financial consequences of their delivery decisions until those decisions have already been made. By the time the close report lands, the choices are locked.

An agency leader who knows, each week, whether the firm is on track to hit its margin targets for active projects (and what the forward pipeline means for capacity and pricing confidence) is in a materially different position than one who discovers margin issues at month-end billing or project close.

Planning gap is not just a forecasting problem. It’s a margin problem. Benchmarks describe what’s possible when the planning layer is working. Most agencies land below those ranges because it isn’t.

If your margins are consistently below where they should be for your agency type and the explanation isn’t obvious, the first place to look is usually the connection between what you’re pricing, what you’re staffing, and what you’re actually delivering against your estimates. We have seen this pattern enough to know where to start. Happy to walk through it.

Margin benchmarks tell you where to aim. Closing the planning gap is how you get there. Most agencies already have the data. The work is connecting it into a view someone can act on before the quarter is over.

Most agency owners can recite revenue per billable headcount from memory. Ask them how their middle managers are doing and you’ll get a longer pause. The metrics tell a clean story about revenue and utilization and miss almost everything that determines whether the business is still standing in two years.

That gap is the through-line of Episode 2 of Billable. Grant and Kurt spent 25 minutes pulling apart the numbers agencies rely on, and what those numbers don’t see. Not a “throw out your KPIs” argument. More like a “your KPIs are answering a question you stopped asking five years ago” argument.

Revenue per billable headcount, utilization, gross margin. Those are fine. They tell you how the business performed last month. They don’t tell you whether the team carrying that performance is two months from a resignation wave, whether the project that made the margin number look healthy was actually a write-off in disguise, or whether the growth that smoothed over last quarter’s bad call is about to stop being a cushion.

Most agency leaders weren’t trained for the management problem

A small group of agency owners chose this path on purpose. Most didn’t. They were designers who got good at client management, engineers who built something around a CMS, account managers who kept getting promoted until the title said “partner.”

No MBA. No operations training. Nobody handed them a playbook for running a 40-person company.

Grant’s version of this: he started in account management, moved into project management, and gradually ended up as COO. Not a career plan. A series of situations that required someone to figure it out.

Easy to read that origin story as a weakness. It’s not. Agencies that stay nimble, that adopt new models faster than their enterprise counterparts, do so precisely because their leaders aren’t anchored to a textbook framework. But it also means the measurement systems those leaders build tend to be borrowed. Pulled from a Deltek report or an industry benchmark without much interrogation of whether those numbers actually describe the firm in question.

What comes out the other side is a dashboard that looks rigorous and feels reassuring, built on assumptions nobody chose deliberately. Worth asking, periodically, whether the questions your systems are answering are still the questions you need answered.

Five numbers on a desert island

Grant proposed an exercise partway through the conversation. If you were on a desert island and could only see five to ten numbers about your organization, which ones would tell you whether it was healthy?

Revenue per billable headcount makes the list. Revenue per total headcount. Utilization rates. Fine. Standard.

But Grant’s point was sharper than the exercise. Those numbers don’t tell you whether your team is burning out, whether the person carrying three projects is two months from quitting, or whether the senior PM who’s been holding the agency’s worst client together is starting to look at her LinkedIn for the first time in years. They can’t measure culture erosion. They definitely can’t tell you whether the growth that looks so good on the dashboard is actually sustainable.

You can build vanity KPIs that say you’re winning while the organization underneath is hollowing out. Growth in revenue, growth in headcount, growth in new logos, growth in conference appearances. Any of it can mask structural problems that only surface when the growth slows down. Kurt’s line on this one landed hard: growth covers up a lot of problems.

What changes isn’t the KPI set. It’s how you read the gap between what your numbers show and what your week feels like. When those two stories stop agreeing, the numbers are usually wrong. Or asked the wrong question.

Communication is the infrastructure, not the tool

Communication came up three separate times in the episode, which tells you something about how central it is to the argument.

Kurt’s framing: most problems in a business are communication problems. Not a new idea. The layer he added was useful, though. Having Slack doesn’t mean communication is happening. Having a weekly standup doesn’t mean the right information is moving to the right people. The tools exist. Confirmation that anyone received, processed, and acted on the message usually doesn’t.

His rule of thumb, borrowed from his father: something has to be read seven times, heard three times, and felt once before it sticks. If you said it in a Slack message and assumed it landed, you communicated at yourself, not at your team.

This is the part most agencies miss when they invest in operational maturity. More tools get bought. More standups get scheduled. Nobody closes the loop on whether the cadence is actually producing alignment. A weekly resourcing meeting that ends with “we’ll figure it out” is not a resourcing meeting, it’s a calendar event. The same logic applies to every other recurring touchpoint on the calendar.

Micromanagement is inconsistency, not oversight

Sharpest reframe in the episode. Kurt defined micromanagement not as too much oversight, but as inconsistent oversight. He called it the seagull maneuver: fly in, make a lot of noise, leave a mess, disappear.

Teams resist that pattern, not the manager who checks in regularly with clear expectations. They resist the one who shows up unpredictably, reacts to whatever catches their eye, and vanishes until the next crisis.

Consistency is the differentiator. Predictable check-ins, clear definitions of what good looks like, follow-through on the things you said mattered last week. Teams don’t push back against structure. They push back against randomness.

There’s a measurement angle here too. Predictable management produces predictable performance, and predictable performance is what makes forecasting possible. When leadership is reactive, the line between “this PM is underperforming” and “this PM is being thrashed” gets impossible to draw. Dashboard says one thing. Reality says another.

Where coaching effort actually compounds

Grant and Kurt landed on a framework for team performance that agencies rarely follow in practice. A bottom 10 to 15 percent exists on every team, the people who won’t get it no matter how much time you invest. They end up absorbing a disproportionate share of management attention. That math almost never works.

Kurt’s version: hiring is guessing, firing is knowing. You’ll never be 100 percent certain a hire will work out. But if someone has been on the team long enough and the pattern is clear, the decision is already made. You just haven’t acted on it yet.

Real leverage lives in the middle 80 percent. Not the stars who’ll be fine regardless. Not the bottom tier who probably need a different role. It’s the large middle group that responds to investment, coaching, clarity, and a manager who shows up consistently. Effort compounds there.

Worth saying directly: this isn’t about labeling people. It’s about where leadership time actually moves the needle. Most agency owners we talk to are spending 40 percent of their management bandwidth on the 10 percent of the team where it produces the least return.

Retainers change what you measure

Toward the end of the conversation, the topic turned to a shift that deserves its own episode. Progressive agencies are moving from time-and-materials billing to retainer-based recurring revenue. Sounds like a pricing decision. It’s actually an operations decision.

When you bill by the hour, your KPIs are built around utilization, billable hours, and efficiency per person. When you bill on a retainer, the measurement changes. Kurt pointed to agencies where the new performance signal is iteration speed. Three campaign cycles in a day instead of one. Value delivered to the client in a Tuesday test that nobody can cleanly attribute to a single role.

Old measurement infrastructure can’t capture that. And most agencies haven’t built the new one yet. They’re trying to run a recurring-revenue business on a billable-hour scoreboard, and the numbers keep telling them the work is fine even when the client is quietly disengaging.

Watch the operational signal underneath, not just the financial one. Whether the team’s planning rhythm has actually changed to match the new commercial model is what tells you if the shift is real. Pricing without an operating model behind it is just a number on an invoice.

One more thing about incentives

Grant brought up Anthropic giving unlimited Claude tokens to employees as an incentive. Not a pizza party or a plaque. Access to the tool that makes you better at your job, without a meter running.

Small example, but it says something about where incentive design is heading. Agencies that figure out how to reward the behaviors they actually want, not the behaviors their KPI dashboard happens to measure, will pull ahead. Everyone else will keep optimizing for last year’s scorecard and wondering why their best people keep leaving.

If any of this lines up with the conversations you keep having about your own agency, the full episode is worth 25 minutes. Grant and Kurt go deeper on every thread above, and a few that didn’t make it into this post.

Surviving the next two years won’t come down to who has the cleanest KPI dashboard. It’ll come down to who noticed what those dashboards weren’t showing them.

A planning gap is the space between the decisions an agency must make and what its current systems can actually show. Most agencies have one.

Few notice until margin starts moving in ways nobody can quite explain. These five questions are how to find out, before the next quarter forces the issue.

You probably already know the answer

Thursday afternoon. Pipeline meeting. Things look fine on the surface. Deals are progressing. Last month’s margin came in close to plan. Then someone mentions, almost in passing, that your senior dev is already booked through August, and your biggest active proposal needs that person in six weeks.

Nobody panics. Someone says “we’ll figure it out.” The meeting moves on.

Then you drive home and realize you priced that proposal three weeks ago. You assumed capacity. You didn’t actually know. And “figuring it out” usually means margin gets quietly absorbed somewhere in delivery, where leadership notices it three months later if at all.

That moment, the gap between what you decided and what you actually had to decide with, is the planning gap. Five questions help you tell whether your agency has one and how expensive it’s becoming.

Question 1: When you priced your last big project, did you know who would actually be available to deliver it?

Pricing on a capacity gut check is the most common entry point for a planning gap. The cost shows up in margin two quarters later, not at sale time.

A planning gap usually announces itself first at the pricing stage. If sales priced based on a generic team rate or a yes-we-have-bandwidth gut check from ops, the gap has already cost you margin. You just won’t see the bill for two quarters.

Most agencies have a CRM that shows what’s likely to close and a PM tool that shows who’s working on what today. Almost none have a single view that connects the two. Sales runs the timeline. Ops checks the calendar. Whoever has the most leverage in that conversation wins, and the answer that emerges has very little to do with what your team can actually deliver in the proposed window.

This is fixable in spreadsheets, briefly, until the company grows past about 25 people. After that, the manual reconciliation between pipeline and people takes longer than the deal cycle, so the assumption hardens before the data catches up. Pricing decisions get made on yesterday’s headcount picture. Margin leaks the difference.

If you can answer this question with a name, a date, and a confidence level rather than a feeling, you’re operating without a planning gap on this dimension. Most agencies operating with disconnected pipeline and capacity data cannot.

Question 2: How far ahead can you see capacity before you have to commit?

Planning happens at the pace of visibility. Most agency decisions span 8 to 16 weeks, but most forecasts show only 4 weeks ahead.

Planning happens at the pace of your visibility. If you can see four weeks ahead, you can plan four weeks ahead. Anything past that is a guess dressed up as a forecast.

Here’s the hard part. Most major agency decisions span eight to sixteen weeks. Hiring takes 60 to 90 days. Onboarding takes another 30. A new client’s first project usually scopes 12+ weeks out. Quarterly utilization plans require visibility through end-of-quarter at minimum.

So if your visibility is four weeks and your decisions span twelve, you’re not actually planning. You’re reacting on a slight delay.

Note that this isn’t a question of whether your tools could show capacity twelve weeks out. Most could, in theory. It’s whether they show it in a way leaders trust enough to make a real decision off of. A spreadsheet with hard-coded availability does not count. A PM tool with no demand signal does not count. The forecast has to combine pipeline weight, current allocations, planned PTO, anticipated ramp, and confirmed delivery, in one place, refreshed often enough that the numbers have not gone stale. (That’s the gap spreadsheets quietly fail to fill.)

A useful test: when did your capacity forecast last update? If the answer is “a month ago, when I rebuilt it,” you have a planning gap.

Question 3: When utilization drops, do you know whether to hire, redeploy, or wait?

Utilization moves. The planning gap is whether you can tell, in the moment, if it’s structural or temporary, before the decision window narrows.

Utilization moving is information. What to do about it requires interpretation. The planning gap is the difference between the two.

Most agencies see utilization shifts after the fact. By the time the number lands in a finance report, the team has already absorbed the impact, and the decision window has narrowed. The reactive moves, scrambling for billable work, deferring hiring, redeploying a senior to fill in, all cost more than the planned moves would have. (A weekly resourcing meeting can close this loop, if it’s run as a planning meeting and not a status meeting.)

What you actually need to answer is whether the drop is structural, like a long client wound down or the pipeline weight shifted, or temporary, like two PMs are between projects and three start dates moved. Those situations want opposite responses. Without enough planning context to tell the difference, agencies tend to overcorrect on whichever signal is loudest. They hire too late, then over-hire when revenue catches up. They redeploy a strong senior into a junior role to fill a week, and they don’t replace that senior when their slot opens up two weeks later.

If your last three responses to utilization shifts looked the same regardless of cause, the gap is showing up in your headcount plan and probably in your hiring budget.

Question 4: When a project slips, can you see margin impact in the same view as the schedule impact?

Projects slip. The planning gap is whether the schedule impact and the margin impact arrive at leadership in the same conversation, in real time.

Projects slip. That part is normal. The planning gap is whether you can see what the slip costs at the moment it happens, or only later, when finance closes the books.

PM tools show the slip clearly. New end date. Updated milestone. Owner notified. Finance, in a separate tool, with separate timing, shows the cost: extra hours billed, fixed-fee margin compression, downstream impact on the project that was supposed to start when this one finished.

Those two views rarely connect. PMs flag the slip. Finance closes the month. Nobody in between converts “two weeks late” into “$32,000 of margin spread across this project and the next two.” Leaders learn about the cost at the next month-end, by which point three more projects are slipping and nobody can disentangle which slip caused which margin miss. (An agency wrote off $100K against one project they couldn’t see in time.)

Connecting the two views is what closes this part of the gap. It does not require a financial dashboard for every PM. It requires that the schedule and the margin live in one planning layer, so the slip and the cost arrive at leadership in the same conversation.

If you can name your top three slipped projects this quarter and tell us their margin impact in one sentence each, this part of your gap is small. Most agency leaders cannot.

Question 5: If your top three projects each shifted timeline by a week, would your forecast update automatically?

Static forecasts freeze at creation. Volatility doesn’t. The planning gap is whether your forecast keeps up with the world, or has to be rebuilt to.

Static forecasts freeze at the moment they’re created. The world does not. Volatility shows up in projects daily. The planning gap is whether your forecast can keep up.

Open your forecast right now. If it lives in a spreadsheet that someone manually rebuilds every Monday, the answer is no, it would not update. Someone would have to remember the slips, find them, transcribe them in, recalculate the dependencies, and reissue the file. Most weeks, that does not happen on Monday. It happens the week the CFO asks. By then the forecast has drifted from reality by enough to be misleading.

A connected planning layer updates the forecast as the underlying data moves. The schedule changes, capacity shifts, pipeline weight rebalances, and margin reflects all of it. Leaders can ask questions of the forecast without needing it rebuilt first.

This is the test that catches the most agencies. Answers to questions one through four might be partial. Question five is binary. Either the forecast keeps up, or it doesn’t.

What the answers tell you

Be honest about the count.

One uncomfortable answer usually means a single team or process has a planning tension. Worth fixing. Probably manageable inside a quarter without new infrastructure.

Two or three uncomfortable answers means the gap is structural. Margin is leaking in places nobody can yet quantify, but it’s leaking. The fix is rarely another PM tool or another finance system. The fix is a planning layer that connects what the existing systems already collect.

Four or five means the gap is shaping decisions that drive the business. Pricing, hiring, capacity, margin. Every quarter without addressing it costs more than the previous one, because volatility compounds against weak forecasts faster than it does against strong ones.

Based on Parallax’s work with over 130 clients. Sample period: 2024 to 2025. Source: aggregate Parallax planning data. Most agencies in that group land at three uncomfortable answers when they first run through these questions. The work to get from three to one isn’t reorganizing the team or replacing tools. It’s giving leaders a planning view that matches the decisions they’re being asked to make.

A planning gap is not a tooling problem

These questions can feel uncomfortable because most agency leaders have already invested in good tools. PM tools work. Finance systems work. CRM works. The gap isn’t that the tools are broken. It’s that they were each built for a different job, and nobody built the layer that connects them for forecasting purposes.

Agencies feel the gap rather than see it because no one tool is failing. Each is doing exactly what it was built for. What’s missing is the forecast, and forecasts don’t show up as a missing tool. They show up as decisions that don’t quite line up with the data, again and again, until someone names it.

Parallax was built to be that planning layer. Naming the gap is the first move. Closing it is the next.

What to do with this

If three or more of these questions made you flinch, the most useful next step is to see what the planning layer looks like in practice, applied to your own agency’s decisions. A walkthrough takes about thirty minutes and produces a written read on where your gap sits and what closing it would change.