Independent hotels

How to Set Hotel Rates Without a Revenue Manager

Whether you run 40 rooms in Bangkok or 45 on Koh Samui, the rate on your website tonight was probably set by whoever had five minutes between other jobs — the GM, the owner, a duty manager covering front desk. It was probably based on last year’s rate for the same date, plus or minus a look at one or two competitors on a booking site. Nobody’s job title includes “set today’s rate,” so the rate gets set when someone remembers, not when the market changes.

That’s not a criticism of how independent properties are run. A 20–80 room hotel or resort doesn’t have the volume to justify a full-time revenue manager, and most of the people doing this work well already have a full day of other responsibilities. The problem is that pricing is one of the few jobs in a hotel where “get to it when there’s time” produces a specific, measurable cost — rooms sold for less than someone would have paid, and rooms left empty because the rate was higher than the market would bear.

This post covers what a revenue manager actually does, why the work looks different for a Bangkok boutique hotel than for a Phuket or Koh Samui resort, and what a small property can realistically do about it without hiring one.

What a revenue manager’s day actually involves

“Revenue management” sounds abstract until you break it into tasks. In a hotel that has someone doing this job properly, it looks like:

• Checking the competitive set — the handful of properties guests actually compare you against — several times a week, sometimes daily, to see where rates are moving.
• Adjusting for lead time — how far ahead of the stay date it is, because a room 90 days out and the same room 3 days out behave like different products.
• Reading pace — whether bookings for a given date are running ahead of or behind where they were at the same point last year, and nudging the rate accordingly.
• Tracking demand drivers on the calendar — public holidays, conferences, festivals, school holidays — and pricing around them in advance rather than reacting once rooms are already gone.
• Enforcing rate parity — making sure the same room on the same date isn’t quietly cheaper on one channel than another, which undermines trust with all of them.

None of this is a once-a-quarter task. It’s a standing, repeated loop, which is exactly why it tends to fall off a busy GM’s list — not because it’s hard to understand, but because it’s hard to do consistently on top of everything else.

Where the boutique hotel and the resort diverge

The underlying job is the same for both property types. The mechanics are not.

A Bangkok or Chiang Mai boutique hotel typically has a short booking window — often inside two to three weeks — and a large, broadly similar competitive set: dozens of independent hotels in a comparable price band. Demand moves with the working week, corporate travel, trade fairs and public holidays. Because the window is short, a rate that’s wrong today is a rate that’s wrong for a booking that happens this week — there’s little time to correct course once the mistake is visible in the numbers.

A Phuket, Koh Samui, Koh Phangan or Krabi resort works on a much longer booking window — often three to six months — against a compset of maybe a handful of genuinely comparable properties nearby. Demand swings hard by season: high season can run close to full, low season and the monsoon months can be very quiet, and the swing between them is the defining feature of the business, not a footnote to it. Because guests book far ahead, a resort has more time to correct a rate before the date arrives — but also more months where a stale rate quietly costs money before anyone notices.

This is why an annual average occupancy figure is close to useless for a resort — 85% in January and 35% in September can average out to something that looks comfortable on paper and describes neither month. A city hotel’s demand is steadier across the year, so an average means more there, but even then it hides which specific nights (a conference weekend, a public holiday) actually drove the number.

What a stale rate actually costs

It’s easier to reason about this with a worked example than with an industry statistic — because nobody can tell you what “typical” looks like for your specific property, and any number claiming to isn’t one you should trust. Use your own figures once you’ve read the method.

Take a 40-room property, either type. Suppose that during a period of unusually strong demand — a long weekend with a public holiday for the city hotel, the start of peak season for the resort — the rate stayed at its normal level because nobody was watching closely enough to raise it. Say 15 rooms a night were sold 400 THB below what the market would have supported, across six nights. That’s 15 × 400 × 6 = 36,000 THB left on the table in one window.

Now the other direction, which matters just as much and is easier to miss because nothing shows up as a lost sale — it shows up as an empty room. Suppose during a quiet stretch — a slow Tuesday run in Bangkok, low season on the islands — the rate stayed at last year’s higher figure instead of coming down to match demand. If 5 rooms a night that would otherwise have sold at 2,000 THB stayed empty for 10 nights, that’s 5 × 2,000 × 10 = 100,000 THB in bookings that simply didn’t happen.

Multiply either scenario by how often it recurs across a year — a handful of long weekends and public holidays for a city hotel, entire shoulder-season months for a resort — and the total moves from tens of thousands of baht to a figure with more zeros on the end. And that’s only counting the nights you’d have noticed. The nights nobody thought to check aren’t in this total at all.

What a small property can do without a dedicated revenue manager

Short of hiring someone full-time, three habits close most of the gap:

1. Put a recurring slot on the calendar — even 30 minutes, weekly — specifically for checking compset rates against your own for the next two to four weeks. For a resort, extend that check to the coming season rather than just the coming weeks, since the booking window is longer.
2. Build a demand calendar once, then reuse it. List the trade fairs, public holidays and events that move demand for a Bangkok or Chiang Mai property, or the monsoon timing and overseas school holiday calendars that move it for an island resort, and price around them in advance rather than reacting after rooms are already booked or already empty.
3. Check parity across your channels occasionally, not just when a guest complains about seeing a lower rate somewhere else.

Done consistently, this gets a small property most of the way there. The honest limitation is the word “consistently” — a manual weekly check is much better than nothing, but it is still a snapshot, not a continuous read of the market. Rates that are right on Tuesday can be wrong by Thursday, and a once-a-week check will miss most of that movement by definition.

That gap — continuous, rather than occasional, attention — is the actual problem AutomIQ’s software addresses: an AI agent that never sleeps, continuously publishing optimal rates across your channels rather than waiting for someone to have time. It runs on hardware at the property rather than sending guest data to a cloud service, which matters to owners thinking about where their data lives, though it isn’t a substitute for your own judgement on PDPA compliance — that’s a legal question for your own advisers, not a claim this software makes.

Automation isn’t the answer to everything here. It doesn’t know about a VIP guest relationship, a room taken out of inventory for renovation, or a group rate being negotiated by phone — those still need a human decision, and a system that pretended otherwise would be lying to you. What it does well is the repetitive, time-bound part: watching the compset, adjusting for lead time and pace, keeping channels in parity, every day, without someone having to remember to do it.

Frequently asked questions

We already adjust rates for high season and low season — isn’t that revenue management?

It’s one input to it. Seasonal adjustment is usually a calendar set once a year; revenue management is the continuous work of checking the compset, reading booking pace, and adjusting around specific events on top of that seasonal baseline. A property doing only the seasonal part is doing the easiest part of the job.

How often should rates actually change?

It depends on your booking window. A city hotel with bookings arriving inside two to three weeks benefits from checking rates several times a week, especially as a date gets close. A resort with a three-to-six-month window can check less frequently for far-out dates, but should tighten that up as the date approaches and pace data becomes more reliable.

Isn’t this something my channel manager already does?

No — your channel manager distributes whatever rate you set to your booking channels. It doesn’t decide what that rate should be. Revenue management is the decision layer above distribution, not a feature of the distribution tool itself.

We don’t have time to check competitor rates every day — is that really necessary?

That’s the honest reason most independent properties don’t do this manually, and it’s a completely reasonable constraint on a small team. It’s also exactly the gap that automated, continuous repricing is built to close — the checking and adjusting happen without needing someone’s spare 30 minutes to exist that day.

What about guest data and Thailand’s PDPA?

Thailand’s Personal Data Protection Act is real and applies to guest data your property holds. On-premise hosting — where the software runs on hardware at the property rather than sending data to a cloud service — is a genuine architectural difference, but it isn’t a requirement for PDPA compliance, and any claim that it is would be overstating the law. Speak to your own legal adviser about what compliance requires for your property.

What a next step looks like

If this describes how your property currently sets rates, the first useful conversation is a short one about your compset, your channels, and how far ahead your bookings typically come in — not a sales pitch. That’s what determines whether continuous, automated pricing is a good fit before anything else is discussed. Get in touch to start there.