July 24, 20267 min read
Two-Sided Marketplace MVP: Which Side Do You Build First?
StrategyMarketplace
A
Don Wishvantha
The short answer is supply. Here's why you build the seller side of a marketplace before the buyer side, and how we did exactly that shipping Autara.
// tl;dr
Build the supply side first. In almost every two-sided marketplace the sellers are the harder, slower side to acquire, and the reason buyers show up at all. So you recruit a small set of high-quality suppliers, give them real tools, and only then open the doors to demand. When we built Autara, an Australian vehicle-care marketplace, we shipped the merchant side to feature-complete before the customer app, five apps in six months, merchant-first. This guide covers why supply-first is the default, the two situations where it isn't, and how to sequence a marketplace MVP so you're never building both sides at once.
Why “which side first” decides your whole MVP
Every marketplace starts with the same trap: the chicken-and-egg problem. Buyers won't come without sellers, and sellers won't stay without buyers. The instinct is to build both sides at once so neither is missing at launch. That instinct is what kills most marketplace MVPs.
A two-sided or multi-sided marketplace MVP typically costs $15,000–$60,000 in 2026, several times more than a simple SaaS tool at $2,000–$5,000, precisely because it is really two products. Build both halves on one early-stage budget and you get two half-finished apps, neither good enough to attract its side. Sequencing the two sides is how you spend that budget once instead of twice.
The default answer: build supply first
In most marketplaces the supply side is the constrained one. Good sellers are scarce, they take real effort to recruit and verify, and their inventory is the entire reason a buyer opens your app. Demand, by contrast, is comparatively easy to point at something once that something exists. The rule of thumb every experienced marketplace founder repeats: fill the store before you open the doors.
“Sellers will wait around for buyers. Buyers won't wait around for sellers.”
The practical move is to recruit a small group of “anchor” suppliers, five to fifteen high-quality sellers whose presence makes the marketplace feel worth visiting, using incentives like reduced commission, free listings, or early-partner status. Give them tools good enough that they'd use you even before the buyers arrive. Then, and only then, turn on demand.
| Supply-first (default) | Demand-first (rare) | |
|---|---|---|
| Build first | Seller tools, onboarding, listings, payouts | Buyer discovery + booking |
| Best when | Sellers are scarce or high-value | Sellers are an abundant commodity |
| Cold-start tactic | Anchor vendors, fee holidays, concierge onboarding | Pre-aggregate demand, waitlists |
| Main risk | Launching to thin demand | Sellers churn before buyers arrive |
| Example | Autara, merchants first | Some attention / ad marketplaces |
When to build the demand side first instead
There are two honest exceptions. First: when supply is an abundant commodity and the buyers are the scarce, valuable side, if any seller will happily join the moment there's demand, then demand is your real constraint and you build for it first. Second: when you can aggregate demand cheaply (a waitlist, an audience, an existing channel) and use that demonstrated demand as the pitch that recruits supply. Both are rarer than founders think. If you're unsure which side is scarce, it's almost always supply.
How we sequenced it for Autara
Autara is a two-sided vehicle-care marketplace connecting Australian car owners with vetted detailing and wrapping merchants. We built the merchant side to feature-complete before the customer-facing app: guided onboarding with business verification (ABN, insurance, licences), Stripe Connect for split payments and payouts, full service management, and automated image moderation, the whole onboarding flow backed by 90+ automated tests. Five apps in total across iOS, Android and web, shipped in six months, merchant-first.
Two decisions made supply-first affordable. The architecture is serverless (AWS Lambda, AppSync), so infrastructure costs stay near zero while the platform recruits its first merchants. And because the merchant tools were genuinely useful on their own, early sellers had a reason to onboard before a single buyer existed. That's the point of building supply first: the seller side has to stand up on its own.
A supply-first marketplace MVP checklist
- Recruit 5–15 anchor suppliers before you write a line of buyer-facing code.
- Give suppliers real tools, onboarding, listings, payouts, not a spreadsheet and a promise.
- Build trust signals early: identity/business verification, secure payments, reviews.
- Make one real transaction possible end-to-end. That first transaction is the whole MVP.
- Instrument supply liquidity before opening demand, know your inventory is real.
- Keep infrastructure cheap (serverless) until both sides exist.
Sequence the sides, prove one real transaction, and keep your infrastructure cheap until demand is real. Do that and the chicken-and-egg problem stops being a paradox and becomes a schedule.
// frequently asked
Which side of a two-sided marketplace should you build first?
Supply, in most cases. Sellers are usually the scarce, high-value side and the reason buyers show up, so you recruit a small group of quality suppliers and give them working tools before opening the marketplace to demand.
Why build the supply side of a marketplace first?
Because buyers won't visit an empty marketplace, and sellers are the harder side to acquire and verify. Sellers will wait around for buyers to arrive; buyers won't wait around for sellers. Build the store's shelves before you open the doors.
How much does a two-sided marketplace MVP cost?
Typically $15,000–$60,000 in 2026 for a marketplace or multi-sided platform, versus $2,000–$5,000 for a simple SaaS tool. Building both sides at once on an early budget is what blows it, sequencing the sides is how you avoid paying twice.
How long does it take to build a marketplace MVP?
Most single-product MVPs run 8–12 weeks. A multi-app marketplace is larger: we built Autara's five apps across iOS, Android and web in six months, merchant (supply) side first.
When should you build the demand side of a marketplace first?
Only when supply is an abundant commodity and buyers are the scarce, valuable side, or when you can cheaply aggregate demand (a waitlist or existing audience) and use it to recruit supply. Otherwise, default to supply-first.