Author: Callum Broderick

 

A lot of operational frustration in agencies is not caused by bad tools.

It is caused by good tools being asked to do work they were never designed to do.

That is when you see teams forcing a project tool to behave like a planning system.

Or forcing a CRM to answer delivery questions.

Or forcing finance reporting to become a forecasting process.

The tool is fine. The job is wrong.

This post is a practical way to spot those mismatches, understand why they keep happening, and fix them without turning your stack into a bigger mess.

 

Quick takeaways

• Tool frustration often means a role is trying to make decisions without the right kind of visibility.
• Execution tools track work. They do not reliably forecast tradeoffs across projects.
• CRM tracks deals. It does not know delivery capacity or timing constraints.
• Finance reporting explains what happened. It does not steer what happens next.
• If you name the job clearly, you can choose the right system behavior, often without replacing everything.

 

Definitions

Execution or Delivery tool
A tool designed to manage work already in motion, tasks, owners, due dates, and delivery coordination.

Planning tool or planning layer
A system built for forward-looking decisions that connect demand, capacity, timing, and tradeoffs.

System of record
The source you trust as the official answer for a specific category of truth, pipeline, time, billing, staffing, delivery status.

Decision layer
The cross-functional view leaders need to make commitments without guessing.

 

The mismatch pattern

Here is the pattern that shows up over and over.

A team needs to answer a question.

The existing system does not answer it in a clean way.

So someone builds a workaround.

The workaround becomes a new process.

The process becomes a dependency.

Then the tool gets blamed for not being flexible enough.

This is not a team failure. It is a category mismatch.

 

Check out Why Spreadsheets Keep Showing Up in Tech Stacks

 

Four common examples in agencies

1) Using project management for resource forecasting

What the team is trying to do

Predict whether the agency can take on work, staff upcoming projects, and avoid double booking.

Why the tool feels like it should work

It already contains projects, tasks, and a schedule.

Why it usually breaks

Project tools are designed around what is planned inside a project.

Resource forecasting is designed around what is possible across all projects, plus pipeline, plus real-life volatility.

The tool can show a schedule, but it struggles to answer:

• What happens if we move this start date?
• Which roles are constrained six weeks out?
• If we accept this deal, what is the tradeoff?
• Where is double booking hiding across multiple teams?

The symptom

Spreadsheets appear to connect the dots.

2) Using CRM for delivery commitments

What the team is trying to do

Use pipeline and stages to predict start dates, staffing needs, and revenue timing.

Why the tool feels like it should work

Deals and dates live there.

Why it usually breaks

CRM is optimistic by design. That is not a criticism. It’s the job.

But delivery reality has constraints.

• Roles are limited
• People are already committed
• Timelines shift
• Scope changes

The CRM can tell you the sales story. It cannot tell you whether that story is compatible with capacity.

The symptom

Start dates get promised and then renegotiated after the deal closes.

3) Using finance reporting as a forecasting process

What the team is trying to do

Understand margin risk and profitability early enough to act.

Why the tool feels like it should work

Finance reports show margin, revenue, costs.

Why it usually breaks

Finance reporting is historical.

It answers what happened. Leaders need to know what is about to happen.

Forecasting margin risk requires:

• current actuals that are close enough to trust
• staffing plans for the next six to twelve weeks
• scope and timeline shifts
• change request volume

The symptom

Margin surprises show up when it is too late to change the plan.

4) Using a PSA as the only decision system

What the team is trying to do

Use one system to manage staffing, time, billing, and forecasting.

Why it feels like it should work

It touches many parts of the business.

Why it usually breaks

Many PSAs do parts of this well, but decision-making still requires cross-team alignment.

Even when the data exists, the workflow for making tradeoffs is often missing.

The symptom

The PSA becomes a reporting tool, while planning decisions happen elsewhere.

 

How to diagnose mismatches quickly

Here is the fastest way to spot when a good tool is being used for the wrong job.

Step 1) Start with the questions

List the recurring questions that create stress.

Examples

• Can we take this work without breaking delivery?
• Who is overloaded in the next six weeks?
• What work is at margin risk and why?
• When should we hire versus contract?
• What is the tradeoff if we pull forward a start date?

Step 2) Identify the tool being used to answer each question

Often, the same tool gets forced into answering multiple unrelated categories.

Step 3) Look for mismatch symptoms

Mismatch symptoms include

• manual exports and copy-paste
• multiple versions of truth
• heavy reliance on one person to reconcile data
• long meetings that end with no decisions
• changes made in conversation but not reflected in the plan

If you see these patterns, the tool is not the problem.

What you are asking it to do is wrong.

 

What to do about it

This does not require a rebuild of your whole stack.

It requires naming the jobs and making sure the right systems own each one.

Here is the simplest approach.

1) Declare systems of record

This reduces arguments.

Examples

• CRM owns pipeline truth
• Project tool owns work status
• PSA or time tool owns actuals
• Finance owns invoicing and financial truth

Then you identify what is missing

The decision layer.

2) Add or build a planning layer

The planning layer connects the dots leaders need.

It is designed to answer

• demand by confidence
• capacity by role
• timing and tradeoffs
• what happens if we shift dates
• where margin risk is building

This layer can be a dedicated system or a structured process backed by the right views.

The point is that it must be forward-looking and resilient to change.

3) Create a weekly decision cadence

Even the best system fails without a cadence.

A weekly rhythm with clear inputs and decision rules turns planning into an operating habit.

 

📕 Check out the Resource Management Best Practices guide for meeting cadence and agenda templates.

 

4) Reduce side door work

Most tool mismatch pain is amplified by uncontrolled change requests.

If work changes scope, timing, or staffing, it needs one intake path and an explicit tradeoff.

 

Copy and paste templates

Tool mismatch worksheet

Question we need to answer

Who asks it and why?

What tool we use today?

What breaks or feels painful?

Workarounds we rely on?

What job this question really belongs to?

What system should own it?

What cadence should support it?

Phrase that keeps it calm

We are using a good tool for a job it was not designed to do. Let’s name the job, then decide what should own it.

 

Checklist: Signs you are in tool mismatch mode

• The tool works fine for its core job, but feels terrible for planning
• People keep asking for custom fields, reports, or views to force it into a new role
• Spreadsheets keep appearing as glue
• Meetings are long because the data is not aligned
• Decisions are made but the source of truth is never updated
• Ops depends on heroic upkeep to keep plans current

If you checked more than two, you are likely dealing with job mismatch, not tool failure.

 

FAQ

Does this mean we chose the wrong tools?

Not necessarily. Most stacks cover execution and financial reporting well. The gap is usually a planning and decision layer.

Why does this show up more as agencies grow?

Because volatility increases. More projects, more roles, more overlap, more change requests. The cracks show up faster.

What is the fastest first move?

List the recurring questions leadership needs answered weekly, then map them to systems of record. The gaps will be obvious.

Do we need to replace our CRM or project tool?

Usually no. Most teams keep those and add a planning layer that connects the dots.

 

Next step

If you want a practical operating rhythm that reduces mismatch pain, start with the Resource Management Best Practices guide.

That guide lays out the weekly cadence, forecasting approach, and decision routines that keep planning decisions grounded in reality.

 

Callum Broaderick
Vice President
Parallax

 

January is usually the month when agencies feel the most organized.

New year energy. Fresh plans. Clear priorities.

Then February shows up with a client surprise, a deal that starts early, a project that runs long, and someone on the team taking a much-needed break.

And suddenly, the plan becomes a guessing game again.

If your agency can see one month clearly but the rest of the year feels like fog, you are not failing. You are missing a forecasting rhythm that can survive volatility.

This post is a practical way to think about year planning that does not collapse after January. It is built for agencies where work changes constantly and planning needs to be more like steering than scheduling.

 

Quick takeaways

• Annual plans fail when they try to be exact. They work when they create direction, guardrails, and decision cadence.
• You do not need a perfect twelve-month plan. You need a reliable six to twelve-week forecast that you refresh weekly.
• The goal is fewer surprises, faster tradeoffs, and clearer hiring and start date decisions.
• Planning is not a document. Planning is a rhythm.

 

Definitions

Rolling forecast
A forecast window, often 6 to 12 weeks, that is refreshed weekly so the plan stays connected to reality.

Capacity
The people and time available to do work, by role and skill.

Demand
The work you need to deliver, including active projects and likely upcoming work.

Confidence bands
A simple way to separate sold work from likely work from speculative work, so you do not staff hope like it is reality.

 

Why January feels clear

January is clear because it contains fewer unknowns.

• Projects already in flight are known
• Holiday schedules stabilize
• Many clients slow down or reset
• New work is still in early stages

That temporary calm makes it easier to plan.

The problem is what most agencies do next.

They treat January planning as the plan.

Then reality returns and the plan breaks.

 

The real reason annual plans break in agencies

Annual plans fail when they are treated as a schedule.

Agencies are too volatile for a fixed schedule.

Clients pause and restart.

Scope expands after kickoff.

Approvals slip.

Sales cycles stretch.

Work that was supposed to end in March has been extended to May.

So the goal of annual planning is not to predict everything.

The goal is to create a direction and a decision system that can respond when the year changes.

 

The planning stack that works

Think of planning in three layers.

Layer 1) Annual direction

This answers

• What are we trying to accomplish this year?
• What types of work do we want more of?
• What do we want to avoid?
• What are our constraints, hiring limits, margin targets, client mix goals?

This layer should be stable.

Layer 2) Quarterly focus

This answers

• What matters most this quarter?
• What bets are we making?
• What capacity assumptions are we operating on?

Quarterly planning is where you decide where leadership attention goes.

Layer 3) Rolling six to twelve-week forecast

This is where reality lives.

This answers

• What is likely to start soon?
• Where are the role hotspots?
• What tradeoffs do we need to make now?
• Where is margin risk building?

This layer changes weekly.

If you only have layer 1 and layer 2, you will feel good in January and stressed by March.

If you add layer 3, planning stops being a quarterly surprise.

 

The weekly rhythm that keeps the year from collapsing

This is the simplest planning rhythm that works in real agencies.

Weekly

• Update delivery changes, scope shifts, timeline shifts, staffing shifts
• Update pipeline changes, start date shifts, and confidence shifts
• Review the next six to twelve weeks for capacity hotspots by role
• Decide on tradeoffs
• Update the plan the same day

Monthly

• Review margin risk and client health signals
• Review whether hiring or contracting needs to change
• Review client mix and delivery strain

Quarterly

• Reconfirm quarterly priorities
• Adjust annual direction only if necessary

This rhythm is how you get control without pretending the year will behave.

 

📕 Check out the Resource Management Best Practices guide for meeting cadence and agenda templates.

 

How to plan the year without fake precision

Here is a practical approach that keeps the year honest.

Step 1) Define what success means

Not in slogans. In a few clear outcomes.

Examples

• Grow revenue by a certain amount
• Improve margin consistency
• Reduce delivery fire drills
• Shift client mix
• Build capacity in a key discipline

Step 2) Define guardrails

Guardrails protect the plan when the year gets chaotic.

Examples

• No new work enters delivery without a start date assumption and role needs
• Change requests require a tradeoff
• Double booking above a threshold triggers a decision, not overtime
• Timesheets close weekly, so forecasts stay connected to reality

Step 3) Forecast demand using confidence bands

Separate demand into three buckets.

Green, sold, and scheduled

Yellow, likely but timing may shift

Red, early, or speculative

This prevents the most common annual planning mistake.

Staffing hope.

Step 4) Forecast capacity by role, not by person

Most resourcing stress is role-based.

You run out of senior design capacity.

You run out of technical leadership.

You run out of a specific delivery role.

Role-based forecasting lets leadership make clearer decisions on hiring versus contracting versus timing shifts.

Step 5) Decide what happens when reality changes

Write down the default actions.

If a deal slips

• move it to lower confidence
• release held capacity unless explicitly approved

If a client adds scope

• intake the change
• confirm tradeoff
• reset timeline or staffing if needed

If a role becomes overloaded

• change work
• change staffing
• change commitments

The point is not to avoid change. The point is to have a consistent response to change.

 

Copy and paste templates

Annual planning questions for leadership

• What do we want more of this year?
• What do we want less of?
• What is the biggest constraint, people, sales, delivery, margin, leadership attention?
• What capacity bets are we making?
• What risks do we want to avoid?
• What operating guardrails will we enforce?

Weekly rolling forecast checklist

• What changed in delivery?
• What changed in pipeline?
• What are the next six week role hotspots?
• What tradeoffs do we need to make?
• Who owns each update?
• What gets updated today?

 

📕 Check out the Resource Management Best Practices guide for meeting cadence and agenda templates.

 

Checklist: Signs you are planning only one month at a time

January looks clean, the rest of the year looks like vibes

• Hiring decisions feel urgent instead of intentional
• Start dates get promised then renegotiated after the deal closes
• The same resource conflicts repeat weekly
• Leadership sees margin issues after they happen

If you checked more than one, the fix is not more planning meetings. It is a rolling forecast with clear decision cadence.

 

FAQ

Do we really need a twelve-month plan?

You need annual direction. You do not need a twelve-month schedule. Agencies win by steering, not by predicting.

How far out should we forecast capacity?

Six to twelve weeks is usually the sweet spot. Far enough to see hiring and staffing issues early. Close enough to still be real.

What is the fastest way to make annual planning feel real?

Add a weekly rolling forecast and treat planning as a cadence. That is what keeps the year from drifting.

How do we keep sales and delivery aligned?

Use confidence bands and a weekly review to update start-date assumptions and staffing realities together.

Next step

If you want a practical guide behind this, start with the Strategic Planning Guide 📕

That guide lays out the weekly cadence, forecasting approach, and decision routines that keep plans connected to reality beyond January.

 

Callum Broaderick
Vice President
Parallax