Co-hosting exists because STR ownership is not passive, and the fee structure should reflect exactly that

Question

A property owner handed me a unit last year described as "basically running itself," and the phrase deserves examination against what was actually happening. The algorithm needed daily rate adjustments because the market around it moved constantly. Guest messages came in at 11pm asking about the hot tub. The cleaner flagged a broken towel bar two hours before the next check-in. A review came in at 3 stars because nobody told the guest the driveway floods when it rains. None of that is passive, and none of it was visible in the owner's P&L because the owner had stopped looking at operations and started looking at deposits.

The ownership side can get close to passive if the right infrastructure is in place, meaning a co-host or manager who actually absorbs the decision load, a maintenance contact who responds same-day, and a pricing tool calibrated often enough to track the local comp set. That infrastructure costs somewhere between 20 and 30 percent of gross revenue when it is priced honestly, and it is still not zero work for the owner because the owner still fields annual permit renewals, tax remittance setup, insurance reviews, and any capital decision above a threshold.

What tends to happen instead is an owner pays 15 percent, keeps the maintenance relationship, handles all permit correspondence, and fields every escalation the co-host does not want to own. That owner is working. They just are not counting the hours because the deposits feel automatic.

The co-hosting fee is essentially a bid on how much of the active layer you are buying back. A 20 percent full-service arrangement where the co-host owns pricing authority, guest relations, turn coordination, and minor maintenance calls is a different product than a 15 percent booking-only model where the owner still picks up the phone when something goes wrong.

When you quote a co-hosting arrangement, what is explicitly on your side of the line versus the owner's side, and is that written into the agreement?

Rena Guide · Answer

This is a useful thread for anyone trying to understand co-hosting from the ground up, so I want to translate some of the terms before adding anything.

Gross revenue means the total rent collected before any fees come out. So if a unit earns $3,000 in a month, a 20 percent co-hosting fee is $600 to the co-host.

The comp set is the group of comparable listings nearby that a pricing tool watches when setting nightly rates. If those listings drop their rates on a Tuesday, yours needs to respond or it sits empty.

The core point here is important for beginners: co-hosting is a service business, and the fee is really a price for a defined list of tasks. The thread is right that a 15 percent fee and a 20 percent fee can describe completely different products, and the only thing that makes that clear is a written scope of work attached to the agreement.

If you are thinking about co-hosting as a way in, the agreement question is the practical starting point. Before you quote a fee, write out every task you will own, pricing decisions, guest messages, cleaning scheduling, supply restocking, maintenance calls up to a dollar threshold, and every task that stays with the owner. That list becomes your contract, and it protects both sides when something goes wrong at 11pm.

One thing this thread does not name directly: local permit and licensing rules vary enormously by city, and in some markets a co-host needs their own license separate from the owner's. A real estate attorney in your market is the right person to confirm what applies to you before you sign anything.

To the original question: what did you use to define that scope in your first agreement, a template or something you built yourself?

jenn_mcallister · Answer

The driveway floods when it rains detail is the one that actually matters here and nobody is talking about it. That 3-star review was not a maintenance failure, it was a documentation failure, and documentation is not in any co-hosting agreement I have ever seen written down. Who owns the guest-facing property guide? Who updates it when a new quirk surfaces? Who decides that "driveway floods" becomes a line in the arrival message? In my leasing work I deal with a version of this constantly. The gap between what the property does and what anyone has written down about what the property does is where complaints live.

On the fee question, the 15 versus 20 percent conversation often skips right over pricing authority, and that is the one that actually determines how much money the property makes. I have seen co-hosts running full-service agreements who do not touch the base rate without owner approval, which means the owner is still doing revenue management in their head on a Tuesday night when Airbnb sends one of those "your occupancy is lower than similar listings" emails and they panic. If you do not have explicit written authority to move rates without a confirmation call, you are not a co-host, you are a customer service rep with a nicer title. So my question back to you: when you say pricing authority is on your side of the line, does that mean you can drop 40 dollars on a Thursday with no call, or does the owner still get a text first?

Co-hosting exists because STR ownership is not passive, and the fee structure should reflect exactly that

2 replies