01Founding choice
"human relationship"
Odia is built operator-first, for boutique DMCs. The automation guards the relationship instead of standing in for it.
The shared premise
The keynote gives the language. Odia gives it a system.
The deck needs to show the actual bridge: each keynote line has a corresponding product decision in Odia.
Same idea, one altitude down
The analogy is strongest when quote and shipped surface sit together.
02Live
"supercharge humans"
Human-in-the-loop is engineered with review gates, classifier thresholds, and metered model calls.
03Live
"not an IT project"
AI sits inside the live Journey: email triage, imports, service drafts, and margin work happen in the trip record.
04Live
"bad at and dislike"
Odia removes re-entry first: a link or PDF becomes a priced service draft while the operator keeps judgment.
Where we are taking it
The AI Swarm needs one human-approved surface.
The keynote names a mesh of specialized bots. In Odia, the control surface is the live Journey: shipped assists today, a gated agent layer next.
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
Human Moat line: more memorable, more meaningful, more personal, more human. Honest line: the agent layer is roadmap.