Built for boutiques. Made to scale with groups.
HotelThread is live with independent and boutique hotels today. We're building the multi-property layer now — with a small group of founding partners shaping it. If you run five or fifty properties, this is the moment to get in early.
Mae runs on WhatsApp for independent hotels, with the Now dashboard, staff app and direct-booking microsite in pilot. This is real, and it's working at single-property scale.
The portfolio layer — multi-property access, group briefings, consolidated insights — is in active development. We'd rather build it with a few founding groups than guess.
A plan, not a contract — shaped with our founding partners. We don't publish dates we can't keep.
Portfolio briefing
In designOne briefing per property, and a single portfolio read for the owner — the morning across every hotel in a couple of minutes.
Multi-property access
PlannedOne identity across the group, role-scoped per property, with SAML / OIDC for your IT team.
Group brand standards
In designSet Mae's voice and escalation rules at group level. Properties inherit the defaults; GMs keep room to adjust.
Consolidated insights
PlannedDirect-booking share, commission saved and guest sentiment, rolled up across the portfolio with per-property drill-down.
- — Early-stage. We don't hold SOC 2 yet, and we won't pretend otherwise.
- — Data-minimisation by design — we ask for what Mae needs, nothing more.
- — Consent receipts and an audit trail are built into the design from the start.
- — A SOC 2 path and a Data Processing Agreement as we move from pilot to production.
- — Region-pinned data residency, agreed with you before any production data flows.
- — A sub-processor list you can review — open line to our team, any time.
Help shape HotelThread for groups.
A handful of founding partners, founder-led onboarding, and a say in what we build next.