IT StrategyUpdated November 2026

How To Build a Three-Year IT Roadmap and Budget

A simple process for turning IT from a series of emergencies into a plan the board can approve.

Caleb Adoh
Caleb Adoh Growth Marketing Manager
Consultant and business owner planning an IT roadmap on a laptop

Key Takeaways

  • Start from business goals, not from technology.
  • Audit what you have and when it reaches end of life.
  • Group projects by year and attach realistic costs.
  • Review the plan every year.

Without a plan, IT spending is driven by failures. A roadmap shifts the conversation from reacting to deciding, and it gives finance directors something to budget against rather than a series of unexpected invoices.

This guide answers the questions leaders ask us when they want to bring order to IT. It reflects how our vCIO services team builds roadmaps, and it links to NCSC and vendor resources.

Why do you need an IT roadmap?

Technology touches every part of the business, yet many organisations manage it project by project. The result is rushed purchases, ageing equipment and security gaps that nobody planned to fix.

A roadmap lets you decide in advance what to spend, when, and why. It aligns IT with where the business is heading, rather than where it has been.

↑ Back to Contents

Where should you start?

Team discussing technology budget and IT strategy around a table

Start with the business, not the technology. Ask what the company wants to achieve in three years: growth, new sites, new services, tighter compliance or better customer experience.

Write these goals down in plain language. Each IT project on the roadmap should link to at least one of them, or it needs a strong reason to be there.

↑ Back to Contents

What should you audit first?

Record hardware, software, licences, contracts, suppliers and renewal dates. Note each system’s owner, its age, how critical it is and when the vendor stops supporting it. Microsoft and other vendors publish lifecycle dates that show what is coming.

The audit also needs people: who knows how each system works, and what happens if they are away.

↑ Back to Contents

How do risks feed into the plan?

List the risks that worry you most, such as ransomware, a failed server, a supplier going out of business or a key person leaving. Rate each by likelihood and impact.

Use the NCSC board toolkit and Cyber Essentials as a checklist. High-risk items with low cost go to the top of the list.

↑ Back to Contents

How do you turn gaps into projects?

Each gap becomes a project with an owner, a goal, a rough scope and dependencies. Typical examples include replacing ageing laptops, improving backups, moving to cloud services, introducing multi-factor authentication or consolidating suppliers.

Avoid vague items. A project such as “improve security” is hard to cost and hard to finish.

↑ Back to Contents

How should you prioritise?

Rank projects by risk reduced, value delivered, cost and urgency. Some are non-negotiable, such as replacing unsupported software. Others can wait.

Be realistic about capacity. A plan that asks a small team to deliver ten projects in a year will fail.

↑ Back to Contents

How do you cost the roadmap?

Estimate one-off and recurring costs for each project, including licences, hardware, services and internal time. Add a contingency of around ten to twenty per cent, and be explicit about assumptions.

Include running costs, not only purchase prices. A cheaper system can be more expensive over three years if support or licensing costs are higher.

↑ Back to Contents

How do you present it to the board?

Boards want to know what they are buying, what risk it removes and what happens if they do nothing. Present the plan on a page: goals, key projects by year, cost and the risks addressed.

Keep technical detail in an appendix. Offer a clear decision, such as approval of the first year and indicative budgets for the next two.

↑ Back to Contents

How do you separate run costs from change costs?

Run costs keep the lights on: licences, support, connectivity and replacement cycles. Change costs deliver new capability. Separating them shows how much of your budget is already committed.

This clarity helps when you need to cut spending. You can see what is flexible and what is not.

↑ Back to Contents

Who should own the roadmap?

A senior person with authority should own it, such as an IT director, operations lead or a vCIO. Ownership means keeping it current, reporting progress and raising issues.

Without a named owner, roadmaps become documents that nobody reads.

↑ Back to Contents

How often should you review it?

Review it at least annually, and whenever the business changes significantly. Check progress, update costs, add new risks and re-rank priorities.

A quarterly check-in on delivery keeps momentum without turning into a large process.

↑ Back to Contents

What do we see go wrong with IT roadmaps?

In our experience, roadmaps fail when they are written once and filed, when they list technology rather than outcomes, or when nobody has the capacity to deliver them.

Short, practical, regularly reviewed plans work better than comprehensive documents.

↑ Back to Contents

What questions should you ask a partner who offers to build one?

Ask how they will involve the business, whether they are tied to specific vendors, how they will cost the plan and how they will report progress. Ask to see an example, with confidential details removed.

Check that they will hand the document over in a form you can update yourself.

↑ Back to Contents

What does a one-page roadmap look like?

A useful one-page roadmap has three columns for years one to three and four rows: people and process, infrastructure, security and business applications. Each cell lists two or three projects, with a cost range and an owner. Colour coding for risk or priority helps a board see where effort goes.

Resist adding detail. The page is for decisions, and the supporting detail sits in appendices. If a project cannot be described in one line, it probably needs to be split or clarified.

↑ Back to Contents

How do you handle hardware refresh cycles?

Laptops typically last three to five years, servers and network equipment longer, though support and warranty periods vary. List each asset class, its age and its planned replacement date, and spread replacements across years so that costs do not land at once.

Consider leasing or device-as-a-service where cash flow matters. Compare the total cost over the lifecycle, including support, disposal and the productivity cost of failing devices.

↑ Back to Contents

How should cloud and licence costs be forecast?

Subscription costs change with headcount, features and price increases. Forecast them by multiplying users by current prices and adding an allowance for growth and annual rises. Review renewal dates and negotiate early, since discounts often depend on timing and term.

Watch for licence overlap. Many businesses pay for tools that duplicate features they already own, and a licence audit before each renewal usually finds savings.

↑ Back to Contents

How do you budget for security and compliance?

Include baseline controls such as multi-factor authentication, endpoint protection, backups, email filtering and staff training, plus assessments such as Cyber Essentials and penetration testing. Allow for incident response, because even well-run businesses face disruptions.

Link spending to risk. A short statement of what each item reduces, such as the chance of ransomware or the time to recover, helps a board accept the cost. Our penetration testing service and phishing simulator are examples of controls that can be budgeted annually.

↑ Back to Contents

How do you deal with unplanned work?

Roadmaps meet reality. A supplier fails, a regulation changes or an opportunity appears. Reserve capacity and budget, typically ten to twenty per cent, for unplanned items, and agree a simple process for deciding what moves when something new arrives.

Record changes to the plan and the reason. A short change log shows the board that the plan is managed, and helps next year’s forecast.

↑ Back to Contents

How do you track progress and report to the board?

Report quarterly on projects completed, projects at risk, spending against plan, key risks and decisions needed. Use simple red, amber and green ratings with a sentence of explanation for each amber or red item.

Keep the format consistent so trends are visible. Boards trust reports that admit problems early and show what is being done. A vCIO can prepare and present these updates if you lack the time.

↑ Back to Contents

What mistakes should you avoid in your first roadmap?

Avoid listing products rather than outcomes, ignoring ageing systems, leaving security to the end and setting more projects than the team can deliver. Avoid, too, a plan that nobody owns or reviews.

Start small, deliver visible wins in year one, and build credibility. Our guide to choosing between a vCIO and an IT manager helps with ownership, and our IT consultancy team can run planning workshops. We support businesses in Birmingham, Manchester and Leeds.

↑ Back to Contents

How do you get buy-in from department heads?

IT plans fail when departments feel that decisions are made without them. Interview each head about their goals, frustrations and upcoming changes, and show how the roadmap addresses them. Use their language, not technical terms.

Invite a representative from each area to the annual review. When people see their needs reflected, they defend the plan, and they flag changes early. A vCIO can facilitate these workshops if internal time is short.

↑ Back to Contents

What does a good first-year plan look like?

The first year should deliver visible wins and reduce the biggest risks: for example, multi-factor authentication, tested backups, replacement of unsupported devices and a clear support arrangement. Keep it to a handful of projects the team can finish.

Report progress quarterly, and use early success to justify years two and three. Our IT consultancy team can run planning workshops, and we support businesses in Leeds and Nottingham.

↑ Back to Contents

How do you prioritise when everything seems urgent?

Use a simple scoring grid: risk reduced, value gained, cost, effort and dependency. Score each project from one to five, then discuss the results with leadership. Hard dependencies, such as replacing unsupported systems, move up regardless of score.

The exercise also shows what to stop. Projects that score low on every axis can wait, which frees capacity for the ones that matter.

↑ Back to Contents

How do you keep the roadmap flexible without losing direction?

Fix the first year in detail, plan the second year in outline and treat the third as direction. Review every quarter and re-plan every year. Flexible does not mean loose: changes need an owner and a reason.

Communicate changes in plain language. Our vCIO team helps keep plans current, and we support businesses in Reading and Bath.

↑ Back to Contents

How do you handle legacy systems in the roadmap?

Legacy systems carry hidden risk: unsupported software, key-person knowledge and costly workarounds. Decide for each whether to retire, replace, wrap or keep with mitigations, and give it a date.

Do not leave them undecided. Our IT consultancy team helps assess options, and we support businesses in Leeds and Birmingham.

↑ Back to Contents

Map each major risk to the project that reduces it. Show insurers and auditors which controls are planned and when. This turns the roadmap into evidence of good governance.

Update the mapping when projects complete. Our vCIO team maintains this link for clients.

↑ Back to Contents

How can NetMonkeys help?

Our vCIO services include roadmap and budget creation, supplier review and board reporting. We support businesses across the UK, including IT support in Leeds, IT support in Birmingham and IT support in Nottingham.

Our guide comparing a vCIO and an in-house IT manager may help you decide who should own the plan.

↑ Back to Contents

Frequently Asked Questions (FAQs)

What should an IT roadmap include?

Business goals, current state, planned projects by year, costs and owners, and key risks.

How far ahead should an IT budget look?

Three years is a common balance. Further than that becomes guesswork.

Who should own the IT roadmap?

A senior person with authority, such as an IT director or a vCIO, with sign-off from the leadership team.

How much contingency should an IT budget include?

Many organisations add around ten to twenty per cent, depending on how well scoped the projects are.

How do we keep the roadmap alive?

Name an owner, review it quarterly and refresh it annually.

↑ Back to Contents

Sources and Further Reading