Virtuosos of Price

How We Count Revenue

Most revenue management services publish a headline number and stop there. The number is large, the font is large, and the methodology is absent. A host reading it cannot tell whether the figure counts gross booking value, net payout, projected nights that have not yet occurred, or something assembled from a model rather than from actual reservations. The number is designed to impress, not to inform.

That gap matters if you are deciding whether to trust a service with your listings. A figure you cannot interrogate is not evidence. It is decoration. What follows is a plain account of how Revande's booked revenue figure is constructed, what we chose to leave out, and what you should check before you treat any number like this, including ours, as a reason to act.

The number our industry does not publish

Revenue management services have a strong incentive to publish the largest defensible number. Projected revenue is larger than confirmed revenue. Gross booking value is larger than host payout. Lifetime projections are larger than figures bounded by a specific period. None of those choices are necessarily dishonest, but none of them are disclosed either, which means the reader cannot compare one service's headline to another's.

The number Revande publishes is booked revenue: the sum of confirmed reservation values across active client listings, denominated in the currency of each booking and converted to a single reporting currency at the exchange rate in effect at the time of conversion. It does not include projected revenue from unbooked nights. It does not include revenue from listings that were onboarded but never activated. It does not include revenue that a client earned before they joined Revande.

The reason this matters is that the alternative is easy to manufacture. If a service manages listings in a market where average nightly rates are high, and it projects forward occupancy at a generous assumption, the resulting figure can be very large without a single confirmed booking behind it. There is no industry body that audits these claims. There is no standard definition of "revenue generated." The number our industry does not publish is the one that shows only what guests have actually paid for confirmed stays.

Worked example: suppose a listing has three confirmed reservations totalling a specific gross booking value, and twelve unbooked nights at the current listed rate. A projection-based figure would include all fifteen nights. Our figure includes only the three confirmed reservations. The twelve unbooked nights contribute nothing until a guest books them.

Checklist for evaluating any revenue claim you encounter:

• Ask whether the figure is confirmed bookings or projected revenue
• Ask whether it is gross booking value or host payout after platform fees
• Ask whether it covers a defined calendar period or an open-ended accumulation
• Ask whether listings that churned off the platform mid-period are included or excluded
• Ask whether the figure has been audited by anyone outside the company publishing it

If the service cannot answer all five questions, treat the number as unknown.

What we refused to count

Deciding what to exclude is as important as deciding what to include, and it is harder, because exclusions reduce the headline figure. The following categories were considered and deliberately left out.

Projected revenue from unbooked nights. A listing with strong historical occupancy will probably book future nights. That probability is not a booking. We do not count it.

Revenue from the period before a client joined Revande. Some clients come to us with listings that were already performing well. Their prior revenue is theirs. It does not belong in a figure that is meant to represent what our service contributed.

Revenue from listings that were set up but never went live. Occasionally a client begins onboarding and then pauses or cancels before their listing is activated. Any revenue those listings might have generated is not in the figure.

Cancelled reservations that were not subsequently rebooked. A reservation that is cancelled before the stay does not result in a guest sleeping in the property. In most cases it does not result in a full payout to the host either. We exclude cancelled reservations unless they were rebooked at a rate that resulted in an actual payout.

Revenue from listings we do not manage. Some clients have multiple listings. If they have given us management of two listings and retained management of a third themselves, the third listing's revenue is not in our figure.

Decision rule: if there is any ambiguity about whether a reservation belongs in the count, the default is to exclude it. The figure should be conservative enough that a client could verify it against their own Airbnb payout history and find it plausible, not inflated.

What a client actually books

Understanding the figure requires understanding what a confirmed reservation looks like from the host's side, because the number a guest sees and the number a host receives are not the same.

When a guest books a listing, they pay a total that includes the nightly rate, any cleaning fee, and the Airbnb service fee charged to the guest. The host receives a payout that is the nightly rate plus the cleaning fee, minus the host service fee that Airbnb charges. The guest-facing total and the host payout are different numbers, and neither of them is what Revande's rate strategy directly controls.

What rate strategy controls is the nightly rate. The cleaning fee is typically set by the host and adjusted infrequently. The service fees on both sides are set by Airbnb. So when we describe booked revenue, we are describing the gross booking value of confirmed reservations, which is the nightly rate multiplied by the number of nights, plus the cleaning fee, before Airbnb's host service fee is deducted.

This is not the same as the host's net payout, and we do not represent it as such. A host who wants to reconcile our figure against their actual earnings should expect the net payout to be lower, because Airbnb's host service fee is deducted before the payout is transferred.

Worked example: a guest books four nights at a rate set by our pricing strategy, plus a cleaning fee set by the host. The total the guest pays includes an Airbnb guest service fee on top of that. The figure that enters our booked revenue count is the nightly rate multiplied by four, plus the cleaning fee. The guest service fee does not go to the host and is not counted. The host service fee is deducted from the payout but the gross booking value before that deduction is what we record.

Checklist for a host verifying their own contribution to the figure:

• Pull your confirmed reservations from your Airbnb host dashboard for the relevant period
• For each reservation, record the nightly rate and the number of nights
• Add the cleaning fee for each reservation
• Sum those figures across all confirmed reservations
• That sum should be close to what Revande records for your listings

If there is a discrepancy, the most common cause is a reservation that was cancelled and excluded from our count but still appears in your dashboard as a historical booking.

Already stayed, and still ahead

A booked revenue figure that includes future reservations is partly a forecast. A guest who has booked a stay three months from now may cancel. The reservation may be modified. The payout may differ from the booking value if a resolution claim is filed. None of that uncertainty is resolved until the stay has occurred and the payout has been transferred.

Revande's figure includes both completed stays and confirmed future reservations. We do not wait until every stay has occurred to publish the number, because that would mean the figure is always significantly behind the actual state of the portfolio. But we think it is important to be clear about the composition.

At any point in time, the figure has two components. The first is revenue from stays that have already occurred and for which payouts have been transferred. The second is revenue from confirmed reservations for stays that have not yet occurred. The first component is settled. The second is confirmed but not yet realized.

The reason we include both is that a confirmed reservation on Airbnb represents a contractual commitment from the guest, backed by Airbnb's payment processing. It is not a projection or an estimate. It is a booking with a specific value, a specific set of dates, and a specific guest who has paid. The probability that it results in a payout is high, though not certain.

Decision rule: if you want to assess only the settled portion of the figure, ask us for the breakdown between completed stays and upcoming confirmed reservations. We can provide that. The total figure is the sum of both, and we think that is the right way to report it, but we also think you should know the composition.

Seven currencies, one number

Revande manages listings across multiple countries. Guests book in the currency of the market where the listing is located. A guest booking a listing in Australia pays in Australian dollars. A guest booking a listing in the United Kingdom pays in pounds sterling. A guest booking a listing in the United States pays in US dollars. The same is true for other markets in the portfolio.

Reporting a single aggregate figure requires converting all of those currencies into one. We use a single reporting currency, and we apply the exchange rate in effect at the time the conversion is performed. We do not use a fixed historical rate, and we do not use a projected rate. We use the rate at the time of reporting.

This introduces a source of variability that has nothing to do with the performance of the listings. If the Australian dollar strengthens against the reporting currency between one reporting period and the next, the Australian listings will contribute more to the aggregate figure even if their booking values in Australian dollars are unchanged. The reverse is also true.

The table below records the information a host should capture if they want to understand how currency conversion affects the figure over time.

The practical implication for a host is that the aggregate figure Revande publishes is not a precise measure of what any individual listing earned in its local currency. It is an aggregate across a multi-currency portfolio, converted at a point-in-time rate. If you want to assess your own listing's performance, the most reliable figure is your booking value in the currency your listing operates in, not the converted aggregate.

Before you trust this number

A figure published by the service you are evaluating is not independent verification. Revande compiled this number from our own records. We have described the methodology, but we have not had it audited by an external party. You should weigh that when you decide how much confidence to place in it.

There are several things you can do to form your own view.

First, you can ask for a breakdown by market or by listing count. A large aggregate figure from a small number of listings in high-rate markets tells you something different from the same figure spread across a large number of listings in moderate-rate markets. The composition matters.

Second, you can ask for the period the figure covers. A figure accumulated over a longer period is not more impressive than a figure accumulated over a shorter period unless you know the rate of accumulation. Ask for the start date and the end date.

Third, you can speak to existing clients. A client who can show you their own Airbnb payout history and describe how it changed after joining Revande is a more reliable signal than any aggregate figure. We can facilitate introductions where clients have agreed to speak with prospective clients.

Fourth, you can look at what the figure does not tell you. It does not tell you what the same listings would have earned without Revande's involvement. That counterfactual is genuinely unknown. We cannot tell you what your listing would have earned if you had managed it yourself or used a different service. No one can. Any service that claims to know the counterfactual is asserting something that cannot be verified.

Fifth, you can consider the incentive structure. We have an incentive to publish a large number. We have tried to constrain that incentive by excluding categories that would inflate the figure, but the constraint is self-imposed. An independent audit would be a stronger constraint, and we do not currently have one.

Decision rule: treat the figure as a description of confirmed booking activity across the portfolio, not as a measure of what Revande caused. The causal claim is plausible but not provable. The booking activity is real and verifiable in principle, even if you cannot verify every reservation yourself.

Checklist before drawing any conclusion from a revenue figure published by any service:

• Confirm the definition of revenue being used (gross booking value, net payout, projected, or confirmed)
• Confirm the period covered and whether it is still accumulating
• Confirm what was excluded and why
• Confirm the currency treatment if the service operates in multiple markets
• Ask whether the figure has been independently audited
• Ask for a client reference who can speak to their own experience
• Identify what the figure cannot tell you, specifically the counterfactual

None of these checks will give you certainty. They will give you a more accurate picture of what the number represents and what it does not.

Where this becomes someone else's job

Evaluating a revenue figure is one thing. Generating the bookings behind it is another. If the work of daily rate adjustments, listing monitoring, and ongoing optimization is time you do not have or do not want to spend, Revande offers two ways to hand it off.

Performance gives you a full software stack for dynamic pricing, with daily adjustments made by experienced rate strategists. It includes Airbnb listing performance monitoring and email alerts when visibility or booking conversion drops below expected levels, along with monthly reports so you can see what is happening across your listings without having to pull the data yourself.

Maestro includes everything in Performance and adds done-for-you listing optimization. Proactive Airbnb listing performance monitoring means that visibility and booking conversion issues are not just flagged to you but handled for you. Maestro works with Airbnb directly or with your existing channel manager, and it includes ongoing listing refinements as the platform and your market conditions change.

The difference between the two is not the quality of the rate strategy. It is the scope of what gets done without your involvement. Performance keeps you in the loop and in control of listing decisions. Maestro removes the listing work from your plate entirely. Which one fits depends on how much of the operational layer you want to retain and how much you want to delegate.