Latest / Marketplace Businesses with Fexingo: Two-Sided Networks, Liquidity, and Take Rates / How Airbnb Keeps Liquidity When Listings Vanish
Transcript
- Lucas: It's mid-August 2026, and the California wildfire season is already breaking records. But I want to talk about a moment from last October, because it's the cleanest stress test of a two-sided marketplace I've ever seen. Luna: You mean when the Palisades fire wiped out thousands of Airbnb listings overnight? Lucas: Exactly. One day you have a healthy marketplace in Los Angeles with hosts and guests transacting normally. The next day, tens of thousands of listings are either burned, damaged, or inside evacuation zones. And simultaneously, demand for temporary housing goes through the roof. That's a liquidity shock on both sides of the network at the same time. Luna: So the core problem is that supply just evaporated while demand spiked. How do you even start to fix that? Lucas: Well, the first thing Airbnb did was freeze new reservations in the affected areas for seventy-two hours. That might sound counterintuitive — you'd think you want to maximize supply — but it gave them time to figure out what was still bookable and what wasn't. Luna: Right, because if you let guests book a listing that's actually destroyed, you're creating a terrible experience and eroding trust. Lucas: Precisely. And trust is the currency of a marketplace. So they paused new bookings while they audited their inventory. Then they turned on a new tool that let hosts in safe areas mark themselves as offering emergency housing. That's not a normal feature — that's a specific crisis response. Luna: But that tool only works if hosts actually opt in. How many did? Lucas: Airbnb says that within a week, over twelve thousand hosts in the region had activated emergency housing status. That's a meaningful chunk of supply appearing out of what was previously a static inventory. The key was making the opt-in essentially one click and tying it to a clear promise: you're offering your place to someone who's been displaced. Luna: So they're turning the marketplace into a crisis response platform. But that raises a question — how do you set the take rate in a situation like that? You can't just keep the same commission when people are desperate. Lucas: And they didn't. Airbnb waived all guest and host fees on emergency housing stays for the first few weeks. That's a direct cut to their own revenue, but it's a smart long-term play. It signals that the platform is not just a middleman — it's a partner in the community's recovery. Luna: Interesting. So they're trading short-term take rate for long-term trust and retention. But how does that affect liquidity in the broader sense? Lucas: Think about it this way: liquidity isn't just about matching supply and demand at a given moment — it's about having enough depth on both sides so that transactions happen quickly and at reasonable prices. By waiving fees and making it easy for hosts to opt in, they're increasing the depth of supply. And by helping guests find housing quickly, they're increasing the velocity of transactions. Luna: So you're saying the fee waiver is essentially a liquidity subsidy, similar to what they might do in a cold-start scenario? Lucas: Exactly. The cold-start problem is about getting a marketplace off the ground — here, they're re-igniting liquidity in a specific region that's been shocked. The playbook is remarkably similar: subsidize one side, reduce friction, and get transactions flowing again. Luna: And what about the hosts who lost their properties? How does Airbnb help them, beyond the fee waiver? Lucas: They set up a host relief fund, and they worked with insurance partners to fast-track claims for hosts who had damage. But more importantly, they allowed hosts in unaffected areas to temporarily list additional spaces — like a spare room or a backyard unit — without going through the usual approval process. Luna: That's a clever way to increase supply without waiting for new hosts to onboard. It's like turning the network's idle capacity into emergency inventory. Lucas: Right. And that's the kind of elasticity you can only get if you've built your platform with flexible listing types from the start. Airbnb has always allowed hosts to list a room, a shared space, or an entire home. So when the crisis hit, hosts who normally only rented their whole place could switch to listing a single room — and they had the infrastructure in place to do that. Luna: Let's talk about the demand side for a second. You mentioned demand spiked — but who was actually booking? Was it just displaced residents, or were there other actors? Lucas: Mostly displaced residents, but also first responders, insurance adjusters, and even journalists covering the fires. Airbnb created a separate search category for 'emergency stays' that filtered for hosts who had opted in. That made it easier for guests to find verified safe options, instead of scrolling through a list of unvetted listings. Luna: So that's a product decision that directly addresses the information asymmetry in a crisis. It's not just about having listings; it's about making sure the listings you see are actually available and safe. Lucas: Exactly. And it's a reminder that in a two-sided marketplace, the product is not just the listings — it's the matching logic and the trust layer that surrounds them. Luna: I want to go back to something you said earlier about the seventy-two-hour freeze. That seems like a really short window for such a huge logistics challenge. How did they manage to audit tens of thousands of listings in three days? Lucas: They didn't audit every single listing manually. They used a combination of satellite imagery, fire perimeter data, and host self-reporting. They cross-referenced their own database against a map of the burned areas and automatically flagged any listing inside the perimeter. Then they reached out to hosts to confirm their status. It's a data-driven approach that scaled. Luna: So the freeze wasn't about manually checking — it was about giving the algorithm time to ingest the new data and update the availability status. Lucas: Exactly. And that's a key lesson for any marketplace operator: your data pipeline needs to be able to ingest external signals, like a fire perimeter, and act on them quickly. If you're relying on hosts to update their own calendars, you're going to have a bad time. Luna: And what about pricing? In a crisis, you'd expect prices to surge. Did Airbnb do anything to prevent price gouging? Lucas: They introduced a pricing cap for emergency stays. Hosts who opted into emergency housing had to agree to price their listing at no more than the average rate from the previous year. That's a clear signal that they were willing to sacrifice some take rate to keep the marketplace functional and fair. Luna: So that's another way to maintain trust — you're protecting guests from being exploited, and you're protecting the platform's reputation. Lucas: Right. And it's interesting because some economists would argue that surge pricing would allocate scarce housing more efficiently. But in a crisis, the optics of that are terrible, and it would erode trust in the platform. So Airbnb made a deliberate trade-off: they capped prices to preserve trust, even if it meant some inefficiency. Luna: Do you think that's the right call for the long-term health of the marketplace? Lucas: I think so. The platform's value proposition isn't just 'we have listings' — it's 'we have listings that you can trust.' And in a crisis, trust is the most important asset you have. If they had let prices spike, they would have alienated a whole cohort of users who might never come back. Luna: It's also worth noting that Airbnb did something similar during the early pandemic — they offered free housing to healthcare workers. So this isn't a one-off; it's part of their DNA. Lucas: Exactly. And that's why this crisis response feels so polished. They've had practice. But the wildfire case is different because it's a supply shock, not just a demand shock. During the pandemic, they had plenty of supply but no demand. Here, they had a sudden drop in supply and a sudden surge in demand. That's a much harder balance. Luna: Let's think about the operational playbook for a moment. What are the key levers that Airbnb pulled, and could another marketplace replicate them? Lucas: The first lever is the ability to instantly change the product logic — like the emergency housing toggle and the search filter. The second is the fee waiver, which is a direct financial incentive for supply to come online. The third is the pricing cap, which protects demand-side trust. And the fourth is the integration with external data, like fire perimeters. Luna: So it's a combination of product, pricing, and policy. That's a lot of moving parts. Lucas: But the underlying principle is simple: when a liquidity shock hits, you need to move fast to rebalance the network, even if that means temporarily sacrificing margin and breaking your own rules. The goal is to keep the network alive so that when the crisis passes, you can rebuild faster than your competitors. Luna: And has Airbnb seen any long-term benefits from this approach? I'm thinking about host loyalty and guest retention. Lucas: Early data suggests that hosts who opted into emergency housing are more likely to stay active on the platform a year later, compared to hosts who didn't. And guest retention in affected areas is also up. It's a small effect, but it's measurable. Luna: That makes sense — you're building a relationship with both sides during a vulnerable moment. They'll remember that you helped them when they needed it. Lucas: And that's the ultimate take rate strategy: not just charging more, but creating a marketplace that people don't want to leave. Because in a two-sided network, your biggest moat is the loyalty of your users. Luna: Before we wrap, I want to go back to the seventy-two-hour freeze. Was there any pushback from guests who had existing reservations? I mean, they were told their booking was on hold. Lucas: There was some panic, of course. But Airbnb's communication was key. They sent proactive emails to guests with upcoming reservations in the affected zones, explaining the situation and offering full refunds or rebooking assistance. They also gave hosts a window to confirm whether their place was still available. If a host couldn't confirm, the reservation was automatically canceled with a full refund. Luna: So it was a very clear policy: either you confirm your listing is safe, or we cancel and refund. That's a decisive way to avoid ambiguity. Lucas: Exactly. And it's a good example of how a marketplace can handle a crisis without alienating either side. The key is to be transparent and to make the decision on behalf of the user when the user can't make it themselves. Luna: Now, when you think about the future of marketplace design, what's the one takeaway you hope listeners walk away with? Lucas: That liquidity isn't just a metric you measure — it's something you actively manage, especially in times of shock. And the best marketplaces are the ones that have a playbook for rebalancing supply and demand when the unexpected happens. That's what separates a platform from a directory. Luna: That's a great note to end on. Thanks for breaking this down with me, Lucas. Lucas: Anytime, Luna. For our listeners, if you're building or running a marketplace, remember that your network is only as strong as its ability to weather a storm. See you next time.