Tag: Budget Management

The COO needs a headcount plan that’s grounded in what the business actually needs to deliver its commitments. The CFO needs a headcount plan that’s tied to revenue assumptions and financial constraints. The CEO needs a headcount plan that reflects the company’s strategic priorities and growth ambitions.

These three perspectives are often in tension — which is exactly why most headcount plans satisfy none of them.

Start With Demand, Not Org Charts

The most common mistake in headcount planning is starting with the org chart — who do we have, what roles are open, what does the next tier of management look like? That’s supply-side thinking.

Start with demand: what work needs to be done to deliver the company’s strategy, and what skills and capacity does that work require? The gap between required capacity and current capacity defines the hiring need.

Connect Headcount to Deliverables

Every headcount request should be tied to specific deliverables: what will this person enable the company to do that it cannot do now? Generic headcount requests (“we need another engineer”) don’t get funded. Specific ones (“we need a senior backend engineer to deliver the enterprise API by Q3, which unlocks the $2M sales pipeline”) do.

The COO’s job is to ensure that every headcount request in the plan is connected to a specific deliverable and a specific strategic priority.

Model the Timing

Headcount has a long lead time. A senior engineering hire takes 3–4 months from approval to start date. Add ramp-up time — another 1–3 months before the person is fully productive — and a decision made in January might not generate capacity until Q3 or Q4.

Build this lag into the plan. Show not just when hires are planned, but when they’ll be productive — and how that productivity curve affects project delivery timelines.

Build in Scenarios

The CFO will want to know: what if revenue underperforms? What if we raise a round sooner than expected? Build two to three headcount scenarios tied to financial outcomes. Scenario A (base case): full headcount plan. Scenario B (conservative): 70% of headcount plan, priority roles only. Scenario C (accelerated): expanded headcount plan, funded by upside.

Having the scenarios pre-built means leadership can make fast decisions when conditions change, without having to go through a full replanning cycle.

Present It as an Investment, Not a Cost

The framing of headcount as “cost” is both accurate and limiting. The CEO and CFO also respond to “investment” framing when it’s connected to returns: “This hire cohort will cost $X and will enable us to deliver $Y in new revenue / $Z in efficiency savings / the A strategic initiative.”

The COO’s skill is connecting the people investment to the business outcome — making the headcount plan a strategy document, not just a staffing document.

Budget reporting is one of those functions that everyone does but few do well. Here are the five most common mistakes COOs make in budget reporting — and the fixes.

1. Reporting Actuals Without a Forecast

Reporting “we’ve spent $X against a budget of $Y” is retrospective and therefore actionable only if you’re already over budget. The more useful number is the forecast — what you expect to spend by year end. Always pair actuals with a forecast.

Fix: Add a “forecast to completion” column to every budget report. This is the number that drives decisions.

2. Too Much Detail at the Leadership Level

Leadership-level budget reports that contain every line item produce the same outcome as no report at all: nobody reads them carefully enough to act. Leaders need the exception view — what’s off track and by how much — not the full ledger.

Fix: Lead with the exceptions. Show the four or five biggest variances from plan, with brief explanations and recommended actions. Detailed breakdowns go in an appendix.

3. Lagging Data

Budget reports that are 30 days behind are management history, not management tools. By the time a March overspend appears in a report reviewed in May, the decisions that caused it were made in February.

Fix: Move to real-time or near-real-time budget dashboards for operational use. Reserve monthly reports for governance and compliance purposes.

4. Not Connecting Spend to Outcomes

“We spent $500K on the platform migration” means nothing without the context of what was delivered. Budget reports that track spend without connecting to deliverables and outcomes treat money as the end rather than the means.

Fix: For every major project or initiative in the budget report, include a one-line delivery status alongside the financial status.

5. Treating All Variances Equally

A 5% overspend on a critical strategic programme and a 5% overspend on office supplies are not the same problem. Budget reports that surface all variances with equal urgency cause decision fatigue — leaders either chase every variance or ignore them all.

Fix: Flag variances by materiality and strategic importance. A threshold-based alert system (e.g., flag variances over 10% on strategic projects, over 20% on operational costs) focuses attention appropriately.

They’re the moment when you have enough actual data to know whether the original plan was realistic — and enough time remaining in the year to do something about it if it wasn’t.

Here is a framework for running a mid-year review that produces real decisions, not just updated spreadsheets.

Before the Review: Prepare the Data

Gather three sets of numbers for each project and cost category:

1. Original budget: What was approved at the start of the year?
2. Actuals to date: What has actually been spent through the mid-year point?
3. Full-year forecast: Based on actual run rate and known future commitments, what do you expect to spend by year end?

The comparison between original budget and full-year forecast is the key number. Variance between actuals and budget at mid-year is expected — projects run at different rates. Variance between forecast and budget at year-end is what tells you whether you need to act.

The Four Quadrants

Categorise every project into one of four quadrants:

• On track: Forecast within 10% of budget, delivery on plan
• Over budget but on scope: Forecast exceeds budget, but scope is justified — requires either reallocation or budget amendment
• Under budget: Forecast below budget — may indicate slow delivery, scope reduction, or delayed hiring
• Off track: Forecast over budget AND delivery behind plan — highest priority for intervention

The Conversation for Each Quadrant

Each quadrant requires a different conversation. Over budget but on scope needs a funding decision. Under budget needs a delivery accountability conversation. Off track needs an intervention plan with a named owner and a clear decision point.

The mistake most organisations make is treating all variances as the same — requiring justification for every variance, regardless of whether it signals a real problem. The four-quadrant framework lets you focus intervention energy where it matters.

Reallocating Budget at Mid-Year

Mid-year reviews often surface opportunities for reallocation — underspend in one area that can fund a priority in another. Treat mid-year reallocation as a strategic decision, not just a financial one. Before moving budget, ask: why is there underspend? Is it because the work isn’t happening, or because it’s being done more efficiently? The answer matters.

It is, by a wide margin, the largest cost category. And yet in most organisations, people costs are managed at the departmental level in HR systems and payroll, completely disconnected from the project budgets and capacity plans where they actually matter.

This disconnect has real consequences.

The Attribution Problem

When a software engineer spends 60% of their time on one project and 40% on another, which project pays their salary? In most companies, the answer is: neither. The salary goes to “Engineering.” Both projects show no people cost in their budget. Both projects appear dramatically under-budget. And no one has a real view of what projects actually cost.

This isn’t just a reporting problem — it’s a decision-making problem. Without visibility into people cost attribution, you cannot:

• Compare the cost efficiency of different projects
• Make informed build-vs-buy decisions
• Understand the true ROI of initiatives
• Set realistic project budgets that include the team’s time

The Tracking Gap

The reason people costs aren’t tracked at the project level is usually that it’s hard. Actual salary data is sensitive. Allocation percentages change frequently. Calculating “the cost of an engineer’s time allocated to Project X this quarter” requires integrating capacity data, HR data, and project data — three systems that rarely talk to each other.

The pragmatic fix is to use a blended rate approach: establish a cost rate per role (e.g., “senior engineer = $X/day fully loaded”) and allocate to projects based on capacity allocation percentages. It’s not precise to the dollar, but it’s directionally accurate — which is what you need for operations decisions.

What You Unlock With People Cost Visibility

When people costs are attributed to projects, a set of powerful analyses become possible:

• True project cost: What did that feature actually cost us to build?
• Cost per team: What does it cost to run the platform team for a quarter?
• Scenario cost modelling: If we hire two senior engineers next quarter, how does that change the project’s financial profile?
• Make vs buy: Is it cheaper to build this in-house or contract it out?

None of these questions can be answered well without people cost attribution. With it, you have the foundation for genuinely data-driven resource and budget decisions.

Budget overruns are nearly universal in project-based organisations. Studies consistently show that more than half of significant projects exceed their initial budget — in some industries and project types, the number is closer to 80–90%. And yet budget overruns are often treated as isolated failures rather than systemic symptoms.

Root Cause 1: Optimistic Estimation

The most documented cause of budget overruns is optimistic estimation at the project inception stage. Teams consistently underestimate the time, complexity, and cost of novel work. This is not a character flaw — it’s a cognitive bias (the planning fallacy) that affects everyone.

The fix is reference-class forecasting: rather than estimating from scratch based on the project plan, look at how similar projects have performed historically. If similar projects consistently take 30% longer than estimated, build that into your baseline.

Root Cause 2: Scope Creep

Projects rarely fail because the original scope was mismanaged. They fail because scope expands — often legitimately — during execution. New requirements emerge. Customer feedback changes the product direction. Technical constraints force different solutions.

Scope changes without budget changes are silent overruns. Every approved scope change should come with an updated budget impact assessment. If the scope change can’t be funded within the existing budget, the question of what gets cut needs to be answered explicitly.

Root Cause 3: Late Visibility

By the time a budget overrun is visible in the financial reporting, it’s usually too late to prevent it. The decision that caused the overrun was made weeks or months ago. Late visibility is a measurement design problem — the reporting cadence and metric selection didn’t give leaders enough time to act.

The fix is earlier indicators: burn rate against plan (not just actuals against budget), commitment tracking, and weekly or biweekly budget signals rather than monthly reporting.

Root Cause 4: Diffuse Accountability

When nobody feels personally accountable for a budget, everyone makes spending decisions that seem individually reasonable and collectively catastrophic. “We only went 5% over on contractor spend” sounds fine — until five teams each go 5% over and the project is 25% over budget.

Clear ownership — a single named person who is accountable for the project budget and whose performance is partly evaluated on budget management — is the single most effective structural change you can make.

Here is a practical framework for managing project budgets in a way that gives you early warning on overruns, clear accountability for spend, and reliable data for financial reporting.

Step 1: Set Budgets at the Right Level of Granularity

Project-level budgets are necessary but not sufficient. A $500K project budget doesn’t tell you whether the engineering work is on track — it just tells you the total envelope. You need budgets broken down by cost category (people, software, external services, infrastructure) and ideally by team or workstream.

The right level of granularity is the level at which you can take action. If you can’t do anything with a budget number, it’s too aggregated.

Step 2: Track Commitments, Not Just Actuals

Most budget tracking focuses on actuals — what has been spent. This is a lagging indicator. By the time a budget overrun appears in the actuals, the damage is done.

Track commitments — approved expenditures that haven’t been invoiced yet. A contractor engagement signed but not yet billed is a commitment. Future salary costs for the team are commitments. The gap between your total budget and your total commitments is your true remaining capacity to spend.

Step 3: Allocate People Costs to Projects

For most tech companies, people costs are 60–75% of total project budget. But people costs are rarely tracked at the project level — they’re tracked by department in the P&L. This disconnect creates a systematic blind spot: projects appear under-budget because people costs aren’t attributed to them.

Fix this by running a simple internal transfer pricing model — assign a cost rate to each team (based on fully-loaded salary + overhead) and allocate to projects based on capacity allocation percentages. It doesn’t need to be accounting-perfect; it needs to be directionally accurate.

Step 4: Establish a Monthly Budget Review Cadence

Every project should have a monthly budget review: budget vs actuals vs forecast. The forecast — what you expect to spend by the project end date — is the critical number. It’s the one that tells you whether you need to intervene now or whether you’re on track.

Any project where the forecast exceeds the budget by more than 10% should trigger an exception conversation: what’s driving the variance, and what’s the decision?

Step 5: Create a Culture of Budget Accountability

Budget accountability requires that project leads see their budget data regularly and feel ownership over it. A budget managed exclusively by finance, reviewed only by the COO, creates no behavioural change at the project level.

Give project leads access to their budget dashboards. Include budget status in project reviews. Treat budget management as a core project management competency, not a finance function.