case study · Off the Beaten Path
Off the Beaten Path designs active outdoor journeys, Private Custom Journeys and Small Group Adventures across many regions. We built them Meera — an AI trip-design assistant on top of their own Salesforce data — so a planner can go from a blank departure to segments, vendors, reservations, routes and a client-ready proposal without ever leaving the conversation. This is the implementation pattern for agencies that want their own planning agent grounded in their own inventory, rules and documents.
the challenge
A single departure can span several regions and weeks. Lodging, activities, guides, meals and transport all have to line up, by the day, across the whole journey — and every change ripples through the rest of the plan.
All of that detail already lived in Salesforce. But building a trip meant clicking through record after record, and turning it into something a client could actually read meant rebuilding it by hand in a separate document — again and again, every time the plan moved.
Off the Beaten Path didn’t need another database. They needed the planning itself to be faster, and the client-facing output to fall out of the work instead of being re-keyed after it.
implementation blueprint
The agent is only useful if it is connected to the way your agency already plans trips. We implement it by grounding the AI in trusted records, wrapping it in approved planner actions, and generating client outputs from the same live itinerary.
Bring departures, contacts, trip segments, vendors, reservations, routes and document templates into one trusted model. In the Off the Beaten Path build, Salesforce stayed the source of truth; the same pattern works when your agency has a clean CRM plus connected operational data.
Turn the way senior planners already work into explicit tools: find lodging, check gaps, add a reservation, map a route, write a segment narrative and generate a client proposal. The agent does not improvise outside those tools.
High-impact actions use review screens and confirmations. Meera can recommend vendors and prepare records, but a planner approves the change before it writes back to the system.
Start with a small set of representative trips, tune the prompts and guardrails with planner feedback, then expand to more destinations, document types and operating rules as the team trusts the workflow.
what we built
Not a generic chatbot bolted onto a CRM — Meera is grounded in Off the Beaten Path’s own data and their own proven booking process, on the platform they already run on.
Meera, the in-app AI assistant, builds the itinerary with the planner. Ask her to rough out a multi-leg skeleton or add lodging for a segment; she searches Off the Beaten Path’s own inventory, proposes options as interactive cards, and — only after the planner confirms — writes them to Salesforce.
Segments, lodging, activities, guides, meals, transport and travel days laid out by the day on a single Gantt. A missing night’s lodging or an orphaned activity is obvious at a glance — no scrolling through records to reconstruct the plan in your head.
Search the team’s curated destinations and vendors — lodging, activities, guide services, meals, transport — and watch them drop onto the map as you plan. The knowledge that used to live in senior planners’ heads is searchable for everyone.
Guidebook, Travel Brief, trip descriptions, final covers, participation summaries, evaluations — generated from the live trip data instead of rebuilt by hand in a separate document every time the plan changes.
Nothing lives in a side document. Every change a planner or Meera makes is written straight back to Salesforce, so operations, finance and the rest of the team are always looking at the same trip.
Meera reuses the same validated booking flows the team already trusts. She shows an ID-free summary before she changes anything, waits for an explicit yes, and never invents a vendor, price or date — she only uses what’s really in the system.
meet meera
Ask Meera about the trip and she calls real tools, reads the live Salesforce records, and answers — then helps you close the gaps. She proposes, you confirm, and only then does anything get booked. These are real conversations on a live departure.
the narrative agent
Booking is only half the job. Meera’s dedicated Narrative agent writes the trip’s story. On a node-per-segment canvas, each leg gets an evocative, on-brand narrative generated from the trip’s real structure — ready to flow into the guidebook and proposal.
Generate it, read it, regenerate it. The words come from the same live departure the planner just built — never a blank page.
one-click documents
When the trip is built, the working documents are one click away — guidebook, travel brief, trip descriptions, summaries — generated from the same live data the planner just worked on. No copy-paste, no stale Word file, no version that quietly drifts from what’s actually booked.
Generated from a single departure:
the client proposal
One click turns the live trip into a branded, web-based lookbook — a cover, a note from the designer, a trip overview, a day-by-day journey, pricing and inclusions, and an Accept proposal button. It’s responsive across desktop, tablet and phone, exportable to PDF, and published to a private link that expires.
Because it’s generated from the same departure, it never drifts from what’s actually booked — the client opens a polished document, not a heavy email attachment.
why it works
The reason this is useful and not a novelty is that she’s grounded in Off the Beaten Path’s real inventory, real booking flows and real Salesforce records. Meera is scoped to safe, reviewed actions; the work is documented and source-controlled; and the people who run the org day to day can keep extending her after we’re gone.
That’s how we build everything: on solid foundations, handed off cleanly. If you run a travel business and the planning lives in your team’s heads and a pile of documents, we can build the same kind of workspace on top of your data.
for travel teams
Tell us how your team plans trips today: where your vendor knowledge lives, what your planners approve, and which client documents you need. We’ll map the first version of an agent on your own data.