Design
The roadmap comes before the tool, because the order decides what the work costs.
The question this phase answers
What should change, in what order, and what does it cost to get the order wrong? Design turns the map into a sequence: what to build, buy, integrate, delay, or avoid.
What you receive
A technical sequence with its reasons. Architecture options with their trade-offs, not just a recommendation. Estimates that make cost and effort comparable. A name against every part of the sequence.
What you decide with it
Where the money goes first, with alternatives on the table, before any vendor enters the conversation. If someone else implements the roadmap, it still has to stand.
What this looks like in practice
The design conversations that matter are about what not to do yet. Most sequences we write delay something the business arrived wanting, because a dependency has to come first, and that is the part a vendor proposal will never say.