Your first budget
You get a promotion in September and it’s your first time managing a budget.
The new boss sends you a spreadsheet with twenty vendor lines, a headcount sheet, and a note that asks for a “first pass of next year’s budget by Friday.” You’re not familiar with half of the vendors, so you spend some late nights figuring out what they are. Three tools haven’t had a login since March, two do basically the same thing, and there’s a contractor nobody can explain.
You cancel the dead software, consolidate the duplicates, and take $80k out of the plan. You request an additional implementation engineer. One head at ~$120k fully loaded should cut implementation time roughly in half and protect close to $300k of first-year revenue.
You submit a budget up only about 2% from last year, including the new hire, and feel like you treated the company’s money like it was your own.
But your CFO comes back from the budget approval meeting and says every department has to cut 10% out of their expenses. The implementation engineer has to come out.
A more experienced leader reduces their headcount ask from 6 to 4, but it’s not clear to you why they would even need 4.
You will always be asked to sharpen your pencil. Include some buffer.
By March, onboarding new customers is so slow that it’s coming up in every executive meeting. Two customers churn in their first quarter and your best people are spending half their week on escalations.
You make the request again but also have a backlog to clear urgently. The total, including consultants, is north of $400k.
It gets approved in two days.
Prevention gets negotiated, but fires get funded.
You made it through the year, but every month you’re reminded that you are over budget. So when the next budget cycle rolls around, you request one headcount per quarter, as well as a buffer for professional services. You’re not sure you’ll need it, but it’s optionality.
When the CFO asks for an 8% reduction, it’s easy.
During the year, you end up only needing one additional head and see a growing favorable variance in your monthly budget reviews all year long. Your boss starts describing you as a safe pair of hands.
After a rough quarter, a hiring freeze gets implemented. If only you had hired the people when you were authorized to.
Use it or lose it.
The student becomes the master
Fifteen years in, you run a division and a new manager on your team submits an investment request. There’s a clear ROI, it’s not a big ask, and the manager has been thorough.
You take her for coffee and explain how these things work. You tell her to ask for enough to negotiate. Anchor high with an alternative that’s much more expensive. Don’t volunteer savings early; you may need them later. Give yourself options.
She takes the advice and gets the full ask approved. Advice that once would have felt cynical now feels like good management.
You carry one of the largest budgets in the company and almost never miss a number. When corporate asks for 7%, you can find 7%. When the business needs to accelerate, you know how.
Your team trusts you because you protect them. Your CEO trusts you because you don’t surprise him. Finance trusts you because your forecast is usually right.
In your performance review, you are highlighted as an “excellent steward of resources.”
By every measure the company keeps, you are excellent at it.
You take the show on the road
Eventually, you leave for a bigger job.
Your new organization has a much larger budget. The first vendor file you open has more than 120 lines in it.
You ask your team to flag anything obvious, but there are bigger things to focus on. These contracts were approved by somebody for some reason, and the total spend is already in the run-rate. So you start with the existing base, make adjustments around the edges, add some room for the things you know may come up, and submit the plan.
A few large customers leave and suddenly every dollar matters. A RIF is on the table.
You go back into the vendor file. There are tools nobody uses. Overlapping subscriptions. Consultants whose original projects ended months ago. Collectively the savings are worth millions.
You find enough non-headcount savings to reduce the size of the RIF, but it’s still painful.
Now multiply you by every budget owner in the company.
Nobody approved a ten-year plan to accumulate duplicate software, protected headcount, stranded projects, stale vendors.
Decisions were reasonable when they were made, but then the actuals became next year’s baseline, and the baseline acquired a strange inertia. Removing something required more evidence than keeping it.
Managers know that savings volunteered today limit their optionality later in the year. That an unfilled headcount may disappear. That preventive investments are easy to defer and emergencies are easy to fund. That every first proposal will be negotiated.
Fifteen years earlier, you stayed up late figuring out what twenty vendors were for. Now it takes the prospect of layoffs to make 120 vendors worth the same scrutiny.
What have you seen actually break this cycle?