Pricing in hotel tech gets treated as a number. It is mostly a model, and the model determines which properties you attract, how support costs scale, and whether accounts can grow at all.

Per-room pricing

The default for core systems, for good reasons: it scales with property size, feels proportionate to operators, and is easy to explain in one sentence.

The problem is that room count is nearly fixed. A 60-room property will be a 60-room property in three years. Per-room pricing therefore produces stable revenue and almost no organic expansion.

What that does to retention

SaaS Capital's 2025 retention survey puts median net revenue retention at 102 percent for companies in the 25,000 to 50,000 dollar contract band, with the bottom quartile at 97. If your pricing is purely per-room and you have no second product, you are structurally anchored near the bottom of that range.

No amount of account management fixes this, because there is no mechanism through which a satisfied customer can pay you more.

Per-property pricing

Simpler to quote and easier for a multi-property buyer to model. It also decouples revenue from property size, which helps or hurts depending on where your costs sit.

The risk is mismatch between price and cost to serve. A 200-room property generates substantially more support load than a 25-room one. Flat per-property pricing across both means the large one is served at a loss and the small one subsidises nothing.

It works best where support burden genuinely does not vary with size, which is more common in peripheral tools than in core systems.

Flat and tiered pricing

Attractive for self-serve motions and small independents, because it removes the calculation entirely.

The tier design trap

Tiers built around feature gates train customers to find workarounds rather than upgrade. Someone will always discover that two accounts on the lower tier cost less than one on the higher, and they will tell their peers.

Tiers built around a dimension that genuinely grows, such as properties, users or booking volume, create an upward path requiring no sales conversation and no resentment.

The expansion question underneath all three

Whichever model you choose, ask one question: what has to happen for this account to pay you more next year?

If the honest answer is "nothing, unless they buy a different product," you have chosen a model that guarantees flat accounts. That is a structural decision made once and felt every quarter afterwards.

The options are a usage dimension that grows, a second product, or a service layer. Most hotel tech companies eventually need at least one, and the ones that thrive tend to decide deliberately rather than discover it at 97 percent retention.

Pricing for management companies

Portfolio buyers should almost never be priced per property with no structure, because it makes every additional property a fresh negotiation and a fresh opportunity to reconsider.

Portfolio pricing with clear economics for adding properties makes expansion the path of least resistance, which is the entire reason to sell to an operator with fourteen other buildings.

Changing pricing without breaking trust

Two rules.

Grandfather existing customers generously. In a market this connected, the reputational cost of a poorly handled increase travels faster than the revenue arrives, and hospitality talks more than most industries.

Change model and level separately, so you can attribute the effect. Changing both at once means you will never know which produced the result, and you will draw the wrong lesson.

When accounts are flat

Raising the number is rarely the fix. The model is.

A price increase on a structurally flat account buys one year of improvement and leaves the underlying problem untouched, usually while adding churn risk at exactly the accounts you most want to keep.

Related reading

• Choosing Your ICP: Independents, Chains, or Management Companies

• The Four Places Revenue Leaks in a Hotel Tech Company

• Positioning Against an Incumbent You Cannot Out-Feature