← the lab

04 / concept

doce concept · no rooms

Twelve rooms running on one system, not five vendors.

A small hotel where the booking, the arrival, the local knowledge and the photographs a guest takes home are the same product. Right now, in almost every hotel this size, they are four different companies meeting at the front desk.

~/lab/doce/README.md
name        Doce
kind        12-room hotel, owner-operated
premise     one guest record, from first click to checkout
enemy       15-20% OTA commission
design      system, grid and voice          (exists)
building    null                            (the whole problem)
status      concept · the least built of the four

The premise

A twelve-room hotel is a software problem wearing a bathrobe.

The rooms are the easy part. What breaks a small hotel is that it rents its own customers from a booking platform, pays fifteen to twenty per cent for the privilege, and never learns anything about the person who stayed, because the platform keeps that too.

Then the property management system is a second vendor, the door locks are a third, the payments a fourth, and the recommendations are a laminated sheet in the drawer that was printed in 2019. Four systems that do not speak, and a person at the desk doing the integration by hand at eleven at night.

The margin lives in the commission you stop paying.

So build the direct channel first and treat everything else as inventory sync. If the hotel's own page is genuinely better than the listing (faster, honest about what the room actually looks like, with a rate that is never worse), then a share of guests book direct, and each one of those is worth substantially more than the same guest arriving through a platform.

And the guest is one record the whole way through. The person who booked in March, asked about the hike, arrived late, and bought a print of the valley on the way out is one person. Twelve rooms is small enough to actually know that, and small enough that the software can be simple.

How it would work

Five parts, one database.

01

Direct booking that is actually better

Real photographs of the specific room you are getting, not a stock shot of the best one. Availability without a loading spinner, a rate guaranteed never to be beaten by the listing, and no account required to book. direct > OTA has to be true on the page, not just in the pricing policy.

availabilityrate parityguest checkoutstripe + payu
02

Channel sync, one direction of truth

The platforms still get inventory, because turning them off on day one is how small hotels die. But the calendar lives here and pushes out, never the other way, so there is exactly one place where a double booking could come from and it is the place you control.

channel managerical/api pushconflict rules
03

Arrival without a desk

A door code that starts working an hour before check-in and stops the morning after, sent by message, with a photograph of the door because the door is always harder to find than the map suggests. Somebody is still there to greet you. They are just not typing your passport number into a terminal while you stand there.

smart lockstime-boxed codesid capture
04

The guide is a product, not a laminated sheet

Where to eat on a Tuesday when the good place is closed, which walk is worth the early start, what the weather actually does in that valley in April. Written by people who live there, kept current, and the single most quoted reason a small hotel gets remembered.

cms-lightseasonaloffline copy
05

What guests take home

The photographs of the place are made properly and sold as prints at the end of the stay, through the same print pipeline as the gallery. A hotel that already knows who you are and what you looked at does not need a gift shop.

print-on-demandshared with reveladopost-stay

Honest inventory

This is the thinnest of the four, and I would rather say so.

The gallery has an archive behind it and the travel company has a map and ten routes. This one has an argument and a design system. That is worth showing and it is not worth overselling.

● exists today
  • The design system. Type, grid, grade and voice, shared with everything else in the lab.
  • The argument. The commission maths, which is the part most small hotels never sit down and do.
  • The print pipeline. Specified once for the gallery and reused here rather than reinvented.
○ does not exist
  • A building. No property, no city, no twelve rooms. Not even a shortlist.
  • Licences and staff. Everything a hotel legally and physically requires.
  • Every line of the software. Booking, channel sync, locks and guide: all described above, none written.
  • Numbers I trust. I have modelled this the least of the four. The deck says so too.

The long version

The deck is being written.

deck · docein progress

The open page stays open. The long one carries the commission maths properly, the occupancy a twelve-room property needs before any of this pays for itself, and an honest note at the front saying this is the least developed of the four.

Open the deck page →

This opens your own mail client with the request written. Nothing is stored on this site and there is no list to unsubscribe from. I read these myself and answer them myself, which also means I am slow sometimes.

Next