Your KPIs Are Fine. Your Agency Might Not Be.

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

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

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

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

Timesheets Without Resentment

How to get clean actuals without turning into the time police

Nobody grows up dreaming of a career in timesheets, but if you work at an agency, you already know the truth. When timesheets are messy, everything downstream gets messy too. In particular, invoicing and closing the monthly books becomes near impossible and a process fraught with frustration.

The need to “just complete timesheets” so your controller stops yelling at you yields completed timesheets that are wildly inaccurate. From here, it’s a quick and slippery slope to losing the value of timesheets as a primary feedback mechanism, to an administrative task that, when not done, ends with harsh reprimands. This is a practical guide to getting reliable time data without turning timesheets into a culture problem.

Quick takeaways

  • Timesheets fail when they feel like surveillance. They succeed when they feel like protection.
  • Two rules beat a ten-page policy: when time is due, and who owns follow-up.
  • Unless you’re a law firm, focus on 15-minute increments, not precise seconds.
  • A weekly rhythm is the secret: Friday close, Monday cleanup.
  • Managers own compliance. Finance supports. Ops uses the data. Leadership sets the expectation.
  • If you want people to care, connect timesheets to fewer fire drills, better planning, and smarter pricing.

Definitions

  • Actuals: The time that was actually spent, not what was planned.
  • Available hours: The hours a person can work in a period after subtracting time off and non-working time.
  • Billable hours: Hours tied to work the agency bills to a client.
  • Non-billable hours: Hours spent on work that is not billed to a client. For example, internal meetings, admin, training, presales, and internal projects.

The real job of a timesheet

A timesheet is not a moral scorecard it’s a receipt for reality.

It tells you three things you cannot run an agency without.

  • What work actually happened?
  • What did it really take to deliver the work?
  • What is it doing to next month’s capacity?

When timesheets are missing or late, you don’t just lose data. You lose the ability to plan off of the actual effort delivery is requiring. That’s when teams get double-booked, scope creep hides until it is too late, and everyone ends up reacting instead of steering.


Check out the Resource Management Best Practices guide for a list of message templates and meeting guides.

Get the Guide


The simple system that works

Step one: Set two rules

Most timesheet policies fail because they try to cover every scenario. People do not follow policies. People follow expectations.

  • Rule one: Pick a time that matches how your agency actually works. The end of the day on Friday is common. Some teams pick Friday at lunchtime to leave room for cleanup.
  • Rule two: If a timesheet is late, the manager is responsible for follow-up. Not finance. Not ops. Not the resource manager. The manager. This one shift changes the vibe. It stops timesheets from feeling like a finance nag and turns it into a leadership habit.

Step two: Run the weekly rhythm

Timesheets work best as a weekly loop, not a daily burden or a month-end panic.

  • Friday close
    • People submit their time by the deadline
    • Managers do a quick scan for obvious gaps
    • Anything missing gets flagged, not fought
  • Monday cleanup
    • Managers follow up with anyone who missed Friday
    • Corrections happen while memories still exist
    • Then the week starts clean

The goal is not perfection. The goal is a reliable habit, so your planning inputs are good enough to trust.

Step three: Use language that reduces resistance

A lot of timesheet resistance is not about the task. It’s about what people think the task means. If timesheets sound like oversight, they will be treated like a chore. If they sound like protection, they get done.

  • Message to the team: Timesheets are how we protect the schedule. If we don’t know where time went, we cannot forecast capacity, spot scope creep early, or plan. We end up reacting instead.
  • Message to leadership: We are not chasing time to micromanage anyone. We are doing it so we can plan realistically, price work confidently, and avoid putting people into constant fire drills.
  • Message to sales: Accurate actuals help us price projects based on what work really takes, not what we wish it took. It also helps us set start dates that will not implode delivery.

The gentle Friday nudge: Quick reminder to wrap up your time today. It keeps next week’s plan honest and saves future you from a mess.

Step four: Make accountability boring and clear

Timesheets go off the rails when ownership is unclear. Here is the model that keeps everyone sane.

  • Leadership: Sets the expectation that timesheets are part of how the agency stays healthy.
  • Managers: Own compliance for their team and do the follow up.
  • Operations and resourcing: Use the data to forecast and surface risks early.
  • Finance: Uses the data for billing and margin and helps define what good looks like.
  • Individuals: Submit time on schedule and ask questions when something is unclear.

Step five: Use a calm escalation path

You need an escalation path, even if you rarely use it. People relax when expectations are clear and consistent.

  • Step one: Same-day reminder on Friday.
  • Step two: The manager follows up on Monday morning.
  • Step three: If still missing by the end of Monday, the manager and ops align on what is blocked by the missing time. For example, forecasting review, billing review, and project health review.
  • Step four: If someone repeatedly misses, address it as a reliability habit, not a finance issue. This is a leadership conversation, not a spreadsheet fight.

Check out the Resource Management Best Practices guide for a list of message templates and meeting guides.

Get the Guide


Common objections and real answers

Objection: “I forgot what I worked on.”

  • Answer: That is exactly why Friday close and Monday cleanup exist. The longer you wait, the worse it gets. The fix is speed, not pressure.
  • ⚠️ Pro-tip: Timesheets that integrate with calendars or that can be informed by planned work significantly reduce this objection.

Objection: “It takes too long.”

  • Answer: It should take minutes, not an hour. If it takes an hour, your categories are too complex, or your tooling is fighting you. Simplify codes and stop asking for essays.
  • ⚠️ Pro-tip: Remember, we should not be accounting for every second of every working day.  Be as specific as possible without exceeding the 15-minute rule of filling out your timesheet.

Objection: “It feels like micromanagement.”

  • Answer: Make the purpose explicit. Timesheets protect planning, pricing, and sanity. If leaders treat them like surveillance, people resist. If leaders treat them like inputs, people comply.

Objection: “My work does not map cleanly to a project”

  • Answer: That is a taxonomy problem. Create a small set of standard buckets for internal work, presales, and investment time so people are not forced to guess.

Weekly checklist

Friday

  • Send a reminder early enough to act on
  • Team submits by the deadline
  • Managers scan for missing chunks
  • Anything missing gets flagged

Monday

  • Managers follow up on missing time
  • Corrections are submitted
  • Ops updates forecasts and flags risks based on the new actuals
  • Finance moves forward with billing and margin review as needed

Copy and paste message templates

Timesheet policy text for your internal doc

Timesheets are due every Friday by [time]. If you miss the deadline, your manager will follow up on Monday. The purpose is to keep our planning, pricing, and workload sustainable. Timesheets are not used for micromanagement. They are used to understand actual effort so we can forecast realistically and protect the team.

Friday reminder message

Quick reminder to wrap up your time by [time] today. This keeps next week’s plan honest and helps us avoid last-minute surprises.

Monday cleanup message from a manager

Hey, I did not see your time come through on Friday. Can you knock it out this morning so we can finalize planning and reporting for the week?


Check out the Resource Management Best Practices guide for a list of message templates and meeting guides.

Get the Guide


FAQ

Q: What is the best timesheet deadline for an agency?

A: Pick a consistent weekly deadline that matches your work rhythm. The best answer is the one you will enforce every week without exceptions becoming the norm.

Q: Should managers really own follow-up?

A: Yes. When finance owns it, it feels like policing. When managers own it, it becomes a reliability habit tied to how the team operates.

Q: How do we improve timesheet compliance fast?

A: Simplify the policy to two rules, create a Friday close and Monday cleanup rhythm, and have leaders consistently reinforce the purpose.

Q: Do timesheets matter if the work is fixed-fee or retainer-based?

A: Yes. Fixed fee still has a cost. Timesheets are how you learn what work really takes, so you can price the next one smarter.

Q: What if people hate timesheets no matter what?

A: They might. Your job is not to make timesheets fun. Your job is to make them predictable, quick, and clearly connected to fewer fire drills and better planning.


Next step

If you want the full system behind clean actuals, including forecasting cadence, resourcing decision meetings, and conflict resolution routines, start with Resource Management Best Practices for Agencies in Resources.

Grant Hultgren
Vice President
Parallax

The Resource Manager’s Handbook

A practical playbook for the people who keep work running

Let’s be honest. Most resource managers didn’t get a training manual. You learned by doing. Firefighting through bottlenecks, negotiating deadlines, managing the unmanageable, and somehow keeping it all moving.

This guide won’t fix every broken process or magically give you more hours in the week, but it will help you feel less reactive and more in control.

It’s a fast, no-fluff read packed with strategies for:

  • Planning ahead without overcommitting your team
  • Catching resource conflicts before they hit
  • Forecasting needs with more confidence (and less guesswork)
  • Balancing utilization without burning people out
  • Navigating the daily chaos of shifting priorities and surprise work

Whether you’re brand new or have been doing this for years, this guide was made to back you up with real tactics, relatable scenarios, and a tone that respects your time and your role.

The Questions Leaders Ask That No System Really Owns

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.

  1. Question
  2. Category
  3. Current source of truth
  4. What we do today to answer it
  5. Owner
  6. Cadence
  7. 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

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

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