Running IT in a smart hotel

Coordinating the IT infrastructure of a smart hotel from scratch is one of those projects where there isn't one hard technical problem — there are a hundred medium ones tangled together.

Papago Motor Hotel wasn't a normal hotel. The premise: a guest could arrive, stay and leave without talking to anyone. That sounds pretty in a slide and vicious in implementation.

The pieces

• Check-in robots programmed to handle the automatic check-in flow
• QR system in every room for services, controls and payments
• Internal network with isolation policies between IoT and guests
• Backend orchestrating reservations, payments, access, maintenance

Each piece was manageable on its own. The real work was making them talk to each other without ever locking a guest out due to a sync error.

Autonomous check-in

The robot greets the guest, validates the reservation, hands them digital access to the room's QR, explains how everything works, and says goodbye. It has to handle exceptions: someone without a reservation, someone with a pending payment, someone who arrived with a larger group than expected.

Designing for the happy path is easy. Designing for the 47 unhappy paths is the job.

What I took away

• In hospitality, technology is either invisible or useless
• Coordinating teams (front desk, maintenance, IT) is 60% of the work
• The difference between a system that works in a demo and one that works in production is the 45 days of post-launch iteration

Papago taught me to respect the operational complexity of a physical business — something no pure SaaS will ever teach you.