The big platforms are built for guests.
Who is on the host's side?

Airbnb and Booking.com are extraordinary products. They have solved the discovery and booking problem for travellers in a way that was unimaginable twenty years ago. The guest experience on those platforms is genuinely excellent.

But the revenue model of those platforms comes from guests — or more accurately, from the transaction that puts a guest in a room. Which means every product decision, every algorithm, every new feature is ultimately designed to serve the guest journey. The host is the supply side. Necessary, but not the focus.

This is not a criticism. It is just how the economics work. But it creates a real gap.

The fragmentation problem

Into that gap, a whole ecosystem of tools has grown. Channel managers. Dynamic pricing software. Guest communication automation. Digital guidebooks. Smart lock integrations. Review management tools. Each one solves a specific problem reasonably well.

But here is what nobody tells you: you still have to decide which tools to use. You still have to integrate them. You still have to manage the integrations when they break. You still have to train yourself on five different dashboards. And you still have to be the one who picks up the phone when something goes wrong at midnight on a Friday.

"Hosting becomes a real job — and then a full-time business. It keeps the mind occupied in a way that stops you from scaling, or simply stops you from sleeping."

The co-host question

Then there are co-hosts. The pitch is appealing — someone who already knows how to manage short-term rentals takes on your property for a percentage of revenue. The reality is more complicated.

A lot of co-hosts have good ratings recently. Some of those ratings were obtained by following up with guests persistently until they left a review. Not all guest feedback is given freely — sometimes it is given to stop the messages. That does not qualify someone to share profit from your already well-performing property. When you are evaluating a co-host, you need to understand exactly what they are bringing that you are not already doing yourself.

The question to ask is not "do they have good reviews" but "what is the value proposition — what specifically do they do that I cannot or do not want to do?"

What a real service looks like

This is the gap that Dropby's Hosting-as-a-Service was designed to fill. Not a tool. Not a co-host arrangement. A full operational service that replaces the entire stack.

• Dynamic pricing updated daily — not a flat rate set once a month
• Guest communication automated from enquiry to checkout message
• Calendar management across all platforms with real-time sync
• Check-in system that does not require you to hand over a physical key
• Screening logic — we do not accept one-night stays on Friday and Saturday, for example, because the profile of guest and the risk profile do not make sense for the property
• The Dropby tech layer — branded WiFi, digital guide, guest ecosystem

Service versus tool — important distinction

We also have products in our portfolio — specific tools for hosts who want to self-manage but smarter. Those are available at product.dropby.biz. They are good products and we stand behind them.

But it is important to be clear about the difference. A service replaces your entire operational burden. A tool improves a specific part of it. If you are trying to use tools to avoid needing a service, you will end up with a collection of tools that you still have to manage.

The HaaS model is designed for the host who has decided they want the result — revenue, good guests, maintained property — without the operational overhead of producing it themselves. It is a different product from a tool, and it should be evaluated differently.