Everybody in the category already charged a flat share
In 2023 an owner-operator getting a boutique short-term rental management company off the ground in Phoenix asked me to look at the business model. The brief had three parts. Work the model, compare it against how the major property management companies price and operate, and simplify it into something the company could actually launch on. I came to it after years of running community management for a large residential community in California and consulting for other property managers, which is where I learned that a fee schedule can serve the manager as cover instead of serving the owner as clarity.
The people in it were the operator, who was doing everything at launch, from pricing the listings to answering guests at midnight; the cleaning and maintenance contractors, the only people who ever see the inside of a unit between guests; the owners, most often someone who does not live near the property and cannot drop by; and the guests, the only people who see the service as it is delivered. That last point is the whole engagement in one line. The owner pays for the service and cannot see it. The guest sees it and is not the one paying the manager.
Where the company was: small, informal, and about to enter a category that pitches on pricing format. Managers in Phoenix, like managers everywhere, sell "flat fee versus itemized" as if the format were the product. Before accepting that, I checked what the category actually charges. National platforms run a wide range by service level, local managers cluster in a tighter band, and every one of them already quotes a flat share of gross. The cover figure is that comparison. Entering on "flat, not itemized" would have meant entering on the thing everyone already does.
What the company actually needed was narrower and harder. Owners hand a manager the keys to their largest asset and have almost no way to observe what happens next: whether a cleaning was rushed, whether a maintenance call was handled or deferred, whether a guest complaint was fixed or smoothed over. That is a principal-agent problem, and the category's fee schedules, with their add-ons and a markup on contractor invoices no owner can audit, are its symptom rather than its cure. The company needed a fee an owner could hear once and say back correctly, two controls for the risk that fee creates on the cost side, and a way to make something other than the fee the thing that compounds as the portfolio grows.
The sentence, and then the risk the sentence creates
Three options were on the table. Match the category: price in the local band, itemize the add-ons the way everyone does, and compete on marketing and reviews. That is the safe opening move for anyone without the standing to argue the norm is wrong, and itemized billing reads to most owners as accountability. Compete on format: lead with "flat, not itemized" and hope it reads as different. It would not have, because the comparison on the cover says the category is already flat. Or fix the sentence: strip the offer to the one thing an owner can verify, and then build the controls for what the simpler offer no longer covers.
We took the third. The offer became one sentence: a flat share of gross booking revenue, set below what local managers typically charge, with no owner-side add-on billing and no markup on contractor invoices. The share itself stays between the company and its owners. The test that produced it was simple. An owner who hears the fee once has to be able to say it back correctly, and anything that failed that test came out: the cleaning coordination add-on, the maintenance dispatch line, the tier that shifted with occupancy. The number itself was a pricing decision, set to undercut the local band while still, on the modeled check in the section after next, covering the cost the fee absorbs. It was not derived from a cost stack and I do not present it as one.
Here is where the money moves under that sentence, and where the old models hid a spread.
| Who pays | What it is | Who keeps it | Where the old models hid a spread |
|---|---|---|---|
| Guest | The nightly rate, through the platform | Gross booking revenue, from which the manager's flat share is taken | A tier that moved with occupancy, so the owner could not compute the take |
| Guest | The cleaning fee | Passed through to the cleaning contractor at cost, per platform convention | Marked up, or billed to the owner a second time as "coordination" |
| The fee | Small maintenance, below a cost threshold | Absorbed by the manager inside the flat share | Itemized to the owner as a dispatch or handling line |
| Owner | Larger repairs, above the threshold | Paid at the contractor's invoice, no markup, with the owner's sign-off first | A markup in transit on an invoice the owner never saw |
| Guest, or the platform's host guarantee | Damage | The deposit or the guarantee, per platform terms | Billed to the owner as a surprise add-on |
The sentence closed the clearest misalignment, the one an owner could never audit. It did not close the whole gap, and this is the part most pitches in the category skip. A manager who now absorbs small-repair and cleaning-coordination cost out of a fixed fee has a structural reason to under-invest in exactly the maintenance and cleaning quality the fee is supposed to buy. That is the mirror image of the add-on problem the flat fee was built to avoid. So the design was never "pick a fee structure". It was "pick a fee structure and build the controls its own incentive requires".
How I came at this one
The first question was what new incentive the fix itself creates once the add-on incentive is gone, and the answer was a manager with a reason to skimp on maintenance. That question fit because a flat fee is a promise the owner cannot check, and every promise like that needs a control built for the specific way it can be broken.