Tour operators Attractions

Booking websites for tour operators and attractions.

We build booking websites that load fast and connect to the system you already take bookings in, such as Rezdy, so the sale happens on your own site. Behind them, AI systems do the daily admin, and your team checks the result.

Tell us about your tours See pricing
Made in Australia
What's the Problem?

Where tour websites lose bookings.

A tour page that takes ten seconds to load loses visitors before the booking calendar appears. One tour site we rebuilt took that long, on a booking plugin inside WordPress.

Travellers rarely book just one thing. Without a cart that holds several tours and dates at once, the second sale never happens.

Behind the bookings, someone spends part of every afternoon turning tomorrow's passengers into headcounts and emails for each supplier, by hand.

And travellers now ask ChatGPT and Google's AI which tour to take. If your own pages don't answer what they ask, the answer quotes a booking site that charges you commission instead.

Today's Menu

What we build for tour operators and attractions.

The first two run at a small-group tour operator in New Zealand. The third runs at museums and attractions that host school groups.

  1. A booking site connected to Rezdy

    For tour operators who take bookings in Rezdy, or a booking system like it.

    Tour pages are built ahead of time, so they load before the booking system is even asked. Live availability and prices then arrive from Rezdy. Our cart holds several tours and dates at once, takes vouchers, and offers the rest of a package, which is where the second tour gets sold. Card details go straight to Stripe through your Rezdy account and never touch the site.

    A small-group tour operator in New Zealand, moved off WordPress and its Rezdy plugin. Its conversion rate is up 37%, and a second brand, Crew Adventures, runs on the same code.

    1. 01

      A tour changes in Rezdy

      and an automatic update copies it to Sanity, where the team edits the rest.

    2. 02

      The tour page is rebuilt

      ahead of time, so it loads in under two seconds.

    3. 03

      Availability arrives from Rezdy

      two months at a time, with live prices.

    4. 04 A person

      The customer books in our cart

      several tours and departures at once, paid through Stripe on Rezdy's account.

    The result

    Visits that book rose from 1.83% to 2.51%, and each booking now carries 1.18 tours instead of 1.03.

    Read the Cheeky Kiwi Travel case study

  2. Supplier emails drafted every afternoon

    For operators who send their suppliers headcounts every day.

    Bookings are copied from Rezdy as they arrive. Each afternoon the system groups tomorrow's passengers by supplier, applies each supplier's rules, and Claude drafts every email. Staff read them, change what they need to, and send.

    The same staff tool answers questions about bookings in plain English, such as how many passengers travel tomorrow, using only live data it looks up, and does its sums with a calculator rather than guessing.

    1. 01

      Tomorrow's bookings are gathered

      from the copy kept in step with Rezdy.

    2. 02

      Passengers are grouped by supplier

      with cut-off times, capacities and seasonal allocations applied.

    3. 03

      Claude drafts each email

      one for each of the fifteen or more suppliers, written from the bookings.

    4. 04 A person

      Staff check and send

      and every email is logged.

    The result

    Three hours of copying every afternoon became a review.

    Read the Cheeky Kiwi Travel case studyAutomating enquiries and bookings

  3. A tour app on the venue's own phones

    For museums and attractions that host school groups.

    Students follow a trail of questions around the venue on phones the venue owns, locked to that one app. The teacher sees every student's progress live, and the app keeps working when the wifi drops. Venue staff write their own programmes in an editor, with a map of each floor and a test mode.

    Built and on phones 30 days after the first line of code. An update reaches every phone in under 90 seconds, and a dashboard shows each phone's battery and lock status.

    1. 01

      Claude drafts the questions

      from the venue's own education packs.

    2. 02 A person

      An educator approves them

      nothing reaches a phone without that approval.

    3. 03

      Students follow the trail

      on the venue's phones, while the teacher watches their progress live.

    4. 04

      The teacher gets a report

      with every answer, and a certificate for the class.

    The result

    Teachers leave with a report of every answer, which a worksheet never gave them.

    Read the Edtripper case study
Baked In

Included in every tour website.

  • Live availability and prices.

    Loaded from your booking system, which stays in charge of every seat.

  • A cart for more than one tour.

    Several tours and dates in one booking, with vouchers and package offers.

  • Payments through your own account.

    Card details go to your payment provider, never to the website.

  • Pages that answer travellers.

    Each tour page answers the questions travellers ask, which is what search engines and AI tools quote.

  • Fast on a phone.

    Tour pages are built ahead of time, so they load in under two seconds, before availability even arrives.

  • More than one brand.

    A second brand can run on the same code and editor, with its own content.

  • Edited by your team.

    Tours sync from your booking system, and everything else is edited in a visual editor.

  • No lock-in.

    Bookings and payments stay in your booking system, and the site and its code are in your name.

Connected for tour and venue clients so far.

Every name here runs on a tour or venue system we built.

  • Rezdy
  • Stripe
  • Sanity
  • Supabase
  • TripAdvisor
  • Claude
  • Hexnode
  • Cloudflare

FareHarbor and Bókun offer APIs too, which we test against your account before quoting.

Fresh Out

Built for tours and attractions.

Edtripper website
Attractions · school groups Edtripper An Android app that runs school groups through museums and attractions on phones the venue owns, with an editor for the venue's own programmes.
See all work
Price List

What it costs.

Price List
Website build for a tour operator or an attraction
from $9,000 typically $9–18k
Booking platform your own pages and cart, connected to Rezdy or your booking system
from $15,000 typically $20–45k
Automation build such as the daily supplier emails
from $8,000 typically $10–30k
GEO & SEO programme found on Google and named in AI answers · 3-month minimum
from $1,000/month typically $1–2.5k a month
Care plan monitoring, updates, small changes and a monthly speed report
from $250/month

What affects the price:

  • how many tours, brands and languages
  • whether people book in your own cart or in the booking system's widget
  • which booking system and suppliers we connect
  • how much of the admin behind the bookings we automate

Fixed quote after a scoping call. The free AI visibility audit shows where your tours stand in AI answers before you spend anything.

About the audit
Fair Questions

Questions operators ask.

Seven questions we hear from tour operators and attractions. Have another one? Ask us.

Can the website take bookings through Rezdy?

Yes. Cheeky Kiwi Travel's site loads availability and prices from Rezdy and takes bookings in a cart we built, with payments going through Rezdy's Stripe account. Rezdy stays the record of every booking, so nothing changes for the team that runs the tours.

Do you work with FareHarbor or Bókun?

Not yet for a client. Both offer an API, which lets other software connect to them, so the same approach works: the site shows live availability and the booking system stays in charge. We check what your account allows before we quote.

Why not just use the booking system's own widget?

A widget works, and for some operators it's enough. A site of your own loads faster, sells more than one tour per booking, and answers the questions travellers ask, which a widget can't. At Cheeky Kiwi Travel, visits that book rose from 1.83% to 2.51% after the move.

How do we get our tours recommended by ChatGPT?

By answering the questions travellers ask on your own pages, and by being listed where the AI tools look. In our September 2026 audit, Cheeky Kiwi Travel was named or linked in 65 of 153 AI answers to its customers' questions, and its own site was the most-cited source, ahead of Viator and TripAdvisor. The audit is free.

Can one site run more than one brand?

Yes. Cheeky Kiwi Travel and Crew Adventures share one set of code and one editor, and each brand keeps its own content.

Do you build for attractions and museums?

Yes. Edtripper's app runs school programmes at museums and attractions on phones the venue owns, with an editor where venue staff write their own trails. We haven't built a museum's own website yet; its booking side would work like a tour operator's.

Do you work with operators in New Zealand?

Yes. Cheeky Kiwi Travel runs its tours in New Zealand, and we work with businesses in both Australia and New Zealand.

The long answers
Also on the menu All industries
Made to Order

Tell us about your tours.

A couple of lines is enough. After a short call, you'll get our recommendation and a fixed quote within a business day.

Reply within one business day.