Most hotel tech companies start with small hotels. They are easy to reach, the owner picks up the phone, and a 20-room property looks like a simpler job than a 300-room one. Fewer rooms, fewer users, fewer things to go wrong.

The numbers tend to tell a different story. The work a vendor does for an account does not shrink with room count, but the revenue does. That is the cost-to-serve inversion: the smallest accounts on the books can be the most expensive to keep relative to what they pay. Five myths keep it hidden.

Myth 1: Fewer rooms means less setup

The belief: onboarding effort scales with property size. A small hotel has fewer room types and fewer rate plans, so it should go live in a fraction of the time.

What happens: the fixed work stays fixed. Rates still have to be loaded, channels mapped, taxes configured, payment details connected and staff trained, whether the property has 15 rooms or 150. The difference is who does it. A larger hotel has a revenue manager or a front office manager who owns the project. At a small property the owner is also the general manager, the reservations desk and the IT department, so the vendor's team ends up doing the work on both sides. I covered what that means for implementation in designing onboarding for properties with no IT staff.

Myth 2: One decision-maker means a fast sale

The belief: a single owner can say yes in one call, with no procurement process and no committee.

What happens: one decision-maker means one very busy person spending their own money. The owner of a small hotel takes your call between check-ins, misses the follow-up because a boiler failed, and delays the decision until the season ends. The personal financial risk also makes them cautious, not quick. The sale takes fewer meetings than a group deal, but it is rarely short, and it still needs a person on your side to chase it.

Myth 3: Support load follows room count

The belief: a small property generates a small number of tickets.

What happens: support demand follows the experience of the people using the software, not the number of rooms. Small hotels rely on part-time and seasonal staff, they retrain often, and there is nobody in-house to answer the basic questions. That turns your support desk into their training department. It is the pattern described in the front desk turnover problem nobody prices in: each new starter relearns the system through your team. The result is frequent, simple, urgent contacts, often by phone, from the accounts paying the lowest fees.

Myth 4: Low price means low touch

The belief: a low monthly fee can be matched with a self-serve motion, so acquisition and service costs fall in line with the price.

What happens: small hoteliers do not buy like software buyers. They want to see the product with a person, call a number when something breaks and know who is responsible. Vendors who plan for self-serve and then add demos, calls and hand-holding to close deals end up with enterprise effort on small-business pricing. The price went down. The touch did not.

Myth 5: Small hotels churn over price

The belief: when a small property leaves, it found something cheaper.

What happens: many small-hotel losses have little to do with the product or its price. Properties change hands, close for the season and never reactivate, or lose the one employee who knew how to use the system. These events hit small properties harder because there is no second user, no documentation and no head office to keep the account alive. Cutting the price does not address any of them.

The inversion, side by side

None of this is an argument against serving small hotels. Strong hotel tech businesses are built on them. It is an argument against serving them by accident, with a model designed for bigger accounts.

What to do if small hotels are your market

1. Measure cost to serve by segment. Add up onboarding hours and support contacts per account for small, mid-size and large customers, and set them against the revenue from each group. Most teams have never seen this number.

2. Standardise the setup. Build templates for the common property types so that going live means choosing a configuration, not building one.

3. Price the work in. A setup fee, a minimum plan or paid assisted onboarding makes the fixed work visible. The trade-offs between models are in per room, per property or flat pricing.

4. Train the role, not the person. Short, repeatable training that a new receptionist can complete alone reduces the support load that staff turnover creates.

5. Decide who you are for. If small hotels are the segment, design the whole business around their economics. If they are not, stop taking them on as a side effect of having no filter.

The takeaway

Small hotels are not simple accounts. They are accounts where the vendor does more of the work for less of the revenue, and where the reasons for leaving sit largely outside the product. The companies that do well with them know their cost to serve and have built pricing, onboarding and support around it.

If you want to see where that cost is showing up in your own numbers, the 12-point leak audit takes about twenty minutes and covers demand, conversion, activation and retention.

Frequently Asked Questions