A working chef weekend at Horan House. Quinten breaks down a 280-pound heritage hog. You eat, drink, and go home with terrines.
Auto-personalized. You approve before it sends.
All three confirmed within 36 hours. The math worked: Pete brings the room, the room covers Pete. He stays free.
Auto-stitched across WhatsApp + iMessage + Email so everyone sees the same conversation.
Pete made one ask. Three friends said yes. Guesthouse acquired four guests at the cost of one stay credit — and got a story Pete will tell at the next dinner he hosts.
"Network-trophy" made tangible: each Together Stay is a graph of N+1 relationships, and the next host is already in the room.
Friday June 13 → Sunday June 15. No agenda except hot tubs, long walks, and the chef's discretion. You're paying full rate today. The math gets better with every yes.
Adapts to the channel. You always edit before send.
Replies stitch into one thread. You see them all in one place — no checking five apps.
A four-bedroom mountain house built for the gathering economy. Chef-led. Captain-run. Designed for the weekend after which everyone says "we should do that again."
A theme is more than a name — it sets the menu, the partners, the tempo. Quinten's menu changes by theme. Bex's guides change by theme. The house bends to the gathering, not the other way around.
Pick dates. Name a theme. Invite three friends. Pricing scales as they say yes.
Property economics match a standard 4-guest booking. When the host stays free, the room they'd have paid for is the cost of the introduction they made — and the friends they brought are next month's hosts.
Open question: when host stays free, does the property absorb or does OPCO subsidize? Affects how this gets pitched to property partners.