Occupancy and Revenue Intelligence
A hotel already running a booking system — the Hotel Operations Command Center, a third-party product, or a spreadsheet exported monthly — whose owner cannot answer basic commercial questions without someone spending an afternoon.
The problem
The data exists. Nobody can read it. Decisions about rate, channel mix and staffing are made on impression.
In scope
- Data ingestion from the existing source
- Metric definitions agreed with the owner
- Dashboard
- Scheduled reports
- Alerting on thresholds
Out of scope
- Changing or replacing the source system.
- Automated pricing decisions — this system informs a rate decision, it does not make one; automated revenue management on a single property's data would be overselling.
What this would cover
Grouped by module — open the ones you want to read.
Ingestion
- Connection to the booking system's API, database, or scheduled export
- Handling the reality that historical data is usually incomplete
Metric layer
- Occupancy, average daily rate, revenue per available room, length of stay, lead time, and cancellation rate
- Each metric defined once and agreed in writing, so two reports never disagree
Dashboard
- Current position
- Same period last year
- Pace for the coming weeks
Channel analysis
- Revenue and volume by source, net of commission — the number that changes behaviour
Alerts
- Occupancy below threshold for a forward date
- Unusual cancellation volume
- Rate parity breaches across channels
Scheduled reporting
- Weekly and monthly cadence
- Delivered by email or message rather than waiting to be opened
Data model
- SourceConnection
- MetricDefinition
- Snapshot
- Alert
- Report
Invariants
- This system is read-only over the source system — it never writes back.
- Metric definitions are versioned; a changed definition creates a new version rather than silently rewriting history.
- Every figure on the dashboard can be traced to its source rows.
Offline behavior
Not applicable. Reports are delivered to where the owner already reads messages, which matters more than dashboard uptime.
Hard trade-offs
The difficult decisions, stated plainly — not trimmed for length.
A reporting layer cannot fix bad source data, and this is where these engagements disappoint.
If bookings were recorded without a source, channel analysis is impossible. Phase 1 assesses what the existing data can actually support and says so before anyone commits — which occasionally means recommending the Hotel Operations Command Center instead and not selling this at all.
End state
What would be true about their day once this is running.
- The owner opens a dashboard instead of asking three people.
- Channel cost is visible net of commission.
- Forward pace is known early enough to act on rather than after the month closes.
Let's map how your operation actually runs.
One session. We look at what's breaking, and what we'd build around it — whether or not you hire us afterward.
Start the operations review