You made the case for your roadmap, got the budget approved, and it felt like a win. Six months later someone asks how the initiative is actually going, and you don't have a clean answer. You know roughly what you spent, but not what it delivered, so when it's time to ask for next year's budget, you have nothing solid to point to.
Getting your roadmap funded and running that budget well are two different skills. The pitch gets you the money. What you do with it afterward is what gets you the next one.
Most People professionals put all their effort into the pitch and treat approval as the finish line. Once the budget is signed off, tracking becomes an afterthought, something to reconstruct at year-end if anyone happens to ask. That's backwards. The pitch is a single event; managing the money is what actually happens for the rest of the year.
Say you pitched a wellbeing initiative at a fixed cost, projected to cut absenteeism within two quarters. If nobody tracked actual spend against that forecast, or checked whether absenteeism actually moved, the honest answer at the next budget cycle is "I think it helped." That's not a story a finance leader, or whoever holds the budget conversation, finds persuasive twice, and in leaner environments where every line is already under pressure, they won't need to hear it twice to stop taking your numbers at face value.
Building a budget and running one are different jobs, and treating them as the same skill is where most People budgets go wrong. Building it is planning: deciding upfront where the money goes and why, before a dollar moves. Running it is discipline: watching what actually happens against that plan, and adjusting in real time as the year unfolds.
Most People teams do the planning carefully, once a year, under real pressure to get it right. Then the discipline drops away the moment the budget is approved, because nothing forces it to continue. That gap between the two is exactly where next year's credibility is won or lost.
When you're putting together the budget behind your roadmap, be specific about what each initiative on it costs and why. For every line, note the amount, the reasoning behind it, and what you expect it to deliver. That gives you something to check against later, instead of one total that just says "People."
Separate spend into two kinds: costs driven by overall company headcount that benefit the whole business, and costs that specifically support the People team itself. That split stops your budget from looking bloated when the real driver is company growth, not the size of your own team.
Sort every line into one of three categories, so when a cut is asked for, you already know what to protect first.
Once the budget is running, check actual spend against forecast regularly, not just at year-end. If an initiative is costing more than expected, or spending less than planned, treat that as information worth acting on, not a variance to explain away later.
Say your new hiring platform is under budget three months in. That's not automatically a saving to bank quietly. It might mean uptake has been slower than expected, and that's worth a closer look before you assume it's good news.
Look for objectives where your priorities overlap with another team's, and pool resources instead of paying for the whole thing alone. If something you need requires real cooperation from another team, make sure it shows up in their budget too, not only yours. This is easy to miss during planning, and worth deliberately checking for.
Say your roadmap includes a push to build manager capability, and the sales director is separately trying to fix how long it takes new reps to ramp up. That's one problem showing up in two budgets. Raise it directly, and there's a real chance sales funds part of the work, because it solves something they're already trying to solve.
Agreeing on shared spending principles with your finance leader, or whoever holds the budget conversation, before the planning cycle starts helps too. Fixed principles for things like learning and travel spend keep the experience consistent across teams and make each budget conversation faster.
Before committing serious money to a new People initiative, test a smaller version of it first. Confirm there's real demand and value, then use that evidence to justify the bigger spend. In a resource-constrained environment, this is one of the surest ways to avoid sinking money into something that quietly stalls before anyone notices.
Before rolling out a full engagement platform, run it with two teams for eight weeks. If nothing moves, you've avoided the bigger spend. If something does, you walk into the next budget conversation with real numbers, not a projection.
The pitch is a single event. Managing the money is what actually happens for the rest of the year.
Pick one line item from your roadmap's budget that you're currently running. Can you say right now what it's actually cost so far against what you planned, and what it's delivered? If not, that's the first thing to fix, today, not at year-end.
The Commercial Ally gets you credibility in the room: reading the business, building the roadmap, defending and running the budget behind it. It doesn't tell you what to do when a senior leader asks you to do something you think is wrong, when a manager is quietly avoiding a hard conversation, or when you have to make a real People decision without enough data to be sure. That's harder terrain, and it's what the rest of POP Academy is built around.