Most small hotels that try dynamic pricing ask the same question a few months in: is it actually working? The honest answer depends on how you measure it. Occupancy moves up and down for many reasons that have nothing to do with your prices, so a quick look at last month's numbers will not tell you much. This guide shows how to measure the return on investment (ROI) of dynamic pricing in a small hotel of roughly 3 to 30 rooms: which numbers to track, how to set a fair baseline, a simple 90-day plan, a worked example, and the mistakes that make results look better or worse than they are.

What ROI means for a small hotel

ROI compares what a tool gave you with what it cost you. For a hotel there are two kinds of gain. The first is extra room revenue: more money from the same rooms and the same staff. The second is time: the hours you no longer spend checking calendars and competitor rates by hand. Revenue is easier to measure, so most of this guide is about it, but if pricing used to take five hours of your week, that time counts too.

The cost side is simpler. For a pricing tool it is your plan fee for the period you are measuring, plus any other charge your provider adds. We do not quote a price in this guide; Amiqa uses one fixed monthly rate based on hotel size, and the current rates are on our pricing page. The formula is: ROI = (extra revenue − cost of the tool) ÷ cost of the tool. Count the extra revenue after the costs that come with it: if the extra revenue came through an OTA, the commission on it reduces your gain, and a higher rate on OTA bookings also pays more commission.

The numbers to track

Four numbers tell you most of what you need, and you can pull all of them from your PMS or booking reports.

Occupancy is the share of your available room nights that you sold. ADR (average daily rate) is room revenue divided by the room nights sold. RevPAR is room revenue divided by the room nights available, which is the same as occupancy times ADR; our guide to RevPAR explains it step by step. Booking pace, also called pickup, is how many nights you have booked for a future date compared with the same point last year.

Why occupancy alone misleads: you can fill every room by pricing too low, and a full house at a low rate can earn less than a 70% house at a good rate. A pricing tool that raises your rate on busy nights may even lower occupancy a little and still raise revenue. That is why RevPAR is the number to judge by, with ADR and occupancy showing you how you got there. Pace is the early warning: if the nights ahead are filling faster or slower than at the same point last year, you see it weeks before the guests arrive.

Set a fair baseline before you start

You cannot measure a change without knowing what would have happened otherwise. The simplest useful baseline is the same period last year, with the same dates and, as closely as possible, the same weekdays. Before you switch anything on, write down occupancy, ADR, RevPAR and total room revenue for that period.

Then adjust for what changed and has nothing to do with pricing:

Rooms. If you added, renovated or closed rooms, compare per available room (RevPAR already does this) and leave out any room that was out of service.

Events. A festival, a wedding, a conference or a road closure can lift or cut a week all by itself. Note the dates in both years, including holidays that move, such as Easter.

Seasonality. Compare like with like. A shoulder-season month and a peak-season month are not comparable, even in the same year.

Channel mix. If you joined or left an OTA, or your share of direct bookings changed a lot, your revenue after commission changes even at identical prices.

This is also why month-on-month comparisons mislead. October against September mostly measures the end of the season, not your pricing. A quiet month after a busy one looks like failure, and a good month after a bad one looks like success, whatever the tool did.

A simple 90-day measurement plan

1. Before day 1: record the baseline. Write down the numbers above for the same 90 days last year, your pace for the first weeks ahead, and roughly how many hours a week you spend on pricing today.

2. Days 1 to 14: set up and set limits. Enter your rooms, rates and channels, and set a floor and a ceiling price for each room type before any price moves. Do not judge anything yet.

3. Days 15 to 90: apply the suggestions. Use the tool's prices on the nights you agree with, and keep a short log of every time you override one, with the reason. Try not to change other big things, such as a new channel or a big photo refresh, at the same time.

4. Every week: check pace. It takes five minutes. Compare the next 30 to 60 nights with the same point last year.

5. Day 90: compare with the baseline. Prices change future nights, so stays come after the price changes. Count the stays that actually took place in your window, and also look at what you already hold for the following weeks.

6. Adjust and calculate. Remove the effect of events that happened in only one of the two years, work out the extra revenue, subtract the cost of the tool and the commission on the extra revenue that came through OTAs, and add the value of the time you saved. Then decide whether to keep going. Ninety days is a first reading, not a verdict: a full year is better, because it includes every season.

An example calculation

Illustrative example — not a real hotel. The numbers are made up and round, to show the steps. Take a 10-room hotel and a 90-day window, which gives 900 available room nights.

Same 90 days last year: 540 room nights sold (60% occupancy), ADR €100, room revenue €54,000, RevPAR €60.

These 90 days: 558 room nights sold (62% occupancy), ADR €108, room revenue €60,264, RevPAR about €67.

The raw difference is €6,264. Now adjust this year's figure for one-offs. Suppose a local festival that did not happen last year added about €1,000 of room revenue, so take that off: €5,264. Suppose the hotel paid about €500 in commission on the extra revenue that came through OTAs: €4,764. That is the extra revenue the pricing can fairly claim. Then:

Net gain = €4,764 − (3 × your plan cost), and ROI = net gain ÷ (3 × your plan cost). You use three months of the plan fee because the window is 90 days. If the net gain is above zero, the tool paid for itself in that period; the further above, the better. Notice that occupancy only rose two points. Most of the gain came from the rate, which is exactly what looking at occupancy alone would have hidden. Our ROI calculator shows example scenarios, not a forecast for your hotel. Use it to get a feel for the range, then measure your own hotel as described above: your own before-and-after numbers are what count.

What benchmarks can and cannot tell you

You will find articles quoting a typical ROI or revenue uplift for pricing tools, usually as a single percentage. Be careful with them. There is no reliable universal ROI figure for small hotels. The result depends on how much your demand varies across the year and the week, how far your starting prices are from the right level (a hotel that already prices well has less to gain), your market, your room mix, your channels and how much of the tool you actually use. Some quoted figures come from vendors describing their best cases, or from larger hotels with a different mix. A number that does not say how it was measured, over what period and for which hotels is a marketing claim, not a benchmark.

The one real result we can point to is Aáki Hotel in Nicaragua, which replaced manual pricing with Amiqa and grew revenue 14% in 12 months. It is one hotel. It shows what can happen, not what will happen to yours, which is why measuring your own numbers matters more than any benchmark.

Common mistakes

Measuring too soon. A few weeks of data, with stays that have not happened yet, tells you very little. Give it the full 90 days, and ideally a year.

Comparing across seasons. Always compare with the same period last year, adjusted as above.

Counting only occupancy. Judge by RevPAR, and look at ADR and pace next to it.

Overriding the tool constantly. If you change most of the suggestions, you are measuring your own pricing, not the tool's. Override for a reason, such as a local event the tool cannot know about, and keep the log so you can see how often you did.

Forgetting the costs on the other side. Commission on the extra revenue that came through OTAs, and any other fees, belong in the calculation.

When it may not be worth it

Dynamic pricing may not pay off if your rates already change every day with demand and you have the time and data to keep doing that well, or if you have so few rooms and such stable demand that a seasonal price list captures almost everything. It also does little if you will not look at the suggestions at all. Our guide to manual vs automated hotel pricing explains when staying manual is perfectly fine.

Where Amiqa fits

If you decide to try it, dynamic pricing software for hotels like Amiqa reviews each of your next 90 nights every morning and suggests where a different price would earn you more. It learns mainly from your own data, such as your past bookings and how your coming nights are filling, not by copying what other hotels charge. You set a floor and a ceiling for each room type, you choose between accepting suggestions yourself and handing a room type over to Autopilot, and your own prices are kept so you can go back to them. Every plan includes performance analytics and occupancy forecasting, and a free trial you can cancel before it ends. To compare tools before you decide, read how to choose dynamic pricing software for a small hotel.

Ready to measure it on your own hotel? Create your account and note your baseline first, or book a call and we will walk you through it with your own data.

How to Measure the ROI of Dynamic Pricing in a Small Hotel