IT budget planning for a small business fits on one page, not in a spreadsheet

Most small business IT budgets are not budgets. They are a record of things that already broke, written down after the invoice arrived. The line item says “computer stuff” and nobody can say what it was for.

About this piece

  • Article
  • Managed IT
  • Written by Nicholas Backwell · Founder, Redsilicon
  • Updated 2026-08-24

A plan is different, and it is smaller than you think. One page, one row per thing you own, five columns. You can build the first draft yourself in an afternoon walking the building with a clipboard.

The short version

  • Every piece of equipment you own has a replacement year whether you have written it down or not.
  • The point of the page is not accuracy. It is turning surprises into scheduled purchases.
  • Five columns do the whole job: what it is, how old it is, when it gets replaced, roughly what that costs, and what stops working if it dies first.
  • The last column sets priority, and it is the one people leave out.

IT budget planning for a small business starts with what you already own

The reason IT spending feels random is that nobody has an inventory. Without a list, every purchase looks like a fresh shock instead of an item that was always coming.

Equipment does not fail randomly. Switches, firewalls, access points, recorders and computers all have a rough working life, and the vendor eventually stops issuing security updates whether the hardware still runs or not. Both of those are dates you can find out. Once they are on paper, the spending curve stops being a cliff.

The other benefit shows up at the bank. A three year replacement plan is a document a lender or an accountant will actually read, and it makes a capital request look like management rather than panic.

The one page

Copy this format. One row per item.

AssetAge nowReplacement yearCost bandWhat stops if it fails
Firewall at the front of the network6 yearsYear 1MediumInternet and remote access for the whole building
Switch in the main closet7 yearsYear 2MediumEverything wired: phones, printers, cameras, desktops
Wireless access points (6)8 yearsYear 1MediumWarehouse scanners, tablets, guest Wi-Fi
Server or shared storage5 yearsYear 3LargeFile access and the job software everyone uses
Computers (14)2 to 7 yearsRolling, 4 or 5 a yearSmall eachOne person, for a day or two
Camera recorder9 yearsYear 1MediumFootage, and you find out after the incident
Backup serviceRenews annuallyEvery yearSmallRecovery, silently, with no visible symptom
Cabling in the shop14 yearsAs neededLarge if re-runIntermittent faults nobody can trace

Those rows are a worked example of the format, not a quote. Fill your own cost band from your last invoice for that item, or from a real quote. Do not guess with a number you found online, because pricing for network and security equipment moves and the install labour is usually the bigger half.

Set your own brackets for the cost band and stick to them. Small, medium, large and needs financing works fine. Precision is not the goal. Knowing that Year 2 has two large items in it is the goal.

The five columns, and why each one earns its place

Asset. Name it the way your staff name it. “The switch in the closet by the lunchroom” is more useful than a model number nobody recognises. Put the model in brackets if you have it.

Age now. Purchase date if you have it, best guess if you do not. Check the sticker on the bottom, the warranty label, or the year you moved in.

Replacement year. Write the actual calendar year. Two things drive it: the point where hardware failure gets likely, and the point where the vendor stops issuing security updates. The second usually arrives first and is the one people miss, because the box still works perfectly.

Cost band. Rough is fine. What you are protecting against is a year where three large items land together, and a band shows you that coming.

What stops if it fails. This column sets the order. A computer failing costs one person a day. A firewall failing costs the whole building until a replacement is configured, which is not a same day job if nobody has the configuration backed up. Write the consequence in plain words and the priorities sort themselves.

How to fill it in without a technician

Walk the building. Open the network closet, look at the rack, count the access points on the ceiling, find the camera recorder. Photograph every label you see. That single walk gets you most of the asset column.

Then pull twelve months of bank and credit card statements and highlight every recurring technology charge. That finds the renewals you forgot: the backup subscription, the domain, the software seats, the monitoring contract. Renewals belong on the page too, because they are the part of the budget nobody reviews.

Last, search each model number with the words “end of support” and write down the date. Vendors publish these. It is tedious and it is the highest value hour in the exercise.

What this means for your building

Take a machine shop in Courtice, steel building, office at the front. The plan usually reveals the same pattern: the computers are fine and the infrastructure is ten years old.

The access points on the shop ceiling were mounted when the building had four staff and no tablets. The switch feeding them is older than the network it serves. Neither has failed, so neither has been discussed, while the newest and most visible item in the building is the boardroom TV.

Put those on one page and the argument changes. Nobody needs convincing that the shop Wi-Fi is a Year 1 item once the last column says “scanners stop and shipping goes back to paper”.

What to do about it

  1. Do the clipboard walk. One hour, one page, photograph every label.
  2. Pull the statements and add every recurring charge as its own row.
  3. Look up end of support dates for the network and security equipment first, then the computers.
  4. Fill the cost band from real invoices you already have. Leave a cell blank rather than guessing.
  5. Sort by the last column, not by age. Consequence beats calendar.
  6. Take the page to your accountant before year end and split it into what gets expensed and what gets financed.
  7. Bring an outside opinion in for the rows you cannot fill: whether the cabling supports what you want to do next, and what the replacement network equipment should be.

Steps one through six are yours. You do not need help with any of them, and doing them yourself is why the page ends up honest. Step seven is where an IT consulting session or your managed IT provider should fill the gaps in an hour, and if they cannot produce end of support dates for your own equipment, that tells you something separate.

Want this scoped for your site?

Tell us the building and what you’re trying to achieve. We’ll tell you what it takes, and whether you actually need it.

Before you call

How far out should the plan go?

Three years. Five is fiction for a small business and one year is just next year’s invoice. Redo it every year at budget time and roll the window forward.

Do I need software for this?

No. A single sheet of paper or one tab in a spreadsheet is the right size. The moment it becomes a system with fields, nobody updates it.

What if I cannot find the age of anything?

Guess high and mark it. An item you cannot date is usually older than you think, and marking the uncertainty is more honest than a fake purchase date.

Is there a point where I should not bother?

If you are under about eight people, fully cloud based, with no server, no cameras and no network equipment beyond what the ISP supplied, the page is four rows long and you can keep it in your head. Write it down anyway when you hire your ninth person.

\n
\n \n