The operation this was built inside.

Guesty, plus a Google Sheet the whole team edited at once. The PMS held the bookings and took a percentage. The spreadsheet held the cleaning rota, the key handovers and the deposit returns: the things that actually decide whether a Tuesday goes well. And the leases lived in a Word template, filled in by hand, emailed out, signed with a photograph, and filed in whichever inbox received them.

None of that is unusual. It is what nearly every mid-term operator is doing right now, because the software market is built for a different business and the gap gets filled with whatever is to hand.

The spreadsheet. Not dramatically. It just became the system of record for things the PMS did not model, which meant it could not be wrong and could not be checked. Two people editing it at once is a normal Tuesday. A cleaning missed because a booking moved and the sheet did not is also a normal Tuesday.

The second thing was the paperwork. A tenancy agreement signed by photograph is fine right up until a deposit is disputed eleven months later, at which point what you need is proof of who signed what and when, and what you have is an email thread.

The operations board replaced the sheet, not by importing it but by deriving it. Today’s check-ins, check-outs and cleanings are computed from the reservations, so a booking that moves takes its cleaning with it and there is nothing to keep in step. What staff add on top is only the decisions: who is doing it, at what time, and where the key is.

The Word template became a real template. A lease is now drafted from the reservation, sent when someone presses Send, signed in a browser, and filed against the tenancy with a record of who signed it, when, from where, and a hash of exactly what they signed.

And the website stopped being a separate universe. It reads published snapshots through the API, so a half-finished edit is never live. Availability is always current, because a booking taken thirty seconds ago has to block the site immediately.