A useful IT budget connects a business need to its complete cost and an accountable owner. Start with existing commitments, add the changes you can explain, and keep a separate view of when cash will leave the business.
The method below is for a small or midsize organization's annual planning. The example uses invented U.S. dollar amounts. It is a cash-planning exercise; your finance team determines capitalization, depreciation, tax and financial-reporting treatment.
Build a baseline from commitments and usage
Gather twelve months of invoices, subscriptions, contracts, device records and support costs. Assign every item to an owner and a service: collaboration, customer systems, connectivity, security, data storage or another business function. Record quantity, unit rate, billing interval, renewal date and cancellation notice period.
Distinguish the forecast, your best current estimate, from the budget, the approved funding. The FinOps Foundation's forecasting guidance emphasizes historical spending, planned changes and timing; its budgeting guidance connects approved funding with ownership and variance management.
Check whether a purchase replaces an existing service or adds another bill. An annual contract remains a commitment even if its license count is unused. Treat an expected cancellation saving as provisional until the notice has been accepted and the final billing date is known.
Work through one complete annual plan
This fictional business has 50 staff and buys external IT support. All amounts are USD for one planning year, before taxes. The categories are mutually exclusive: the software line excludes security and backup, which appear separately. Internal staff time is outside this cash example and should be assessed separately when comparing projects.
Scroll sideways for all columns. Keyboard users can focus the table and use the arrow keys.
| Cost | Calculation | Annual USD |
|---|---|---|
| User subscriptions | 50 users × $18 × 12 months | 10,800 |
| Device replacements | 10 devices × $900 | 9,000 |
| Hosting and connectivity | $600 × 12 months | 7,200 |
| External IT support | $2,000 × 12 months | 24,000 |
| Security and backup | $400 × 12 months | 4,800 |
| Migration and training | One planned project | 6,000 |
| Baseline subtotal | Sum of the six cost lines | 61,800 |
| Reserve | 10% of baseline; illustrative choice | 6,180 |
| Funding envelope | Baseline plus reserve | 67,980 |
The reserve is available funding, not a prediction that every dollar will be spent. Choose its size from uncertainty, service criticality and your organization's approval process. A fixed percentage is convenient for this example, but a contract with known pricing and an experimental workload need different treatment.
Download the worked cost table and its instructions and scenario calculations. The CSV contains fixed example values; replace inputs and recalculate in your own planning tool.
Change the assumptions before changing the total
For a growth scenario, add ten users for the final six months: 10 × $18 × 6 = $1,080. Add $200 of monthly hosting for those six months, or $1,200, and five extra $900 devices, or $4,500. The increase is $6,780. The new subtotal is $68,580; the same illustrative 10% reserve is $6,858, giving $75,438 in funding.
That scenario assumes external support capacity and security pricing remain unchanged. Confirm those assumptions with the contracts; extra users may affect both. Write the growth trigger beside each line so a postponed hiring plan can be reflected without rebuilding the whole budget.
For a constrained scenario, identify the result of each deferral. Delaying a migration may avoid its initial cost while prolonging two subscriptions or unsupported hardware. Capture the revised service risk, ongoing bill and latest safe decision date. Necessary maintenance should have an explicit funding decision.
For a proposed automation project, estimate usable hours saved, who can actually redeploy them and what review work remains. An employee-hour estimate is an economic benefit; it becomes a cash saving only if a specific paid cost is reduced. AI services can add usage, evaluation, access-control and human-review costs to the plan.
Review cash timing and variance every month
Spread the approved plan across the months when bills fall due. A $12,000 annual invoice due in January creates a different cash requirement from $1,000 paid each month. Link the schedule to the business's cash forecast and working-capital plan.
At each review, retain the original budget, record actual spending and revise the remaining forecast. Explain changes as price, quantity, timing or scope. If a line budgeted at $600 costs $750, its $150 unfavorable variance is 25% of budget. Find the cause before assuming that the extra cost repeats for the rest of the year.
Give every exception an owner, action and date. Record whether reserve funding was released, an activity was deferred or a contract changed. A useful review ends with decisions and a revised year-end expectation, not simply a chart of last month's invoices.