A 24 month co-hosting term means little if the owner can withdraw any unit on 30 days notice

This is a mistake worth studying because it hides inside a clause that reads like protection. Say a co-hosting agreement covers five units under one owner, all within a fifteen minute loop. Fee structured at 15 percent of collected nightly revenue portfolio wide, 24 month term, and buried in there a clause letting the owner terminate or withdraw any unit on 30 days written notice. The 24 months binds the operator. It protects nothing on the revenue side, because the withdrawal right lets the book shrink to zero one unit at a time while the operator stays locked in. Against that, a reasonable buildout looks like a part time turnover coordinator around $19 an hour, 25 hours a week, roughly $2,050 a month, plus $340 a month of channel and pricing software across five listings. On gross running near $17,300 a month, a 15 percent fee nets about $2,595, against maybe $200 a month of margin plus the operator's own labor. That's an acceptable trade if the point is building a base to add owners onto. The trap springs when the owner lists three of five units for sale in month four. Buyers want them vacant, calendars go dark, the fee drops to around $1,450 a month on what's left. Fixed labor and an annual software tier don't shrink with the book. Cut the coordinator's hours and turn quality slips, review average can fall from something like 4.9 to 4.6, and a newer owner brought on in the meantime can walk over exactly those reviews. Nine months in, a book like this can run roughly $6,900 behind plan, with a trained coordinator lost along the way. What holds up better: a minimum monthly fee per unit so the floor doesn't move with a sale, a withdrawal fee for any unit leaving the book inside the term, 90 days notice rather than 30 since a hiring cycle needs more runway, and labor priced per turn rather than fixed against revenue that can walk on a month's notice, at least until the book has more than one owner in it.