One operating system for the front desk, the rooms and the restaurant
A hospitality operating system holds the whole property in one record: who is arriving, which rooms are genuinely ready, what was eaten and drunk, and what is owed by whom. Most lodges and guesthouses here keep those four things in four places — a reservations diary, a clipboard in housekeeping, a till in the restaurant, spreadsheets in accounts — and the gaps between them are where double bookings and unbilled meals live.
The problem is not the diary. It is the handover.
Nobody loses money because a booking was written down. They lose it at the handovers: the room the desk sold because the housekeeping sheet had not come back, the lunches signed to a room that never reached the folio, the corporate invoice raised from memory a week after check-out. One shared record removes those gaps, and each department reads its own view of it.
Built for how African properties actually trade
A lodge in Harare does not trade like a hotel in Frankfurt. You quote in United States dollars and take local currency at the desk, settle by mobile money as often as by card, and hold corporate and NGO accounts on terms beside walk-in tourists paying cash. The rate engine carries resident, non-resident, corporate, agent and group rates against the same room, so nobody does arithmetic under pressure.
Housekeeping and the front desk finally agree
Room status is the most expensive piece of information in a property, and it usually travels on paper at walking pace. Housekeepers update rooms from a phone — dirty, cleaned, inspected, out of order, maintenance flagged — and the desk sees it change as it happens, so late arrivals go into rooms that are genuinely ready.
The restaurant, bar and stores sit on one ledger
Orders taken at the table post to the guest folio or settle at the till, so charging to a room is a tap rather than a chit that may never reach reception. Recipes draw down stock as dishes sell, which turns the bar count from an argument into a variance report. Where cameras already cover the stores, computer vision can evidence deliveries rather than leaving them to be debated.
It has to work when the power and the line do not
Anything that stops taking check-ins during a power cut is not an operating system, it is a website. The property runs on equipment on site, so the desk and housekeeping keep working while the connection is down, then reconcile when it returns.
Highlands House
Highlands House is a boutique guest lodge in Harare with thirty-six en-suite rooms, gardens, a pool and a garden restaurant, and the Hotel OS build there is in progress. It has the shape that makes this work interesting: rooms and a restaurant sharing guests, grounds needing access control, one owner wanting one view.
What it covers
Reservations and availability
One calendar across rooms, room types and rate plans, carrying holds, deposits, group blocks and cancellation terms. Website enquiries, walk-ins, agents and repeat guests land in one place.
Enquiries over WhatsApp
Guests here enquire on WhatsApp, at night, and expect an answer. An AI agent handles availability and rates, then hands anything unusual to a person with the conversation attached.
One folio, one bill
Room, restaurant, bar, laundry and extras post to a single folio, so check-out is a statement rather than a reconstruction. Company and guest splits are set at check-in.
Housekeeping on a phone
Room status, task lists, linen and minibar consumption and maintenance faults are captured by the person doing the work, on the handset in their pocket.
Gate, access and attendance
Movement through the gate and back-of-house doors can run on access control and number plate recognition using cameras already on site, and that clock-in record feeds payroll.
The owner's view
Occupancy, rate, revenue by department, debtors and stock variance in one place on a phone, without waiting for month end.
How it works
Site assessment
In week zero we walk the property — reception, back office, housekeeping store, kitchen, bar, gate — and document what you already run: the diary holding bookings, the till, the cameras, the network, the power arrangement.
Integration
Over weeks one to three we connect what exists rather than replacing it wholesale: booking history, rate cards, room inventory, point of sale, accounting and gate hardware. The system mirrors your live operation before it is allowed to act.
Rules and guardrails
In week four we set the rules that make it yours: who may discount and by how much, how a charge-to-room is authorised, when a booking is released, what escalates to a duty manager. These are tested against your real bookings.
Go live and optimise
From week five the property runs on it, with staff trained on their own screens and a weekly review while it settles. A first system typically takes four to six weeks.
Questions buyers ask
Do we have to throw out the system we already use?
No. If your reservations system or restaurant till works, we integrate with it and fill the gaps around it — usually housekeeping, folios and reporting first. Replacing it is a decision you take later, on evidence.
Will it work during a power cut or when the internet is down?
Yes. It runs on equipment on site, so check-in, restaurant orders and housekeeping updates continue while the link is down and reconcile when it returns. We plan for that at the site assessment.
Can it produce tax-compliant invoices and statements?
Yes. Folios, receipts, credit notes and statements come from one ledger in the formats your accountant and the revenue authority require, including multi-currency settlement and accounts on terms.
We are a small lodge, not a hotel group. Is this too much for us?
Scope follows your bottleneck, not your room count. Many properties start with one piece — WhatsApp enquiries, or housekeeping and folios — and add departments once that is earning its keep.
Who owns the guest data, and where does it live?
You do. It runs in your environment or a dedicated tenant, with a retention period agreed in writing, and access is controlled by role. The system acts only on verified information and escalates anything uncertain to a named person rather than guessing.
Book a platform briefing
Fifteen minutes with an engineer, not a sales pitch. Tell us how your property runs today — how bookings arrive, how rooms are handed over, how the restaurant bills — and we will tell you what is worth automating first and what is not. Email sales@eigenstatesystems.com or WhatsApp +263 77 636 6999.