/ Insights
Writing on the systems, dashboards, and AI workflows that make hospitality data legible. Written by operators, for operators.
Hotels pace rooms to the dollar and let catering revenue run blind until the month closes. Here is how operators build a catering pace curve, what to measure, and why the data never connects.
Hotel automation that bolts onto a broken process just runs the mess faster. The discipline is to map and fix the workflow first, then automate what is left.
Operators are drowning in AI demos that die on contact with a real property. The fix is not a strategy deck, it is one use case that survives Monday morning.
Classic menu engineering only works on clean POS data, and Toast data is rarely clean. Here is a playbook to fix the source first, then run real menu engineering an operator can trust.
Most hotel labor models break the moment demand moves. Here is how operators build a labor model that flexes to forecasted occupancy and covers, and the signals that keep it honest.
Five PMS fields that quietly corrupt every revenue report, why your team works around them, and the governance fixes that actually hold up under audit.
Most hotels build a comp set once and never revisit it, then read STR and Lighthouse reports against the wrong set and price off a distorted index. Here is how a hotel comp set goes stale, what a defensible one looks like, and why it is an operator problem.
Most hospitality data platform projects fail before they ship: scope creep, definition drift, no adoption, stale before launch. Here is the phased rollout that proves value in weeks instead.
Most hospitality dashboards quietly die ninety days after launch. Here is what actually kills them, and what we build instead to keep operators using them.
Build vs buy hotel software is a false binary. The third option is build-with-a-partner: a connected intelligence layer on the systems you already own. When each of the three is right, including when to just buy.
When packaged software wins, when a partner wins, and the four questions a CFO or asset manager should answer in writing before any vendor call or SaaS contract.
Data implementation best practices for hotel groups, from the operator's chair. Seven real mistakes operators make on data and BI projects, why they happen, and the fix for each.
Most hospitality data strategy lives in a forty-page deck that dies in a drawer. Here is the one-page version that answers four questions and actually changes how the building runs.
Hotel data governance is not a compliance project. It means one definition per metric, one owner per source, rules for how codes get used, and an audit trail that holds up in front of an owner.
A teardown of the hotel KPI dashboard a multi-unit operator actually reads by 8am. The handful of numbers a COO needs, and the forty widgets to leave off.
Most hotel ownership reviews open with a sixty-slide deck nobody trusts. Here are the four reports a hotel ownership review should actually start with, and what each one has to contain to be believed.
Hotel ownership reporting almost never arrives clean. When you acquire a property or a portfolio, you inherit the operator's systems and definitions. Here is the gap between what an owner needs and what an operator hands over.
RevPAR vs GOP is the gap that defines an operator's year. Here is why top-line RevPAR climbs while profit stays flat, and how to manage the whole-P&L operating number instead of the headline.
The hotel flash report operators run the building on is often wrong or stale. Here is why the numbers drift, why operators trust it anyway, and what a flash report that tells the truth actually requires.
A COO owns the whole hotel P&L but gets five different answers to the same question. Here is why your systems never reconcile, what it costs, and how to build a hotel single source of truth without ripping anything out.
Hospitality data is not one thing. It is the operating reality of a hotel scattered across seven systems that do not talk. Here is what hospitality data actually is from the operator's seat, and why it is a connection problem, not a collection problem.
/ Subscribe
A short note via the contact form is enough — mention "Insights" so we know to add you to the list.
