Stop 2 of 9 · Weekly
Roadmap and budget
Asset and licence exports in, a one-year and three-year roadmap out, with a budget table Hazem prices himself and a client deck built from it.
The quarterly conversation, prepared in an hour
Every managed client should get a roadmap and hear about it once a quarter. In practice Hazem writes two a year and apologises for the rest, because building one means reading an asset export, a licence report and a warranty list, then arguing with himself about horizons. That is a reading job, and it is the part to hand over.
What goes in: the RMM asset export with serials removed, the Microsoft 365 licence report, the hypervisor inventory, the Meraki device list with support dates, and last year roadmap so the new one shows what moved. What stays out: licence keys, tenant identifiers you would not print, and anything from the vulnerability scan, which has its own stop.
Two horizons, one trigger each
| Horizon | What earns a line |
|---|---|
| One year | Support end, warranty end, lease end or renewal inside twelve months, or a capacity threshold already crossed |
| Three years | The same triggers dated later, plus the platform moves that need a budget conversation now |
The trigger is the whole argument. A Meraki MX out of support in eleven months is a one-year line whether or not Bellhaven Law wants to spend, and the roadmap is where that gets said in writing before it becomes an outage.
[attach the asset export with serials removed, the licence report and the device support list] Build a technology roadmap for Bellhaven Law from these files. Group assets by role: endpoints, servers, network, identity and licensing, backup, telephony. For every group give me the one-year lines and the three-year lines, and for each line state the dated trigger, the risk if we do nothing, and the work in engineer days. Sort each horizon by risk, highest first. Where a support or warranty date is missing from the files, list the asset under Unknown dates rather than guessing. Do not include any price.
From the roadmap above, build a budget table with one row per line item and these columns: item, quantity, model or licence, engineer days, price. Leave the price column empty for me to fill from quotes. Split the table into capital items and recurring monthly items, subtotal each, and put anything under Unknown dates in a third section labelled needs verification.
Hazem fills the price column from distributor quotes. That is fifteen minutes on a table he did not have to build, and it means every figure in front of the client came from a quote with a date on it.
Turn the priced budget table and the one-year roadmap into a short client deck for the Bellhaven Law partners: one slide on where they are now, one per roadmap group with the trigger date and the risk in plain language, one on the year total, and a last slide with the three decisions I need from them this quarter. No jargon, no acronyms without a first-use expansion.
The artefact
A roadmap document with dated triggers, a two-part budget table you priced, and a partner deck. All three are handed to the client at the quarterly review.