Work record / Operating / Phoenix short-term rental launch
A Phoenix rental manager's launch: a fee the owner can repeat
Every manager in this category already quotes a flat share of gross, and owners cannot see what happens between guests. The opening was trust, not price format.
The seat
I have been an advisor on this launch since 2023, and still am. Before this I spent years running community management for a big residential community in California, and I consulted for other property managers.
| Sector | Short-term rental and property management |
|---|---|
| Type of work | Business model and launch |
| Where | Phoenix, Arizona |
| Years | 2023 to present |
| How long | Three years and ongoing |
| Through | Common Ground |
| Credits | Common Ground Jesse Fowler, Advisor |
What I was brought in to decide
In 2023 an owner-operator was starting a boutique short-term rental management company in Phoenix. The category already quoted a flat share of gross, and owners had no view of what the manager did between guests.
My job was the business model: work it through, compare it with how the major managers price and run things, and simplify it into something the company could launch on.
What we did
- We checked what the category really charges before accepting flat versus itemized as a pitch. It was already flat, so the pricing format was never the opening.
- We named the trust gap precisely. It was billing for services not fully rendered, marking up contractor invoices on the way through, and logging a maintenance call as handled when it had been deferred.
- We rewrote the offer as one sentence an owner can repeat back: a flat share of gross booking revenue, priced under what local managers usually charge. No owner-side add-ons, and no markup on contractor invoices. Whatever failed that repeat-it-back test came out: the tier that moved with occupancy, the maintenance dispatch line, and the cleaning coordination add-on.
- A simpler fee creates its own risk: a manager with a reason to skimp on maintenance and cleaning. We named it and designed the control. Each owner sets a maintenance-cost threshold at onboarding, and any spend above it needs the owner's sign-off.
- A guest-message log, kept by category next to reviews, catches a service failure during the stay, not weeks later in a review that most guests never write.
- An owner-onboarding question set finds inherited costs and fixes the threshold before a property joins.
- The model asked what the fee must carry before the operation can pay salaried people instead of leaning on an operator wearing many hats. With a flat share of gross, each unit leaves a margin of a few hundred dollars a month once the absorbed costs are paid. An operations lead and a guest-experience seat, two salaried roles, only become real at a few dozen units. The inputs are illustrative and are not the portfolio's books.
- What compounds is the categorized issue history across the portfolio, because a fee is something any competitor could copy in an afternoon.
Results
- It launched on this model, and the model still runs the company.
- Airbnb reserves a band for Superhosts, with a published floor of a 4.8 rating, and the company's listings have stayed inside it. I read that as the downside protected, not the upside proven.
- The operator came away with four tools: the guest-message log, the onboarding question set, the one-sentence fee test, and a maintenance threshold that needs the owner's sign-off.
The lesson
A fee works only if the owner can say it back. Complexity in the fee is where trust leaks out.
Questions about Phoenix short-term rental launch, answered
Firm record
Common Ground keeps its own account of this engagement: Phoenix short-term rental launch on the Common Ground wiki.