Small Hotel PMS — The Lean Scope for 10–60 Rooms

What does a small hotel need?

A fast core and a channel connection. The desk must find a reservation, check a guest in, post a charge, take a payment and close the day without a specialist.

Which modules are essential?

Reservations, front desk, cashier, housekeeping, night audit, reporting, rate plans and a channel manager. Without the channel manager, the team re-keys OTA bookings and creates availability errors.

What can wait?

POS, membership, procurement and multi-property can wait until the volume or the guest proposition justifies them. The data model should allow them to be added without a second migration.

What does it cost?

A small property pays a room-tier subscription plus implementation, interfaces and training. The exact quote depends on the channel, payment and lock connections. Compare the three-year total.

How long does it take?

A single small property can go live in a few weeks when the interfaces are standard and the data is clean. Training is typically two to four days, with cover through the first week.

Can a lean team run it?

Yes, if the system is designed for a multi-skilled team. One-screen arrival, mobile housekeeping and a guided night audit are not luxuries; they are how a small team survives the shift.

What does a 30-room go-live look like?

Migrate the profiles, future reservations and open balances, and reconcile them before the cutover. A small property still has history and open folios; do not treat the move as a fresh install.

Train the desk on the arrival, the folio and the close, and housekeeping on the board and tasks. Two days by role is usually enough, with a refresher before the first weekend.

Cut over on a quiet day. Run the first night audit with support present, and review the exceptions in the morning. Keep the old system read-only for an agreed period.

Review the first month-end with finance. The measure of success is a clean close and a desk that does not keep a parallel spreadsheet.

What should the first-month review cover?

The first close, the open folios, the rate overrides, the housekeeping exceptions and the channel reservations that needed manual repair.

Ask the desk which workarounds they invented. Those are the next configuration changes, not training failures.

Review the support tickets by theme. A repeated question is a design or training gap, not a user problem.