IT budgeting in mid-sized Indian companies is frequently done by taking last year's spend and adding a percentage. It produces a number that is approximately right and is wrong in the specific places that matter, because IT cost does not grow smoothly — it steps, when a licence tier is crossed, when a contract renews at a new rate, when hardware reaches end of support, or when headcount pushes you into a different pricing band.
Build it from a register rather than from history. Every software subscription with its renewal date, current price and user count. Every hardware asset with its age and warranty expiry. Every service contract with its notice period. Every recurring cloud or hosting cost. Most companies doing this for the first time find subscriptions nobody uses, a contract that auto-renewed twice, and at least one service still being paid for after the project it supported ended.
Then look ahead for the steps rather than the trend. Which licences move to a higher tier if headcount grows as planned. Which machines pass the age at which failure becomes likely and support ends. Which contracts renew this year and what the increase clause allows. Which capacity — storage, bandwidth, seats — is on a trajectory to cross a threshold. Those are the four places where an IT budget goes wrong, and each is knowable in advance.
Split the budget into three lines that behave differently, because presenting one number invites a uniform cut that damages the wrong things. Keeping the lights on: licences, hosting, support, hardware replacement — largely non-discretionary, and cutting it produces failures later. Risk reduction: security, backup, compliance work — discretionary in the short term and expensive to defer. And change: new systems and projects, which is where genuine choice exists.
Include the costs that always arrive and are never budgeted. Hardware failure and replacement outside the planned refresh. An incident that needs external help. A compliance requirement arriving mid-year, which in India happens with some regularity. A contingency of a stated percentage against these is more honest than a budget with none, which simply means the overrun is discovered rather than planned.
Then measure against it monthly rather than annually, because the value of the exercise is not the forecast — it is knowing early when something has changed. A subscription that grew by forty per cent, a cloud bill drifting upward, a renewal approaching with no decision made. Companies that review monthly negotiate from a position of information; companies that review at year end discover what happened and pay it.
