The budget the CFO can defend. Is the budget that survives.

Inside an SMB, the IT budget gets read by people who don't share the IT team's vocabulary. The CFO is looking for a story they can defend to the rest of the executive team and, in the businesses we work with, often to a board or a private-equity sponsor on the other side. They need the numbers to tie back to the strategy, the strategy to tie back to the business outcome, and the whole thing to read as something an adult thought about — not a list of line items inherited from last year.

When the IT team can tell that story themselves, the budget gets approved and the conversation moves on. When they can't, the CFO writes the story for them, and the story they write is usually the one that ends with a haircut. Most of the budget conversations we get pulled into start with the second version — an IT leader who knows the work matters and is struggling to put language around why.

Our job is to put that language around it. Not by inflating the numbers or dressing them up, but by mapping each one to the business outcome it's protecting or enabling. The budget that survives is the one written in the CFO's vocabulary, not the IT team's.

The most common piece of work we do early in a budget engagement is translation — taking the IT organisation's view of the spend and reshaping it into the view the CFO needs to operate from. The numbers don't change. The framing does, and the framing is what determines whether the conversation turns into a haircut or an approval.

That translation runs in both directions. The CFO needs the IT spend mapped to outcomes the business cares about — revenue protection, customer experience, audit posture, M&A readiness — not to the technology categories the IT team naturally thinks in. And the IT team needs the CFO's constraints translated back the other way — the cash flow shape this year, the capital plan the board has already approved, the covenants on the operating line, what counts as growth-funded versus run-rate.

When that translation is in place, the rest of the budget exercise gets easier. Reservations and savings plans become a cash-flow conversation instead of a tooling one. License rationalisation becomes a run-rate optimisation instead of a procurement project. Capex requests come with the opex consequence already attached. The CFO starts treating IT as a function that understands the business it's operating inside, and the dynamic of the budget cycle changes.

Budget work runs on either an annual rhythm or an optimisation rhythm. The annual rhythm follows the fiscal cycle. The optimisation rhythm follows the forcing function — a renewal, a surprise bill, a leadership ask. Underneath both, the arc of the work is the same four steps, in the same order, for the same reasons.

One — the questionnaire and the baseline. Short, async, completed by the business before we meet, paired with a pull of the actual data — current Azure consumption, M365 licence counts and assignments, on-prem maintenance contracts, the current-year IT P&L. Twenty minutes of structured questions plus a clean baseline of where the money is actually going. The current state is a fact the business already has. We pull it into a form the working session can operate from.

Two — the working session. Half day or full day, with the IT leader, the CFO or controller, and whoever owns the strategy the budget is supposed to be funding. We open with the baseline on the table — this is what you're spending, this is where it's going, this is what surprised us in the data. Then we move to the harder work — mapping each line to the business outcome it protects, naming the line items that don't have a sentence written about them, and deciding which of those need a sentence and which need to come out.

Three — the build or the remediation plan. For the annual rhythm, a budget the IT leader can take into the committee, with the outcome-mapped narrative that lets them defend each line. For the optimisation rhythm, a sequenced plan for stopping the bleed — reservations sized against real usage, licences right-sized ahead of the renewal, tagging and policy turned on so the next quarter's drift is visible before it becomes a surprise. Realistic dates, named owners, no theatre.

Four — the rhythm. Whichever shape the engagement took, the last move is the same. A monthly or quarterly check-in that closes the loop between the budget that was built and the spend that actually landed. A short, structured review that catches drift early, when it's a conversation and not yet an incident. This is where we usually stay on as the fractional voice the business doesn't want to hire full-time.

A budgeting engagement produces tangible things. A current-state baseline of where the IT money is actually going. A proposed budget that ties each line to the business outcome it protects. A reservation and licensing posture matched against real usage. Tagging and reporting turned on so the next quarter isn't a guessing game. A rhythm with the CFO that keeps drift from becoming a surprise.

Those things matter. But the outcome the business actually hired us for is less visible. It's the shift in how the IT leader walks into the next budget conversation. Before, the meeting felt adversarial — the CFO probing for fat, the IT leader defending categories they couldn't quite articulate. After, the conversation moves at a different pace. Each number has a sentence behind it. Each line traces back to an outcome the business already agreed mattered. The CFO is comparing the ask to a story they trust, instead of looking for places to cut.

That is the whole deliverable. An IT budget that survives contact with the people who control the money — not because it was inflated or defended cleverly, but because it was built to be defensible from the first line. The capacity to walk into the budget meeting as the leader who knows the business, instead of the leader being asked to justify their existence.