Routte

- What was true about the business
- A product rather than a site. Model output, application state and a booking path have to behave as one system, and the moment they are three systems the thing stops being usable.
- What that decided
- Itineraries generated against a traveller's stated constraints rather than assembled from a template, and the generated result carried forward into a booking path instead of ending on the screen that produced it.
- What it is
- An itinerary planner that generates against a traveller's real constraints rather than filling a template. Model output, application state and a booking path in one product — not a marketing page with a prompt box bolted on.






