Odia

The shared premise

The human moat is the product architecture.

You framed AI as a way to protect relationship and experience. Odia takes that thesis one altitude down, into the workflow of a DMC.

Same idea, one altitude down A working system for keeping humans in control.
01Founding choice
Built operator-first, for boutique DMCs.

The automation guards the supplier, agent, and traveler relationships that big platforms cannot own.

02Live
Human-in-the-loop is engineered, not sloganized.

Review gates, classifier thresholds, and metered model calls keep every AI move accountable.

03Live
AI sits inside one live Journey.

Email triage, imports, service drafts, and margin work happen where the trip already lives.

04Live
Re-entry is the first thing removed.

A link or PDF becomes a priced service draft, while the operator keeps judgment, taste, and approval.

Odia | Relationship system 01
Odia

Where we are taking it

The swarm needs one control surface.

A move from anyone should update the trip, the margin, the itinerary, and the AI companion through one human-approved record.

The live Journeyone trip record
Supplierbumps a room rate
Travel agentasks for later checkout
Travelertexts a late arrival
DMC, youswaps in a better hotel
Itinerarydocuments update
AI companionre-plans the day
Memoryremembers the spa
Price and margincut kept clear
Honest line: some of this runs today. The coordinated agent layer is the roadmap, kept gated, metered, and human-approved.
01 02