Supply-First Marketplace Building
Marketplaces aren't chicken-and-egg — they're two-sided, and you always start with supply.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 92%
Camille Hearst rejects the standard 'chicken-and-egg' framing of marketplaces. Having run the supply side at Hailo (the London ride-hailing competitor to Uber/Lyft) and later at Patreon and Spotify, she argues the sequencing question is already settled: build supply first, because no amount of demand, marketing, or UX polish survives an empty shelf. The framework is a sequencing rule plus a conflict-resolution rule for when the two sides' interests collide.
Origin
Hearst's own experience running the supply side of Hailo in the US, where she launched their private-hire (livery) product from zero against Uber and Lyft — and watched a beautiful ops backend and UI fail the moment a user opened the app and no cars were available. Reinforced across her creator-side roles at YouTube, Patreon and Spotify, all of which are supply-side (creator) positions in a two-sided market.
Core principles
- 01A marketplace is two-sided, not chicken-and-egg — the ordering is knowable, and supply comes first.
- 02Supply is the stuff on the shelves: without inventory there is no store, no matter how good the storefront.
- 03Demand quality is capped by supply quality — great UX and marketing amplify an empty marketplace into a faster disappointment.
- 04Pick a side to prioritise in advance, so that when the two sides' interests conflict you have a pre-made decision instead of a debate.
- 05Supply pain is business risk: unhappy suppliers churn, strike, or get regulated out, and the demand side feels it instantly.
- 06The rule has exceptions — where the supply act is trivially easy and inherently appealing, demand becomes the hard side.
How to run it
- 1
Name the two sides explicitly and reject the chicken-and-egg frame
Write down who supplies and who demands. Refuse the framing that both sides must be solved simultaneously — decide that supply is the side you will invest in first, and give the team that clarity up front.
Pro tip Use the store metaphor to settle internal debates: if you have a shop, supply is the stuff on your shelves, and no shopfront saves you from empty shelves.
- 2
Run the empty-app test before investing in demand
Simulate the moment a user opens your product with today's actual supply. If the answer is 'nothing available' or 'nothing good available' in your target segment, every dollar spent on marketing or UX is spent early.
Watch out Great operations plus great UI feeding an empty inventory is the exact failure Hearst lived through — the polish hides the problem from the team, not from the user.
- 3
Check the rare inversion before committing
Ask whether supplying is easy, fun, and obviously worth it for the supplier. If almost anyone would happily do it (Hearst and Lenny's example: Rover — who wouldn't make fifty dollars watching a dog?), supply may be the easy side and demand the real constraint. Otherwise, assume supply is hard.
Pro tip Test this by trying to recruit ten suppliers cold. If it takes weeks, supply is your bottleneck and the default rule applies.
- 4
Solve real supply pain, not just supply acquisition
Go deep on the suppliers' actual needs and pain points — earnings, tooling, predictability, treatment — because the whole business rests on their continued participation. Acquisition without retention just refills a leaking bucket.
Pro tip In creator marketplaces, the supply pains are usually audience growth and reliable income; in logistics marketplaces they are utilisation and regulation.
Watch out Suppliers who are unhappy, striking, or blocked by regulation take your demand side down with them.
- 5
Pre-commit a tiebreak side for conflicts
Decide in advance which side wins when the two sides' interests genuinely conflict (pricing, fees, quality bars). Optimise for the other side within that constraint rather than re-litigating the trade-off case by case.
Watch out You cannot be successful with only one side — the tiebreak is a priority order, not permission to neglect demand.
In the wild
Hailo dominated European taxi-hailing but had no product for the US 'livery' / private-ride model that Uber and Lyft ran on. Hearst had to launch that from scratch: get drivers on, create the supply. The team had built a strong operations backend feeding a strong UI, but the user-facing truth was brutal — open the app, no cars.
→ The experience permanently converted Hearst to supply-first: it doesn't matter how nice the user experience is, how great the marketing is, or how much demand you generate if the app is empty when someone opens it.
Lenny's marketplace research surfaced a rare counter-case: Rover, the dog-sitting marketplace, found supply trivially easy to recruit because plenty of people happily wanted to make fifty dollars watching a dog for a few hours. Demand, not supply, was their harder side.
→ Confirms the inversion test — when supplying is easy and appealing, the default supply-first rule flips, but this is the exception, not the norm.
The usual objection is eBay: they aggregated demand so effectively they could dictate terms to sellers. Hearst pushes back — she can't imagine the thing started without someone going out and figuring out which key suppliers to get on the platform first, so that there was anything worth aggregating demand around.
→ Even the canonical demand-side marketplace almost certainly bootstrapped supply first; the demand-side power came later.
Common mistakes
Treating the launch as chicken-and-egg and splitting effort evenly
Hedging across both sides means neither reaches the density that makes the marketplace usable. The two sides are sequential, not simultaneous.
Polishing the storefront while the shelves are empty
Investing in ops, UI, and marketing before there is real inventory just makes the empty experience arrive faster and more professionally.
Treating supply as an acquisition funnel rather than a set of pain points
You can't lose sight of solving real pain points and needs for the supply side — suppliers who churn, strike, or get regulated out collapse the demand experience too.
Is it for you?
Best for
Founders and product leaders launching or scaling a two-sided marketplace (rides, creators, services, goods) who are deciding where to spend the first year of effort.
Not ideal for
Single-sided SaaS or DTC products, and the rare marketplace where supplying is trivially easy and self-motivating (Rover-style), where demand is the real constraint.
From the transcript
“I actually just think they're two-sided and you should start with the supply.”
“And it was like it doesn't matter how nice the user experience is, how great the marketing is, how much demand you can generate if…”
“you just can't lose sight of the solving real pain points and needs for the supply side in order to make sure the entire business…”
“The way I think about it is that's like if you have a store, that's the stuff on your shelves.”
From the episode
Monetizing passions, scaling marketplaces, and stories from a creator economy vet
Camille Hearst (Spotify, Patreon, Apple, YouTube)