The Six Manual Joins Hiding in Every Reservation

Most operators can name their systems without pausing. Property management system, pricing tool, locks, cleaning app, payments. Four or five, all chosen for good reasons, all doing what they were bought to do.

Far fewer have counted how many of them a single reservation passes through, and what a person has to do at each border. It is worth counting, because that count is where the working day goes.

Follow one booking all the way through

A reservation lands on a channel and drops into your property management system. That part works. It is the one join the software industry has genuinely solved, and it is the reason the rest of the stack feels fine until you look at it closely.

Then:

• The guest gets verified. Usually in a separate screening tool, in another browser tab. The result lives there. Nothing else in your stack can read it.
• The deposit gets held. Taken through a payment gateway, then reconciled by hand against the booking later, often days later, often on a Sunday.
• The access code gets issued. Generated by the lock app on the day, then copied by a person into a message. If the arrival moves, the code and the message move separately, or one of them does not move at all.
• The turnover gets scheduled. Assigned in a cleaning app that cannot see the real arrival time, so the arrival time gets relayed by a person, usually into a group chat.
• The guest gets messaged. Answering questions the booking record already contains. Which house, which code, which rate, whether the late checkout was paid for.
• The owner gets reported to. Assembled from exports that were stale before they were attached to the email.

That is six joins after the first one. Six points where information exists in one system and is needed in another, and the transport mechanism is a person.

The joins are the job

Here is the uncomfortable part. Every one of those tools is good. The lock app locks doors reliably. The cleaning app schedules cleans reliably. The screening tool screens. None of them is failing at what it was bought for.

What none of them does is hand the result to the next one. And that is not an oversight waiting for a product update. It is structural.

Every software company in this market wants to be the system of record. That is where the pricing power sits, where the renewal sits, and where the acquisition multiple sits. No vendor has a commercial reason to build careful, reliable connections into a competitor's product, because doing that well makes the competitor easier to keep.

So the connection never gets built, and the operator becomes it.

What it costs, roughly

Take the messaging join alone. Operators consistently report spending three to five hours a day answering guest messages across channels. Call it four.

4 hours a day
28 hours a week
Roughly 120 hours a month

That is most of a full time role, spent largely on questions the booking record could have answered without waking anyone. And messaging is only one of the six.

The others are quieter but not cheaper. A deposit reconciled by hand is a deposit occasionally not reconciled at all. A code sent late is a guest standing outside a locked door at eleven at night, which becomes a review. A cleaning schedule held together in a group chat is one missed message away from an arrival meeting an unmade bed.

None of these appear as a line on any statement. They appear as evenings.

What to do about it

The instinct is to buy another tool. Usually the wrong instinct, because the new tool will also want to be the system of record, and you will end up with seven.

The useful move is smaller and less exciting. Pick one join. Watch it for a week and write down every time a person moves information across it. Not what the documented process says, what actually happens. The documented process is rarely the process.

Then decide whether that specific handoff is worth connecting. Some are not. A join that happens twice a month and takes four minutes should stay manual, and anyone who tells you otherwise is selling something.

The ones worth connecting share a shape: they happen on every booking, they carry information that already exists somewhere, and getting them wrong is expensive or public. On most portfolios that is three or four of the six, not all of them.

Start with the one that woke you up most recently.