IT Budget Planning for NZ Businesses

This guide shows how IT budget planning builds that plan and keeps it current. If you are already partway through the financial year, use actual costs to date and forecast the remaining months.

It is written for New Zealand business owners and managers who need a technology budget they can explain to an accountant, a board or a business partner. It covers what to spend, how to structure the budget, how to cost changes during the year, how to plan payment timing, how much reserve to hold and how to track actual costs against the plan. The steps work whether the budget is prepared by an internal team, an accountant or an IT provider.

How much should a business spend on IT?

There is no single percentage of revenue that tells you what your business should spend on IT. Start with the cost of running your current systems, then add known renewals, planned replacements and approved projects. Include the cost of supporting any growth, and agree a reserve for uncertainty. A benchmark is useful only when it compares businesses and costs similar to yours.

A revenue percentage says nothing about whether your devices need replacing this year, whether a major licence renewal is due or whether a planned project is ready to start. IT budget planning built from those inputs gives you a figure you can explain line by line, rather than one you have to defend against an average.

Build your IT budget from these six categories

Six categories give IT budget planning a clear structure. They are a way to organise costs, not a prescribed share of the total, because the right balance depends on what your business already has and what it plans to change.

For each line in your IT budget planning, record supplier, category, quantity and rate, months, payment dates, annual forecast, cost source and date, and owner. Mark committed or proposed and state the GST basis. Use invoices, contracts or quotes where available, and label estimates and assumptions.

Record annual fees and one-off payments on their own basis. Check cancellation terms, because monthly billing does not necessarily mean a monthly commitment.

Count each cost once

In IT budget planning, give each cost one place. Security included in a managed support agreement should not appear again as a separate bill, and hardware bought for a project should not be counted under both hardware and projects. If you need to see total project or security spend, use tags as another view of the same costs, not another amount to add.

• Backups and recovery. Include backup services and restore testing explicitly, such as Microsoft 365 backup, unless they are already part of another agreement.
• Internal costs. Decide whether internal IT staff time is in the budget, and state whether the budget covers all technology costs or only external supplier spend.
• Change costs. Include training, setup, migration and the period when old and new subscriptions overlap.
• End-of-life work. Include disposal, secure data removal and lease-return costs where they apply.

Base replacement timing on condition, not age

A device’s age alone does not tell you when to replace it. Base replacement timing on condition, business needs, support status and warranty. Our guide to hardware lifecycle planning explains how to decide when to repair or replace, and gives the inputs IT budget planning needs for the hardware line.

How do you cost changes during the year?

Budget each change for the months it applies to. A common mistake in IT budget planning is to take the bill at year-end and multiply it by twelve, which overstates the cost of anything that grows during the year.

The example below shows the IT budget planning method without prices. It assumes a flexible monthly subscription charged per user, with 20 users from April to September and 25 from October to March, and no rate changes, setup fees or annual commitments.

Multiply the user-months by the monthly rate per user to get the annual forecast. Taking the year-end headcount of 25 and multiplying by 12 months gives 300 user-months, which overstates this year’s forecast by 30 user-months. Budget the months each change applies to, subject to the real contract’s terms, including any minimum commitment or notice period.

The same method applies to anything charged per user or per device, such as endpoint protection, backup licences or support priced per seat. Where a supplier charges annually in advance, record the payment month separately from the months the service covers.

How do you build an IT budget step by step?

IT budget planning works best as a short sequence that moves from what you already pay to what needs approval.

How do you plan cash timing?

An annual total can be affordable while individual months are not, and IT budget planning should show both. Annual renewals, deposits and staged project payments can create peaks, so build a monthly payment view alongside the annual cost plan. Business.govt.nz describes a cash flow forecast as an estimate of the money coming in and going out of a business over a future period, and the IT payment view feeds into that wider forecast.

Recurring and one-off payments are not the same as opex and capex

Recurring versus one-off payments are useful planning fields, but they are not the same as operating versus capital expenditure. A project can contain both, and paying monthly does not settle how a lease is accounted for. Ask your accountant to classify expenditure and confirm GST treatment. Inland Revenue’s guidance on types of business expenses is a starting point for those conversations.

In IT budget planning, rather than preferring one payment model in every case, compare the total commitment, flexibility and cash needs of each option. That applies equally to computer leasing and to subscriptions. Use a consistent GST basis throughout the IT budget, and allow for actual GST cash movements in the wider business forecast.

How much reserve should an IT budget include?

IT budget planning needs a reserve agreed on how uncertain your estimates are, which systems the business depends on and what funding is available to respond to a problem. There is no single figure that suits every business. If you use a percentage, say whether it is added to the base budget or included in the final total.

Known renewals and scheduled replacements belong in the base budget, not the reserve. A reserve will not necessarily cover a major incident and does not replace a response plan, so pair it with an incident response plan. Record what the reserve is for and who can release it, so it is not used for routine overspends that should be approved separately. What IT budget planning gives you is clearer visibility of commitments and earlier decisions, not freedom from unexpected costs.

When should you start IT budget planning?

Start before the financial year begins, leaving time for quotes, approvals and notice periods. Inland Revenue’s guidance on balance dates explains that the standard balance date is 31 March, but some businesses use another date, so confirm yours with your accountant.

If you have just closed off the year, our EOFY IT checklist covers the stocktake of assets, licences and contracts that feeds straight into IT budget planning. Contract notice periods can close weeks before a renewal, so a budget review that starts late may miss the chance to change a supplier or a plan.

What should be ready before you start?

IT budget planning moves faster when the inputs are gathered first.

• Contracts and renewal dates. Support, software, connectivity and phone agreements, with notice periods.
• Last year’s actual costs. Invoices or accounts showing what was spent, by supplier.
• Headcount plans. Expected starters, leavers and changes in roles that affect licences and devices.
• Device list. Devices with their condition, support status and warranty.
• Roadmap projects. Projects due this year, with any quotes already received.

What goes wrong in IT budget planning?

The problems that undermine IT budget planning are predictable, which means they can be checked for before the budget is approved.

• Last year plus a margin. Adding a percentage to last year’s total carries forward costs that have ended and misses ones that are new.
• Missed annual payments. Annual renewals and price changes get left out when the budget is built from monthly bills.
• Double counting. Security or backup costs are added separately when they are already inside another agreement.
• Year-end bill multiplied by twelve. Growth during the year is budgeted as if it applied from the first month.
• Missing change costs. Setup, training, migration and overlapping subscriptions are left out of project lines.
• A budget that goes stale. Without monthly comparison, overspending only appears at year-end.

A short review of these points before approval makes IT budget planning more reliable with little extra work.

How does IT budget planning relate to the roadmap?

An IT budget answers how much the business will spend this year and where the money goes. An IT roadmap sets the order of technology work over a longer period, and IT strategy sets the direction. The roadmap shows which projects are due this year, and IT budget planning costs them alongside the running costs.

When a project is deferred, move both its costs and its ongoing running costs out of the budget, so the forecast reflects the work that will actually happen.

IT budget planning support from Exodesk

Exodesk can help with IT budget planning, from current commitments and renewals to replacements and projects. Our IT consulting work covers scoped budget preparation, and our vCIO services include ongoing reviews where that is part of the agreed scope. Where support is provided through managed IT services, a fixed fee makes the included scope predictable, so the budget still needs lines for anything outside it. If you need a starting picture of your systems, an IT assessment can provide one.

Exodesk has supported New Zealand businesses since 1989. Today, our Christchurch and Dunedin teams support businesses nationwide.

Contact us or call 0800 396 337 to talk through your IT budget.