Hotel systems, operations & data
How modern hotels actually work — and how their systems should be designed.
Placeholder introduction. Long-form essays on operations, data, and automation in hospitality. Written for people who build, buy, or run the systems a property depends on.
Featured essay · No. 01
Systems Thinking
The Property Is the System
Placeholder deck — a hotel is not a building with software attached; it is a system of constraints that software either respects or fights.
14 July 2026 · 12 min read
Recent
All essaysThe Data Layer
Where Hotel Data Goes to Disagree
Placeholder deck — the PMS, the channel manager, and the CRM each hold a different truth about the same guest. That is a design outcome, not an accident.
9 min read
Automation
Automation Is an Operations Decision
Placeholder deck — most automation projects fail as process design long before they fail as technology.
11 min read
Field Notes
The Night Audit as a Diagnostic
Placeholder deck — the most revealing hour in a hotel is the one where nothing is supposed to happen.
6 min read
Systems Thinking
Integrations Are Organisational Contracts
Placeholder deck — every API between two vendors encodes an agreement between two departments that may never have spoken.
10 min read
Series
Placeholder — essays are organised into a growing body of work rather than a feed.
Systems Thinking
4 essaysPlaceholder — how the parts of a hotel constrain each other, and why local fixes create global failures.
The Data Layer
3 essaysPlaceholder — reservations, profiles, rates, events: where hotel data actually lives and why it disagrees with itself.
Automation
3 essaysPlaceholder — what should be automated, what must stay human, and how to tell the difference.
Field Notes
6 essaysPlaceholder — short observations from property floors, night audits, and integration post-mortems.