I build operations systems for guest houses, boutique hotels and serviced apartments: bookings with channel sync, housekeeping boards, folio billing, OTA reconciliation and owner dashboards — sized below the enterprise property-management tier.
What does a small hotel’s day actually look like?
Bookings arrive from three directions — OTAs, the phone, walk-ins — and collide into the overbooking that happens roughly one Sunday a season. Housekeeping status is shouted down corridors and remembered wrong at least once a day. Extras leak off folios: the kitchen order, the laundry, the late checkout that someone waived verbally and nobody recorded. And OTA commissions are accepted as billed, because reconciling a platform’s maths at month-end is nobody’s idea of a Tuesday.
Meanwhile the enterprise property-management vendors want enterprise money for software built around revenue managers and rate-parity strategies you do not have staff to run. So the register wins by default, and the register costs you weekends.
What does the system cover?
- One booking board. Every source on one calendar, so double-booking becomes structurally difficult rather than a recurring apology.
- Channel sync. Availability pushed to OTAs; where you already run a channel manager, I integrate beneath it rather than replacing what works.
- Housekeeping. Room status board, cleaning checklists and maintenance tickets, updated from the phone by the people doing the work.
- Folio discipline. Room, extras and taxes per stay, so checkout takes minutes and nothing is forgotten at the counter — which is where most small-property revenue quietly disappears.
- OTA reconciliation. Payouts against bookings against commission, per channel, with the mismatches surfaced rather than absorbed.
- Owner view. Occupancy, average rate and collections, from a phone, because owners of small properties are rarely at a desk.
The two numbers that change behaviour
Occupancy by day of week, over a season. Most small properties know they are busy at weekends and quiet midweek, but not by how much, and not consistently enough to price for it. Once that is a chart rather than a feeling, midweek offers and corporate tie-ups stop being guesses.
Revenue per stay, not per room. The extras — F&B, laundry, late checkout, airport pickup — are where a good property separates itself from a cheap one, and they are exactly what falls off the folio when checkout is rushed. Properties that start measuring revenue per stay usually discover the gap is larger than their entire OTA commission bill, which reframes what the operational fix is actually worth.
Related reading
/industries/restaurant — the attached F&B operation · /industries/travel — agencies and tour operators booking into you · /products/whatsapp-automation — booking confirmations and pre-arrival messages · /industries/catering — banquet functions
The Saturday question
How many times last season did you apologise for a room you had already sold? If the answer is more than zero, that is a calendar problem with a known fix. /contact — atithi devo bhava; double-booking devo nahi.
Questions I actually get
Is a six-room guest house too small for this?
No — small properties are a core use case and priced accordingly. The enterprise property-management vendors price for hotels with revenue managers on staff; the register prices your weekends. This sits deliberately between, and a six-room operation gets the booking board and folio discipline without the enterprise rollout.
We already use a channel manager.
Keep it. I integrate underneath rather than rebuilding it — channel managers do their job well, and replacing working software is rarely the value. The gap is usually what happens after the booking lands: housekeeping, folios, extras and reconciliation.
How does OTA reconciliation work?
Payouts matched against bookings against commission, per channel, per cycle, with mismatches queued. Commission deductions are almost never verified by small properties because the maths is tedious, and tedious is precisely what software is for.
Can it stop overbooking?
Yes — one calendar holds every source: OTA, phone, walk-in and direct. Overbooking becomes structurally difficult rather than a thing you apologise for on Sunday mornings. That single change is the most common reason owners adopt it.
We have a restaurant attached.
Room charges and F&B post to the same folio, so room 12's dinner lands on room 12's bill without anyone remembering to tell the front desk. The restaurant side is covered in depth on its own page.
What about housekeeping?
A room-status board with checklists and maintenance tickets, updated from a phone by the staff who actually clean the rooms. Status stops being shouted down corridors, and a room's readiness becomes a fact the front desk can see rather than ask about.