Market pulse

The week ahead — computed demand pressure around your venue. What the number above is priced against.
loading market pulse…

What to do next

The playbook — prioritized from your own derived data. Each card: the evidence, the instructions, and an honest dollar impact.
loading the playbook…

Data pillars

Live coverage per evidence pillar, computed server-side. Select one to lens the outcomes.

Guest 360

The person behind the numbers, on their own page.
Guest 360
The enriched person behind the numbers — identity, consent, taste, behaviour.
Open Guest 360 ↗
Relative success is computed server-side, 0–100: ≥70 strong · 40–69 watch · <40 critical. “Thin data” marks low-evidence computes. Every number on this board is computed server-side and fetched live — nothing is hand-entered. The tiles come from GET /v1/insights/outcomes-summary; the demand and pulse panels from /demand-decomposition and /market-pulse; the playbook from /actions; drill-downs from the endpoint each one names. Tiles marked all venues count the whole tenant; a guest, a consent grant and a crew are not owned by a room. What is settled and what is not. Anything marked next 7 nights is projected from a measured elasticity, and the playbook recommends rather than reports. Revenue counts only closed tabs on nights that have finished — tonight is never in it — and its change is stated per settled night, because two windows holding different numbers of settled nights are not comparable: one unclosed tab makes a flat room read −3.3% on window totals. Where a comparison cannot honestly be made the tile says so instead of showing 0%. Two figures here are modelled, not measured, and say so where they appear: the no-show rate is a cancellation proxy, because the schema records no no-show status; and dark revenue is a share of all recorded spend, including tabs still open tonight. Everything else on this board is settled fact.