How to build a three-year IT plan for a small business

Why three years is the right horizon

Most office hardware lasts somewhere between three and five years, most software contracts renew annually or every few years, and most business plans struggle to see beyond about thirty-six months. A three-year window is long enough to catch every laptop, firewall and server that will need replacing, yet short enough that the assumptions stay believable. A one-year plan tends to become a shopping list, while a ten-year plan becomes a wish list nobody revisits.

The plan does not need to be long. Four to six pages, or a single well-built spreadsheet, is plenty for a business of ten to fifty people. What matters is that it exists, that the owners have read it, and that it is updated at least once a year. Keep it where the owners can find it, written in words a non-technical reader can follow.

Step one: write down where you are now

Start with an honest inventory. List every computer, phone, printer, server, network device and cloud subscription, with its age, who uses it and when its warranty or contract ends. Note the systems the business cannot trade without: accounting, practice or job management software, email, phones and the internet connection. Then record the known weak spots, such as the shared drive that keeps filling up, the old server under the reception desk, or the one staff member who knows how the payroll export works.

If you have an IT provider, ask them for this list rather than building it yourself. Their monitoring tools usually hold most of it already, and the gaps they cannot fill are themselves useful findings. Anything nobody can account for, such as a subscription with no known owner or a device that is not in any system, deserves a line of its own in the plan.

Step two: connect IT to what the business wants

An IT plan that ignores the business plan is just a maintenance schedule. Sit down with the owners and ask what the next three years look like. Are you hiring, opening another site, taking on larger clients who will ask about security, moving to a new building, or planning to sell? Each of those answers creates IT work. Growth from twelve to thirty staff means more licences, a bigger network and probably a different way of managing devices. Winning corporate or government work usually means written security policies and evidence that you follow them.

Write each business goal next to the IT change it implies. That pairing is what makes the plan persuasive when it is time to spend money, because every line can be traced back to something the owners already agreed they wanted. It also helps you say no. An IT project that does not support any stated goal is a candidate for postponing, however enthusiastic its champion is.

Step three: lay out the replacement calendar

Using the inventory, mark when each item is due for replacement or renewal and put it in the year it falls due. Spread laptop replacements across years where you can, so you are not replacing every machine in the same quarter. Flag anything that falls off vendor support, such as an operating system or firewall model that will stop receiving security updates, because those dates are fixed and unforgiving.

Add the projects that came out of step two, such as moving files off an old server, adding a second internet connection or rolling out a new practice management system. Give each project a rough quarter, a rough cost range and an owner inside the business, even if the actual work is done by someone outside.

Step four: put rough numbers against it

Each year in the plan should show three kinds of spending: running costs that recur every month, such as support, licences and internet; scheduled replacements; and projects. Use ranges rather than exact figures, because prices move and quotes come later. The point is to show the owners that year two is heavier than year one, for example, so they can decide whether to smooth it out or accept the bump.

Include a modest contingency for things nobody can predict, such as a failed server or an urgent security fix. A plan with no contingency gets abandoned the first time something unexpected happens, because the numbers immediately stop matching reality. Many small businesses hold back something in the order of ten percent of the planned spend, but the right amount depends on how old your equipment is and how much risk you carry.

Keeping the plan alive

Review the plan once a year, ideally a couple of months before your financial year starts so the numbers can feed the budget. Roll it forward: the old year two becomes year one, and you add a new year three. Mark what was done, what slipped and why. A quick quarterly check against the list is also worthwhile, especially if your IT provider runs regular reviews with you.

If you want a starting point, an independent health check of your current setup produces most of the inventory and risk list in one go, and Office IT can turn that into a first draft of the plan for the owners to shape. Whoever drafts it, the owners should mark it up, challenge the priorities and sign the final version, because a plan the decision makers never agreed to is easy to ignore when money gets tight.