From a message to a managed journey.

Five steps, and you are involved in two of them. You tell us where you need to be. We read the request against your preferences and your history. Your company’s rules are checked. You confirm and we book. Then we stay available for whatever moves. The rest happens without you.

We read it in context rather than as a search query. Your preferences, your past journeys and the reason for the trip all shape what comes back. Your company’s policy, budget and approval rules are applied first. What you receive is a short set of options you are already permitted to choose from.

From how you actually travel, not from a form you filled in once. Aisle or window, the hotel you went back to, how early you like to reach the airport, the city you visit often enough that we should stop asking. The understanding sharpens every journey, which is why each request gets shorter.

No. Searching, comparing and confirming are jobs for a machine, and we treat them that way. You describe the journey and we do the looking. If you would rather see the whole field yourself, we will show you the whole field. The default is that you do not have to.

Before an option reaches the traveller. Your approval rules sit inside the request, so a trip needing a manager’s sign off is routed for it and a trip that does not is simply arranged. Approvers are asked once, with the cost and the policy position attached, not chased across three email threads.

Tell us what changed and we work out the rest. Rebooking, the hotel night that now needs moving, the car meeting a flight that no longer lands at that time. Disruption is the part of a journey where judgement matters, so it is handled by a person rather than an automated rebooking rule.

Airport transfers, car rental, lounge access, trains, visa arrangements, conference attendance, company retreats, and private aviation where a schedule genuinely requires it. Anything attached to the journey is part of the journey. If you are unsure whether something falls within scope, ask. The answer is usually yes.

Yes. Group bookings, team offsites and multi city itineraries with people joining from different places are arranged as one request rather than several. Each traveller keeps their own preferences and their own policy position. You receive one itinerary, one set of costs and one point of contact.

Your travel policy, your approval structure and the names of the people who travel. If the policy lives in someone’s head rather than a document, tell us what it is and we will write it down for your approval. Preferences are not needed upfront. We learn those from the first few journeys.

Days rather than months. There is no software to deploy, no seats to provision and no training programme, so setup is a conversation about your rules and your travellers rather than an implementation project. Most companies send their first real request in the same week they decide to start.

Yes, though most stop wanting to. Nothing prevents a traveller from arranging their own journey, and some prefer to for short domestic hops. What changes is that the alternative is now one message, so doing it yourself stops being worth the effort after the first few trips.

It is a companion, not a booking tool. Use it to view your bookings, track a request in progress, see what has been spent, and read recommendations built from how you travel. Travellers see their own spend, administrators see the company’s. Everything it shows can also simply be asked for in a message.

No. It removes the repetitive coordination and leaves your travel team in control. Searching, comparing, confirming and chasing are the parts that get taken away. Supplier decisions, policy design and the judgement calls on the journeys that really matter stay where they belong, which is with your people.