Roadmap turns the plan into stages and dates, up to go-live. It is computed from the rollout settings and the plan, and asks nothing about the solution itself.
Where: Recommendations, Roadmap.
Summary
The one-off build in hours, the saving at full run, the first go-live date and the payback.

Rollout settings
The same values as Setup → Assumptions, editable here too: who builds, how many people and hours each, spec review, deploy from spec, connector hours with and without an API, test in shadow mode, pilot share and length, approval to go live, full review after go-live.
They set the dates, so they are worth checking before the readout.
Stages
kawaru.app proposes the stages; they can be renamed, split or merged, and each ends with a decision gate such as "G1 · Specs signed off".
Each agent goes through:
- Spec review
- Deploy and connect
- Test in shadow mode, which runs on real items and changes nothing
- Pilot, on a share of the items
- Production with every item reviewed
- Sampling, once approval reaches the agreed level
A ready-made product goes through onboarding, pilot and production. Configure and skills go live with no pilot.

Back-office solutions come before customer-facing ones, then the order follows the saving. Where the volume is below the threshold, the pilot takes the whole flow instead of a share.
As-is → to-be
Each process today, during the pilot and after: volume, minutes per item, who does it, and the pilot dates.

Result: a dated plan with decision gates.
Why this step: each gate is a decision. The first one, specs signed off, starts the build.