Product in Public
We're building this openly. Not because transparency is trendy, but because:
- The problems are real and shared across the industry
- The solutions need input from venues, agents, and travellers
- Trust requires legibility
When we don't know something, we say so. When our thinking changes, we update it.
Jobs to be Done
We use Jobs to be Done (JTBD) as our product framework. The idea is simple: people don't buy products, they hire them to do a job.
A traveller doesn't want "an AI agent" - they want to find somewhere that fits their occasion. A venue doesn't want "structured data" - they want to be found by the right guests.
By focusing on jobs rather than features, we stay grounded in real outcomes. The specs exist to answer these jobs. The product exists to make those answers accessible.
The JTBD approach
- Identify the job someone needs done
- Understand it from multiple perspectives (traveller, venue, agent)
- Design infrastructure that serves all perspectives
- Validate by asking: does this actually help get the job done?
What's here
Core Jobs
The fundamental jobs in any booking: finding, matching, trusting, booking, paying, tracking.
Ecosystem Jobs
What curators, enterprise partners, and builders need from the infrastructure.
How it connects
Jobs (WHY) → Product (WHAT) → Specs (HOW)
─────────────────────────────────────────────────────────────
Finding → Echo, Catalog → Venue, Curator
Matching → Vibe, Fit → Bookable.fit
Trusting → Evidence → Bookable.evidence, Curator
Booking → SDK Actions → Stay
Paying → Wallet → Folio
Tracking → Wallet history → Stay, Folio
This section explains why. The docs explain what we built. The specs explain how the protocols work.
The specs refer to the Agentic Booking specification—an open standard for AI agent discovery and booking in hospitality. It extends A2A and UCP with hospitality-specific vocabulary.