An IT budget becomes difficult to defend when it combines “keeping things running,” new projects, overdue replacements, and emergency remediation in one unprioritized total. Give each dollar a category and a reason.
Use four budget buckets
| Bucket | Includes | CFO question |
|---|---|---|
| Operate | Support, subscriptions, connectivity, monitoring, routine security | What is the stable run-rate? |
| Refresh | Hardware, software versions, network, backup and recovery lifecycle | What becomes risky or expensive if deferred? |
| Change | ERP, integrations, automation, acquisitions, plant or site changes | What must be true before this project starts? |
| Reduce exposure | Recovery tests, access controls, segmentation, incident readiness | Which investment reduces the largest business interruption risk? |
Feedback from finance leadersVisibility before invoices arrive matters. A good budget should show committed renewals, vendor terms, in-flight project spend, and replacement obligations before month-end reporting.
Questions to resolve before approval
- What is contractually committed in the next 12 and 24 months?
- Which assets or systems are past their supported life, and what business process depends on them?
- Is this project solving a proven business problem, or compensating for unclear ownership and poor process?
- Who will operate the result after implementation, and what is the recurring cost?
- What recovery or security assumption is the budget relying on, and when was it last tested?
A board-ready output
For every major line item, show the business dependency, owner, timing, total cost, recurring cost, deferral consequence, and validation evidence. That creates a decision record without requiring the board to evaluate technical tools.