Chickens, Eggs, and Liabilities “I will not promote”

TL;DR: Solve discovery, not transactions.

Building a marketplace as a solo founder is one of the hardest startup options to choose.

If you don’t have supply, users leave. If you don’t have demand, suppliers churn. Doing the manual grinding to fix both sides by yourself simply doesn’t scale and you’re competing with incumbents with potentially billions in ad spend a year.

The shortcut I’ve learned is to separate discovery from transactions. Google Flights doesn’t convince airlines to list flights one by one. It aggregates existing inventory and redirects users to complete the booking with the airline.

I think the same model can work for short term rentals.

1. The chickens may already exist

The biggest realization for me was that the supply side may already exist.

In many industries, suppliers have already organized themselves. They already have inventory, pricing, availability, and their own customer-facing websites.
Instead of convincing them to join another marketplace, discover the marketplaces they’ve already built.

Supply then becomes a software problem, not a sales problem.

2. Reducing Transactional Liability

Traditional marketplaces are responsible for payments, fraud prevention, chargebacks, customer disputes, trust and safety, and significant operational overhead.

Google Flights avoids nearly all of that by never becoming part of the transaction.

The same architecture works here. Guests are redirected to the property manager’s existing checkout, where payments, identity verification, fraud prevention, insurance, and customer support already occur.

By separating discovery from transactions, the platform avoids becoming the merchant of record while dramatically reducing operational complexity.

3. Protect the Eggs

Supply can be aggregated. Demand can’t.

Suppliers already have businesses to run, so they’re relatively durable. Consumers are different. Lose them once and they’re usually gone for good.

The real long-term asset isn’t the suppliers. It’s every guest you convince to come back. Each one can become a repeat customer, refer friends, and grow demand across the entire network.

Why I’m Following This Approach

I never wanted to build another OTA marketplace.

The original vision was a network of hosts where guests could easily find and book directly with hosts while helping hosts reduce dependence on high commission platforms.

As I kept building, I realized the real opportunity wasn’t recreating another booking platform. It was making the growing ecosystem of direct booking websites searchable

Professional hosts are already investing in their own distribution. Their inventory is simply fragmented across thousands of independent websites.

I’m still solving the demand side beyond organic growth. Separating discovery from transactions doesn’t automatically solve distribution.

One thing that surprised me was how much guest data came from a relatively small amount of supply. With just 4 hosts managing a little over 80 properties, my PMS integrations have already imported over 20k guest profiles (not all include contact information since many are inquiry-only profiles). It makes me wonder what that looks like at much larger scale.

Aggregating those sites creates value for both travelers and hosts without requiring another centralized marketplace.

What This Could Mean for OTAs

As more professional hosts invest in direct booking, centralized marketplaces may become less important as the only place travelers discover inventory.

Traditional OTAs still have enormous advantages in brand, reviews, trust, and customer acquisition, but discovery and transactions don’t necessarily have to live on the same platform.

Separating those layers creates a very different cost structure for new entrants.

The Takeaway for marketplace builders

Stop trying to build a better marketplace and start building a better way to discover one.