Case study · En Route Luxe · 2025–
A business run on agents
The lifelong travel advisor. One relationship that holds your family's story: the babymoon, the first safari with kids, the anniversary you didn't have time to plan. Every trip that matters, for decades.
En Route Luxe is a boutique luxury travel advisory I founded and run. Behind the human touch runs a virtual team of AI agents built with Claude Code. Agents draft. Guardrails check. The founder edits.
By the numbers
Real clients, real revenue, real margin
- 20+
- clients a year
- 50+
- trips a year
- $500K+
- in annual bookings
- 100%
- repeat and referral growth
Grown entirely through repeat bookings and referrals. No paid acquisition. 100% repeat and referral growth is the early proof of lifelong relationships: a client who hands you their next trip, and their sister's honeymoon, is telling you the relationship is the product.
What clients say
“We'd been to Africa before, but never like this. They knew exactly when and where to be — the migration crossing we witnessed wasn't luck, it was planning.”
“Japan was our dream trip for years. We were overwhelmed until En Route Luxe showed us it wasn't about doing more — it was about timing it right. Our kids still call it the best week of their lives.”
“What surprised us most was what they told us NOT to do. That restraint — knowing what to skip — made the trip feel effortless instead of exhausting.”
Destinations
Where the trips go
Itineraries designed across 30+ countries, including:
- Japan
- Kenya
- Tanzania
- South Africa
- Namibia
- Zimbabwe
- Italy
- Greece
- Croatia
- Thailand
- Cambodia
- Spain
- Portugal
- England & Scotland
- French Polynesia
- The Bahamas
- + more
Trips designed across four continents
The operating stack
Agents draft. Guardrails check. The founder edits.
The advisory runs on an AI operating stack built and shipped daily: Claude Code agents plus a library of custom skills, scheduled automations, and a markdown knowledge base. Every output ends at a decision point: approve, redirect, or kill.
Data and tools
- Destination intelligence: 190+ destinations
- Flight-search MCP server
- Markdown knowledge base
- Call transcripts and research ingest
Agents draft
- Destination research
- Itinerary assembly and QA
- Brand voice
- Content engine
- Scheduled automations
Guardrails check
- Closure checks
- Transfer buffers
- Ticketing rules
- Contingency paths
- Receipt tests on content
- AI-tell scans
The editor layer: the founder decides
- Approve, redirect, or kill
- Supplier selection stays human
- Disruption response stays human
- Taste stays human
The discipline that makes it work: knowing what NOT to automate. Judgment is the only step that does not scale, so the system spends the founder's time only there. The architecture is public in agent-skills.
The judgment story
Six weeks out, the airline cancelled
Kenya and Tanzania: 25 travelers, six families, timed to the Great Migration. Six weeks before departure, the airline cancelled the route.
An agent would have rebooked the same plan on the next available carrier. That is what optimization looks like when the objective function is “restore the itinerary.”
The actual call: re-route the entire group through London, absorb 12 time zones with kids, and turn the disruption into the trip's strongest opening. Camp selection followed the same logic: location beats brand in the reserve.
That wasn't a data lookup. It was taste, timing, sequencing, and knowing when the obvious answer is wrong. For trips that have to count, that judgment IS the product.
The same review pattern that gated 1M+ documents a year at Zillow now runs a travel advisory. Different stakes, same discipline: agents draft, guardrails check, the human decides.