Welcome to Q4, ladies. That magical time of year when the budget planning process transforms normally rational executives into gladiators fighting over every last dollar like it’s the final slice of pizza at a team lunch. As your resident Chief of Staff who has survived more budget cycles than I care to admit (my therapist says I shouldn’t keep count), I’m here to guide you through what I lovingly call the Annual Budget Hunger Games.
Spoiler alert: May the odds be ever in your favor. But unlike the actual Hunger Games, we’re armed with spreadsheets, business cases, and an alarming amount of coffee.
The Awakening: When Finance Sends “The Email”
You know the one. Subject line: “FY26 Budget Planning Timeline” with that little red exclamation mark that might as well be a warning siren. Your stomach drops. Your coffee suddenly tastes like anxiety. And somewhere in the building, a finance person is cackling while watching their inbox explode with panicked responses.
This email typically arrives in early October, which is corporate speak for “we need this by Thanksgiving, but we’re pretending you have time.” The email will contain words like “strategic alignment,” “zero-based budgeting,” and my personal favorite, “do more with less.” That last phrase is executive code for “we have no idea what you actually do, but we’re pretty sure you can do it cheaper.”
As Chief of Staff, you’re not just a participant in these games. Oh no. You’re somewhere between tribute, gamemaker, and reluctant therapist for every leader who suddenly realizes their brilliant ideas require actual money.
Round One: Gathering Your Arsenal (Also Known as Data Nobody Kept)
The first challenge is compiling everything your technology organization spent money on this year. This sounds straightforward until you realize that:
- Half your vendors changed names after mergers
- Someone definitely expensed that “team building” escape room as “collaboration software”
- Nobody can remember if that cloud migration project was under infrastructure, innovation, or “Steve’s Wild Ideas”
- The intern who set up your expense tracking system is now a senior developer at Google
You’ll spend approximately 47 hours tracking down receipt trails that lead to dead ends, Slack conversations that provide zero context, and purchase orders signed by people who no longer work at the company. This is the perfect time to question every career decision that led you to this moment.
Pro tip: Start a running document in January labeled “Stuff We Bought and Why We’re Not Idiots.” Future you will be moderately less angry.
Round Two: Translating Tech Speak into Executive Speak
Here’s where the real games begin. You need to justify why your CTO needs budget for things like “technical debt reduction” and “infrastructure modernization” to executives who think “the cloud” is just weather and “legacy systems” are old computers in the basement.
The translation guide:
What Tech Says: “We need to refactor our monolithic architecture into microservices” What Executives Hear: “We want to rebuild something that already works” What You Say: “We’re reducing system failures by 60% and cutting future development costs by millions”
What Tech Says: “Critical security patches and compliance requirements” What Executives Hear: “Boring IT stuff” What You Say: “Avoiding the headlines that end with ‘data breach’ and ‘lawsuit'”
What Tech Says: “Developer experience tooling” What Executives Hear: “Toys for engineers” What You Say: “Retaining talent that costs $200K to replace”
The key is connecting every technical initiative to either making money, saving money, or preventing the company from imploding. Bonus points if you can work in phrases like “competitive advantage” or “digital transformation.” Executives love digital transformation. Nobody knows exactly what it means, but everyone wants it.
Round Three: The Mythical “Real” Priorities
Now we enter the phase where every other department explains why their priorities are “real” and yours are just “keeping the lights on.”
Sales needs budget for a new CRM because the current one “doesn’t have good vibes.” Marketing needs budget for an AI tool that writes LinkedIn posts because apparently that’s worth $50K annually. HR needs budget for a cultural transformation consultant who will tell everyone to “bring their authentic selves to work” while providing zero actionable advice.
Meanwhile, your request to upgrade servers that are literally held together with hope and outdated warranties gets flagged as “nice to have.”
Here’s the truth bomb nobody wants to hear: Without technology, none of those “real” priorities happen. Sales can’t use their vibes-based CRM if the network is down. Marketing can’t AI-generate content if the systems crash. HR can’t transform culture if everyone is too busy manually processing things that should be automated.
Your job as Chief of Staff is to make this point without actually saying “nothing works without us, you ungrateful carbon-based life forms.”
Instead, try: “Let’s discuss the interdependencies between our strategic initiatives and the technical capabilities that enable them.” It’s the same message, but with 100% less chance of career-limiting consequences.
Round Four: The Art of Strategic Compromise (or Losing Gracefully)
Let’s be real. You’re not getting everything you asked for. Nobody does. The finance team started with a target number that’s 30% lower than last year’s budget, somehow expecting 50% more output. Math isn’t mathing, but here we are.
This is where you channel your inner negotiator. Some battles are worth fighting. Some are worth strategic retreats. And some are worth the political capital you’ll spend.
Hills to die on:
- Security and compliance (literally nothing good comes from data breaches)
- System stability for revenue-generating platforms
- Regulatory requirements (the law doesn’t care about your budget constraints)
Hills to tactically retreat from:
- That shiny new tool everyone saw at a conference
- The innovation project with “potential”
- Upgrades that can technically wait another year (even though they really shouldn’t)
Hills to fake die on so you can compromise later:
- Ask for 20% more than you need in discretionary categories
- Include some “reach” projects you can sacrifice dramatically
- Build in buffer for the inevitable “unforeseen circumstances” (which everyone foresees)
Document everything you’re cutting or delaying. When things inevitably break or slow down next year, you’ll need receipts showing you predicted this exact scenario. Being right later is cold comfort, but it’s better than being blamed for problems you warned about.
Round Five: Building Alliances (The Sponsor Games)
You cannot win budget battles alone. You need executive sponsors who will go to bat for technology priorities. The trick is making them care about your priorities as much as you do.
Find the CFO who’s tired of manual financial processes. Buddy up to the Chief Revenue Officer who’s losing deals because your sales tools are prehistoric. Make friends with the CEO’s Chief of Staff (if you’re not also serving that role) who needs better dashboards for board meetings.
These alliances require ongoing cultivation. You can’t just appear during budget season asking for favors. Throughout the year, you need to:
- Make their lives easier whenever possible
- Share credit for wins generously
- Provide air cover when things go sideways
- Remember their priorities (and their kids’ names if you’re into that level of relationship building)
When budget battles heat up, these sponsors become your tributes from other districts. They’ll argue for technology funding in rooms you can’t access. They’ll translate tech needs into language other executives understand. They’ll trade their support for your priorities in exchange for your support of theirs.
It’s corporate politics, and pretending it doesn’t exist won’t make you noble. It’ll just make you unemployed or chronically underfunded.
Round Six: The Final Presentation (Performance Art Meets Spreadsheets)
Budget presentation day arrives. You’ve prepared a 47-slide deck that you’ll be asked to condense to 10 slides during the meeting. You’ve rehearsed your key messages. You’ve practiced your “surprised but flexible” face for when they cut 25% of your request.
The actual presentation is part theater, part negotiation, part therapy session. Executives will ask questions they could have asked weeks ago. Someone will definitely suggest “exploring offshore options” as if that’s a new idea. Another person will propose “just using AI for that” without understanding what “that” actually involves.
Your role is to stay calm, stick to your key messages, and resist the urge to flip the table when someone suggests you “work smarter, not harder” as a budget solution. Working smarter is great. It doesn’t, however, make software licenses free or servers run on good intentions.
Come armed with:
- Three-year total cost of ownership (not just year one)
- Risk assessments for what breaks if you don’t get funding
- Competitor intelligence on their technology investments
- Customer impact statements (executives love customers)
- At least two “quick win” projects that show immediate value
And for the love of all that is holy, have backup slides. They will ask about the thing you almost cut from the deck. Murphy’s Law is undefeated.
The Aftermath: Living with the Results
Congratulations! You survived! You got 65% of what you asked for, which is honestly better than the 50% you expected. Now comes the fun part: delivering 100% of the expected outcomes with 65% of the requested resources.
Welcome to technology leadership.
Your immediate post-budget tasks:
- Thank everyone who supported you (even if their support was lukewarm)
- Communicate decisions to your team with appropriate context
- Revise project timelines based on actual budget
- Start the “we told you so” file for next year
- Book that therapy appointment you’ve been putting off
Remember to celebrate the wins. You got security funding. The infrastructure upgrade is happening. That critical system replacement is finally approved. Yes, you had to sacrifice the nice-to-haves and push some projects to next year, but you kept the lights on and moved important initiatives forward.
Lessons from the Arena: Wisdom for Next Year’s Games
After surviving multiple budget cycles, here’s what I wish someone had told me:
Start early. Like, January early. Build relationships, document needs, track metrics, and plant seeds for next year’s priorities throughout the current year.
Everything is negotiable except what isn’t. Know your absolute minimums and communicate them clearly. But be genuinely flexible on everything else.
Speak their language. Executives don’t care about technical elegance. They care about business outcomes. Connect every technology initiative to revenue, cost, risk, or customer experience.
Build credibility through delivery. The best way to get next year’s budget is to knock this year’s initiatives out of the park. Track and communicate wins religiously.
Accept that you’ll never get everything. Budget planning is about prioritization, not wish fulfillment. The sooner you accept this, the less painful the process becomes.
Take care of yourself. Budget season is marathon, not a sprint. Sleep occasionally. Eat something that isn’t vending machine coffee. Your stress management directly impacts your effectiveness.
The Victory Lap (or at Least Making it to December)
You made it through another budget cycle. You fought the good fight. You won some, lost some, and lived to fight another day. Your technology organization has funding for another year. The company will keep running. Systems will keep humming (mostly).
Is the budget perfect? Absolutely not. Did you get everything you needed? Of course not. But you got enough. And in the corporate Hunger Games of budget planning, enough is actually a victory.
Now take a day off, delete all those draft emails you wrote but wisely never sent, and maybe treat yourself to something nice. You’ve earned it.
And hey, only 11 months until we do this all again. But who’s counting?
May your business cases be strong, your executive sponsors be plentiful, and your budget be at least somewhat adequate. Until next year’s games, tributes.
