One message starts the trip
A parent writes where, when, who is coming and the budget, the way they would text a friend. No forms, no filters to learn.

Launch on real suppliers without first hiring a travel-tech team: search, a price check before every charge, hosted checkout and an admin, on a core we already run.
From $14,900 · fixed price per phase · first call free
Price and availability check before payment
62 ms
See the planner go from one message to payment: the trip brief, a full plan and a price check before the card is charged. The AI assistant add-on runs on the same booking engine we build for you. Shown on the Kinward family trip planner.
A parent writes where, when, who is coming and the budget, the way they would text a friend. No forms, no filters to learn.
The family gets a plan for every day of the trip with the budget beside it: what is paid now, what the extras will likely cost and what is left.
Right before payment, every price is checked with the suppliers again. If the hotel price has changed, the family sees the new total and approves it before anything is booked.
Most founders start with a clever idea and a few supplier APIs, then spend months on plumbing: search that is slow, prices that change at checkout, and no tools for the team. If you sell your own tours instead of building a product, see software for tour operators.

The traveler sees one price, clicks pay, and the supplier answers with another price or no availability. You refund, apologize and lose the customer.
The booking engine checks price and availability with the supplier again right before payment. If anything changed, the traveler sees the new price first. The booking is confirmed only after the supplier confirms.
Each flight or hotel API has its own formats, errors and limits. Without a clean layer in between, adding a second supplier means rewriting the first.
A supplier layer that maps each source to one internal format. Results are merged, duplicates removed and your margin rules applied in one place. New sources plug in without touching the front end.
Bookings sit in a database nobody can read. Support answers questions by asking a developer, and a failed supplier call goes unnoticed until a customer writes in.
An admin and back-office with every booking, payment status, traveler record and supplier error in one place, with roles for the people who work in it.
Four core modules and optional add-ons. We start with the ones that get you to your first paid booking.
Search by destination, dates and travelers, filters, ranked results and a booking flow that rechecks price and availability with the supplier before payment. The flow is built to WCAG 2.2 AA, with an accessibility report at handover.
GDS, bedbanks, flight and hotel aggregators and any other supplier API, REST, SOAP or XML, in one layer. You bring the accounts and contracts, we connect them.
Payment on your payment provider's hosted checkout, so card data never touches our servers. Confirmation emails, vouchers and receipts are sent automatically after the supplier confirms.
Bookings, payment status, traveler details, supplier errors and your margin rules in one admin, with roles for your team and reports by channel and supplier.
A chat that finds flights and hotels from a traveler's message, on top of the same booking engine. You can try it live on this page.
Faster response in season, a monthly report and two hours of changes each month.
A first working version of your booking product: booking engine, first supplier connections, checkout and back-office.
Prices exclude applicable taxes. Clients outside the EU are invoiced in US dollars, EU clients in euros.
Tell us what you are building. In 20 minutes you know whether we are the right team and what a first version would take.
In two short workshops we agree on modules and suppliers, and within 10 business days you have an architecture and a fixed price for each phase.
You click through a working version after each phase. Before launch we test price changes, failed supplier calls and checkout, then hand over the code, the documentation and the accessibility report.
A small studio in Europe. Here is how the day to day works when your team is in the US.
Support for live systems runs weekdays, 9:00 AM to 1:00 PM ET, by email and ticket.
Clients outside the EU are invoiced in US dollars, with a fixed price for each phase.
Calls, scope documents and handover documentation are in English.
Your data and the code we write for you are yours. Our core comes with a perpetual license to use it in your system.
We document the API, the architecture and the procedures, so a new developer can take over without a long ramp-up.
Monthly $229/mo
Support after launch that speeds up in season, when bookings can't stop.
Whatever suppliers and tools your product runs on, we connect them behind one booking engine. You bring the accounts and contracts, we build the connections.
Straight answers about price, timing, ownership and what you bring to the project.

The timeline depends on which suppliers you connect and which modules you need, so it is agreed per project and written into the fixed-price plan from the Diagnosis.
No. You bring the supplier accounts and contracts, and we connect them to your booking engine, whether that is a GDS, a bedbank, a flight or hotel aggregator, an activity supplier or any REST, SOAP or XML API.
Most of what a travel booking system needs (supplier layer, quotes, margins, admin) is already built in our core. We adapt it to your business instead of starting from zero, and you work directly with the people who build it. You get fixed prices per phase in writing before any build starts.
Bring your idea, your target suppliers and your timeline. In a free 20-minute call we tell you what a first version would take.
Book a free 20-minute call