How to build an IT roadmap for MSP clients, quarter by quarter

An IT roadmap for MSP clients is a dated plan of the technology work a customer will fund over the next two to three years, laid out quarter by quarter, tied to their business goals and to a budget they have stated. It is the document a strategic business review reads from and updates. This guide covers how to build one: what to collect, how to plan hardware refresh cycles, how to place work in quarters, how to price it, and how to keep it current so the next review starts from what the last one decided.

What an IT roadmap for MSP clients contains

A roadmap that survives contact with a customer's finance lead has five parts. Missing any one of them is how a roadmap turns into a wish list.

• Goals, in the customer's words. Up to five things the business is trying to do this year, each with a status (on track, at risk, off track) and a line on why it matters.
• A stated budget. A figure, or the words they used when they would not give one, plus what it has to cover. Keep a budget per fiscal year for this year and the next two.
• Initiatives on a timeline. Each item of work in the quarter it is planned for, with an owner, a one-time cost and a monthly cost.
• Evidence. The devices, tickets, contract or risk behind each item, so anyone can ask "why this, why now" and get an answer.
• Decisions. Who approved, deferred or declined each item, and when. A roadmap without decisions is a proposal.

Start with goals and budget, not the asset list

It is tempting to open the RMM, sort by device age and build the roadmap from the oldest machines down. That produces a refresh schedule, which is useful, but it does not tell the customer why the money should go there instead of the new office they are opening in spring. Start with a short conversation:

• What does the business need to be true in 12 months? (Open a second location, pass a cyber insurance renewal, hire 15 people, move off a line-of-business server.)
• What did you spend on IT projects last year, and is this year more, less or about the same?
• What does that budget have to cover? (Hardware only, or licensing and projects too?)
• Who decides, and how often do you want to review the plan: quarterly, twice a year or annually?

Write the answers down with the date and the name of the person who gave them. Six months from now you will need to ask "is this still true?", and the answer means more when you can say who said it and when.

Plan refresh cycles from real device data

Hardware refresh is the most predictable line on any roadmap, and the easiest to defend, because it is dated and checkable. Build it from data, not from a rule of thumb applied to the whole fleet.

Pull three facts per device

• Age, from purchase or first-seen date.
• Warranty end date, from the OEM or a lifecycle tool.
• Operating system support status, from your RMM.

Operating system dates are fixed in advance and public. Windows 10 Home and Pro, for example, reached end of support on October 14, 2025 per Microsoft's lifecycle page, so any machine that could not move to Windows 11 belonged on a roadmap well before that quarter. Check the vendor lifecycle pages for the systems your customers run and put each date on the board.

Set a refresh policy per device class

Agree a target life with the customer for each class (laptops, desktops, servers, firewalls, switches, wireless) and write it on the plan. Then group replacements so you are not proposing one laptop a month. A fictional example: Harbor Lane Accounting, 40 staff, has 12 laptops past warranty and 6 more whose warranty ends in Q3. Two batches, Q2 and Q4, are easier to approve and to deliver than eighteen separate line items.

Price it with your own replacement prices

Keep a default replacement price per device type and use it for every early estimate. Say on the roadmap that the figure is at your default price, and replace it with a real quote when the item gets close. A plan that says "value on quote" is better than one with a guessed number nobody can trace.

Lay the work out quarter by quarter

Quarters match how customers budget and how reviews run. Use columns from last quarter to eight quarters out, plus an Unscheduled column for work that has no date yet. Then sort each item into a theme so the customer can see the balance of the plan:

• Security: MFA coverage, endpoint protection gaps, email security, awareness training.
• Lifecycle: refresh batches, operating system upgrades, server retirements.
• Growth: a new site, a new line-of-business app, onboarding a wave of hires.
• Compliance: what an auditor, insurer or regulator will ask for, and by when.
• Continuity: backup coverage, recovery testing, failover.

Sequence the quarters with three rules. Dependencies first (identity cleanup before a tenant migration). Dated items at least one quarter ahead of their date (an OS end of support, a contract renewal, an insurance renewal). And no quarter holding more than the customer's stated budget allows, unless you show them the overrun on purpose.

Show the budget against what they said

Draw the plan's investment by quarter for three years, split into contract renewals, hardware refresh, one-time initiatives and recurring initiatives (count a monthly item three months per quarter from the quarter it starts). Then draw the customer's stated budget for each year as a line across that year's quarters. The customer can see in one look whether the plan sits under or over what they said, and you can have the trade-off conversation with the numbers on the screen.

Leave a year blank when nobody has answered for it. A customer who has said nothing about 2028 has not said zero.

Get decisions in the room

Present the roadmap in the review and ask for a decision on each item in the next two quarters: approve, defer (to which quarter, and why) or decline (and why). Record who decided. Approved items should turn into opportunities or quotes the same day, otherwise the decision fades before anyone acts on it. The QBR guide covers the agenda around this part of the meeting.

Keep it current between reviews

• Re-confirm goals and the budget on the cadence you agreed: after 90 days on a quarterly cadence, 180 on twice a year, 365 on annual.
• Feed new findings in as suggestions, not as approved work: a failing backup, a drop in MFA coverage, a ticket theme that repeats across five or more tickets in 90 days.
• Open each review with what was promised last time and what happened: delivered, slipped, dropped or still open.
• Export the budget for the customer's finance team as a spreadsheet or PDF that holds prices only, never your cost or margin.

How Current builds the roadmap for you

Current gives every company a roadmap that follows the method above. The account plan holds up to five goals, the budget with what it covers, the cadence, the next review and who sits in the room, and every field carries a confirmation stamp that asks "Still true?" when it goes stale. The board runs from last quarter to eight quarters out with the five theme lanes, a status menu on every card, and a Schedule for quarter picker.

A Suggested tray fills from the systems you already run: hardware past warranty and unsupported operating systems from ScalePad Lifecycle Manager and your RMM, priced at your default replacement prices; backup problems from Datto BCDR, Backup Radar, Slide, Acronis or MSP360; MFA coverage gaps; repeating ticket themes; standing risks; and services a customer keeps asking about but does not buy from you (whitespace). Accept turns a suggestion into a proposed card with its evidence. Draft a plan proposes goals, initiatives and sequencing, and you accept, edit or drop each line before anything is written.

The Budget view draws three years by quarter with the stated budget as a dashed line, and exports to Excel or a branded PDF. In the business review, the road ahead slide is the board itself, with Approve, Defer and Decline working live; an approval opens an opportunity on your Expansion pipeline. The full walkthrough is in the Roadmaps help article.

Step by step

1. Step 1
   Record goals and budget in the customer's words

   Ask what the business needs in the next 12 months, what it spent on IT projects last year, what this year's budget covers, who decides and how often to review. Note the date and who answered.

2. Step 2
   Collect device age, warranty and OS support dates

   Pull age, warranty end and operating system support status for every device from your RMM and lifecycle tool, and add the public end-of-support dates for the systems the customer runs.

3. Step 3
   Agree a refresh policy and batch replacements

   Set a target life per device class, group replacements into quarterly batches, and price them at your default replacement prices until a real quote exists.

4. Step 4
   Place every initiative in a quarter and a theme

   Use columns from last quarter to eight quarters out plus Unscheduled, sort items into security, lifecycle, growth, compliance and continuity, and sequence by dependency and due date.

5. Step 5
   Compare planned investment to the stated budget

   Chart the plan's one-time and recurring investment by quarter for three years against the budget the customer stated for each year, and leave unanswered years blank.

6. Step 6
   Ask for a decision on the next two quarters

   In the review, have the customer approve, defer or decline each near-term item, record who decided, and turn approved items into opportunities or quotes the same day.

7. Step 7
   Re-confirm and feed in new findings on a cadence

   Re-confirm goals and budget when they go stale, add new findings as suggestions, and open each review with what was delivered, slipped or dropped since the last one.