Thread - HospitalityOS

Thread — the autonomous multi-agent operations brain for luxury hospitality. The problem: Luxury hospitality runs on context , who the guest is, what they prefer, which property they've stayed at before, how their day is unfolding. Today that context lives in a dozen disconnected systems (PMS, CRM, restaurant POS, valet log, spa booking, concierge notebook, flight tracker) and a hundred staff brains. When things go right it's because someone in the back office stayed an extra hour. When things go wrong, three preventable failures cost real revenue: 1. Booking-funnel revenue evaporates. A guest fills the cart, opens payment, looks at the room one more time, then closes the tab. Nobody at the property knows it happened — there's no concierge capable of calling within 90 seconds to recover the booking. Hotels typically lose 60–70% of started bookings to abandonment. 2. Operational shocks aren't orchestrated. A flight delay cascades into a rebooked dinner, a reshuffled cab pickup, a stale turn-down schedule, and a confused front desk. Every department learns about it separately, by phone, after the fact. 3. Arrivals feel generic. A returning guest checks in and the desk agent reads their name off a screen. Nothing about their last stay, their pronunciation, their preferences, or the gesture the property sent them last December is at the agent's fingertips before the guest finishes saying "Hi." The solution: Thread is two surfaces over one nervous system. An operator dashboard (Reception, Live Dashboard, Operations, Investor Metrics) shows every event animated into the UI in milliseconds. A booking clone demonstrates the recovery cascade on demand. Underneath sits a multi-agent fabric — nine specialist agents (Conductor, Booker, Reception, Outreach, Memory, Brief, Housekeeping, Maintenance, Concierge) gossiping over a single event bus and reaching the outside world exclusively through MCP tools.

Team

Placement

Participant