Most IT roadmaps live in parallel to the CFO's three-year plan, not inside it. The MSP produces a slide deck once a year. The CFO produces a separate three-year financial plan. The two documents reference each other politely and decide nothing together. The result is IT spending that surprises finance every quarter and finance decisions that strand IT every fiscal year.
The IT roadmap that actually fits inside the CFO's plan covers four specific intersections.
Intersection one — capital expenditure timing. Server refresh cycles, infrastructure upgrades, Microsoft 365 license expansions, network equipment replacements. Each has a real dollar number and a fiscal-year impact. The IT roadmap that does not put these on the same calendar as the CFO's capital plan is going to produce mid-year budget surprises that erode the trust between the two functions.
Intersection two — operational scaling cost. As headcount grows, license costs grow, support tickets grow, infrastructure capacity grows. The IT roadmap should model this against the headcount plan in the CFO's three-year forecast — not against a generic per-seat assumption. Most MSPs do not have the financial discipline to produce this; most CFOs do not have the IT context to demand it.
Intersection three — major business events. ERP migration, acquisition integration, new location opening, fundraise. Each is a known event in the CFO's plan and a major IT undertaking. The roadmap should sequence IT capacity against these events explicitly — not discover them six weeks before they happen.
Intersection four — security and compliance investments tied to revenue stage. SOC 2 readiness when the business hits an enterprise sales motion. Cyber insurance underwriting when revenue crosses a threshold. Audit-readiness investments when the business approaches an equity event. These are CFO decisions with IT execution requirements. The roadmap should flag the trigger points explicitly.
Across the engagements where I have served in an integrated CFO-CTO function, the IT roadmap was reviewed alongside the financial plan in the same quarterly executive meeting. Both documents updated together. Neither operated independently. The IT spending surprises stopped happening because the underlying decisions were no longer happening separately.
If your IT roadmap is a deck the MSP presents to the IT manager and the CFO has not seen it this year, it is not a roadmap. It is a sales document. The fix is putting the IT roadmap inside the same conversation the CFO is already running.
Filed under
