What I build

Software for travel and tourism

Booking and payments

Tours, packages and deposits booked and paid online, with availability that stays accurate.

Itinerary builder

Branded day-by-day itineraries built from templates and booking details, shared as a link.

Traveller portal

Travellers see their trip, documents and updates in one place, on any device.

Enquiry and CRM tools

Enquiries, quotes and follow-ups tracked from first message to booking.

Supplier and operations tools

Suppliers, guides and allocations managed in one internal tool.

Reporting

Bookings, margins and seasonality in one dashboard.

AI, right now

Where AI genuinely helps

Travel businesses now compete with consumer apps on experience: travellers expect real-time updates and a polished, branded trip. 2026 guides describe AI taking over document parsing, content and first-line questions, while bookings and payments still need a human decision.

I haven’t built for a travel company yet, so I won’t pretend otherwise. What I bring is the same building blocks I’ve shipped for real clients, shown below.

  • Answers for travellers, any time zone

    Questions about trips, visas and policies answered from your own information, with a hand-off to a person.

  • Booking documents into itineraries

    Confirmations parsed into itinerary items automatically, checked by your team.

  • Trip content drafting

    Descriptions and day plans drafted from your templates, then edited by you.

  • Lead qualification

    Enquiries sorted and summarised, so your team replies first to the ones ready to book.

Similar work

Data, security and access

  • Traveller and passport details kept private and visible only to the staff who need them.
  • Payments through Stripe or your provider; card details never touch your servers.
  • Bookings and changes logged for every trip.
  • Final bookings and payments always confirmed by a person or the traveller, never by AI alone.

How a project runs

  1. Call

    A 30-minute call about what you need, who it is for, and what success looks like.

  2. Scope

    A written scope: features, architecture, timeline, price range and risks.

  3. Build

    Working increments you can click through, not a big reveal at the end.

  4. Ship

    Live on your domain and hosting, with a handover so you know how it runs.

More in how I work, or see mvp and saas development.

Questions

Common questions

Can this connect to GDS or supplier systems?

Where the supplier offers an API, yes. Which connections make sense is decided in the scope, based on how you book today.

Why custom instead of a travel agency platform?

If a platform fits, use it. Custom software suits operators with their own products, unusual booking rules or a traveller experience they want to own.

Can travellers use it on their phones?

Yes. Portals and itineraries are built mobile-first in the browser, with nothing to install.

How much does it cost?

A focused first version is a fixed-price project, scoped and priced after a 30-minute call (MVPs start from $3,000). Ongoing work can run on a monthly retainer.

Building booking or itinerary tools for travel?

A 30-minute call is enough to tell whether it fits, what the first version should include, and how long it takes.

Book a 30-minute call