Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Business Software 5 min read

SME IT budget planning: six approaches compared

Six IT budgeting models compared on effort, cost control, flexibility and board confidence, with a hybrid that works for a growing SME.

E
EncryptTechBD · 0 comments
Keyboard, notebook and laptop on a wooden desk
Photo: Wilfred Iven / StockSnap

An IT budget is not a list of renewals. It is a set of promises about what the business will run, change and risk over the next year. SMEs usually choose a planning model by habit, then discover too late that the model cannot answer the board's real question. The six approaches below are not ranked; each one buys a different kind of control.

The six models at a glance

ModelEffort to runCost controlFlexibilityData neededBest fit
IncrementalLowWeakLowLast year's spendSmall, stable estate
Percentage of revenueLowMediumMediumRevenue forecastA single board rule
Zero-basedHighStrongMediumActivity and cost detailA reset after drift
Activity-basedHighStrongMediumService catalogue and timeShared services and chargeback
Driver-based rollingMedium to highStrongHighDrivers and monthly actualsGrowth and seasonality
Benchmark-basedMediumMediumLowComparable peer dataChallenging a proposal

What the table does not show

Incremental is the least demanding model and the easiest to defend in a small business, but it preserves last year's mistakes and rewards whoever spent early. Percentage of revenue gives the board one transparent number, yet IT cost steps up with headcount, branches and regulation rather than with sales alone, so the percentage drifts out of date.

Zero-based budgeting exposes every cost and every justification, which is valuable after a year of uncontrolled spending. It also consumes management time and can cut the maintenance that prevents incidents. Activity-based budgeting makes cost per service visible, but only works when a service catalogue already exists and someone maintains the time data behind it.

Driver-based rolling forecasts connect spend to things the business can see, such as staff, sites, orders or students. They are the most useful model for a changing SME, provided the drivers are measured monthly rather than guessed once. Benchmark-based planning is a challenge tool, not a budget: peer data is rarely comparable enough to set your number, but it is good at exposing a proposal that looks unusual.

Consider a distributor opening a third branch and a small online channel. Last year's spend is a poor guide, because the branch changes headcount, connectivity, devices and support load before it changes revenue. A percentage-of-revenue rule would fund the branch only after sales rise, which may take months. A driver-based forecast using branch count, staff and order volume shows the step-up earlier, while a zero-based review tests whether each new line is genuinely needed. The combination is usually more informative than any single model.

Choose the model that fits your constraint

  • Choose incremental when the estate is stable and finance capacity is thin, but ring-fence security, backups and renewals before adding anything new.
  • Choose percentage of revenue when the board wants one rule it can explain publicly; review the percentage whenever headcount, sites or regulation change.
  • Choose zero-based when costs have drifted or a new owner needs a clean baseline; run it every few years, not every year.
  • Choose activity-based when shared services must charge back to departments and a service catalogue already exists.
  • Choose driver-based rolling when growth, seasonality or new branches make last year a poor guide.
  • Choose benchmark-based as a second opinion alongside another model, never as the only method.

A hybrid that stays readable

Most SMEs end up with a fixed baseline for run costs, a driver-based layer for volume-linked services and a zero-based review for anything new. Present it in three lines: run the business, change the business and protect the business. Run covers licences, hosting, support and the staff who operate them. Change covers projects and migrations. Protect covers security, backup, training and compliance. Every line needs an owner, a renewal date and a link to the service it funds.

Omissions that distort the number

  • Implementation, migration and data cleanup, not just the licence.
  • Security monitoring, incident response and the time to handle an alert.
  • Backup storage and the restore test that proves it works.
  • Training and the process change that makes a tool useful.
  • Hardware replacement, disposal and the cost of running old equipment.
  • Renewal price changes and currency movement on foreign licences.
  • Internal staff time spent administering tools nobody owns.

Add a contingency line and state what it is for. An unlabelled contingency is usually spent twice: once in the budget and again when the real cost appears.

Run the cycle in five steps

  1. Collect contracts, renewal dates and twelve months of actual spend.
  2. Classify every line as run, change or protect, with a named owner. A category owner is not the same as the person who can approve the spend.
  3. Agree the drivers and assumptions: staff, sites, orders, students and peak periods.
  4. Review new requests against the operating plan, not against who asked loudest.
  5. Publish a one-page budget, a quarterly variance report and the date of the next review.

Metrics the board can use

  • Budget variance by category, with the reason for each material gap.
  • Run versus change spend, so maintenance is not quietly sacrificed.
  • Cost per employee, site or transaction, using a consistent definition.
  • Share of contracts with an owner and a recorded renewal date.
  • Unplanned spend as a proportion of the approved budget.
  • Incidents traceable to deferred maintenance or expired licences.

Turning the budget into a managed plan

We help SMEs turn this budget into a maintained operating plan through Managed Technology & Cybersecurity, covering monitoring, maintenance, backup and renewal planning. Retainer options and their inclusions are listed on the pricing page. For the year-by-year view of the same decisions, read SME IT budgeting, year by year.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes