At some point, every agency or services leader has had this moment.
You are in a meeting about a new piece of work that looks good on paper. The scope feels manageable. The timeline seems reasonable. Sales is confident. Then someone asks the question that quietly determines whether the next few months are calm or painful: do we actually have the right people available to staff this work next month?
The room goes quiet.
Not because the team is underperforming. Not because delivery is broken. And usually not because the tools are bad.
Most agencies today are highly capable. They deliver complex work, juggle multiple clients, manage scope creep, and keep things moving with a stack of tools that gives decent visibility into projects and utilisation. The problem is not execution. The problem is that those tools are increasingly being asked to answer resourcing and planning questions they were never designed to solve. So the spreadsheet comes out. Again.
This is not a “your stack is broken” post
It is worth being clear about that upfront. If your PM tool, PSA, and a handful of spreadsheets are doing a lot of work for you, that is not a failure. It is a sign your team is resourceful.
You have systems that do a good job of tracking work once it is sold, showing who is busy right now, and reporting on utilisation, time, and margin after the fact. That setup works reasonably well when things are steady. The tension shows up when things move.
A deal slips. Scope expands. A client pauses. A senior lead gets pulled into pitches. Someone resigns. Holidays stack up at the wrong moment. Suddenly leadership is not asking what is happening today. They are asking what is likely to happen next. That is where resourcing starts to creak.
The questions your tools keep getting asked
These are not hypothetical questions. They are the ones agencies wrestle with every week. If this deal lands, who actually staffs it without blowing utilisation? If we move a senior person onto a pitch, what breaks elsewhere? Can we take this work without creating delivery debt? Are we genuinely under-resourced, or just badly allocated? Do we need to hire now, or can we hold if a couple of projects slip?
What these questions have in common is not complexity. It is timing. They are forward-looking, scenario-based, and dependent on assumptions that change constantly. This is resourcing work, but it is also planning work. Most teams are trying to do it with tools built to report on work that already exists.
Why great execution tools struggle with planning
Most PM tools and PSAs are built to do three things very well: track approved work that is in flight, capture time, cost, and utilisation once the work exists, and report performance against plans that were already set. They are systems of execution and record.
Resourcing and planning require something different. They need a view of demand before it is final, a view of capacity that includes trade-offs rather than just availability, the ability to model what happens if work lands or slips without rewriting history, and visibility into how resourcing decisions affect margin, delivery confidence, and hiring timing.
When execution tools are pushed into that role, one of two things usually happens. Either they give answers that are technically true but practically unhelpful, or teams create a parallel planning world outside the system. That parallel world is usually held together with spreadsheets, placeholder projects, and a lot of manual effort. Spreadsheets are not the villain. They are the universal adapter. They appear when the business needs a planning layer and does not have one. The problem is that this layer is fragile by design.
Why this is getting worse right now
Many agencies got away with spreadsheet-led resourcing when the business was smaller and more predictable. That is no longer the environment most teams are operating in.
Margins are tighter, so small resourcing misses show up as real profit loss. Demand is more volatile, so next month is always partly unknown. Client expectations are higher, so delivery confidence matters more than ever. Volatility does not create resourcing problems. It exposes them.
When planning is fragile, resourcing absorbs the uncertainty. When resourcing absorbs too much uncertainty, everything downstream starts to wobble. That shows up as taking work you should not take because it looks fine for now, passing on good deals because staffing confidence is low, hiring late because the signal arrives after burnout starts, and re-scoping work midstream because the original resourcing assumptions never quite held. Most margin misses start here, not in delivery, but in resourcing decisions made weeks earlier.
A simple way to talk about it
One way to make this click inside leadership teams is to separate the time horizons. Execution tools tell the truth about now. Finance systems tell the truth about the past. Planning needs the truth about next.
That “next” truth is not clean. It includes probability, assumptions, and trade-offs. But it is still the truth leaders need to make confident decisions. Resourcing sits right in the middle of this gap. It is where future demand meets real capacity. When there is no clear place to model that future, spreadsheets become the default planning layer, and that layer becomes fragile because it relies on constant manual upkeep.
What to do about it without blowing up your stack
This is not a call to replace your PM tool or finance system. Those tools should keep doing their jobs.
A healthier approach is to be clear about roles. Execution tools remain execution tools. Finance remains the system of record. Then you add a planning and foresight layer designed specifically for resourcing decisions that sit ahead of delivery pressure and margin loss. That layer does not need to be perfect. It needs to be stable. A place where assumptions are visible, scenarios can be revisited, and leaders trust the inputs.
A quick resourcing check worth running
If you want one practical way to pressure-test how resourcing decisions are really being made, start here.
Think about the resourcing calls that come up most often. Staffing new work. Pulling senior people into pitches. Deciding whether to hire or wait. Choosing which deals feel safe to accept.
For one or two of those decisions, write down the actual question being answered. Not the report you look at, but the question behind it. Who is realistically available if this lands? What breaks elsewhere if we move people around? How much delivery risk are we comfortable carrying into next month?
Then look at where the answer comes from today. Is it coming from a system you trust, or from stitching together partial views? Does it rely on someone translating between tools? Would the answer still hold if a project slipped, scope changed, or someone was suddenly unavailable?
Anywhere the answer depends on manual reconciliation or one person’s context is a weak spot. Not because the team is careless, but because the business is being asked to plan without a stable place to do it. You do not need to fix everything at once. Pick one decision that tends to create pressure when it goes wrong and give it a more reliable home. A place where assumptions are visible, scenarios can be revisited, and the conversation does not reset every week. That alone changes how resourcing feels.
Where Parallax fits in (as an example)
If you are using this framing to align the team for the year, it helps to name the category.
A planning and foresight layer is additive. It sits alongside execution and finance systems and exists to answer forward-looking resourcing questions before they turn into fire drills. Parallax is built for that layer.
It connects current delivery, real capacity, future demand, and financial context into a single forward-looking view. Not to manage tasks or replace accounting, but to help leaders make better resourcing, pricing, and hiring decisions while there is still time to adjust. Execution stays where it is. Finance stays where it is. Resourcing and planning finally have a home.
The point of this framing
This is not about saying your tools are bad. It is about recognising that tools have jobs.
When good tools are used for the wrong job, smart teams compensate with effort. For a while, that looks like adaptability. Over time, it turns into hidden risk. If teams can agree on the gap, the rest of the year gets easier to navigate.
You can have clearer conversations about what delivery debt looks like before margin erodes, how scope creep and client pauses really affect resourcing, how to protect senior people without starving pitches or delivery, and how to make deal decisions with confidence instead of hope.
As agencies become more dynamic, resourcing stops being a weekly scramble and starts needing a real planning system behind it. Not because teams are failing, but because the business has outgrown the tools it is stretching to plan the future.
Callum Broaderick
Vice President
Parallax
