Constraints, not footnotes
Each one is modeled inside the plan, where it can change the route — not bolted on afterwards as a filter or a disclaimer.
Use cases
Four hard problems, modeled properly
Some problems don't belong to one kind of business. A lodge, a destination organization and an adventure outfitter all need to plan for wheelchair users, quiet months and groups that can't agree. Here's how we handle each.
Choose a use case
Each page covers the problem, the constraints and signals we model, a worked example, and who it's for.
- Route Engine · Itinerary StudioAccessible travel planningStep-free routes, rest blocks, sensory load and venue data with a verified date — modeled as part of the route, not added as a note at the bottom.
- Route EngineLow-carbon routingA lower-emission plan shown beside the fastest one, with the extra hours and the estimated savings stated plainly. The traveler chooses.
- Route Engine · ConciergeGroup travel coordinationIndividual constraints plus shared ones, plans that split and rejoin, and a fairness check so nobody gets outvoted every single day.
- Signals · Itinerary StudioShoulder-season demand shapingBooking pace, events, weather norms and traveler intent read together, ten weeks out, with package ideas worth building.
What the four have in common
Your data first
Your venue knowledge, booking history and supplier notes do most of the work. Outside data fills the gaps, and every source is labelled.
People approve
Draft, don't decide. The system proposes and explains; your planners, guides and revenue leads choose.
Measured in a pilot
Each use case starts with one agreed measure, tracked the same way before and after, and reported as a pilot measurement.
Related
Keep exploring
- SolutionsSolutionsAI solutions for tour operators, advisors, DMOs, lodges, activity providers, event planners and adventure outfitters, plus four cross-cutting use cases.
- PlatformRoute EngineConstraint-based itinerary routing that weighs opening windows, travel time by mode, pacing budgets, accessibility, weather and capacity, and explains each day.
- PlatformSignalsDemand forecasts, cancellation risk, price sensitivity and shoulder-season shaping, each with a confidence range, its drivers and a next step a person approves.
- Field Notes · Route & Itinerary ScienceThe Itinerary Is a Constraint ProblemWhy multi-stop itineraries fail in the field, and how to model them as constraint problems: time windows, door-to-door travel times, slots, slack and weights.
Have a problem that isn't on this list?
These four are the ones we're asked about most, not the only ones we model. Tell us what keeps breaking in your trips.