Virtuosos of Price

King Rental Homes' seven Greater Boston units against Airbnb's own comparison set: 7 of 7 above on occupancy, 5 of 7 on rate, April 21 through September 19, 2026, and the same comparison any manager can be asked for

Record at a glance

Revande has managed daily pricing for King Rental Homes since February 20, 2026, under its Performance service. Todd King's team owns the properties, the guests and the operations across Greater Boston, Massachusetts South Shore and North Shore. Revande sets the pricing strategy on the seven units in the managed portfolio, monitors it daily, raises alerts when a listing drifts, reports monthly, and maintains the path that publishes those rates to the channels. The properties, the guests, cleaning and maintenance stay with King Rental Homes, and the owner approves the guardrails Revande prices within.

Across June 21 through September 18, 2026, entirely inside that managed period, those seven units recorded USD 232,784.15 in PriceLabs Portfolio Analytics reported trailing-90 revenue, a recorded figure and not a projection, reconciled in integer cents and confirmed in USD across the seven source payloads. The historical records were captured on September 19, 2026 at 14:00 UTC. The seven units were matched deliberately: five on exact PriceLabs listing identifiers, two on exact channel identifiers. One historical row that did not match the current managed cohort is excluded, a scope decision rather than a result.

On the September 19, 2026 capture date every one of the seven managed units had price sync ON and pricing strategy COMPLETE, with reported last-push timestamps between 13:15:13 and 13:15:35 UTC. That is Revande's publishing path, live rather than nominal.

Revande created the pricing strategy that revenue was booked on, and has maintained it daily since February 20, 2026. What the record does not do is put a number on how much of the total Revande added, because an incremental figure needs a comparable period from before February 20, 2026 and a design accounting for seasonality and inventory changes, neither of which is supplied here. Every boundary of this evidence is stated below rather than left for a reader to discover.

This page is the operating record behind that figure: the service, the cohort it covers, the pricing configuration observed on the capture date, and the method. It is written for property managers deciding whether to outsource pricing, and it states plainly what the number is and what it is not.

On this page

• Record at a glance
• What Revande does for this portfolio
• Recorded revenue for the seven managed units
• Revenue, reported ADR and configured rates
• The publishing configuration Revande maintains
• Guest demand and search performance on Airbnb
• How the seven units price against their market
• Where this becomes someone else's job
• Method and limits
• Frequently Asked Questions (FAQ)
• Related reading and next step
• About the Author
• Sources

What Revande does for this portfolio

Scope of the Performance service

King Rental Homes is on Revande's Performance service. Its scope is specialist led daily pricing: Revande sets each unit's pricing strategy, monitors it daily, raises alerts when a listing drifts, and reports monthly. The properties, the guests, cleaning and maintenance stay with King Rental Homes, and the owner approves the guardrails Revande prices within.

Responsibility boundary

The boundary matters for reading every figure below. A number produced inside this arrangement describes a portfolio whose rates Revande set and whose operations someone else ran, so it is evidence about the arrangement as a whole rather than about either party alone.

Continuity of the engagement

Service has run continuously since February 20, 2026. The measurement window below runs from June 21 to September 18, 2026, so it opens after that start date and closes while the engagement is still running. Revande therefore authored and maintained the pricing strategy for the whole of the measured window, start to finish.

Recorded revenue for the seven managed units

The recorded figure

For King Rental Homes, Todd King's Greater Boston portfolio, Revande recorded USD 232,784.15 as PriceLabs Portfolio Analytics reported trailing-90 revenue for the seven units under Revande's pricing management, covering June 21 through September 18, 2026 and captured September 19, 2026 at 14:00 UTC. Revande authored and maintained the pricing strategy those seven units were priced under across that window. This is observed revenue recorded under Revande-managed pricing, not an estimate of revenue Revande added.

The figure is the portfolio's own recorded revenue over those ninety days. It is not a projection, not a goal, and not a share of revenue attributed to Revande. The method and its boundaries are set out below.

How the seven unit cohort was reconciled

The USD 232,784.15 figure for King Rental Homes' seven Greater Boston units, recorded for June 21 through September 18, 2026 and captured September 19, 2026 at 14:00 UTC under the pricing strategy Revande authored, rests on a specific cohort reconciliation. The total covers seven distinct units within one shared window. Five were matched on exact PriceLabs listing identifiers and two on exact channel identifiers carried by the preferred Hostaway records. The identifiers stay private; what is public is the matching method and the resulting cohort. This reconciliation describes observed source records under Revande-managed pricing, not an estimate of how much revenue Revande added.

The excluded row is a scope decision, not a result. Its absence says the row could not be attributed to the current managed cohort under the matching rules, not that a property failed or stopped operating.

Revenue, reported ADR and configured rates

Reported ADR across the cohort

For the same seven King Rental Homes units in Greater Boston, the historical evidence Revande reconciled reports a per-unit average daily rate range of USD 270.60 to USD 657.70 for the June 21 through September 18, 2026 window, captured September 19, 2026 at 14:00 UTC, under the pricing strategy Revande authored and maintains. ADR means average daily rate. Here it is the range of the seven units' source ADR values for the window, not a portfolio-weighted average. This is an observed rate range recorded under Revande-managed pricing, not an estimate of a rate Revande added.

Configured Minimum and Base on September 19

For King Rental Homes' seven managed units in Greater Boston, a separate live UI observation on September 19, 2026 recorded a configured Minimum span of USD 125 to USD 300 and a configured Base span of USD 242 to USD 490, under the pricing strategy Revande authored and maintains. Both spans are anonymized. The table below sets them beside the historical per-unit ADR range so the two source classes stay visibly distinct:

These are observed pricing settings recorded under Revande-managed pricing for King Rental Homes' seven managed units, not an estimate of revenue Revande added.

Why the two spans are not comparable

ADR comes from the historical performance evidence; Minimum and Base come from the September 19 UI observation. They are different measurements taken for different purposes, and the endpoints do not identify which unit holds which value. Pairing endpoints across the two would not produce a pricing gap, and averaging the ADR endpoints would not produce a portfolio ADR, which needs compatible revenue and booked-night denominators for the same cohort and window.

Historical ADR and current Base settings can differ while both observations remain valid. One summarizes performance across a past period; the other describes a configured input on one date. No current nightly quote is inferred from either span.

The publishing configuration Revande maintains

What sync ON and strategy COMPLETE establish

The September 19 Customer API observation identified Hostaway as the preferred integration for all seven managed units, with Airbnb and Vrbo channel bindings on the preferred records. Revande maintains this Hostaway publishing path as part of the pricing strategy it authored for King Rental Homes' seven Greater Boston units. This configuration snapshot is an observed state of Revande-managed pricing infrastructure on one date, not an estimate of any conversion or booking outcome the configuration produced.

Sync ON and strategy COMPLETE on every managed unit means the pricing path was live and configured on that date, with push activity recorded to the second. The timestamp bounds describe reported push metadata across the records, not the runtime of a distribution job.

The same Hostaway sync ON for 7 of 7 managed units, the same 3 Airbnb-direct records with sync OFF, and the same configured Minimum span of USD 125 to USD 300 and Base span of USD 242 to USD 490, were independently observed again on September 20, 2026 from the PriceLabs Pricing Dashboard. This is a second observation of the configuration already reported above from the September 19, 2026 Customer API and UI snapshots, not a new or different configuration.

What a configuration snapshot cannot confirm

What a configuration snapshot cannot do is confirm the rate a guest saw for a particular stay night. That needs a matched channel observation, which is set out under a later record below. The Airbnb-direct records with sync OFF are non-preferred records, not failed units and not three additional properties.

Guest demand and search performance on Airbnb

Airbnb computes booking-conversion metrics for each listing from its own search and listing traffic; Revande does not compute these metrics and does not control most of their inputs. Revande read these figures from the Airbnb host Performance surface on September 20, 2026, for the same seven King Rental Homes units in Greater Boston covered above. The metrics cover the window August 20 through September 19, 2026, with Airbnb reporting them last updated September 19, 2026. That window does not match the June 21 through September 18, 2026 revenue window above, so these figures must never be joined, summed, averaged, or read as measuring the same period as the recorded trailing-90 revenue figure.

Across the seven units, Airbnb reports these cohort-level ranges:

These are cohort-level ranges only. No per-unit row, unit name, brain code or listing identifier is published here.

Revande authors the pricing strategy for these seven units. Search ranking, photography, title, reviews and market demand are not Revande-controlled inputs. No conversion figure here is evidence that Revande caused, added, increased or drove any conversion, booking or revenue outcome; these are observations at a capture instant, not a measured trend and not a controlled experiment.

How the seven units price against their market

Airbnb computes a comparison set of similar listings in the same area and reports each listing's nightly rate and occupancy beside that set's. Revande read this comparison from the Airbnb host Performance surface on September 20, 2026, for all seven King Rental Homes units in Greater Boston, covering April 21 through September 19, 2026. The window was fixed in advance, no month, week or outcome was selected, and it sits wholly inside the managed period that began February 20, 2026.

Across that period all seven units recorded a higher occupancy rate than their Airbnb comparison set, and five of the seven also recorded a higher average nightly rate. The seven averaged USD 520.57 per night against approximately USD 414 for comparable listings in the same area, and their occupancy ran between 75.6% and 94.9%.

Two units priced below their comparison set while running occupancy above it. This record reports that pattern and does not present it as a deliberate trade, because the decision record that would establish intent is not included here.

What the rate and occupancy comparison does not establish

What this comparison does not establish is cause. Revande authors and maintains the pricing strategy these units sold on, and King Rental Homes approves the guardrails Revande prices within. A unit may out-rate comparable units because of the pricing work, because it is a better property, or both, and no counterfactual is supplied here to separate them.

Airbnb's comparison set is its own, its selection criteria are not disclosed, and Revande cannot audit which listings it contains. Airbnb also states each occupancy difference as a percentage without specifying whether it means percentage points or a relative change, so this record quotes the figures Airbnb reports and does not compute a combined revenue multiple from them.

This comparison covers April 21 through September 19, 2026. That window does not match the June 21 through September 18, 2026 revenue window reported above, so the two must never be joined, summed, averaged or read as measuring the same period.

This is an observation recorded under Revande-managed pricing, not an estimate of revenue Revande added.

Where this becomes someone else's job

What this record shows a property manager

For a manager weighing an outsourced pricing service, this record answers three practical questions.

It shows the scale the service runs at: seven units priced by a Revande strategy every day of a ninety day window, recording USD 232,784.15 on those rates. It shows the publishing path is live rather than nominal, with sync enabled and strategy complete on every managed unit and push activity timestamped on the capture date. And it shows where the boundary sits, which is the subject of the next two parts.

This is observed revenue recorded under Revande-managed pricing for a portfolio Revande manages, not an estimate of revenue Revande added.

What Revande owns and what the manager owns

Revande owns the rates: the strategy, the daily decisions and the path that pushes those rates to Airbnb and Vrbo. King Rental Homes owns the properties, the guests, cleaning, maintenance, and the approval of the pricing guardrails Revande works within and of any manual override.

That division is where an outsourced pricing service stops and property management begins. A manager evaluating this record should read it as evidence about the pricing half, because the operational half was never Revande's to run.

What this record establishes

What this record establishes is authorship: the pricing strategy behind USD 232,784.15 is Revande's, created at the start of the engagement and maintained daily through the window.

Method and limits

Sources of the figure

The figure combines the historical Portfolio Analytics records, the September 19 Customer API identity response and the currency fields in seven same-day pricing payloads. The collector stores the Portfolio Analytics revenue field directly alongside its window and capture time. The total was reconciled using integer cents, and USD was confirmed on each of the seven source payloads. A read-only source inspection and reconciliation was completed on September 19, 2026.

What the figure is

Reported trailing-90 revenue for the seven managed units, covering June 21 through September 18, 2026, captured September 19 at 14:00 UTC.

What it is not

These are first-party operating records, not independently audited financial statements. The revenue field has not been reconciled here to cleared payouts, to net profit, or to the treatment of every refund, fee and tax, so the article keeps the source metric's own label rather than restating it as bank-cleared cash. It is neither a total of current Base settings nor a forward goal. No comparable prior period or counterfactual is supplied, so no share of the total is attributed to Revande's work.

Common misreadings to avoid

Four readings of this page would be wrong, and each is a risk worth naming directly.

1. Adding the excluded row back in. The excluded historical row could not be attributed to the current managed cohort under the matching rules. Adding it would inflate the total with a row whose ownership is unestablished.
2. Counting the three Airbnb-direct records as properties. They are non-preferred integration records with sync OFF. Seven managed units plus three direct records is not ten properties.
3. Pairing an ADR endpoint with a Base endpoint. The two spans come from different sources on different terms, and neither identifies which unit holds which value, so the gap between them measures nothing.
4. Reading the total as the amount Revande added. Revande created the pricing strategy the portfolio sold on, and USD 232,784.15 is what it recorded on those rates. How much of that total is incremental is a different question, and it needs the comparison described above.

What remains open

The identity match connects these seven historical records to the current managed units; it does not establish that the current configuration held unchanged throughout the window, which would need dated configuration history. No matched post-change channel capture is included here, so no guest-facing rate on a particular night is verified. Maximum settings were generally unset in the inspected UI, and neither the unset count nor the number of settings rows checked is recorded. The September 19 configuration is an observation on one date rather than a promise of continuing state.

These are the boundaries of this evidence. They are not findings that the work did not happen, and the distinction is worth stating precisely because the two are easy to confuse.

A boundary describes what this evidence was designed to establish and where that design stops. The absence of dated configuration history means the article cannot say the configuration held unchanged across the window; it does not mean the configuration changed. The absence of a matched channel capture means no guest-facing rate on a particular night is verified here; it does not mean a rate failed to publish. The unrecorded Maximum-settings count means that population was not measured; it does not mean the settings were wrong.

A finding, by contrast, would be something this evidence actually observed and reported. Every finding on this page is stated as one: the recorded revenue, the cohort reconciliation, the sync and strategy state on seven of seven units, and the reported push timestamps. What separates them is not confidence but measurement, and a reader is entitled to see which is which without inferring it.

What a later record will add

A second operating record, measured the same way, would support a comparison this one cannot, if it holds:

• The cohort stays fixed, with additions, removals and unmatched records reported separately, so a changing portfolio is not read as changing performance.
• The metric, currency, window length and capture discipline stay compatible, with refunds, cancellations, fees and taxes handled identically on both sides.
• The approved decision, the affected units and stay dates, the previous and intended values, the decision maker and the publication time are on record.
• A channel observation is verified against unit, stay dates, guest count, currency and length of stay, distinguishing nightly charges from discounts, fees and taxes, and stating how many units or nights were checked.

Seasonality, available inventory and other material changes would still have to be reported alongside any comparison. These are requirements for that future record, not checks presented as already completed here.

Frequently Asked Questions

How much revenue did the managed portfolio record?

The seven units under Revande's pricing management recorded USD 232,784.15 in PriceLabs Portfolio Analytics reported trailing-90 revenue for June 21 through September 18, 2026, captured September 19 at 14:00 UTC. One historical row that did not match the current managed cohort is excluded. The figure describes this cohort and this window. It is not an estimate of revenue Revande added.

Does this show that Revande increased revenue?

It shows that Revande created the pricing strategy the portfolio sold on, and what the portfolio recorded on those rates. What it does not do is size the increase. Measuring how much Revande added would need a comparable period from before February 20, 2026 and a design that accounts for seasonality and inventory changes. Neither is supplied here, so no uplift figure is claimed. Authorship of the strategy is established; the size of its contribution is not quantified.

What exactly is Revande responsible for on this portfolio?

The pricing strategy for each of the seven managed units, the daily rate decisions, the monitoring and alerting, the monthly reporting, and the maintenance of the path that publishes those rates to Airbnb and Vrbo. King Rental Homes owns the properties, the guests, cleaning, maintenance, and approval of the guardrails Revande prices within.

Is USD 270.60 to USD 657.70 the current pricing range?

No. It is the range of per-unit reported historical ADR values for the window. The separately observed Minimum and Base spans are current pricing settings. None of the three is a portfolio-weighted ADR, a guest quote, or evidence that a particular unit was priced too high or too low.

Does sync ON confirm that Airbnb and Vrbo displayed the intended rates?

It confirms the publishing path was enabled and configured, with reported push timestamps, on all seven managed units. Confirming a displayed rate is a separate check: it needs a matched observation for the relevant unit and stay details, with its checked population recorded.

Does the guest-demand data from Airbnb show that Revande's pricing increased demand for these units?

No. Airbnb computes those conversion and impression figures from its own search and listing traffic, and Revande does not control most of the inputs behind them, including search ranking, photography, title, reviews and market demand. Revande authors the pricing strategy for the seven units, but no conversion figure is evidence that it caused, added, increased or drove a conversion, booking or revenue outcome.

Why does the guest-demand window not match the revenue window?

The guest-demand figures cover August 20 through September 19, 2026, the window Airbnb itself reports as last updated. The recorded trailing-90 revenue figure covers a different window, June 21 through September 18, 2026. The two evidence classes measure different periods from different sources and are never joined, summed, or presented as describing the same period.

Do these units charge more than comparable listings?

Five of the seven do, and all seven fill more nights than their comparison set. Across April 21 through September 19, 2026 the seven averaged USD 520.57 per night against approximately USD 414 for the set of similar listings Airbnb computes for their area, with occupancy between 75.6% and 94.9%. These are observations, not estimates of revenue Revande added, and the comparison set is Airbnb's own.

Why do two units price below comparable listings?

This record does not say. What it observes is that both units run occupancy above their comparison set while pricing below it. Establishing whether that was a deliberate pricing decision would need the decision record, the affected units and stay dates, and the approval, none of which is included here. An unestablished intent is not a measured one.

Related reading and next step

For the service boundary, read how pricing services work for property managers and where pricing service ends and property management begins.

Revande's booked-revenue methodology describes a separate company aggregate. This operating record does not establish this portfolio's inclusion in that aggregate, and the figures should not be added together.

Discuss your PM pricing workflow with Revande. Bring your unit count, PMS and approval responsibilities. Ask how the service will document decisions, publishing and the evidence used to check the result.

About the Author

Revande is a revenue management service for short-term rental portfolios. King Rental Homes is on its Performance service, which sets and maintains daily pricing under guardrails the owner approves.

This operating record was prepared by Revande from its own client records. Every figure on the page carries the source class, the window and the capture date it came from, and every boundary of the evidence is stated in Method and limits rather than left implicit. Revande publishes these records so a prospective client can check the reasoning, not only the result.

Sources

Every source above is a first-party operating record. None is an independently audited financial statement, and the private identifiers inside them are deliberately not published.