Luca Rarau

Tour Platform

At IdeaPlaces, 2026. In production at Kalitravel.

The office system for tour bus companies: trips, seats, drivers, cash, in six languages.

In daily use at Kalitravel, Multi-tenant Postgres, Six languages.

The problem

A tour operator’s office ran on spreadsheets and phone calls.

What I built

The software a tour operator’s office runs on, built for a real first customer, Kalitravel. Trips, pickups, seats, customers, what the driver collects on board and hands in, manifests to print, and an email ledger so the office can see what was sent to whom. Multi-tenant from the start, with row-level security in Postgres and an audit log, and every screen in six languages.

My part

  • Office booking core, then row-level security and the auth audit trail across tenants.
  • Cash on board: the figure the driver collects is typed, never derived, and rides the printed manifest and both exports.
  • The email ledger, the pickup-times reference data, and a "What’s new" panel with per-person read state.
  • Internationalisation parity across six languages, proven by Playwright tests against the real cookie and base URL.

The result

Kalitravel’s office runs on it every day.

Kalitravel’s office runs on it day to day, in place of the spreadsheets and phone calls it replaced. Every feature since June came from what their office needed next.

What’s new

  1. The app’s AI assistant, Faro, works from inside Claude and ChatGPT over MCP, with the person’s own sign-in. Its answers now come with the platform’s own views drawn in the chat: a confirmation card, the pickup grid, driver availability, revenue tables.
  2. Accessibility pass: text holds 4.5:1 contrast in both themes, keyboard focus rings hold 3:1, and every control is a 44 px touch target on a phone.
  3. Onboarding for the travel desks that sell the tours: an invitation by email and WhatsApp with a QR code card, follow-ups until the first booking, and two versions of each message measured against each other.
  4. Found why a caller went unheard under load on WhatsApp calls: werift’s DTLS client mishandled a second HelloVerifyRequest.
  5. A WhatsApp control tower: the office sees every desk chat, takes one over from the AI, replies from the app, hands it back, and leaves private notes that steer the assistant.
  6. Mail in: the assistant reads operators’ booking emails, scored on a golden set, and the office approves each one on a Mail screen. Automation books only exact matches.
  7. The day’s board goes out as a PDF printed by Chromium, by email or WhatsApp in each person’s language, and every exported file is kept byte for byte for 12 months.
  8. Usage-based billing: an hourly job reports each day’s bookings to a Stripe meter at the commission they were made at.
  9. Cash on board: the figure the driver hands in is typed on the forms and printed on the manifest’s total row.
  10. Sign-in links are masked on the way into the email ledger; only the recipient sees their own.
  11. A "What’s new" panel beside the bell. An entry is read when it has been read, per person, per cluster.
  12. The email ledger shows where it matters: My profile, Team, and the message itself.
  13. Row-level security shipped, with the auth carve-out proven on a non-superuser admin.