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 plays, from your own data. Each one: what it is worth and what that rests on, who it is for, and one thing to do.
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, permission to contact, 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 on the server and read live — nothing is hand-entered. Tiles marked all venues count the whole organisation: a guest, a permission to contact 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 effect, and the plays recommend rather than report — every figure on a play is tagged an estimate. Revenue counts only tabs paid 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 do not match: one unclosed tab makes a flat room read −3.3% on window totals. Where a comparison cannot be made the tile says so instead of showing 0%. Two figures here are estimates, not measurements, and say so where they appear: the no-show rate counts cancellations, because no-shows are not recorded as their own status; and dark revenue is a share of all recorded spend, including tabs still open tonight. Everything else on this board is settled fact.