The hospitality CRM is usually a downstream copy of guest state, refreshed nightly from the POS, the bookings system, the Wi-Fi sign-up. Cohorts are built over yesterday’s snapshot. Attribution stops at the campaign send. The marketer is one step behind the floor.
Stampede inverts that. The CRM reads from the same graph the floor writes to. A segment built at 2pm reflects state from 1:59pm. A campaign send creates open and click edges that the floor team can see when the same guest walks in for dinner. Attribution rolls up the graph — campaign sent, campaign opened, guest visited, guest spent — in one traversal.
Segments without SQL
Building a segment is asking the assistant. "Lapsed VIPs in Soho who haven’t visited in 90 days, ranked by lifetime value" is a Segment node in five seconds. The query runs on the live profile; the segment is a saved query that re-evaluates on every read.
From there, campaigns and workflows attach to the segment. Drafts arrive in the venue’s tone of voice; personalisation pulls from the live profile, not from a flat export. The marketer approves; the floor sees the response within minutes.
Attribution that means something
Last-touch attribution dies in hospitality the moment a guest walks in without clicking a link. Stampede attributes off the graph: campaign sent → opened → walk-in within attribution window → spend recorded. The full chain, on the same record.
Start at /docs/operations/marketing for the console and /docs/guest-profile/segments for the segment model.