Start Bespoke, Become a Marketplace Later
A marketplace never starts as a marketplace; win with a pre-liquidity value prop first.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 92%
Because the true marketplace value proposition (removing the friction of two sides finding each other) only exists at scale, early-stage founders must ship a bespoke value proposition that works when they have no liquidity. Solve one sharp, concrete problem first, earn a foothold, then evolve toward matching and monetize the friction that actually matters.
Origin
Ramesh Johari, from work at odesk and observing UrbanSitter's early days.
Core principles
- 01The marketplace value proposition is at-scale friction removal, which you don't have on day one
- 02Your early value prop is necessarily bespoke and often has nothing to do with matching
- 03Solve one concrete, painful friction to seed liquidity, then shift monetization to the matching friction as it emerges
- 04Early monetization commitments can tie your hands once you actually become a platform
How to run it
- 1
Name the friction you can solve with zero liquidity
Find a concrete, painful problem in the space that you can resolve today, before you have scaled supply or demand.
Pro tip UrbanSitter's first wedge was simply 'we accept credit card payments for babysitting' — solving the cash-on-hand friction, not matching.
- 2
Ship that wedge and seed liquidity
Deliver the bespoke value so both sides have a reason to show up before any matching magic exists.
Pro tip odesk's first value prop was work-verification tooling (screenshots, tracking) that let remote workers prove hours and employers trust output.
- 3
Evolve toward matching once liquidity exists
With both sides present, shift toward solving the finding-and-making-matches frictions that define a real marketplace.
Pro tip UrbanSitter used parents' and sitters' Facebook networks to build trusted introductions once it had a base.
- 4
Re-price around the friction that now matters
Move monetization from the initial wedge to what customers now pay for: finding and vetting the other side.
Watch out A constant take-rate set in the early days can strand you when mature relationships need less of what you originally charged for (disintermediation risk).
In the wild
UrbanSitter launched not as a matching engine but by solving that high-school babysitters wanted paying at day's end and parents lacked cash: it simply accepted credit-card payment for babysitting. It then used Facebook networks for trusted introductions and later re-priced around interviewing and contacting sitters.
→ It seeded liquidity via a bespoke friction, then migrated monetization to the matching value once it had scale.
Common mistakes
Building matching features before there's anyone to match
Promising to help users find the other side when you have three of them is solving a non-existent friction.
Locking in a monetization scheme too early
odesk's constant 10% take became mismatched with value as relationships matured and the platform's contribution shrank, feeding disintermediation.
Is it for you?
Best for
Pre-liquidity founders in a space they believe will become a marketplace and need a day-one value proposition
Not ideal for
Businesses that already have two-sided scale and are optimizing an existing flywheel
From the transcript
“a Marketplace business never starts as a Marketplace business”
“when you start you had better be thinking what's my value proposition in a world in which I don't have that scale”
“which is literally just we accept credit card payments for babysitting that's it”
“the initial value proposition of odesk was to provide tools for workers to verify they were working the hours and doing the things that they…”
From the episode
Marketplace lessons from Uber, Airbnb, Bumble, and more
Ramesh Johari (Stanford professor, startup advisor)