Technology has a way of quietly draining a budget. One month everything feels under control, the next there is a failed laptop, a licence renewal nobody diarised and a subscription that has been running since 2022 for a tool nobody uses.
Getting on top of it is less about spending less and more about knowing what you are spending on. Here is the approach we take with clients.
Start with what you actually have
Three questions, and most businesses find money in the answers:
- What hardware and software does the team genuinely use every day?
- Are two tools doing the same job because different people chose differently?
- Are you still paying for subscriptions and user licences that belong to people who left?
That last one is remarkably common. Microsoft 365 licences in particular tend to accumulate, because removing a person from the payroll and removing them from the tenant are two different jobs.
Separate spending from investing
Both are real costs, but they behave differently. Spending keeps the lights on. Investing changes something: it removes a recurring problem, reduces a risk you can name, or lets the team do more without adding people. When budget is tight, protect the second category and question the first.
Give the budget a structure
Break it into categories you can actually track rather than one line called IT:
- Hardware, including a replacement cycle rather than replacement panics
- Software and licences, per user where that is how they are billed
- Support and managed services
- Security and backup
- Connectivity
- Projects, budgeted separately from running costs
Once it is split up, the question "why has IT gone up" has an answer instead of a shrug.
Find the waste, then stop creating more
Cancel what is unused, consolidate overlapping tools, renegotiate at renewal rather than letting things roll, and be honest about which expertise you need on the payroll and which you do not. A managed service exists partly to give you a senior view of this without a senior salary attached to it.
Budget for the things that have not happened yet
A failed laptop, a fibre outage, a security incident. None of these are unusual, and all of them are cheaper when there is a spare machine, a second line and a tested backup already in place. Keep a contingency and review the whole thing quarterly rather than annually.
Plan around what the business is doing
New hires, an office move, a shift to more remote working, a new site. These have IT costs attached and they are far cheaper when they appear in a budget than when they appear in a hurry.
Good IT budgeting is not about cutting costs wherever possible. It is about being able to say what every rand is doing, and being unsurprised in March by something you could have seen in January.