So here's a fun scenario for anyone who's ever built or evaluated guest-facing technology. A host in Hermosa Beach rents her townhome on Airbnb. Guest books for a month, pays for 48 days, then just... stays. Refuses to leave. And because California law grants tenant rights to anyone occupying a property for 30 consecutive days, the host now has to go through a formal eviction process that could take six months and cost her upward of $70,000 in lost income, mortgage payments, property taxes, and legal fees. Airbnb's response? "We can't enforce local eviction laws." That's it. Platform washes its hands. Host is on her own.

This isn't even the first time. Back in 2021, a Los Angeles host had a guest overstay for approximately 570 days. Five hundred and seventy. The guest demanded a $100,000 relocation fee to leave. And she had legal cover because the unit had unpermitted construction, which under California law meant the host couldn't even complete the eviction. The platform that "disrupted" hospitality couldn't do a single thing about it.

Look, I'm not here to pile on Airbnb for fun. I've spent my career evaluating technology platforms, and I apply the same test to all of them: what happens when the system fails? What's the recovery path? For hotels, the answer is straightforward. Guest won't leave? You call the police. It's trespassing. The legal framework is clear, the operational playbook exists, and the front desk knows what to do at 2 AM. For Airbnb hosts, the "recovery path" is hiring a lawyer and waiting six months while someone lives in your property for free. That's not a platform failure. That's an architecture failure. The entire system was built without accounting for what happens when a bad actor exploits the gap between short-term rental technology and long-term tenancy law.

And Airbnb's recent policy changes aren't helping. They retired their "Strict" cancellation policy in late 2025, replacing it with a "Firm" policy that's more guest-friendly. They started sharing hosts' full addresses and contact information with guests immediately upon booking. They now allow payout reversals after a stay is complete if a guest disputes. Every single one of these changes shifts risk from the platform and the guest onto the host. I've evaluated vendor relationships where the provider slowly transfers operational risk to the customer while maintaining the same fee structure... it's one of the oldest moves in the book. The host is bearing more risk, getting less protection, and paying the same commission. That math doesn't work for long.

What actually fascinates me here is the technology question nobody's asking. Airbnb is one of the most sophisticated technology companies on the planet. They have AI-powered pricing, dynamic search algorithms, identity verification systems, and review analytics that would make most hotel PMS vendors weep with envy. And yet they cannot solve for a guest who simply refuses to leave. The technology handles the transaction beautifully. It handles the failure state not at all. I think about this a lot because I built a product once that handled the demo perfectly and fell apart the first night it went live. The difference between a technology that works in the presentation and a technology that works at 2 AM when nobody's watching... that's the whole game. Hotels figured this out decades ago. The legal infrastructure, the operational protocols, the staffing models... they all account for the worst-case guest scenario. Airbnb built a $80 billion company on the assumption that the worst case wouldn't happen. It keeps happening.

Let me tell you what keeps me up at night. Not OTA commission creep. Not tariffs on imported FF&E. It's the stuff that blindsides you because you never thought to look for it.

A guy walks into a Manhattan hotel in 2018. Pays $200 for one night. Then he doesn't leave. He finds an obscure New York City housing law that applies to buildings constructed before 1969... this particular hotel was built in 1930... and requests a six-month lease as a single-room occupant. The hotel's legal team apparently didn't show up to the housing court hearing. A judge awarded him "possession" of the room by default. By default. Let that sink in. Because someone didn't put a lawyer in a chair, this guy lived rent-free for five years.

But here's where it gets truly insane. He didn't just squat. He escalated. Forged a deed and uploaded it to a city property records website claiming he owned the entire hotel. Then he tried to collect rent from a commercial tenant in the building. Registered the property under his name for water and sewage payments. Attempted to transfer the hotel's franchise agreement. Tried to borrow against the property. At one point, he offered to "sell" the hotel back to its actual owners for $14 million. This went on from 2019 to 2023 before he was finally evicted. He just pleaded guilty to fraud charges and got six months (time served) plus five years probation. Six months. For a scheme that lasted five years and targeted a property worth hundreds of millions.

I knew a GM once at an older downtown property... pre-war building, beautiful bones, the kind of place with a hundred years of legal quirks baked into the walls. He told me the scariest call he ever got wasn't about a burst pipe or a guest injury. It was from a process server. Someone had filed a lien against the property based on a fabricated contract. Took eight months and $60,000 in legal fees to unwind. Eight months where the ownership group couldn't refinance, couldn't sell, couldn't do anything because the title was clouded. His takeaway? "I check our property records every quarter now. Every quarter. Like I check the fire suppression system." That's the mindset.

Look... most of you aren't running historic Manhattan hotels with pre-1969 housing law exposure. But the principle here is universal. Every property has legal vulnerabilities that nobody thinks about until someone exploits them. Tenant protection laws vary wildly by jurisdiction. Property record systems in most municipalities are shockingly easy to manipulate. And the single biggest failure in this case wasn't the obscure law or the forged deed... it was that nobody showed up to court. That's an operational failure. That's a process failure. That's the kind of thing that happens when legal compliance lives in someone's email inbox instead of on a calendar with alerts and accountability. If you're a GM, you need to know three things right now. One: what housing and tenant protection laws apply to your specific property based on its age, its jurisdiction, and its zoning classification. Call your attorney this week and ask. Two: who is monitoring your property records for unauthorized filings? If the answer is "nobody" or "I assume our management company handles that," you have a problem. Title monitoring services exist. They cost almost nothing compared to the alternative. Three: do you have a written protocol that ensures legal representation at every single court proceeding related to your property, no matter how trivial it appears? Because "trivial" is how a $200 room night turns into a five-year occupation and a forged deed claiming your entire building.

The guy got six months. The hotel got five years of headaches, massive legal bills, a room generating zero revenue, and its name in every headline as the property that got conned by a single guest with a $200 reservation. The math on prevention versus response here isn't even close.