Where the money actually goes in a mid-market Hong Kong IT budget.

Bottom line first: the 40% did not come from one clever decision. It came from re-reading commitments that had been renewing themselves for years. Nothing was being stolen. It was being renewed.

A mid-market IT budget here — call it 50 to 300 staff — is usually five or six lines. People. Licences and subscriptions. Maintenance and support contracts. Connectivity. Hardware. Projects. The waste is almost never spread evenly across them.

The lines it actually comes from

Licences nobody uses. Seats bought for people who have left. Two products doing the same job because different managers bought them in different years. A premium tier renewed annually when nobody has used the premium features since the person who wanted them moved on. This is the first place I look, because it is pure saving — cancelling an unused licence changes nothing about how the business runs.

Maintenance contracts renewed by habit. Support agreements carry an annual uplift, typically 5 to 8%, and compound quietly. Ten years in, you can be paying serious money to support hardware that would cost less than one year's contract to replace outright. Nobody re-reads these contracts because renewal arrives as an invoice rather than a decision.

Connectivity from another era. Leased lines and circuits specified when bandwidth was scarce and expensive, still billing at the old rate. The market moved. The contract did not.

Hardware replaced on a cycle rather than on condition. A refresh cycle is a vendor's idea of a schedule. Servers and desktops tell you when they need replacing if you monitor them. Some kit genuinely needs a short cycle. Most of it does not.

Projects that exist because somebody proposed them. The hardest line to challenge, because every project has a sponsor. The question that works is not is this a good idea but what stops working if we do not do it. A surprising share of the answer is nothing.

How you take the money out without breaking anything

The order matters more than the ambition. Measure first, cancel second — assumption is how things break. Every change out of hours, one change at a time, so any problem has one possible cause. That discipline is why the business never lost a working hour while the budget came down.

And some lines you do not touch. Backups. Security basics. The one person who understands the legacy system. A budget cut that removes any of those has not saved money, it has borrowed it — at a rate you will not enjoy.

The honest bit

A reduction of this size needs the owner in the room, because half of it is cancelling things somebody once championed. It is also not available from an adviser whose income depends on the vendors staying in place. Independence is not a slogan here, it is the mechanism.

And 40% was one business, over a sustained engagement, with authority to act. Your number might be 15%. On a mid-market budget that is still real money, every year, for work that is done once.

The test

Pull the last twelve months of IT invoices — there are usually fewer than forty — and ask three questions of each. What is this for. Who uses it. What happens if it stops. If you cannot answer all three for more than a quarter of them, the finding is not that your IT team is careless. It is that nobody has been paid to ask.

---

Adam Bell runs Innov8 in Hong Kong. He has run IT budgets as Interim CIO, and reviews them for owners who suspect the number should be smaller — scoped, priced and agreed in writing before any work starts.