Who they are — and why the stack looked the way it did
This group built its portfolio through acquisitions over a decade. Each deal came with a PMS contract, a channel manager, sometimes a separate revenue spreadsheet, and local habits for how BAR was set. On paper, every property was “on systems.” In practice, the portfolio had no single place where pace, restrictions, and overrides lived with an audit trail.
General managers are capable people; they were stuck being integration glue. Monday revenue calls started with “which export is correct?” instead of “what do we do about compression next weekend?” Owners saw strong properties and weak properties but struggled to tell whether gaps were market-driven or discipline-driven.
The hidden cost: time, not subscription fees
License costs were visible on invoices. The larger tax was managerial time: copying occupancy into spreadsheets, screenshotting comp sets from different tools, and reconciling ADR after OTA promotions. One GM estimated she spent two full workdays a month just preparing numbers for ownership — before discussing strategy.
Fragmentation also hid bad habits. A property could undercut the portfolio’s brand positioning on shoulder nights because nobody saw the full picture until the monthly rollup. Another held rates flat during local events because the “events calendar” lived in someone’s inbox.
What they decided “success” would mean
Leadership framed the project in three outcomes, not feature checklists:
- One source of truth for rates, restrictions, and pickup versus same time last year.
- Documented governance: who may override floors and ceilings, and when.
- A weekly operating rhythm that did not require a dedicated revenue scientist at each hotel.
They chose HotelSystems because it could span commercial and operational context without forcing a single “big bang” cutover across all five properties on day one.
Rollout: pilot, then clone with discipline
Weeks 1–3 focused on the largest property — enough complexity to stress-test workflows, not so many rooms that failure would paralyze the brand. Integrations and channel rules were validated there first. Training emphasized a simple cadence rather than every advanced feature on day one.
Weeks 4–8 brought the remaining properties online in pairs. Portfolio-level rules (minimum stays on high-demand weekends, blackout dates for group blocks, brand floors) were configured centrally. Local overrides were allowed but had to be logged with a reason code so leadership could review patterns monthly.
The weekly rhythm that stuck
- Monday: Review next 14–30 days for pickup versus STLY; flag underperforming stay dates.
- Mid-week: Adjust BAR and restrictions for upcoming compression; confirm OTA parity strategy matches net contribution goals.
- Rolling: Same-day and last-minute pickup — authorized tactical closes or opens per playbook, not ad hoc panic.
- Monthly: One honest post-mortem — where money was left on the table, where they overshot, one process tweak.
Early signals (first 30 days)
Before RevPAR moved, quieter metrics shifted. Emergency rate reversals dropped because changes were visible and explainable. Owner questions got faster answers because the trail lived in one system. GMs reported sleeping better — not because the job got easier, but because ambiguity dropped.
Culture shifted slightly: revenue conversations referenced the same dashboard in every market, which reduced defensive debates in group calls.
Commercial outcomes (first quarter)
Versus the same quarter the prior year, portfolio RevPAR rose 18%. ADR contributed more than occupancy: the group captured compression nights with cleaner restriction strategy instead of discounting shoulder nights reactively.
They are explicit that local events and a strong leisure season helped. The durable claim is not “everyone gets 18%” — it is that unified visibility plus governance made it possible to execute consistently across five different general managers.
Lessons for other multi-property independents
- Pilot on your messiest property if you can tolerate the risk; pilot on your largest if you need political cover — but never skip a pilot.
- Write override rules before you turn on automation; otherwise automation amplifies chaos.
- Measure time-to-answer for owner or asset-manager questions — it is a blunt but honest scoreboard for stack health.
What is next for this group
They are evaluating tighter links between commercial decisions and guest-facing messaging so public promises and on-property delivery stay aligned — the same direction Multisystems builds toward across HotelSystems and adjacent products like ReputationSystems.