SaaS-Marketplace Transition Test
A SaaS business can add a marketplace only if it touches its customer's customer and those customers need multiple suppliers
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 88%
A two-condition test for whether a SaaS business can successfully layer on a marketplace, plus the general principle that marketplace-adds-SaaS is far more replicable than SaaS-adds-marketplace because it de-risks the hardest part up front.
Origin
Casey Winters' framework, drawn from advising and operating across Eventbrite (SaaS adding marketplace), Faire (marketplace adding SaaS), and observing OpenTable, Substack, Patreon and others.
Core principles
- 01A marketplace means you drive demand to supply — otherwise you're just a tool they use
- 02Marketplaces are hard no matter which side you start from
- 03Doing the hard part (the marketplace) first opens up adjacencies; doing it last means years to de-risk the hardest step
- 04Marketplaces win on selection or on standardization/availability
How to run it
- 1
Test condition one: do you touch the customer's customer?
The SaaS product must serve both your customer and your customer's customer (like Square, Substack, Patreon, Eventbrite), so you already have a relationship and brand with the demand side. Contrast Stripe, a white-labeled backend the end buyer never sees.
Watch out Most SaaS businesses fail this — if buyers never know your brand, you can't easily drive them as marketplace demand.
- 2
Test condition two: do those customers need multiple suppliers?
The customers you have a relationship with must have a reason to transact with more than one of your current suppliers — a genuine discovery or selection need. If they'll always use the same single supplier, there's no marketplace.
Pro tip Marketplaces win either on selection (more choice) or standardization (guaranteed availability, like an Uber arriving in five minutes regardless of driver).
Watch out Patreon, GoFundMe and early Substack found buyers had no discovery need — 'nobody needed that, it wasn't a problem.'
- 3
Prefer building the marketplace first
If you can, get the hard part (the marketplace and its cross-side network effects) done up front; then a SaaS layer becomes a customer-acquisition, workflow, or retention tool — a much more common and replicable pattern.
Pro tip Faire built the wholesale marketplace first, then added a free SaaS tool to onboard brands' existing retailers — which cross-sold those retailers to other brands without a sales team.
Watch out Planning to build SaaS now and 'a marketplace business on top five years later' means a long slog to de-risk the hardest part last.
- 4
If going SaaS-to-marketplace, target real cross-side lift
Success looks like the marketplace unlocking cross-side network effects — the platform itself drives a growing share of demand, until suppliers choose you for the demand rather than the tooling.
Pro tip Eventbrite now drives ~25% of ticket sales itself and growing, but Winters estimates it needs ~50% before creators pick Eventbrite for its demand rather than its SaaS quality.
In the wild
Faire built a wholesale marketplace between independent retailers and brands, then added a free SaaS tool letting brands onboard their existing retailers for better payment terms and free returns — charging nothing on those rebookings but cross-selling the onboarded retailers to other brands and taking a cut on those transactions.
→ Onboarded more independent retailers without a sales team and grew quickly — a model Winters calls one that worked out really well.
Eventbrite started as SaaS-like (payments, event-creator tooling) where creators did their own marketing. It's now layering the marketplace value prop of driving demand, moving from creators marketing themselves to Eventbrite driving ~25% of ticket sales.
→ Growing faster than the rest of the business, but Winters says it 'has a ways to go' and needs to approach ~50% to unlock real cross-side network effects.
Common mistakes
Assuming your buyers want discovery when they don't
Patreon and early Substack assumed patrons wanted to browse and discover more creators; nobody needed that — supporters weren't looking for more people to give money to, so the marketplace premise failed.
Calling a payments/tooling product a marketplace
If supply signs up primarily for tooling or payments rather than because you bring them extra business, it's a SaaS-like network, not a marketplace — it lacks the cross-side network effects.
Is it for you?
Best for
SaaS and marketplace founders deciding whether and how to add the other business model
Not ideal for
SaaS businesses whose buyers never see their brand (white-labeled backends) or whose customers only ever need a single supplier
From the transcript
“all of these are examples of SaaS businesses that in providing the SaaS service deal with the customer and the customer's customer”
“those customers that you're building a relationship with they need to have a reason to transact with more than one of your current customers on…”
“in my eyes it's your driving demand to supply that's like the Nuance right because otherwise you're just the tool that they're using to do…”
“if you get the hard part done up front it opens up a lot of amazing you know adjacencies different ways to grow”
From the episode
Thinking beyond frameworks
Casey Winters (Pinterest, Eventbrite, Airbnb, Tinder, Canva,