Login Get a Demo

Author: Parallax

Why Agency Project Profitability Is So Hard to Predict

By Parallax |

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.

Frequently Asked Questions

Why do so many agencies struggle with project profitability?

Three structural reasons: the data lives across different systems (CRM, time tracking, project management) with no native connection; visibility is retrospective by default (monthly reports answer last month’s question); and agency work resists fixed scope because client input changes requirements mid-project. None of these are management failures. They’re properties of how agency work is structured. Getting ahead of them requires a live connection between those data systems, earlier in the delivery cycle.

How do you improve project profitability at an agency?

Start upstream. The highest-leverage point is estimation accuracy and change order discipline during scoping and delivery. After that: an in-flight variance tracking habit that runs at a two-week interval rather than month-end. That gives you time to act on what you find. Agencies that run consistent post-project reviews on margin also improve faster, because they’re learning from each project’s data rather than repeating the same estimation patterns.

What causes project profitability to be lower than expected?

In rough order of frequency: scope creep without change orders (informal additions that compound over the project), underscoped discovery (the original estimate didn’t account for the work it would actually take), unexpected rework cycles from unclear client direction, resource mix drift where senior staff end up doing work that was scoped for lower rates, and late-project hour spikes as the team works to deliver on time despite earlier delays. Usually two or more of these occur on the same project.

How far in advance can agencies predict project profitability?

With a connected data layer, four to six weeks of lead time is achievable on active projects. That’s enough time to take corrective action: open a change order conversation, swap resources, scope down a phase, or have a direct conversation with the client about the situation. Without live data, most agencies discover issues at month-end or project close, when the decisions that drove the outcome are already locked in.

Is there a standard profit margin for agency projects?

On a direct-cost basis, healthy agency project margins typically land in the 35-50% range. Below 30% on a recurring basis suggests either systematic underscoping, scope creep absorption, or margin compression from client pressure. The more useful benchmark is your own trailing four-quarter average, segmented by project type. Understanding your actual margins by engagement type tells you far more than industry averages about where to focus.

What is the planning gap in agency project profitability?

Most agencies have their delivery data in project management tools and their financial data in accounting systems. What’s missing is a connected planning layer that sits between them: something that can answer “given current delivery pace, what will this project’s margin be at completion?” in real time. The planning gap is where that visibility should exist but doesn’t. Closing it doesn’t require replacing either system; it requires connecting the data across them.

Your Time Data Is in the Wrong System

By Parallax |

When agency teams log hours in a payroll or HR system instead of a planning tool, the data that should drive capacity and margin decisions never arrives where it’s needed. Planning runs on assumptions. Actuals sit in a system built for compliance, not forecasting. That structural gap is why so many agencies can’t see margin risk until it’s already baked in.

Two systems, one missing connection

Most payroll and HR platforms do one thing well: they process compensation accurately. Hours go in, paychecks come out. Compliance is satisfied. From a finance perspective, the system is doing exactly what it was built to do.

What it wasn’t built to do is feed a planning layer. Payroll systems don’t know what project those hours belong to, whether the work was on-budget or over, or whether the team member who logged eight hours is now over-allocated for the next three weeks. That context doesn’t exist in the system because the system was never designed to hold it.

So when a planning tool sits on the other side of that gap, it’s working with estimates. Planned hours, not actual hours. Forecasted utilization, not real utilization. Margin projections built on assumptions that no one has validated since the project kicked off.

A timesheet is not a moral scorecard. It’s a receipt for reality. When that receipt goes to the wrong system, the planning layer never gets it.

Why this happens at so many agencies

It’s worth being direct about how this pattern starts: it’s not negligence. Most agencies didn’t choose to split time data across systems. It happened incrementally.

Payroll came first. HR came next. Both required time input, so people started logging there. When a planning tool arrived later, the habit was already set. Asking people to log time in two places is a fast way to get compliance in neither. So teams kept logging where they always had, and the planning tool got whatever data someone remembered to enter manually, if anyone entered it at all.

Some teams try to bridge this with exports. Someone pulls a CSV from payroll every two weeks, reformats it, and pastes it into the planning tool. That works until the person who does it goes on vacation, or the export format changes, or the project codes don’t match between systems. Then it quietly stops working and no one notices for a month.

What “arbitrary” hours actually signal

One pattern that shows up in conversations with ops leaders: team members logging time with no clear connection to project reality. “I put eight hours in” because eight hours is a full workday, not because the work took eight hours or because anyone asked them to track against a specific deliverable.

When hours are logged in a payroll system, this is almost guaranteed. Payroll needs total hours for compensation. It doesn’t need project codes, phase breakdowns, or task-level detail. So people log what satisfies the system, which is a number that adds up to the right total for the pay period.

That data, when it eventually reaches a planning tool, looks like actuals. It gets treated as actuals. But it isn’t. It’s a rough approximation of time worked, stripped of the project context that would make it useful for forecasting.

Forecast variance doesn’t always come from bad estimates. Sometimes it comes from actuals that were never real in the first place.

The planning layer is flying on assumptions

Consider what a resource manager is actually working with when time data doesn’t flow from the right source. Planned hours exist in the planning tool. Actual hours exist somewhere else, in a format that doesn’t map cleanly, updated on a payroll cycle rather than in real time. The gap between plan and reality is invisible until a project is already over budget or a team member is already burned out.

Capacity planning in this state isn’t planning. It’s guessing with extra steps. A resource manager might look at a team member’s allocation and see 80% utilization, which looks healthy. What they can’t see is that the actual hours logged in payroll last week were 55 hours, not 40. Or that a project that looked on-track in the planning tool is already two weeks behind because no one updated the estimates after scope changed.

This is the structural gap. Not a process failure, not a people failure. A data architecture problem that makes accurate forecasting structurally impossible regardless of how disciplined the team is.

Integration isn’t just a technical problem

Fixing this requires more than connecting two systems via API. It requires deciding where time data should live and what it needs to do.

If hours need to serve payroll and planning, the entry point matters. Logging in payroll and syncing to planning usually produces the stripped-down data described above: totals without context. Logging in a planning tool and syncing to payroll preserves project-level detail and gives the planning layer what it actually needs.

That’s a workflow change, not just a technical one. It means asking people to log time in a different place than they’re used to, with more structure than payroll required. Change management is real here. So is the need for the planning tool to make time entry low-friction enough that people actually do it.

Some agencies land on a middle path: a dedicated time tracking tool (Harvest is the most common) that sits between the two systems and syncs to both. This works when the integration is maintained and the project codes stay aligned. It breaks down when either system changes and no one updates the mapping.

Whatever the architecture, the principle is the same. Actuals need to reach the planning layer with enough context to be useful. Hours without project codes, phase tags, or role context aren’t actuals. They’re noise.

What changes when the data flows correctly

When actual hours reach the planning layer in real time, with project context intact, a few things shift.

Forecast variance becomes visible earlier. If a project is tracking 15% over on hours in week three, that signal exists in the planning tool while there’s still time to act on it. Scope conversations can happen before the budget is gone. Resource adjustments can happen before someone is already at 120% utilization.

Margin visibility improves at the project level and across the portfolio. A resource manager can see not just whether a project is on-track in hours but whether the mix of roles delivering those hours is consistent with the margin target. Senior hours on tasks scoped for junior delivery show up as a cost signal, not just a staffing note.

Capacity planning becomes grounded in what’s actually happening rather than what was planned to happen. When a team member logs 50 hours in a week, that affects their available capacity for the next week. When that data arrives in the planning tool, the forward view adjusts. When it doesn’t, the forward view stays optimistic until reality arrives as a surprise.

None of this requires perfect data. It requires data that’s directionally accurate, project-aware, and timely enough to inform decisions before they’re locked in.

A note on where Parallax fits

Parallax is built to be the planning layer that sits over your existing stack, including your time tracking setup. Whether your team logs time in Harvest, Jira, or a dedicated time entry workflow, the integration architecture matters because the planning layer is only as useful as the data feeding it. When hours arrive with project context and role detail, Parallax can surface capacity risk, margin pressure, and utilization drift before they become problems. When hours arrive as payroll totals, that visibility disappears.

If you’re carrying this data gap in your own shop and want to see what closing it looks like with your actual stack, we can walk through it with you.

Actuals that never reach the planning layer aren’t actuals. They’re a gap with a cost that compounds every week you don’t close it.

Agency Utilization Rate: Forecasting It, Not Just Measuring It

By Parallax |

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.

Frequently Asked Questions

What is a good utilization rate for an agency?

For direct production staff (creative, strategy, development, analytics), 70-80% billable utilization is generally considered healthy. Below 65% suggests over-staffing or pipeline gaps. Above 85% runs a risk of burnout and delivery quality issues. For management and account roles, 60-70% is more typical because their work includes more coordination overhead. Agency leadership is often in the 40-60% range. The right target depends on your pricing, overhead model, and growth stage.

How do you calculate agency utilization rate?

Billable hours divided by available hours, times 100. Available hours should exclude approved PTO, holidays, and any non-working days. The most common errors: including all hours worked (not just billable) in the numerator, or using total calendar hours instead of actual available hours in the denominator. Role-level calculation is more useful than firm-level aggregation for most decisions.

What is the difference between billable and productive utilization?

Billable utilization counts only hours charged directly to client projects. Productive utilization includes both billable work and non-billable productive work (new business, internal projects, R&D). Billable utilization is the cleaner metric for capacity and revenue decisions. Productive utilization is useful for understanding total team output, but it can mask genuine capacity issues if non-billable work is growing without corresponding revenue.

How far ahead should agencies forecast utilization?

Six to eight weeks is the practical range. Far enough out to take action on what you find (start a hire, increase sales pressure, plan subcontracting) but close enough that the forecast is credible. Beyond twelve weeks, forecast accuracy for agency-type work degrades quickly because pipeline timing and scope are too variable. At the firm level, quarterly horizon planning makes sense for staffing decisions with longer lead times.

Why does utilization fluctuate so much at agencies?

Project-based work by definition creates gaps between engagements. The transition periods between project close and project start are the structural cause of utilization dips. The other major driver is scope variance: projects that end sooner than expected leave team members with unplanned availability. Agencies that manage transitions actively (overlap resourcing, internal project buffer, new business pipeline cadence) have less utilization volatility than those that plan project-to-project without visibility across the portfolio.

How does utilization connect to agency profitability?

Directly. Low utilization means you’re paying for capacity that isn’t generating revenue. High utilization above a sustainable ceiling means you’re degrading the capacity itself through burnout. At the target range (70-80% for production roles), you’re generating enough billable output to cover team costs and overhead with room for margin. Resource forecasting that connects utilization, pipeline, and cost structure gives leadership the visibility to optimize across all three rather than managing them as separate problems.

Agency Profit Margin Benchmarks: A Planning-Gap Perspective

By Parallax |

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.

Frequently Asked Questions

What is a good profit margin for an agency?

It depends on the agency type and revenue model. Creative and strategy agencies with primarily service revenue typically target 40-55% gross margin. Performance marketing and full-service agencies, which often include media pass-through, see blended gross margins in the 35-50% range. Operating margin, which includes overhead, is often in the 20-30% range for well-managed mid-size agencies. Net profit of 10-20% is achievable at disciplined firms. Your own trailing four-quarter average by service type is more useful than any industry average.

How do agencies improve profit margins?

Three levers: pricing confidence (are you pricing consistently based on what the work actually costs?), delivery efficiency (are projects running at estimated hours, or consistently over?), and utilization (are you running billable capacity at target rates?). Most agencies have room to improve on at least two of the three. The one that’s most often ignored is utilization, because it requires forward visibility into pipeline and capacity rather than backward-looking financial reporting.

What is the average profit margin for a marketing agency?

Reported ranges vary significantly by source and agency type. For independently owned agencies with primarily service revenue, gross margins of 40-55% and operating margins of 20-30% are often cited as healthy. Holding companies and large networks tend to optimize for different metrics. These figures are directional; actual firm performance varies widely based on pricing model, client mix, and operational maturity.

Why do agency margins fluctuate so much?

Project-based revenue creates natural volatility: project timing, scope changes, and utilization gaps between engagements all affect margin in a given quarter. The agencies with the most stable margins tend to be those running primarily retainer revenue at consistent utilization, with active change order and scope management discipline. Margin volatility is often a signal that scope, utilization, or pricing decisions are being made without real-time financial visibility.

What is the planning gap, and how does it affect agency margins?

Most agencies have their delivery data in project management tools and their financial data in accounting systems. What’s usually missing is a connected planning layer that shows how pipeline demand, team capacity, and project-level costs interact week to week. Without that layer, pricing is conservative (because capacity is uncertain), scope creep gets absorbed (because the financial consequence isn’t visible in real time), and bench cost accumulates (because utilization isn’t being managed forward). Those three forces together are what keep agency margins chronically below what the work and rates would otherwise support.

How do you track profit margins at an agency?

Start with a consistent definition: project margin (direct costs only) is the most actionable number for delivery decisions. Gross margin (direct plus allocated overhead) is the number for pricing strategy. Run project-level margin tracking at a two-week in-flight cadence rather than waiting for month-end close. Build a simple variance tracking habit: planned margin versus actual margin, by project type, updated quarterly. Over time, that dataset will tell you more about your margin drivers than any industry benchmark.

How to Evaluate a Planning Platform’s Longevity Before You Commit

By Parallax |

Ops leaders are now asking whether a planning platform will still exist in two years before a demo ends. That’s a fair question. Evaluating vendor longevity means looking past funding announcements at product investment cadence, customer concentration, and what a forced migration would actually cost your team.

One prospect put it plainly: “We want to make sure we’re not continuing to invest time and effort into a platform that maybe isn’t going to be here for the long term.” That’s not a procurement concern anymore. It’s surfacing at the top of the funnel, before contracts, before security reviews, sometimes before a second conversation. Ops leaders have watched enough SaaS consolidations and shutdowns to know that switching a planning tool mid-stride is expensive in ways that don’t show up in any vendor’s pricing page.

Why this question is coming up earlier now

Vendor consolidation in the agency software space accelerated after 2022. Several planning and PSA tools were acquired, repositioned, or quietly wound down. Agencies that had built workflows around those platforms spent months rebuilding integrations, re-training staff, and absorbing the planning gaps that opened up during the transition.

Switching a time-tracking tool is annoying. Switching a planning and forecasting platform is a different problem entirely. Your resource plans, utilization history, pipeline-to-capacity logic, and margin tracking all live there. When that platform goes away or pivots hard, you don’t just lose a tool. You lose the institutional memory embedded in it.

So when an ops leader asks about longevity early in an evaluation, they’re not being difficult. They’re doing the math on switching cost before they invest another year of workflow into a vendor relationship that might not hold.

What vendor longevity actually means in practice

Funding stage matters less than most buyers think. A Series B announcement tells you a vendor raised money. It doesn’t tell you whether the product is growing, whether the customer base is concentrated in one segment, or whether the team has the depth to sustain a multi-year roadmap.

Four things are worth examining directly.

Product investment cadence. Ask for a changelog. Not a roadmap slide, an actual release history. Vendors who are building have a visible cadence of shipped features. Vendors who are coasting or in financial difficulty ship slowly and talk about roadmap instead. If a vendor can’t point you to six months of meaningful product updates, that’s a signal worth weighing.

Customer concentration. A vendor whose revenue is concentrated in a handful of large accounts is more fragile than one with a distributed customer base. Ask directly: how many customers do you have, and what does the size distribution look like? Vendors with 130+ active customers across multiple agency segments have a different risk profile than one with 15 enterprise logos.

Integration depth vs. integration breadth. Vendors who have built deep, maintained integrations with tools like HubSpot, Salesforce, Jira, and Harvest are harder to abandon. Those integrations represent real engineering investment and real customer dependency. A vendor with five shallow API connections is easier to shut down than one whose data flows are embedded in a dozen agency stacks.

What migration would actually cost. Before you evaluate any new platform, price out what leaving it would cost in 18 months if you had to. How long would it take to export your data? What would break in your reporting? Which workflows would need to be rebuilt from scratch? If you can’t answer that, you’re not evaluating switching risk, you’re just hoping it won’t happen.

The cost of staying on fragile workarounds

Here’s where the longevity question gets complicated. Most ops leaders asking about vendor viability are currently running planning on spreadsheets, a PM tool stretched beyond its design, or some combination of both. Staying on those workarounds has its own risk profile, one that’s easy to underweight because it’s familiar.

Spreadsheets don’t go away. But they also don’t scale, don’t connect pipeline to capacity in real time, and don’t surface margin risk before it’s already baked into a project. Every month a team plans on a fragile workaround is a month of decisions made without the visibility those decisions actually require.

Switching risk is real. So is the cost of not switching. Framing the evaluation as “should we take the risk of a new platform” misses the other side of the ledger: what does staying on the current approach cost, month over month, in planning errors, reactive hiring, and margin erosion that arrives too late to fix?

A useful exercise: estimate what your current planning approach costs in wasted time, missed capacity signals, and one or two pricing decisions that went sideways last year. That number is the baseline. Vendor longevity risk gets weighed against it, not in isolation.

Questions worth asking in any platform evaluation

Most vendor evaluations focus on features. Longevity evaluation requires a different set of questions.

Ask about ownership structure. Is the company founder-led, PE-backed, or VC-funded? Each has different incentive structures around growth, exit, and product continuity. None is inherently bad, but each shapes how a vendor behaves when the market gets difficult.

Ask about the support model. Vendors who are thinning out tend to thin support first. If you’re getting routed through a generic help desk on your first sales call, that’s a preview of what post-sale looks like.

Ask what happens to your data if you leave. A vendor confident in their product will answer this cleanly. One who hedges or redirects is telling you something about how they think about customer relationships.

Ask about the product team’s size and tenure. A planning platform that has shipped consistent updates for three or four years has institutional knowledge in its engineering team. A platform that’s been through two rounds of layoffs and a pivot has a different kind of institutional knowledge.

How to weight longevity against capability

No vendor is zero-risk. The question is whether the longevity risk is proportionate to the capability gain.

If a platform closes a planning gap that’s currently costing your team real money, in margin erosion, in reactive hiring, in forecast variance that shows up as a surprise every quarter, then some vendor risk is worth accepting. The alternative isn’t safety. It’s a different kind of risk, one you’ve already normalized.

If a platform is roughly equivalent to what you have now, with a less certain future, that’s a different calculation. Don’t pay switching cost for lateral movement.

Longevity questions are worth asking early. So is the question of what you’re actually buying. A planning platform that connects pipeline to capacity to margin, and surfaces those signals before decisions lock in, is a different investment than a scheduling tool with a nicer interface. Evaluate them differently.

Parallax surfaces those forward-looking signals, utilization pressure, margin risk, capacity gaps, before they become delivery problems. If you’re in the middle of an evaluation and want to walk through what that looks like against your own pipeline data, we can do that.

Vendor risk is real. So is the cost of planning blind. Most agencies that ask the longevity question early are doing it because they’ve already paid that cost once.

Frequently Asked Questions

How do I evaluate whether a resource planning platform will still exist in two years?

Look past funding announcements. Ask for a real changelog, shipped features, not roadmap slides. Ask about customer count and distribution. Ask what your data export looks like if you need to leave. Vendors who are building confidently answer these questions directly. Ones who are coasting or struggling tend to redirect.

What does switching a planning platform actually cost an agency?

More than most people track. Beyond the license cost of a new tool, you’re looking at data migration, integration rebuilds, retraining staff, and the planning gap that opens up during the transition. Agencies that have been through a forced migration after a vendor shutdown or acquisition typically estimate three to six months of disrupted planning workflows. That’s the number to weigh against vendor risk.

Is staying on spreadsheets safer than adopting a planning platform with some vendor risk?

Spreadsheets don’t disappear, but they carry their own risk profile, one that’s easy to underweight because it’s familiar. Decisions made without real-time pipeline-to-capacity visibility have a cost: pricing errors, reactive hiring, margin erosion that arrives too late to fix. Vendor risk and workaround risk both belong on the same ledger.

What ownership structure signals should I look for in a planning software vendor?

Founder-led, PE-backed, and VC-funded companies each have different incentives around growth, exit timing, and product continuity. None is automatically disqualifying. What matters is whether the incentive structure aligns with long-term product investment. Ask directly how the company is capitalized and what the exit horizon looks like. A vendor confident in their trajectory will answer plainly.

Why are ops leaders asking about vendor longevity earlier in the buying process?

Because they’ve watched enough SaaS consolidations and shutdowns to know the cost of rebuilding workflows mid-stride. Planning platforms carry more embedded institutional knowledge than most tools, resource history, utilization patterns, margin logic. When that platform goes away or pivots, the disruption is significant. Asking early is rational risk management, not procurement paranoia.

Your KPIs Are Fine. Your Agency Might Not Be.

By Parallax |

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.

Frequently Asked Questions

What's wrong with standard agency KPIs like utilization and revenue per head?

Nothing, taken on their own. They tell you how the business performed. They don't tell you why, or whether the performance is durable. Utilization can look healthy while two of your senior PMs are running on fumes. Revenue per head can hit target while a client relationship is quietly unraveling. The numbers aren't lying. They're answering a narrower question than most leadership teams realize.

How do you know if your KPIs are missing what matters?

Simplest test: when your dashboard says one thing and your week feels like something else, the dashboard is usually wrong. Or at least incomplete. Most agency owners can name two or three problems they've been watching for months that don't show up anywhere in their reporting. That gap is the answer.

Is micromanagement always bad?

Episode 2 reframes the term. What teams resist isn't oversight, it's randomness. A manager who checks in consistently with clear expectations is not micromanaging. A manager who descends unpredictably, reacts to whatever catches their eye, and disappears until the next crisis is. Consistency is the variable that matters.

Why does the move from time-and-materials to retainer change what you measure?

Billable-hour models reward output per person per hour. Retainer models reward value delivered over time, often through faster iteration cycles. The dashboards built for the first model can't read the signal in the second. Agencies making this shift commercially usually haven't rebuilt the operating model underneath it, which is why the numbers stop reflecting reality.

Where should an agency leader spend their coaching time?

Grant and Kurt's framework: not on the top 10 percent, who'll be fine regardless. Not on the bottom 10 to 15 percent, who probably need a different role. Compounding return lives in the middle 80 percent, the team members who respond to investment, clarity, and a manager who shows up consistently.

Why focus on communication when most agencies already have Slack and standups?

Because the tools and the cadence don't guarantee that information is moving. Kurt's rule of thumb in the episode: something has to be read seven times, heard three times, and felt once before it sticks. The agencies that close that loop deliberately, instead of assuming it happens, are the ones whose plans actually survive contact with the team.

Five Questions That Reveal Your Agency’s Planning Gap

By Parallax |

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.

The Planning Gap Grader

Take our 60 second gap grader and get your personal score, so you can start closing your gaps.

Get your score

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.

Frequently Asked Questions

What is a planning gap?

A planning gap is the gap between the decisions an agency is being asked to make and the data its current systems can actually show. PM tools show today. Finance shows last month. Neither shows next quarter in a way leaders can act on. The space between is the gap.

How is a planning gap different from poor planning?

Poor planning is a process failure. A planning gap is a tooling and visibility failure. Most agencies with planning gaps have strong leaders and good processes. The gap is structural, not cultural. The fix is connection, not motivation.

Can spreadsheets close a planning gap?

Sometimes, briefly. Spreadsheets work for agencies under 25 people who have one person tracking everything. Past that size, the manual reconciliation between pipeline, capacity, and margin takes longer than the decision cycle, so the spreadsheet is always behind reality by the time anyone consults it.

How big does an agency need to be before a planning gap matters?

Around 25 to 30 people. Below that, leaders can hold the planning picture in their heads and the gap rarely costs more than the time it takes to fix in spreadsheets. Above that, the gap shows up in margin variance, hiring lag, and forecast accuracy that drifts from reality each quarter.

What signals show a planning gap is costing money?

Forecast variance over 5%. Hiring decisions made reactively after utilization spikes. Pricing decisions made without confirmed capacity. Project margin discussions that happen at month-end rather than at the moment a slip occurs. Any one of these is normal occasionally. All four together are the gap.

Is the planning gap the same as resource management?

No. Resource management is operational, week to week. The planning gap is upstream of that, at the level of pricing, hiring, and capacity strategy. Good resource management can run inside a planning gap, but it cannot close the gap on its own.

Can a fractional CFO close a planning gap?

A fractional CFO usually closes the financial reporting side of the gap by improving the rear-view picture. Agencies with planning gaps still need the forward-view layer, which is operational rather than financial, and which connects pipeline, capacity, and delivery in one place. The two efforts are complementary, not interchangeable.

How One Agency Lost $100K to Operational Blind Spots

By Parallax |

How One Agency Lost $100K on a Single Project (And What It Took to Fix the Problem)

Brian ran a 40-person custom development agency. Within his first two weeks on the job, he discovered a six-figure write-off. Not because the work was bad. Because nobody could see it coming.

 

 

The project that broke everything

Good client. Solid work. Then the client acquired two companies mid-project, and the scope tripled overnight.

What happened next is predictable if you’ve spent any time in agency operations. The project team said yes. Made the client happy. Absorbed the new work without a change order or a revised timeline. Nobody told anyone what the expanded scope would actually cost.

When the invoice landed, the client lost it. Never agreed to pay three times the original price. And honestly? Fair. Nobody had communicated the change. No documentation existed. Not a single person had stopped to say: this is a different project now, and here is what it costs.

Brian met them in the middle. He wrote off over a hundred thousand dollars. In his second week.

“My life is a warning to others,” he told us during a recent Parallax webinar. He wasn’t kidding.

Why scope creep costs agencies more than they think

Scope creep is the most common source of margin erosion in project-based businesses. PMI data shows it affects more than half of all projects. But the real damage goes beyond the one project that goes sideways.

When Brian’s two most experienced (and most expensive) developers got locked into the expanded project, every other client in the pipeline shifted. Nobody told those clients that their timelines had just moved two months. Nobody wanted to deliver that news, so nobody did. Brian found out when phones started ringing.

One project absorbed the senior team. Other projects slipped. Clients got angry about things that had nothing to do with their own work. The ripple effect turned a single scope failure into a company-wide fire drill.

Sound familiar? Most agencies have a version of this story. The write-off is the visible cost. Everything that shifts around it is the real damage: delayed projects, angry clients who had nothing to do with the original problem, trust you can’t invoice your way back from.

What zero visibility actually looks like inside an agency

Brian’s systems were a mess. And not in a “we should tidy this up someday” kind of way. In a “the accounting system was still DOS-based” kind of way.

His CRM was designed for manufacturing. It tracked inventory quantities, not project timelines or resource plans. Asana handled what was in flight, but backlogs lived in spreadsheets. And the timecard system? Looked like Windows 98.

Zero integration between any of them. So when Brian needed to understand what was happening across the business, he pulled data from four different places, stitched it together in Excel, and hoped the formulas didn’t break.

They always broke.

“I used to joke that I was going to submit some of my formulas to Microsoft’s formula contest,” Brian said. “I was proud of that complexity. And that was the problem.”

Eventually the spreadsheet got so complex that Brian was the only person who could update it. Project managers would email him changes. He’d manually input them. By Thursday or Friday, he had a view of the business. By Monday, stale.

Why agencies get stuck in reactive mode

Brian spent most of his time doing forensic analysis. Not leading. Not growing the business. Just forensics. A client would call, angry about a missed deadline or a surprise invoice. Brian would scramble to figure out what happened, who was on the project, what was promised, what was actually delivered.

“I wasn’t working on the business,” he said. “I was working inside it. And that’s not what the owners hired me to do.”

If you’ve managed agency operations, you recognize this. Your tools show you what already happened. Financials show up after the project closes. By the time you see a margin problem, the project is done and the only lever left is writing off the difference.

Brian couldn’t tell you his ten most profitable clients. He couldn’t tell you his ten least profitable clients. He couldn’t answer the question “who should we fire as a client?” because the data didn’t exist in any usable form.

“Hey, who are the clients we’re losing money on?” he said. “It was an anecdotal story from people. No data to back it up.”

The real cost of “we’ll figure it out”

Brian’s sales team had quotas. They were incentivized to close deals. So when a client asked “can you get this done by end of year?” the answer was always yes.

“I must have heard a million times: ‘ah, we’ll figure it out,’” Brian said. “That was literally our answer to any problem. With no strategy.”

Timelines were optimistic. Resource plans were nonexistent. The project team would get a signed proposal and ask “who agreed to this?” The answer, every time: “we did, so we could get the business.”

The project always took exactly as long as operations said it would. (It always does.) But the client expected what sales promised. That gap was baked in from day one.

This is the part that doesn’t show up in any dashboard. Optimism replaces planning. Nobody has the data to push back. Sales can’t see capacity, operations can’t see pipeline, and the guesses compound until something breaks.

Why name-brand software doesn’t solve agency problems

Brian’s agency was a technology company. They built custom software for clients. They knew exactly what tools existed and how to integrate them. The irony wasn’t lost on anyone.

“We sat around and laughed,” Brian said. “‘If we took two developers and let them go dark for a month, they could build exactly what we needed.’ But we couldn’t get out of our own way.”

When Brian went to ownership to make the case for new systems, the conversation always drifted toward the big names. NetSuite. Salesforce. The tools every CEO in a Vistage group recommends because they work well for manufacturing, insurance, and paper companies.

None of those were designed for agencies. Built to ship products, not to track time against services or forecast capacity across a portfolio of concurrent engagements. Project-level margin isn’t even a concept in most of them.

“There’s software for shrimp farmers,” Brian pointed out. “So when there’s software for shrimp farmers, there is absolutely something built for professional services organizations where time is the biggest asset.”

Discovery is the problem. Purpose-built tools don’t have the marketing budgets of a Salesforce. They don’t show up first in search results or get recommended in CEO peer groups where nobody else runs an agency.

How to make the business case for better agency operations

Brian had to justify the investment to owners who didn’t experience the chaos directly. Chaos is hard to put a dollar value on. But write-offs are not.

“You remember that hundred thousand I just wrote off?” Brian told them. “Do you know how much the business has written off over the last year? If it’s only going to cost $150,000 to put in an entirely new system, and we wrote off a quarter million dollars last quarter, the math is a no-brainer.”

That ended the conversation. Owners will spend $150K to fix a $250K problem every time. But Brian had to frame it in dollars, not frustration. “I can’t do my job with these tools” wasn’t enough. “Here is exactly how much money we are losing” was.

For agency leaders building a similar case: start with the write-offs. Then add the cost of reactive hiring, the margin erosion you couldn’t prevent, and the revenue from clients who left because communication broke down. The number is always larger than anyone expected.

The cultural shift that made the difference

New tools alone didn’t fix it. The team wanted better systems. They were tired of the chaos. But the real change was process.

Proposals went through operations review before reaching the client. Someone in ops confirmed that what sales was promising could actually be delivered with available resources. Change orders became standard. Any scope change got documented, priced, and agreed to before work started.

Weekly project reviews tracked margin and timeline in real time. Not after the fact. Not at month-end. During the project, while there was still time to adjust.

“Even our clients would say, ‘I’m expecting things to go a little wrong during this project. Just tell me,’” Brian said. “‘Don’t hide it from me. Don’t lie.’”

Communication was the biggest win. Clients didn’t need perfect projects. They needed to know what was happening. Once teams had the data to communicate early, the firefighting stopped. Brian went from years of never talking to a happy client to actually running the business he was hired to run.

What Parallax does differently

Brian joined Parallax because it solved the exact problem he lived through. It sits between your CRM, your project tools, your timesheets, and your financials, connecting data that already exists across those systems into a single forward-looking view.

You pick the CRM that works for your sales team. You pick the project management tool your PMs love. You pick the timecard system that’s least painful for everyone. Parallax brings those signals together so leaders can see capacity, margin, and delivery risk before commitments are locked in.

It doesn’t replace your tools. It makes them work together for planning in a way they were never individually designed to do. And if you swap out one tool (say your PM team wants to move from Asana to Monday), the rest of your stack stays intact. Parallax just connects to the new one.

That flexibility matters. The agencies that stay on duct-taped spreadsheets aren’t lazy. They’ve just been burned by systems that tried to do everything and did nothing well. Parallax is built specifically for project-based businesses that sell time. Not inventory. Not widgets. Time.

Key takeaways for agency leaders

Scope creep is a visibility problem, not a discipline problem. Brian’s team wasn’t careless. They were trying to make the client happy without the data to understand the cost of saying yes.

Your spreadsheet is a symptom. If the most complex formula in your company lives in a planning spreadsheet that only one person can update, that’s not resourcefulness. That’s missing infrastructure.

Reactive management has a dollar value. Add up the write-offs, the margin misses you discovered too late, the clients who left over communication failures. That number is your business case.

Name-brand software is not built for you. The tools your CEO peer group recommends were designed for product companies. Purpose-built options exist for services businesses. They’re harder to find, but they’re out there.

Culture changes alongside systems. Better tools without better process just gives you faster access to the same chaos. Ops review on proposals, documented change orders, and weekly margin check-ins are what close the gap.

FAQ

How much does scope creep cost agencies?

More than most people track. PMI data shows scope creep hits over 50% of projects, and the cost ranges from 10% to 50% of total project revenue depending on severity. But that’s just the direct hit. For a mid-sized agency running multiple concurrent projects, even small scope expansions compound into six-figure annual losses once you factor in the write-offs, the delayed timelines on other projects, and the downstream client trust damage that nobody ever puts a number on.

What causes agencies to lose money on projects

It’s rarely one thing. Disconnected systems prevent leaders from seeing margin and capacity in real time. Sales teams set optimistic timelines without operations input. Change order processes don’t exist or get skipped. And the whole culture tends toward reactive management where problems are only visible after the damage is done. Brian’s story is a textbook case of all four happening at once.

How do agencies improve project profitability?

Two things need to happen together. First, connect your operational data (CRM, project management, timesheets, financials) into a single planning layer that shows margin, capacity, and delivery risk while there’s still time to act. Second, pair that with process changes: pre-sale ops review on proposals, documented change orders, weekly project margin reviews. Tools without process is just faster chaos. Process without tools is just more spreadsheets.

What is the planning gap in professional services?

It’s the disconnect between the decisions leaders need to make right now (pricing, hiring, resourcing) and the information their systems can actually provide at that moment. Delivery tools show what’s happening today. Finance systems explain what already happened. Neither one was built to answer the question leaders actually need answered: what’s likely to happen next? That gap is where agencies lose money, and it’s the reason most operational problems feel like they appear out of nowhere.

The Weekly Resourcing Meeting That Actually Works

By Parallax |

What makes a good resourcing meeting?

If your weekly resourcing meeting feels like group therapy where everyone vents and nothing changes, you are not alone. Most agencies have some version of this meeting. It usually includes a lot of screenshots, a lot of “we will figure it out,” and at least one person quietly updating a spreadsheet that nobody wants to admit is still running the show.

This guide is the version that actually works because it is built around a single idea:

The meeting is not a status meeting, it’s for decisions.

Quick takeaways

  • A weekly resourcing meeting has one job: make tradeoffs before tradeoffs make you.
  • The meeting should be short and consistent. Thirty to forty five minutes.
  • Prep prompts are the difference between decisions and vibes.
  • Decision rules prevent the same debate from happening every week.
  • No decision is real until the plan is updated.

Definitions

  • Resourcing meeting: A recurring meeting where the team decides staffing tradeoffs across projects and pipeline.
  • Status meeting: A meeting where teams report what happened. Useful, but not the same thing as resourcing.
  • Capacity bottleneck: A role or skill that becomes constrained in the next few weeks, creating delivery risk.

If you want meeting agenda templates and checklists, check out the Resource Management Best Practices.

Get the Guide

What this meeting is for

A weekly resourcing meeting has one job. It’s to make tradeoffs before tradeoffs make you.

That means the meeting exists to:

  • Confirm what is real this week
  • Spot capacity conflicts before they explode
  • Make decisions quickly
  • Assign owners to updates
  • Leave with a plan people can follow

What this meeting is not for

  • Project status: Project status meetings belong in delivery.
  • Debating company priorities: Those discussions belong with leadership, with a simple escalation path.
  • Renegotiate old staffing decisions: If the decision is wrong, fix it and move on.

Who should be in the room

Keep this tight. If everyone is invited, nobody feels accountable.

Minimum attendees

  1. Resource owner: This could be a resource manager, operations lead, or whoever owns the plan.
  2. Delivery lead representation: Either a PM lead or a small set of delivery leads who can speak for active work.
  3. Sales or pipeline owner representation: Someone who can speak to changes in near term pipeline and timing.

Optional attendees

  1. Finance or leadership: Only if your agency needs them for fast tradeoff decisions. Otherwise, they are not needed weekly.

Rule of thumb

If someone cannot make or support a decision, they probably do not need to be in the meeting.

If you want meeting agenda templates and checklists, check out the Resource Management Best Practices.

Get the Guide

What you need before the meeting starts

This is the part that makes the meeting work. If you skip this, the meeting becomes vibes.

Every delivery lead comes to the meeting prepared to answer.

  1. What changed since last week?
    Scope change, timeline shift, staffing change, client surprise, anything that affects the plan.
  2. Where are you at risk?
    Anything likely to miss a deadline or exceed an estimate.
  3. What do you need?
    Specific roles, dates, and how much. Not “we need help.”
  4. What can move?
    If you had to give up something, what would it be?
  5. Are timesheets clean?
    Yes or no. If no, what is missing and when will it be fixed?

⚠️ Looking for ideas to make timecards less painful? Check out Timesheets Without Resentment.

The agenda that keeps it moving

This meeting should be 30 to 45 minutes. If it is longer, the inputs are messy, or the decision rules are missing.

Here is the agenda.

1) Quick reality check – 5 minutes

  • Question: What has changed since last week that affects the plan?
  • Output: A short list of changes everyone agrees are real.

2) Confirm capacity bottlenecks – 10 minutes

  • Questions
    • Where are we overloaded in the next two to six weeks?
    • Where do we have excess capacity?
    • Where are we double-booked?
  • Output: A list of conflicts that require decisions today.

3) Make tradeoffs using decision rules – 15 minutes

This is the heart of the meeting. You do not solve every problem. You decide what happens next.

  • For each conflict, answer these questions fast:
    • What is committed versus optional?
    • What has the closest deadline with real consequences?
    • What has unique skill constraints that cannot be substituted?
    • What is the cleanest tradeoff if we move work, swap roles, or adjust scope?
  • Output: Decisions and owners, not just problems.

4) Pipeline impact review – 10 minutes

  • Question: What deals, start dates, or staffing assumptions changed this week?
  • Output: Updated assumptions that feed next week’s forecast.

5) Close and commit – 2 minutes

  • Do this out loud
    • Repeat decisions
    • Confirm owners
    • Confirm what gets updated and by when
  • Output: A clean list of actions and owners.

The decision rules that prevent chaos

If your meetings turn into debates every week, you don’t have decision rules. You have opinions.

Here are simple rules that keep resourcing decisions consistent.

  • Rule 1: Work already sold and in flight wins over new internal requests.
  • Rule 2: If a project is in danger, fix the constraint, not the symptoms. That could mean scope reset, timeline shift, or staffing change. Heroic efforts should be the exception, not the rule..
  • Rule 3: If the same emergency keeps repeating, it is a process failure. Capture it and fix the root cause, not just the current week by escalating to the appropriate leaders and updating the process.
  • Rule 4: If you cannot decide in the room, escalate with clear options. Do not escalate the drama. Escalate the choice.
  • Rule 5: No decision is real until the plan is updated. The meeting output is not the conversation. The meeting output is the updated plan.

If you want meeting agenda templates and checklists, check out the Resource Management Best Practices.

Get the Guide

What the meeting outputs must be

If you want this to feel like a machine, not a conversation, your outputs need to be consistent.

At the end of every meeting, you should have:

  • A prioritized list of staffing decisions
  • Owners assigned to each change
  • A list of risks that need escalation
  • Updated pipeline assumptions
  • A clear list of what gets updated today

If your meeting ends with “we’ll figure it out,” you did not have a resourcing meeting. You had a calendar event.

Common failure modes and fixes

Failure mode: You show up with no prep, then spend the meeting discovering problems.

Fix: Require the 5 key questions are ready to be answered. No prep, no meeting.

Failure mode: The meeting becomes a status meeting.

Fix: Move project status back into delivery and keep this meeting about decisions only.

Failure mode: Every conflict becomes a debate about priorities.

Fix: Use decision rules and an escalation path. Get to decisions fast.

Failure mode: Decisions are made, but nothing is updated.

Fix: Assign an owner to every update and confirm that the update happens on the same day.

Weekly checklist

Before the meeting

  1. Delivery leads answer pre-meeting questions
  2. Timesheets are confirmed clean or flagged
  3. Resource owner updates the view that will be used in the meeting

During the meeting

  1. Changes and risks are confirmed
  2. Conflicts are identified
  3. Decisions are made with decision rules
  4. Owners are assigned
  5. Actions are repeated out loud at the end

After the meeting

  1. The plan is updated the same day
  2. Owners confirm updates are complete
  3. Escalations are scheduled quickly, not next week

If you want meeting agenda templates and checklists, check out the Resource Management Best Practices.

Get the Guide

Copy and paste templates

Meeting invite description

This meeting is for resourcing decisions, not project status. Come prepared with changes since last week, staffing needs, and any risks that could affect delivery in the next six weeks. We will leave with decisions, owners, and updates to the plan.

Message to delivery leads

Before the weekly resourcing meeting, reply with

  1. What changed since last week?
  2. Where are you at risk?
  3. What you need, including role and dates?
  4. What can move if needed?
  5. Whether your team’s time is up to date

Meeting close checklist

  • Here is what we decided today
  • Here is who owns each update
  • Here is what gets escalated

FAQ

Q: How long should a weekly resourcing meeting be?

A: Thirty to forty five minutes. If it takes longer, either the inputs are messy, or the team is trying to solve delivery status in a resourcing meeting. To scale, use 30-45 minute meetings per department or team.  Longer meetings will always deviate from the goals.

Q: Who should run the meeting?

A:The person who owns the resourcing plan. That might be a resource manager, ops lead, or delivery operations leader. The key is ownership of the plan and the authority to assign follow-up.

Q: What is the difference between resourcing and project status?

A:Status is what happened and what tasks are next. Resourcing is whether the right people are available at the right time to deliver what was promised.

Q: What if we cannot make priority calls in the meeting?

A:Then the meeting should produce a clear set of options and quickly escalate the decision. Do not carry the conflict week to week.

Next step

If you want the full operating rhythm for this meeting, including forecasting cadence and conflict-resolution routines, start with Resource Management Best Practices for Agencies

Grant Hultgren
Vice President
Parallax