Case study / Capital decisions and roadmap
When the budget showed purchases, not the business case
In a previous IT leadership role, I inherited an $8.5M one-year infrastructure capital proposal. The presentation specified what to purchase, but it did not establish what the business would need from the technology, what could be retained, or the total cost of supporting the environment after the purchases. Leadership had a procurement request without a dependable investment case.
I took responsibility for rebuilding the decision around business requirements, operating risk and a multi-year cost model. The resulting roadmap was endorsed by the CFO and became the basis for subsequent budget decisions.
The purchase request was missing its business requirements
The original proposal treated equipment age and technical capacity as sufficient reasons to replace the existing estate. There was no reliable consolidated inventory, agreed future-state requirement, or full comparison of alternatives. Hardware, software, licensing, depreciation, support contracts, disaster recovery and anticipated growth sat in separate records. Some of the largest future obligations were outside the one-year purchasing horizon.
The $8.5M request therefore was not a three-year spending baseline. Its price could not be compared directly with a complete three-year plan. Approving it would have committed substantial capital before leadership knew whether the proposed replacements were the right investments or what other costs followed.
Establish the requirement and cost before sequencing purchases
We rebuilt the hardware, software, contract and lifecycle inventory, then worked with business stakeholders to understand growth, recovery needs, reliability expectations and planned application direction. This gave engineers a defined target against which to test existing infrastructure and replacement options.
The resulting roadmap distinguished urgent exposure from later capabilities. It considered what to retain, replace, consolidate or defer, what depended on other decisions, and how the spending would affect ongoing operating costs. A 36 to 48 month sequence connected the technical changes to business requirements. The three-year total-cost model included capital commitments and the recurring costs of operating the future estate.
That work changed how infrastructure requests reached Finance. Capacity and replacement proposals had to show their business requirement, unit cost, dependencies and place in the sequence. A technically plausible purchase was no longer sufficient evidence for approving the investment.
Give Finance a plan it can use
The resulting investment model was approximately $12M over three years, compared with a prior three-year spending trajectory approximately $3M higher.
The CFO endorsed the roadmap, saying, "This is how all departments should run their budgets." Approved spending was redirected to fit the sequence, the model informed subsequent budget cycles, and the Architecture function later extended the approach across additional IT areas.
For an owner, CFO or Operating Partner, a capital budget is credible when it explains what capability or risk each investment changes, the dependencies that affect timing, and the full cost of the chosen path. Those decisions should be established before the purchasing schedule becomes the strategy.
Do you recognize this operating problem?
Start with the decision or result that is currently stuck.
