Two New Trends in Local Software Budgets

After talking with several local IT heads, we sketched this year's budget structures. The overall pool is stable, but three internal shifts are worth recording.

From projects to annual fees

Companies used to approve one-off purchases; now annual maintenance and iteration fees are acceptable. The upside is supplier incentive; the downside is a higher three-year total.

Some split budgets into build and run, roughly seventy-thirty, a saner ratio than previous years.

Paying for advice

A few years ago nobody paid for consulting. Now some clients ask for a two-month study producing process maps and a system plan.

The reason is practical: buying the wrong system is expensive, and a million-yuan shelf ornament hurts. A tenth of that to think clearly is worth it.

More small bets

With limited budgets, starting with one department or one business line and expanding after validation has become common.

That demands something new from vendors: deliver a smallest system that runs on its own, not a monolith that must go live whole.

The absolute budget says little; the structure says a lot. Firms that pay for planning and upkeep succeed noticeably more often.