Blog Archives

The Questions Leaders Ask That No System Really Owns

By Parallax | February 3, 2026

Every agency leadership team has a familiar moment.

Pipeline looks fine. Delivery looks busy but stable. Finance looks mostly fine.

Then someone asks a simple question.

And suddenly, everyone is staring at three different dashboards like they are going to fuse into one answer.

They never do.

Not because your stack is bad. Not because your team is doing anything wrong.

This is because many of the questions leaders rely on are not owned by any single system. They sit in the gaps between CRM, project management, PSA, and finance.

This post is a structured list of those questions and how to use them. Not a pitch. Just a practical way to spot the blind spots that create surprises.

Quick takeaways

Leadership questions are decision questions. They are forward-looking and require assumptions.
Most systems are built around their own world, deals, tasks, time, and invoices.
The unanswered questions live in the overlap between those worlds.
You do not need a new tool to start. You need ownership, a cadence, and a shared scorecard.

Why these questions slip through the cracks

Most tools have a job and a point of view.

CRM is organized around deals and stages.

Project tools are organized around work and tasks.

PSA systems are organized around time, staffing, and billing.

Finance is organized around invoices, costs, and actuals.

Leadership is organized around decisions.

Those decisions are usually about what happens next, not what already happened. They involve tradeoffs. They change when a client pauses, a deal slips, or a senior person gets pulled into a pitch.

That is why these questions become everybody’s problem and nobody’s responsibility.

The six categories of questions leaders keep asking

Use these categories as a map. If a question keeps showing up in exec meetings, it is probably in one of these buckets.

1) Revenue questions that are not really revenue questions

These sound like finance or sales questions until you try to answer them. Then you realize they require delivery reality too.

Common examples

How much revenue is actually likely to land next month, not just what is in the forecast?
If these two deals close, what work starts first and what gets delayed?
Which deals are we quietly counting on, even though staffing them would be painful?
What is the revenue impact if a key client pauses for four weeks?
Are we over relying on one team, one discipline, or one client for next quarter?
If we win this big deal, what do we stop doing to make room for it?
Which deals look profitable in a proposal but become margin problems once staffed with real people?

What this category is really asking?

Are we selling a plan we can execute without breaking delivery and margin?

What makes it hard to answer

CRM can show stages and probability. Finance can show historical run rate. Neither can tell you what happens when the same two senior specialists are already booked across multiple deadlines.

2) Capacity questions that are really risk questions

These show up as resourcing questions, but they are usually risk questions in disguise.

Common examples

Do we have the right people for the work that is likely to start soon?
Where are the real pinch points by skill and seniority, not just total availability?
Which teams are one unexpected absence away from a scramble?
How much capacity is already spoken for by unplanned work?
If we shift a key leader to a pitch, what breaks in delivery?
If we accept this deal, which current clients will feel the impact first?
Who is the hidden bottleneck that every project depends on?

What this category is really asking?

Where does the plan break first?

3) Hiring questions that live between pipeline and delivery

Leaders rarely ask “Should we hire” in the abstract. They ask questions about timing and risk.

Common examples

When do we need to hire so we are not late, but also not early?
What role do we need next, and what work proves it?
Are we trying to solve a skills gap or a scheduling gap?
If we do not hire, what is the cost in missed revenue or delivery strain?
If we do hire, what must be true for that hire to pay off?
Should we use contractors, partners, or a hire based on the shape of demand?
If the pipeline slips by one month, do we still feel good about the headcount plan?

What this category is really asking?

Is this demand a spike, or a new baseline?

4) Delivery risk questions that nobody wants to own

These questions tend to show up late, right after something starts to feel off.

Common examples

Where are we building delivery debt right now?
Which projects look fine on paper but are quietly consuming senior attention?
What happens if scope expands after kickoff, which it usually does?
If timelines compress, which milestones become unrealistic first?
Which clients are about to experience a confidence wobble?
What work is at risk because it depends on a single person or a single approval?
Where are we likely to have to rescope, and what does that do to margin and trust?

What this category is really asking?

What is likely to go wrong next, and do we see it early enough to act?

5) Margin questions that are really planning questions

Margin issues almost never start as finance issues. They start as planning issues, then show up later as financial surprises.

Common examples

Which projects will miss margin if nothing changes?
Which projects can still be saved, and what change would actually save them?
Are we staffing with the right mix, or just the available mix?
How much non billable work is riding along inside delivery?
What work is being done that is not in scope, not billed, and not discussed?
If we keep taking rush work, what does that do to profitability next month?
Are we pricing based on a delivery plan we cannot actually execute?

What this category is really asking?

Are we making preventable profitability mistakes because the plan is unclear?

6) Client questions that do not fit neatly into any dashboard

These are often the most important questions and the least reportable ones.

Common examples

Which clients feel stable but are one mistake away from escalation?
Which clients are at risk because we are stretched thin, not because the work is bad?
Where have we trained a client to expect immediate turnaround that we cannot sustain?
Which relationships rely on one person and would wobble if that person stepped away?
Where are we over delivering to protect trust, and what is the cost of that habit?
Which clients should we push back on now to avoid a larger conflict later?

What this category is really asking?

Where is relationship risk building even if the work looks fine on paper?

📕 Check out Resource Management Best Practices for a list of questions and meeting guides

The real issue is not data. It is ownership.

When a question spans multiple systems, it usually spans multiple teams too.

Sales owns pipeline truth.

Delivery owns staffing reality.

Finance owns margin truth.

Operations owns process and planning habits.

But the executive question is often one combined sentence.

If we win this, can we deliver it without harming everything else

That sentence has no natural owner.

So it gets answered through a mix of exports, spreadsheets, gut feel, and the heroic effort of whoever knows where the bodies are buried.

A simple way to use this list in your next leadership meeting

This turns the post into an action, not a reading exercise.

Step 1: Pick ten questions that come up most often

In a leadership meeting, circle the ten questions you hear repeatedly.

Step 2: Score each question

For each one, answer three quick prompts.

Can we answer it in under two minutes
Do we trust the answer
Who owns the answer

Step 3: Assign ownership and cadence

For questions that are important and hard to answer, assign an owner and a weekly cadence.

Owner does not mean they personally gather every datapoint.

Owner means they make sure the answer exists and is discussed.

Step 4: Turn it into a weekly executive scorecard

Pick a small set of signals that cover the categories above.

Review weekly.

If something is yellow or red, decide what happens next.

📕 Check out Resource Management Best Practices for a list of questions and meeting guides

Copy and paste template: Question ownership worksheet

Use this table in a doc or spreadsheet.

Question
Category
Current source of truth
What we do today to answer it
Owner
Cadence
Action when the answer is unclear

Checklist: Signs the questions are running your business from the shadows

Decisions slow down because confidence is low
Decisions speed up because someone has to make a call anyway
Good deals get passed on because staffing feels uncertain
Risky deals get accepted because the risk is hard to see early
Hiring happens late because the signal arrives after the pain starts
Delivery becomes reactive even when the team is working hard

If you checked more than one, this list is not theoretical. It is already your operating system.

FAQ

Are these questions a sign we have the wrong tools?
Not necessarily. They are a sign that leadership decisions live between systems.

What is the fastest way to reduce the scramble?
Pick a few high value questions, assign ownership, and review them weekly. Consistency beats perfect reporting.

Who should own these questions?
Different questions belong to different owners, but the scorecard belongs to leadership. If leadership reviews it weekly, it becomes real.

What if the answers require assumptions?
That is normal. The goal is not certainty. The goal is early warning and honest tradeoffs.

Next step

If you want the operating rhythm behind these questions, check out the Resource Management Best Practices to keep these tips handy.

That is the place where the weekly cadence, forecasting approach, and decision routines live in one place.

Brian LaMee
Recovering Professional Service Executive
Parallax

Interview recap: Amy Anderson of Wild Coffee Marketing

By Parallax | January 26, 2026

Capacity, clarity, and leading when there is no margin for error

This post is a Q and A pulled from our conversation with Amy Anderson, CEO and co-founder of Wild Coffee Marketing. It is lightly edited for readability, but the answers stay in Amy’s voice. Watch the full interview here

Q: First, what is Wild Coffee Marketing, and do you actually market coffee

A: I am the co-founder and CEO of Wild Coffee Marketing. We actually do not market coffee. It was a plant that was growing outside my window while I was writing a business plan in Miami, and it was growing up over the window, and I kept having to cut it back with a machete. I looked up what it was, and it was called wild coffee. So I thought it was a perfect name for a strategy led group that serves as a growth partner to our clients.

I would not describe us as a typical agency. I am a brand-side marketer of 30-plus years. When I say strategy-led, it is led by CMO thinking and fractional CMO services backed by a fractional marketing team. We have creative services and writing, but we are strategists at heart and lead every engagement with that.

Q: What did 2025 feel like from your seat

A: Postponements and scope demand. We were being asked to do more, and to be more nimble and flexible to drive results in a macroeconomic environment that had a lot of uncertainty.

Because we are strategy-driven, it was so much about our market contracting, where are we going to take the business, where is our area of focus, what are additional platforms, is our messaging right. In this environment, we were really asked to do more, and then had some unexpected turbulence in the market.

Q: You talked about operational clarity. What does that actually mean

A: Operational clarity is really important. Where are your resources going at any given time. When you have to pivot, you have to be able to pivot the resources as well.

So it is really understanding where I had capacity, what people were in what seats, were they in the right seats in order to deliver. That clarity from an operations standpoint is really important. You have to have processes. You have to have the right people in the seat.

Q: As a CEO, what are you focused on day to day

A: My primary areas of focus are always culture, and people, and the numbers. Capacity and utilization definitely comes up as a primary driver of those numbers.

Culture is the umbrella over it. Have you created a great place for your team to work. Feeling psychologically safe so they can be creative. We focused on work-life harmony. I do not even want to call it balance. That is very important, but we also work hard.

So to strike that balance of harmony and safety and kindness while demanding the rigor and the delivery is not the easiest balance to strike, but it is something we need to all be looking at.

Q: Capacity and utilization can get weird fast. What did you learn this year

A: You have to be careful with capacity number discussions. That is a major learning for me this year.

I hear 70 percent billable, 90 percent in an IT focused production firm. Well, we are strategy. How much discussion and work and participating in meetings that may not be directly billable do they do.

I took this year to figure out what that number was. The ambitious leader in me always wanted to drive the billable percentage. But what I started to notice is what is the impact on the team.

Given what I am asking of them, given what clients are asking of them, is it right to continue to try to drive that number up. The answer was no.

What I found is that the billable percentage is lower, and that has to be okay, and you have to run the business around that. But also, how do you talk about that with your team. It is sensitive.

I do not want people coming into meetings defending what their percentage is, and they cannot always control that. Maybe I did not sell enough, and our business development team did not sell enough. Maybe we did not sell something that directly correlated with billable work.

This year was really about learning caution and the nuance of how you handle your capacity in a turbulent market. When I have a lot of it, I have to make business decisions. When I have a little of it, I have to make staffing and operational decisions.

Q: You mentioned giving your team space to think. How do you protect that?

A: We will ask ourselves, what about this pivot. What about these 5 to 7 other strategies that we can deploy in this engagement. Our scopes are flexible because they have to be as an outsourced marketing team, and we have freedom and flexibility to do that.

If I do not give the team enough time to sit and think, they are not going to be able to deliver that. That is hard to quantify. That gray area of billable percentage.

We do reviews every 90 days, and they will ask, can you make sure the next quarter I have space to think.

Q: In a year where there is no margin for error, what do you lean on to make decisions

A: I have a conversation with my CFO quite a bit. He is always looking at margin. I think it is important. It is an important baseline.

What is your most profitable work. What do you think you and your team can lean into the most and be really proud of what you can produce. Where do you see it having a competitive edge in the market. One example of that for us is our branding work.

Q: You also talked a lot about foundations. Why does that matter so much right now
A: In most of our engagements, it does not make sense unless we start with that foundational piece.

Are you positioned right in the market? Because you cannot really afford to miss.

In this market with so much data, there is really not a lot of uncertainty with respect to return. Building that foundational layer is a key part of that. Then you get to know the business and each other so well that the subsequent activities and performance marketing comes from that.

When I say assertive strategy, it is bringing our experience to the strategy, who we are trying to target, bringing our point of view. That is what our clients are paying for. They want us to come in with our point of view, bringing our experience and energy.

Q: Let’s talk AI. What is your real take after living through it with a team
A: I really think I was looking for magic bullet platforms in 2025. Somebody brought one to me with highly trained marketing agencies, and I brought it to my team, and they said, Amy, that is what we are doing.

My big learning was that it is these micro interactions with AI, or AI features being built into multiple platforms that my team is using. That is creating efficiency and broadening the power of their work. It is expanding an idea set, not replacing the people.

Twelve months ago, there was slop work happening. A few prompts, copy-paste into a document, without realizing limitations. So, even helping them build project structure, helping them build instructions, turning off the model so it does not share our IP, that was a big one.

Your eye has to be on the ball, but not on it all the time. Keep looking and thinking and talking and asking, but be sensitive to your team.

Q: Any final thoughts heading into 2026
A: Finding balance in the capacity and the utilization, finding balance in the scale, controlled growth, figuring out how to ride these turbulent times going into 2026.

But I am super optimistic about this year. I find even-numbered years tend to be my better years than odd years, looking back on my life. Fingers crossed.

Watch the full recording here

Why Spreadsheets Keep Appearing in “Modern” Tech Stacks

By Parallax | January 21, 2026

If you have a modern tech stack but spreadsheets are still driving planning decisions, you are not alone. This shows up in agencies of every size, including the well-run ones.

Spreadsheets do not show up because anyone is careless. They show up because they create speed and flexibility, and they are great at answering questions that live between systems.

The problem is what happens next.

As work gets more chaotic, that spreadsheet layer becomes less forgiving. Plans drift. Assumptions harden. And leadership starts making commitments based on a file that cannot adapt fast enough when reality changes.

This post reframes spreadsheets as a signal, not a mistake. A signal that your stack has gaps in planning, tradeoffs, and foresight.

Quick takeaways

Spreadsheets are the universal adapter between systems that were never designed to speak.
They are strongest when used for one-time analysis and quick scenarios.
They get risky when they become the ongoing planning layer for staffing, forecasting, pricing, and growth decisions.
The fix is not another execution tool. The fix is a dedicated planning layer that can absorb change and keep assumptions honest.
You can diagnose the gaps without launching a massive internal project.

Definitions

Execution or Delivery tools
Tools that track work already in motion, tasks, owners, due dates, and day-to-day delivery.

Financial truth
Tools and reports that capture what happened, invoicing, costs, margin, and revenue reality.

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

Tradeoff
A decision that makes one thing possible by explicitly deprioritizing something else.

Volatility
The real-world stuff that changes the plan, scope expansion, client pauses, approvals slipping, rush work, and shifting priorities.

Spreadsheets are the universal adapter

Most stacks do two things very well.

Execution tools show what is happening.

Financial tools show what happened.

Both matter. But many leadership questions sit in the gap between them.

Examples leaders ask all the time

Can we take on new work without creating margin risk?
Do we have the right people for the likely demand, not just signed work?
What happens to utilization and profit if scope expands or timing slips?
Are we pricing deals based on real delivery capacity or assumptions?

That gap is where spreadsheets appear. They connect the dots when no system provides one trusted view.

📕 Check out the Resource Management Best Practices guide for meeting cadence and agenda templates that help you get these answers.

Why leadership planning keeps falling back to spreadsheets

Spreadsheets show up for consistent reasons. None of them are embarrassing.

1) Data lives in separate places

Pipeline lives in the CRM. Delivery lives in the project tool. Financial truth lives in accounting.

Leaders need one narrative across all three, and spreadsheets make that possible quickly.

2) Planning requires assumptions, not just facts

Execution and finance systems track commitments and outcomes. Planning is conditional.

Spreadsheets make it easy to model scenarios without heavy configuration.

3) Tradeoffs are hard to see across projects

Many tools can show project health one project at a time.

Fewer can show what happens when the same person gets pulled across multiple deadlines with competing urgency.

Spreadsheets can create a cross-project view, even if it requires manual upkeep.

4) The business changes faster than systems can be adjusted

Agency models evolve fast. Spreadsheets adapt instantly.

The risk is not the spreadsheet. The risk is false confidence under volatility

When spreadsheets are used for occasional analysis, they are a strength.

Fragility shows up when spreadsheets become the planning layer while the environment gets more volatile.

Volatility often looks like

Scope expansion after kickoff
Client pauses and restarts
Rush work reshuffling priorities
Approvals slipping and compressing timelines

In that environment, spreadsheet planning gets tested.

Risk 1) Plans drift out of date faster than decisions slow down

A spreadsheet is a snapshot. In a world of constant change, snapshots go stale quickly, while leadership decisions still occur weekly or daily.

Risk 2) Growth becomes more stressful than it needs to be

This rarely creates one visible failure. Instead, it produces margin drift, conservative pricing, delivery strain, and growth hesitation that only become obvious after decisions are locked in.

Risk 3) Planning becomes dependent on heroic effort

Many agencies have a spreadsheet that quietly powers key decisions and depends on one or two people to keep it current.

That is not a team flaw. It is a structural dependency that concentrates planning risk on individuals rather than on systems.

The executive lens

A spreadsheet appearing in a modern stack is usually a signal that leaders are asking planning questions the stack does not answer cleanly.

So the useful question is not, why are we still using spreadsheets?

It’s this

What commitments are we making without a reliable forward-looking planning?

Once you ask that, the spreadsheet becomes a helpful indicator, not something to criticize.

A practical audit for leaders

If you want to act without creating a massive internal project, run this audit.

Step 1) List the leadership decisions you repeat

Focus on decisions, not reports.

Pick five to eight, like hiring timing, deal prioritization, when to reshape scope, and how to staff new work without harming delivery.

Step 2) Identify how each answer gets built

Look for patterns

Manual exports and copy-paste
Reconciling multiple sources of truth
Multiple versions of the same file
Heavy reliance on one person’s upkeep

These are not failures. They show where decision-making lacks system support.

Step 3) Name what repeatedly breaks the plan

Ask this

What happens that makes our plan wrong within days

Those answers define what your planning layer must absorb.

Step 4) Decide what stays in spreadsheets and what should graduate

Spreadsheets are great for one-time analysis and quick scenario modeling.

They get riskier when they drive ongoing capacity planning, cross-team staffing decisions, and recurring forecasting that leadership depends on.

If a spreadsheet drives recurring leadership decisions, it is functioning as a planning system, without the reliability, auditability, or adaptability a system requires.

Copy and paste template: Spreadsheet risk analysis

Decision
What decision is this spreadsheet helping us make?

Frequency
How often do we make that decision?

Inputs
What systems does the spreadsheet pull from?

Ownership
Who updates it, and how many people know how it works?

Volatility
What events make it wrong quickly?

Tradeoffs
What tradeoffs does this decision force when reality changes?

Risk level
Low if it is one time analysis
Medium if it is recurring, but low impact
High if it drives staffing, pricing, hiring, start dates, or margin commitments

Checklist: Signs the spreadsheet has become a planning system

The file is used weekly in leadership decisions
People delay decisions because the file is not current
People make decisions anyway because the file is not current
There are multiple versions of the file in circulation
One person carries the upkeep and the institutional knowledge
The file is used to decide staffing or start dates
The file is used to decide pricing or hiring

If you checked more than two, the risk is not inefficiency. The risk is committing the business based on plans that cannot adapt fast enough.

What a calmer stack looks like

Most agency stacks have execution covered and financial reporting covered.

What is often missing is a dedicated planning layer that connects demand, capacity, timing, and tradeoffs in a way leaders can trust week to week.

The goal is not to eliminate spreadsheets. They are useful.

The goal is to stop relying on spreadsheet glue for your highest impact decisions.

FAQ

Are spreadsheets always a problem?

No. They are excellent for quick analysis and scenario planning. The risk starts when they become the recurring engine for staffing, forecasting, pricing, and hiring.

Why do tools not solve this already?

Because most tools are designed around a single world, deals, work, time, billing. Leadership decisions live in the overlap.

What is the fastest way to reduce spreadsheet reliance?

Start with the audit. Identify the two or three spreadsheets that drive recurring leadership commitments, then decide what needs to graduate into a planning layer.

Do we need to replace our CRM or project tools?

Usually no. Most teams keep their execution tools and financial tools. They add a planning layer that connects the dots.

Next step

If you want a practical operating rhythm behind this idea, start with the Resource Management Best Practices guide.

That guide lays out the weekly cadence, forecasting approach, and decision routines that reduce reliance on spreadsheet planning for the decisions that matter most.

Brian LaMee
Recovering Professional Service Executive
Parallax

When good tools are used for the wrong job

By Parallax | January 12, 2026

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. When this happens, you see teams forcing a project tool to behave like a planning system. They might be forcing a CRM to answer delivery questions or trying to get a 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.

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.

Are you seeing this pattern with how you are using spreadsheet? Check out Why Spreadsheets Keep Showing Up in Tech Stacks

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, which is 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. Our Resource Management Best Practices Guide can help set and define that rhythm.

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

Questions 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

Q: Does this mean we chose the wrong tools?

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

Q: Why does this show up more as agencies grow?

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

Q: What is the fastest first move?

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

Q: Do we need to replace our CRM or project tool?

A: 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

Strategic Planning 2026: You’ve Got January. What About the Rest of the Year?

By Parallax | January 5, 2026

New year energy. Fresh plans. Clear priorities.

January is usually the month when agencies feel the most organized. 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. Most treat January planning as the plan and then reality returns and the plan breaks.

The real reason annual plans break in agencies

Agencies are too volatile for a fixed schedule. Clients pause and restart mid-engagement, scope expands after kickoff, approvals slip, and sales cycles stretch in ways that push March work into May. The plan breaks not because of poor planning, but because the conditions it was built on have already changed.

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 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 is where reality lives and 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.

Get the Guide

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 confidence bands. This distinction prevents the most common annual planning mistake of treating hoped-for work as if it were confirmed, and staffing against it accordingly.

The three confidence bands:

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 and you run out of senior design capacity, technical leadership, or a specific delivery role long before you run out of people in general.

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

Step 5: Decide what happens when reality changes

Before the year starts, write down your default responses to the disruptions that will inevitably occur.

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.

Get the Guide

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

Q: Do we really need a twelve-month plan?

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

Q: How far out should we forecast capacity?

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

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

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

Q: How do we keep sales and delivery aligned?

A: 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. The guide lays out the weekly cadence, forecasting approach, and decision routines that keep plans connected to reality beyond January.

Resource Management Best Practices

Callum Broaderick
Vice President
Parallax

Why I Joined Parallax: Helping Agencies Move from Reactive Delivery to Strategic Resourcing

By Parallax | November 24, 2025

Callum Broderick joins Parallax as VP of Sales with deep experience driving operational excellence across the agency world. His career spans hands-on process consulting, operational transformation and leading teams through major platform and process upgrades. That journey has given him a sharp view of the challenges agencies face today and the operational shifts required to stay competitive in a rapidly evolving industry.

After years of working inside agencies and consulting on workflow, project management, and full-service PSA (Professional Service Automation) and project accounting platforms, something became obvious. Most agencies still don’t have a clear picture of where their people and profit are really going. They make decisions with limited visibility, and by the time issues arise, it is already too late to influence them.

That’s a major reason I joined Parallax. I have seen and advised clients on these challenges for years. Agencies don’t just need better task tracking, they need a shift toward strategic resourcing and forecasting so they can protect margins, stay competitive and make smarter operational decisions that actually help with growth.

The Reality Inside Agencies Right Now

Pressure is up. Margins are thinner. Scopes change faster. Timelines keep getting tighter. Talent costs more. Hybrid and remote work make scheduling more complex.

And on top of all that, AI is reshaping how work is scoped, staffed, and delivered. A lot of the lower-effort execution work that once filled calendars is getting automated. That sounds great in theory, but it also widens the gap between simple task management and the bigger, strategic questions that really decide whether an agency is healthy.

Without clear visibility, leaders risk overstaffing in the wrong places, underutilizing high-value teams, and misreading the signals that drive financial performance.

Yet many agencies are still running the business out of spreadsheets, disconnected tools, or project systems that show what is happening today, not what is coming next. They rarely answer simple but important questions like:

Are our teams over capacity or under capacity
Can we take on new work without burning out our specialists
How will AI driven changes in next years workload affect our revenue forecast
What happens to the next quarter if more client demand moves toward automated execution

Traditional project tools are great for getting the work out the door. They were never really built to answer questions like whether you have enough of a certain skill set for the work that is coming, or whether you have enough of the right work coming to keep all those people busy and profitable.

From Task Juggling to Strategic Foresight

This is where Parallax feels different. The focus is not just on tracking tasks. It is on helping agencies plan their people and their pipeline with confidence.

Parallax gives agencies a forward-looking view of capacity, utilization, and financial performance, especially as AI removes manual effort and changes the shape of projects. Sales, delivery, operations, and finance can finally look at the same picture and use the same source of truth.

Leadership can see what is coming, where the risk is, and which levers to pull before a small issue turns into a profit problem. It turns reactive operations into intentional planning.

My Background And What I Kept Seeing

I have spent a lot of time with agencies, including deep experience with Deltek WorkBook. I saw how even strong platforms can run into limits when agencies are spread across multiple tools and only seeing the work in short-term snapshots. You start to see how easy it is for resourcing decisions to get made at the last minute, utilization to swing between too high and too low, delivery teams to feel like they are constantly firefighting, and financial forecasts to feel more like educated guesses than confident plans.

AI is amplifying all of this. As content production, research, QA, admin work, and other execution tasks get automated, the strategic side of resourcing becomes even more important. Agencies need to understand where the real value sits inside their teams, how client demand is shifting, and which skills they will need more of as work moves up the value chain. It is no longer enough to simply know what is in flight this week. Leaders need a clear view of how today’s choices affect revenue, capacity, and profitability in the months ahead.

Parallax goes straight at these questions. It gives agencies a clearer picture of future demand, a shared understanding of capacity and staffing needs, and a way to tie staffing decisions directly to revenue expectations. Instead of reacting to problems after they hit, teams can see issues earlier, adjust faster, and run the business with a lot more confidence.

The Future of Agency Operations

The agencies that win over the next decade will not be the ones that simply deliver the most tasks. They will be the ones who can see farther ahead and adjust faster. Strategic resourcing becomes a competitive advantage when AI takes over more of the repetitive work.

Better visibility. Clearer decisions. More intentional growth. A real understanding of where human talent creates the most value.

That is why I joined Parallax. The industry is shifting quickly, and agencies need to move past reactive project management if they want to protect margins and build strong, durable businesses.

If you are wrestling with resourcing challenges, unpredictable margins, or a foggy view of what is coming next, let us talk. This is exactly the kind of problem Parallax is here to solve.

Callum Broderick
VP of Sales, Parallax

4 Ways to Align Sales and Operations for Agency Growth

By Parallax | August 28, 2025

Running an agency today is a balancing act. Sales teams push for momentum, trying to move quickly enough to win the next deal. Operations teams focus on structure, making sure promises can actually be delivered without overloading people or blowing margins. Both sides are working hard, but without alignment, cracks start to show—missed details, clunky client handoffs, and frustrated clients.

When sales and operations teams are in sync, agencies deliver smoother projects, clients feel more confident, and growth doesn’t feel like chaos.

That’s exactly what we explored in a recent webinar with Grant Hultgren, VP of Customer Success at Parallax, and Jessica Andrews, VP of Marketing at Copper. Here are the four biggest takeaways from their conversation.

1. Simplify and Integrate Your Tech Stack

The more tools in your workflow, the more cracks for information to slip through. A CRM over here, a project management tool over there, a few stray spreadsheets. Every time a deal moves forward, someone has to manually copy details across systems. It’s inefficient, and it creates gaps that slow projects down.

Simplifying the tech stack reduces complexity and keeps everyone working from the same source of truth. As Jessica noted, siloed systems often translate into siloed teams. With Copper, sales and client management live on the same platform. With Parallax, that data connects directly to resource planning for agencies so leaders can forecast confidently and avoid resourcing surprises.

When systems are integrated, sales and ops stay aligned. Everyone works from the same source of truth, and teams can focus on delivering work instead of reconciling data.

2. Automate the Busywork

The more manual the process, the more friction between teams. Sales shouldn’t spend hours on data entry, and ops shouldn’t have to chase down details that should be readily available.

That’s where automation comes in. Automating repetitive tasks—like sending client intake forms, updating opportunity fields, or triggering project kickoff workflows—helps agencies move faster without losing accuracy.

Jessica put it simply: “Don’t bog down the sales team with manual work that’s not necessary. Automate everything you can, from sending intake forms to triggering project kickoffs. The more you automate, the smoother the client experience becomes.”

Grant added that automation also gives ops more reliable data to plan with: “No one wants to sit there and click all the boxes. Automate that, get client-facing, and drive value instead of admin work.”

3. Make the Sales-to-Ops Handoff Seamless

That magical moment when a client signs is more than a milestone—it’s a first impression of delivery. If the client handoff feels clunky, trust erodes fast.

Too often, agencies lose momentum between contract and kickoff. A few days of waiting can feel like weeks to an eager client, and the trust built during sales quickly erodes.

Jessica recalled her own experience: “I signed with an agency and then waited three days before I heard from a project manager. They ended up wowing me later, but those three days had me worried I made the wrong decision.”

A seamless handoff isn’t complicated—it just requires connection. When CRM and delivery systems share data, the introduction to the delivery team and the kickoff process can happen instantly. No awkward gaps. No lost confidence.

Grant put it: “That first impression in delivery can change the trajectory of a project. Even a short delay can ripple into missed schedules and lost confidence. Getting the handoff right matters more than people realize.”

4. Use Delivery as a Growth Engine

Strong project delivery doesn’t just fulfill the promise of a deal—it sets the stage for growth. When clients feel understood and supported, they’re more likely to expand engagements and trust you with bigger initiatives.

Grant explained it this way: “Delivery doesn’t end sales. It’s just the next stage of the relationship. When ops and account teams look for opportunities to add value, growth happens naturally.”

Jessica added: “The best agencies I’ve worked with didn’t push. They listened, understood me, and made thoughtful recommendations. That’s when upsells feel natural instead of forced.”

The Bottom Line

Agencies don’t have to accept the old tension between sales and ops as inevitable. By simplifying tools, embracing automation, creating seamless client handoffs, and treating delivery as a growth driver, you can align your teams and unlock smarter, more sustainable agency growth.

Curious to hear the full conversation between Grant and Jessica? Watch the recording.

How Agencies Are Actually Using AI (And What That Means for You)

By Parallax | July 22, 2025

How are agencies actually using AI right now? That’s what we explored in our recent webinar with Parallax VP of Customer Success, Grant Hultgren and Agency Business Consultant, Kurt Schmidt. This wasn’t about hype, it was about how agencies use AI to streamline daily operations, speed up planning, and reduce overhead.

No wild predictions. No “AI will do everything” declarations. Just a real-world conversation on what’s working, what’s not, and how to start small.

Missed it? Here’s the recap (plus the full recording if you’re more of a watch-and-take-notes type).

Real Agency AI Use Cases (That Aren’t Just Writing Blog Posts)

Kurt walked through examples from his work helping agencies adopt lightweight AI tools to solve targeted operational problems, not rebuild their entire tech stack.

Think:

speeding up the RFP process
automating internal onboarding
consolidating sprint planning notes

These weren’t full-blown AI implementations. They were quick wins that freed up capacity and improved team workflows.

“Most teams don’t need a full-scale AI transformation. They need a better way to get one or two hours back in their week.”
— Kurt Schmidt

This is where AI for agency operations really shines, reducing friction in the day-to-day, not replacing human work.

When Clients Ask About AI, They’re Also Asking About Budgets

One unexpected insight? When clients bring up AI, they’re often talking about efficiency, not innovation.

Are you using AI because it helps you work faster, smarter, and with fewer manual handoffs? And if so, are you passing that benefit along?

Agencies today need a clear point of view on AI and operations, not just for internal efficiency, but to explain how those choices impact client results and budgets.

Build or Buy? Doesn’t Matter, Just Be Strategic

You don’t have to be a developer to start testing AI in your agency. Grant and Kurt agreed: what matters is knowing what problem you’re solving, and being realistic about where AI fits into your workforce planning and overall business strategy.

Whether you’re experimenting with no-code tools or evaluating your current systems, the goal is the same:
Start small. Measure impact. Learn as you go.

For many, that means looking at where AI can reduce overhead, improve project planning accuracy, or support better capacity forecasting, without overhauling everything.

Worth a Watch

If you’re an operations lead, project manager, or agency exec trying to make smarter resourcing decisions with fewer headaches, this conversation is for you.

It’s practical. It’s relatable. And it’s focused on the real operational wins happening at modern agencies today.

Watch the Recording
(60 minutes. Bring coffee. Maybe a notepad.)

AI Is Killing Effort-Based Pricing—Here’s What Agencies Must Do Instead

By Parallax | July 3, 2025

Agency pricing models are under more pressure than ever. Not because clients are being difficult, but because the traditional effort-based model just doesn’t hold up anymore. Especially now that AI can accelerate agency work in ways we couldn’t have imagined.

In a recent conversation with Brian Kessman, founder of Lodestar Agency Consulting, we dug into how creative agencies can shift their pricing strategies to stay competitive and profitable without relying on outdated billing models.

Let’s walk through the key takeaways.

Why Effort-Based Pricing Fails in the Age of AI-Powered Agency Work

What Is Effort-Based Pricing?

Effort-based pricing (also called time-based or cost-plus pricing) is when agencies bill for hours worked or resources used. It’s long been the default for many service businesses, but in today’s fast-paced, AI-augmented world, it’s starting to break down.

Why Is AI Disrupting Traditional Agency Pricing Models?

Here’s the problem: if you charge based on time and effort, then faster delivery equals lower fees. But AI is accelerating how quickly creative work gets done. So clients aren’t wrong to expect price reductions. The logic makes sense.

The result? Agencies stuck in a time-based pricing model are essentially scaling busyness, not value.

“Agencies are burning out because they’re trying to grow by selling more hours. That’s not sustainable. AI is just accelerating the reckoning.”
– Brian Kessman

4 Agency Pricing Models That Work Better Than Effort-Based Billing

Brian outlined four pricing models that work better in today’s market:

Output-Based Pricing
Fixed fees tied to deliverables.
Outcome-Based Pricing
Fees tied to the business result.
Performance-Based Pricing
Compensation tied to KPIs (e.g. conversions, revenue impact).
Value-Based Pricing
The holy grail—pricing based on a percentage of value delivered, not just deliverables or inputs.

You don’t have to leap to value-based pricing overnight. But moving away from “cost-plus” thinking is step one.

4 Key Shifts for Evolving Your Agency Pricing Strategy

This isn’t just a pricing change. It’s a full value model transformation. Brian identified four critical shifts:

Philosophical Shift
Redefine what makes your firm valuable. Think insight, speed, and outcomes, not just execution.
Strategic Shift
Decide which problems you solve best and stop chasing every project.
Operational Shift
Build systems to deliver those solutions repeatably and reliably.
Measurement Shift
Shift your focus from hours logged to problems solved. Effectiveness is the new efficiency.

Start With One Problem, Not One Project

You don’t need to “burn the house down” to get started. Brian recommends:

Pick one high-value problem your agency solves well.
Build a repeatable solution around it.
Test it with a pilot offering.
Measure sales velocity and pricing power.

“It’s not about launching a new service—it’s about solving one problem better than anyone else.”
– Brian Kessman

The Future of Agency Pricing: Focused, Outcome-Driven, and Powered by AI

The future agency isn’t just using AI to go faster. It’s aligned around client outcomes, designed for repeatability, and focused on solving high-value problems.

Yes, pricing is changing. But what’s really shifting is how agencies define their value.

And those that make this shift now? They won’t just be future-ready. They’ll be the ones leading the future.

Want to dig deeper?

Want to see how this shift plays out in real life? Catch the full webinar with Brian Kessman – or let’s chat about how Parallax insights are helping agencies price smarter and scale with confidence.