Request a quote
Emergency SectorsCareers About us Blog Get in touch
Meeting room with a wall covered in yellow sticky notes and two colleagues at a long table

An IT strategy for SMEs on one page

An IT strategy for a small or mid-sized business does not need to be a forty-page report. Its job is smaller and harder: to record a few choices that follow from where the business is going, so you stop reopening the same arguments about laptops, the cloud and suppliers every year. That fits on one page, and this is what goes on it.

6 min read Written by the ITproposal team
Short answer

An IT strategy starts with three questions for the board, not with technology: what changes over the next two to three years, what must never stop, and what is in the way today.

The page holds a direction in one sentence, three to five choices, what you stop, the non-negotiables, a quarterly roadmap and a named owner for each choice.

A choice is only a choice if it rules something out. Keep the page alive with a short quarterly review, and rewrite it after an acquisition, an office move or when your IT person leaves.

Why an IT strategy fits on one page

Large organisations write an IT strategy because hundreds of people need to pull in the same direction. In an SME the problem is different: people do think things through, but every decision is taken on its own. A new laptop when one breaks, a new application when a department asks, a new supplier when the last one disappoints. Added up, that becomes an environment nobody would have chosen.

A one-page IT strategy fixes exactly that. It records which questions have already been answered, so the next decision is quicker and more consistent. What it is not: a project list, a budget or an architecture document. Those can refer to it, but they do not belong on it.

The test is simple: after reading one page, could a new managing director, a new IT manager or a new supplier explain why the IT looks the way it does and what will change in the next two years? Then it works.

Start with the business, not the technology

Most IT strategies that fail start with technology: cloud, AI, zero trust. Start instead with three questions for the leadership team, and write down the answers in their words.

  • What changes in the next two to three years? Growth or contraction, a second site, an acquisition, a new service, more hybrid working, a customer asking about information security, or regulation that reaches your sector.
  • What must never stop? Order processing, the tills, scheduling, email. This decides where you invest in continuity and where a day of downtime is survivable.
  • What is in the way today? The application nobody dares replace, the colleague who is the only one who knows the server, the login process everyone works around.

Only then do you ask the IT question: what does IT need to be able to do to make this possible? That is where the choices come from, not from what a supplier happens to be selling this year.

The baseline: what you have today

A strategy without a picture of the current situation is a wish list. You do not need a full audit, but you do need an honest overview of the main points:

  • Applications: which systems run the business, who supplies them, and where they run (on premises, hosted, SaaS).
  • Devices: how many, how old, and how many different models. An estate with five laptop models costs more to support than one with a single model.
  • Contracts: what ends when. A contract that renews in eight months is a moment to choose; otherwise it renews by itself.
  • Knowledge: who knows what, and what is written down. If part of the environment depends on one person, that is a risk that belongs in the strategy.
  • Security: the basics, not the detail. Is multi-factor authentication on, has the backup been restored in a test, are updates applied?

This overview does not go on the page. It is the material you derive the choices from, and the baseline you compare against in a year.

What goes on the page

Six blocks, in this order. Each one is a few lines; if you need more, write an appendix.

  • Direction, in one sentence. For example: “IT supports growth to three sites without adding IT staff.” Every choice is tested against this sentence.
  • Three to five choices. Principles you stick to: new applications as SaaS unless there is a reason not to; one standard device per role; day-to-day support outsourced, decisions kept in house.
  • What you stop. The on-premises server that goes off after the migration, the second backup product, the exceptions to the laptop policy.
  • Non-negotiables. What always applies, whatever the choice: security, data protection under UK GDPR, continuity, and what customers or your sector require. In the UK, the NCSC’s Cyber Essentials is a sensible floor for most SMEs.
  • A quarterly roadmap for twelve to twenty-four months. No more than a handful of lines per quarter, with the big steps and their order.
  • An owner for each choice. A name, not a department. Who makes sure the choice is followed, and who may approve an exception?

The budget is not on the page, but the roadmap must be traceable in it. How to build that budget is covered in our article on what IT should cost per employee.

A choice is only a choice if something drops out

“We want a secure, modern and flexible IT environment” appears in many IT strategies and says nothing, because nobody chooses the opposite. A useful choice rules something out and helps with the next decision.

  • Too vague: “We are moving to the cloud.” Useful: “New applications are bought as SaaS; the local server goes off once the finance system has moved.”
  • Too vague: “Everyone should be able to work well.” Useful: “There are two laptop models, and the owner approves any exception.”
  • Too vague: “We work with reliable partners.” Useful: “Day-to-day support is outsourced; we keep the choice of applications and suppliers ourselves.”

That last one is the most important choice an SME makes: what you do yourself, what you outsource, and who stays in control. If you do not write it down, you find with every new supplier that control has quietly gone with them.

How to keep the IT strategy alive

A page that disappears into a folder is not a strategy. Three habits keep it in use.

  • One hour a quarter. The board, the person responsible for IT and, where useful, the supplier go through the roadmap: what is done, what has slipped, and why.
  • A fixed place in the budget. The annual budget starts from the roadmap, not from last year’s invoices.
  • Fixed moments to rewrite it. An acquisition, an office move, your IT person leaving, a major incident or a new legal obligation. The direction may no longer hold, and that should not wait until next year.

Use the page as a test for every large purchase too: does this fit the direction and the choices? If not, the question is not whether the purchase is wrong, but whether the strategy should change. Both are possible, as long as it is deliberate.

Four pitfalls in an IT strategy

  • The supplier writes it. Then their products appear as choices. Let a supplier contribute to the baseline and the roadmap, but keep the direction and the choices yourself.
  • It is a wish list. Twenty projects with no order is not a strategy. Choose what comes first, and say out loud what will not happen this year.
  • Nobody owns it. Without a name against a choice, an exception becomes the new rule, and after a year nothing is left of it.
  • It is only about technology. A platform choice without a business reason does not survive the first setback. Every choice must trace back to the direction.

Where our work stops

What we do. We help map the baseline, translate the direction of the business into IT choices and a roadmap, and deliver the technical part: devices, network, cloud, security and support. If you bring in our IT consultancy, you get a page you can carry out without us.

What we do not do. We do not set the business strategy; where the company goes is a decision for its leadership. Nor are we an independent adviser: we supply services ourselves, and if the strategy leads to a choice of supplier, we are one of the candidates. If you want a fully independent view, get it from someone who sells nothing. Financial or legal review, of investments or contracts for example, we leave to your accountant and your lawyer.

Frequently asked

Questions about IT strategy

What SME leadership teams ask us most often.

What is an IT strategy?

An IT strategy records the choices an organisation makes about its IT, and why, so that IT supports where the business is heading. For an SME that means a direction, a few principles, a roadmap for one to two years and an owner for each choice. It is not a project list and not a budget.

What should a small business IT strategy include?

A direction in one sentence, three to five choices, what you will stop, the non-negotiables such as security and data protection, a quarterly roadmap and a named owner for each choice. That fits on one page. The overview of the current situation belongs in an appendix, not on the page itself.

Does a small business need an IT strategy?

Not a report, but a few written-down choices, yes. Without them every purchase and every change of supplier is decided in isolation, and you grow an environment nobody chose. A single page reviewed for an hour each quarter is enough for most small businesses.

What is the difference between an IT strategy and an IT roadmap?

The strategy says why and which way: the direction and the choices. The roadmap says what happens when to get there. A roadmap without a strategy is a project list; a strategy without a roadmap stays an intention.

Can you write our IT strategy for us?

We can map the baseline, work out the IT choices and the roadmap, and deliver the technical part. The direction of the business is set by your leadership. Because we also supply services, we are not an independent adviser; for a fully independent view, ask someone who sells nothing.

Related services

Further reading

What an IT strategy connects to.

Shall we put your IT strategy on one page?

Tell us where the business is heading over the next few years. We map what you have today and put the choices and the roadmap on a single page you can carry out without us.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call