2. Building the Budget
How to Stop Asking for Money and Start Requesting Capital Allocation
THE SCENARIO
It is October. Arjun needs to submit his IT budget for next year. He has never done this before. His instinct is to list everything he needs, add up the numbers, and send it to the CFO. The CFO sends it back with a single comment: 'Justify everything.' Arjun spends a week in meetings defending each line item. By the end, he has lost 30% of his budget and doesn't understand why certain things were cut and others weren't.
Why Most IT Budget Requests Get Rejected
The problem was not the numbers. The problem was the framing. Arjun submitted a list of expenses. The board needed to see a capital allocation strategy. There is a fundamental difference between those two things. An expense is something you spend money on. A capital allocation is a decision about where to deploy limited resources for maximum return.
To frame a budget like a capital allocation strategy, Arjun needed to understand two things: how to structure the budget (the methodology) and how to calculate the true cost of what he is asking for.
The Two Budgeting Methodologies — And When to Use Each
There is no universally correct way to build a budget. The right method depends on what phase the company is in and what question the board is trying to answer.
| Incremental Budgeting | Zero-Based Budgeting (ZBB) |
|---|---|
| What it is: Take last year's budget. Adjust by a percentage for inflation, headcount changes, or known cost increases. Best for: Stable, mature parts of your operation — keeping existing systems running, maintaining licences, routine DevOps. The honest weakness: It allows wasteful spending to compound year over year. Nobody questions a line item that's been there for five years. Use it when: You are managing your 'Keep the Lights On' (KTLO) budget — the cost of not breaking anything. | What it is: Every dollar starts at zero. Every single expense — even recurring ones — must be justified with a direct link to a business outcome. Best for: New initiatives, R&D projects, transformation programmes, or any time the company is under financial pressure. The honest weakness: It is time-intensive. You cannot ZBB everything without exhausting your team. Use it when: You are managing your Innovation or Growth budget — where every dollar must earn its place. |
The CTO Pro-Tip
Don't pick one methodology. Split your IT budget into two buckets. Use Incremental Budgeting for KTLO (the cost of keeping systems running) and Zero-Based Budgeting for Innovation (new projects, new capabilities). This gives the board exactly what they want to see: disciplined management of today's operations AND rigorous justification for tomorrow's investments.
Calculating True Costs: The Two Costing Frameworks
One of the most common mistakes in IT budgeting is underestimating the true cost of a project or service. A licence fee is not the cost of the software. It's just the starting point. The question is: how do you allocate costs to the things that actually consume them?
Activity-Based Costing (ABC): The 'GPU Hours' Model Activity-Based Costing says: trace costs to the specific activities that drive them. If your cloud spend is $500,000 a year, don't split it equally across departments. Ask: which activities are consuming the cloud? Then assign costs proportionally.
Imagine Arjun's company runs a data platform with three customer tiers: Free, Starter, and Enterprise. With ABC, Arjun can discover that Free-tier users consume 35% of total compute but generate zero direct revenue. They exist for growth/conversion purposes — but without ABC, this cost is invisible, buried inside a general 'Cloud Infrastructure' line item.
Why This Matters to the Board
When Arjun presents this analysis, he is not just reporting costs — he is making a pricing strategy argument. 'Our Free tier costs us $175,000 per year in compute. Our conversion rate from Free to Paid is 8%. If we cap Free-tier compute usage, we either reduce costs or increase conversion pressure. The choice is a business decision, not a technical one.'
That is the difference between a cost center and a strategic partner. The board can now make an informed decision. Before ABC, the cost was invisible.
Service-Based Costing (SBC): The 'All-In Cost' Model Service-Based Costing groups all costs — labour, infrastructure, tooling, overheads — into a single 'service' bucket. The goal is to know the total cost of delivering a specific service to an end user.
For Arjun's company, a service might be: 'Customer Onboarding,' 'Real-Time Analytics Dashboard,' or 'Security Operations.' SBC answers the question: 'What does it actually cost us, all-in, to deliver this service?' This is critical for two scenarios:
- Pricing decisions: If it costs you $8,000 per year to serve a Starter-tier customer, and you charge $6,000 — you are losing money on every customer at that tier, and you need to know that before you run a marketing campaign.
- Build vs. Buy decisions: If it costs $400,000 per year to run your own Security Operations Centre, and a managed service provider offers the same capability for $180,000 — the SBC calculation makes the decision obvious.
The Five Budget Mistakes That Destroy Credibility
When Arjun reviewed why certain line items were cut, he identified a pattern. These are the five mistakes that cause board-level budget rejections:
- Using outdated quotes. Submitting last year's vendor quote for a cloud service that has repriced. The CFO's analyst will find this in minutes. Get fresh quotes every budget cycle.
- Hiding security costs. Budgeting for features but not for the security controls to protect them. Every new system is also a new attack surface. If you don't budget for it, someone else will eventually pay for the breach.
- Ignoring the hidden costs of software. A licence fee is not the cost of software. Add: integration effort, training time, ongoing management, and the engineering hours to maintain it. The true cost is typically 2.5x to 3x the licence price.
- Not budgeting for talent retention. Technical talent is the most volatile cost in IT. Underestimating turnover — and the cost of recruiting, onboarding, and the productivity gap of a new hire — is a systematic budgeting error.
- Ignoring technical debt. Every shortcut taken in the past is a future liability. If you don't explicitly budget time and money to retire technical debt, you are deferring a cost that grows at compound interest.
How to Structure Budget Ownership
The way you assign ownership of budget lines shapes the behaviour of your entire team. There is no perfect structure — each has a different trade-off:
| Structure | Best For | Watch Out For |
|---|---|---|
| By IT Stack Layer | Technical efficiency, infrastructure governance | Teams optimise for tech, not business value |
| By Business Unit | Business alignment; each unit owns their IT spend | Shadow IT: departments buy their own tools |
| By Project | High-growth startups; every dollar tracked to output | Hard to manage at scale; many small buckets |
| By Portfolio (KTLO / Grow / Innovate) | Board-level visibility; strategic storytelling | Requires discipline to classify correctly |
"I need 20% more budget because everything is getting more expensive."
"I have structured our IT budget into two methodologies. For our KTLO spend — maintaining existing systems — I have used Incremental Budgeting with a 4% inflation adjustment. For our Innovation and Growth investments, I have applied Zero-Based Budgeting, with every dollar tied to a measurable business outcome. Using Service-Based Costing, I have identified that our Starter-tier delivery cost exceeds our Starter-tier pricing by 12% — and I am proposing a pricing adjustment rather than a budget increase."