Should You Raise Prices on Existing Hotel Customers?

Should You Raise Prices on Existing Hotel Customers?

Published on:

Published on:

Reading time:

Reading time:

5

5

min read

min read

Table of contents:

At some point every hotel tech company notices that its oldest customers are on its lowest prices. The product has grown, support has grown, and the properties that signed in year one still pay year-one rates. Raising those prices looks like the simplest revenue decision available. It is also the one most likely to start a dozen renewal reviews at once.

This is the decision laid out as it actually stands: what an increase gains, what it risks, where the balance lands for different situations, and the rules that make the difference between a quiet uplift and a churn event. If you have already decided to do it, skip to the rules.

The case for raising prices

Pro

Why it matters in hotel tech

What it is worth

Revenue with no new sales effort

Sales cycles stretch across seasons, so new business is slow and lumpy; an uplift lands on a known date

A single-digit uplift across the base often equals a quarter of new sales

Corrects the legacy gap

Early customers are often paying half the current list price for a product that has doubled in scope

The gap compounds every year it is left

Pays for support the properties already use

Hotels lean on support during peak season and staff turnover; that cost rises with every release

Margin on the oldest accounts stops shrinking

Resets expectations

A written annual uplift means the next increase is a line in a contract rather than a negotiation

Fewer renewal conversations about price in future

Signals confidence

Properties read a vendor that never raises prices as one that is not investing

Supports the reference and referral motion

The case against

Con

Why it bites in hotel tech

How to limit it

Triggers reviews that were not coming

A price change is the most common reason a general manager opens a comparison spreadsheet

Announce early, with a named reason, outside the notice period

Lands on the wrong accounts

A flat increase hits your best references and your at-risk accounts the same way

Segment the base before deciding anything

Collides with the owner

The general manager accepted the product; the owner sees only the invoice line

Give the GM a one-paragraph justification they can forward

Exposes underuse

An invoice that rises on a product the property half uses invites the question of why they pay at all

Check usage first, and fix activation before pricing

Low season timing is tight

Hotels decide in the autumn; an increase announced in March waits a year for the budget

Plan the announcement against their budget cycle, not your fiscal year

Where the balance lands

The answer depends less on the product than on the state of the account base. Four common situations:

Situation

Lean

Why

Oldest accounts far below list, usage healthy

Raise, in steps

The gap is real and the properties get value; stage it over two renewals

Base-wide underpricing, usage patchy

Fix activation first, then raise

An increase on a half-used product becomes a churn trigger

Recent churn or a wave of ownership changes

Hold this year

The accounts that would review are already fragile; see the retention signs below

Second product ready to sell

Sell that first

More revenue, and the property gets something new for the money

The second row is where most companies sit and the one most often skipped. If the usage data shows half the base using a fraction of the product, the problem is not price, and pricing problem or sales problem shows how to tell the two apart before you act. The third row is worth checking against the signs of a retention problem, because a price increase on top of an existing retention leak accelerates it.

If you raise prices: the rules

  • Segment before you set the number. Accounts far below list, accounts at list, large groups on legacy terms and at-risk accounts each get their own treatment. A single percentage across the base is the lazy version.

  • Announce at 90 days or earlier, by a person, with a reason. The reason is a capability or a support level the property has received. Not inflation, not costs.

  • Give the general manager a paragraph for the owner. The GM is not the one who objects. The owner is, and the GM needs something to forward.

  • Cap the single step. Anything above ten percent in one move needs a named justification, and anything above twenty is a renegotiation, not an uplift.

  • Exclude the references. The five properties that take your reference calls are worth more than their uplift. Tell them they are excluded and why.

  • Write the annual uplift into the contract from now on. The next increase should be a clause, not a conversation.

  • Offer a trade. A longer term or a second property at the old price gives the property a choice, and choice reduces reviews.

If you do not: what to do instead

  • Move the price list for new customers now, so the gap stops growing.

  • Add the annual uplift clause at every renewal that comes up this year, at zero percent if necessary, so the mechanism exists.

  • Sell the second product into the accounts that would have absorbed an increase easily.

  • Fix activation in the accounts where usage is thin, because those are the ones an increase would have lost anyway.

  • Revisit the decision in one budget cycle with the usage and churn data in front of you.

The pricing structure itself is a separate decision from the level, and pricing hotel tech per room, per property or flat rate covers that choice.

The takeaway

Raising prices on existing hotel customers is usually right for the oldest, healthiest accounts and usually wrong as a blanket move. Segment the base, fix usage before touching price where usage is thin, announce early with a reason the owner will accept, and put the next increase into the contract so this decision does not come around again.

If you are not sure whether the gap in your revenue is price, retention or something earlier in the funnel, the 12-point leak audit takes about twenty minutes and ranks the four leaks on your own numbers.

Frequently Asked Questions

How much can a hotel tech company raise prices on existing customers?

Will raising prices cause hotel customers to churn?

When is the best time to announce a price increase to hotels?

Should the price increase be the same for every hotel customer?

Is it better to raise prices or sell a second product?

Where is your revenue actually leaking?

Twelve questions, about twenty minutes, on your own funnel. The same audit I run on day one of an engagement. No call required.

Get the free leak audit

Unlock Hotelier Demand

Stop Guessing What Hoteliers Want.

I Know What They Really Need.

Let’s engineer your hotel tech into the backbone of every hotelier’s workflow.

Make It Hotelier-Ready

Let’s transform your software into a revenue magnet in 90 days.

Unlock Hotelier Demand

Stop Guessing What Hoteliers Want.

I Know What They Really Need.

Let’s engineer your hotel tech into the backbone of every hotelier’s workflow.

Make It Hotelier-Ready

Let’s transform your software into a revenue magnet in 90 days.