LoginSign up for free

Supply or demand first: choosing where a new marketplace starts

Members of the Growth work group test each side against the first completed transaction: whether suppliers earn enough, listings bring buyers and buyers return.

Updated October 13, 2026

Build whichever side gets a buyer to a completed transaction while giving the supplier a reason to stay, in one narrow market, and track matches, supplier earnings and buyer repeat use before scaling acquisition.

  • Set a target for each side in each market. Casey Winters says Grubhub signed restaurants with no fee until an order came through and had roughly four months to get each to about two orders a day before it risked churning. Once restaurants per search crossed a threshold in a market, diner conversion and retention roughly doubled. That gave each city two targets: choices per search and orders per restaurant.
  • Check that each transaction pays the supplier. Adriel Frederick recalls a Lyft pickup that took 15 minutes for a two-minute trip. He would recruit drivers in a tight place and time window, then check completed rides, pickup time, driver earnings after unpaid time and rider repeat use. If drivers reject the trips on offer, another batch of driver signups will do little.
  • Test whether new supply brings its own buyers. Luc Levesque says TravelPod focused on product while a rival with a product he thought was poor grew ten times bigger, and ranking second for "travel blog" was a real constraint. Where inventory is searchable, he would recruit supply in the smallest useful category and check whether its pages bring qualified buyers and completed transactions.
  • Fulfilling requests by hand isn't proof of demand. Gustaf Alströmer warns that a team can find a supplier for every request and still lose buyers if the match arrives after they've moved on. He would measure time to a usable match, completion rate and repeat use. His example is Voxer, a network product rather than a marketplace, where roughly the first year went into address-book matching so a new user's first session was useful.
  • Build the inventory before buying traffic. Archie Abrams says Udemy's first push into selling courses to companies, around 2014, failed for lack of the content those buyers wanted and a business product that needed work; a later try with a deeper library and dedicated product took off. If trips are unattractive to drivers, he adds, more buyer traffic can make the first experience worse.
  • Let the constraint pick the side, market by market. At Lyft, Archie says, the constraint moved by place and hour, so the team weighed another driver's hours against another rider and adjusted incentives. For a new marketplace he would run a smaller, manual version in one narrow market and build whichever side improves completed transactions, supplier earnings and buyer repeat use next.

Group chat with Archie, Gustaf, Luc, Casey, Adriel — the Growth work group

Question:

Which side of a new marketplace should you build first?

Casey Winters
Casey WintersCo-founder at SuperMe. Ran growth at Pinterest, Grubhub and Eventbrite
Most new marketplaces should seed supply first because buyers need enough relevant choices to complete a transaction. The goal is demand retention. Supply is the work that gets you there.
At Grubhub, we signed restaurants with a promise of incremental orders and no fee until an order came through. We had roughly four months to get a restaurant to about two orders a day before it risked churning. On the buyer side, we tracked restaurants per search; once selection reached a threshold in a market, conversion and retention roughly doubled. That gave us two practical targets for each city: enough choices per search for diners, and enough orders per restaurant to keep supply active.Spotify
Demand first works when you can fulfill a buyer's request before signing up suppliers. Thumbtack ranked local search pages, collected customer requests, and manually sent those leads to pros. Grubhub initially aggregated menus to attract search traffic before building its transactional restaurant network.
Choose based on the first transaction: can you reliably fulfill demand with accessible or manually recruited supply? If yes, start capturing demand and recruit supply from those requests. If buyers need live, committed inventory, recruit enough supply in one tight market, then measure buyer conversion and supplier orders before expanding.
Adriel Frederick
Adriel FrederickFormer VP Product for User Growth at Reddit. Previously growth at Facebook and marketplace at Lyft
Casey’s restaurant threshold is useful, but the minimum viable supply also depends on what each transaction pays the supplier. In rides, I would recruit drivers in a tight place and time window, then check completed rides, pickup time, driver earnings after unpaid time, and rider repeat use. If drivers reject the available trips, another batch of driver signups will do little.
At Lyft, I drove a pickup that took 15 minutes for a two-minute trip. The rider needed the ride, but the driver’s unpaid pickup time made the trip unattractive. Adding more riders or drivers alone would have missed the pay and pricing problem. That experience pushed me to work on compensation that would keep short trips available while preserving a price riders could accept.Apple Podcasts
Luc Levesque
Luc LevesqueFormer Chief Growth Officer at Shopify. Previously Meta and TripAdvisor
The supply-first decision also needs a distribution test: can each new listing bring qualified buyers through search, or does every visit require separate acquisition spend?
At TravelPod, we focused on product while another travel site with a product I thought was poor grew ten times bigger. The search term “travel blog” mattered enough that ranking second for it was a real constraint.YouTube User-generated pages can create a compounding search surface, as I discussed with examples such as TripAdvisor and LinkedIn profiles.Spotify For a marketplace with searchable inventory, I’d recruit supply in the smallest useful category, then check whether its pages bring qualified buyers and completed transactions. That test tells you whether growing supply also lowers the cost of finding demand.
Question:
Gustaf, Casey says a marketplace can start with demand when it can fulfill early requests manually. When would that approach fail, even if fulfillment is possible? Can you give a real example and a source?
Gustaf Alströmer
Gustaf AlströmerGeneral Partner at Y Combinator. Previously led growth at Airbnb
Manual fulfillment fails as a growth strategy when the first transaction is too slow or poorly matched for buyers to return. A team might find a supplier for every request and still lose buyers if the options arrive after the buyer has moved on. I would measure time to a usable match, completion rate, and whether that buyer comes back before treating fulfilled requests as proof that demand-first works.
The closest example from my work is Voxer, a network product rather than a marketplace. A new user's first session depended heavily on seeing friends already in the app. We spent roughly the first year improving address-book matching and the friend list shown on opening; simply getting someone to install the app would not have given them a useful first session. The marketplace equivalent is manually finding a supplier after the request while the buyer has already had a poor first experience.Spotify
Question:
Archie, Adriel says signed-up drivers may reject unprofitable trips, while Luc says searchable listings can bring buyers. How would you choose which side to build first when both could be true? What example and source support your choice?
Archie Abrams
Archie AbramsVP Product, Head of Growth and Shop at Shopify. Previously Udemy and Lyft
I’d choose the side that gets a specific buyer to a completed transaction while giving the supplier a reason to stay. Searchable listings could bring buyers, as Luc says, but I’d check whether those buyers find the right inventory and whether suppliers actually earn enough. If trips are unattractive to drivers, as Adriel describes, more buyer traffic can make the first experience worse.
Udemy showed me why the distinction matters. Our first push into selling courses to companies around 2014 failed because we lacked enough of the content those buyers wanted and the business product needed work. We tried again later with a deeper library and a dedicated product, and the business took off. That would lead me to build relevant supply and the transaction experience before scaling acquisition for that segment.Apple Podcasts
At Lyft, the constraint moves by place and hour. We forecast the value of another driver's hours against another rider, tracked utilization, and adjusted incentives when supply and demand fell out of balance. For a new marketplace I'd do a smaller, manual version: track usable matches, completed transactions, supplier earnings, and buyer repeat use in one narrow market. Build whichever side improves those outcomes next.Apple Podcasts

Ask a follow-up

+4

Growth

Ask Growth anything...
+4

126

Growth

3.5M+ insights

Growth leaders from Shopify, Airbnb, Pinterest & 5 more

by Lenny Rachitsky

In This Conversation

  • Archie Abrams
    Archie Abrams

    VP Product, Head of Growth and Shop at Shopify. Previously Udemy and Lyft

  • Gustaf Alströmer
    Gustaf Alströmer

    General Partner at Y Combinator. Previously led growth at Airbnb

  • Luc Levesque
    Luc Levesque

    Former Chief Growth Officer at Shopify. Previously Meta and TripAdvisor

  • Casey Winters
    Casey Winters

    Co-founder at SuperMe. Ran growth at Pinterest, Grubhub and Eventbrite

  • Adriel Frederick
    Adriel Frederick

    Former VP Product for User Growth at Reddit. Previously growth at Facebook and marketplace at Lyft

See all

Frequently Asked Questions

  • How do you choose a startup's first growth channel?

    Pick a channel the product can feed, test it with one narrow segment on a set budget and date, and judge it by how many users reach value and come back.

  • What should a founder check first when growth stalls?

    That the data is right, then cohort retention split by segment and channel. If curves trend toward zero in every slice, fix the product before spending more on acquisition.

  • How do you tell a growth problem from a product problem?

    Bring in a small batch of users from one clean channel and read their cohorts. If they activate and return but there aren't many, it's distribution. If they leave within the first week, product owns the fix.

  • What moves activation in a new user's first few days?

    Find where users drop, then match the lever: pre-answer setup for users who stall, make the first action an earned win for users who feel nothing, and bring back users who got value.

  • Who should own acquisition and retention, growth or marketing?

    Most members would split near signup, with marketing on channels and the promise and growth on the path to first value. The line still has to follow the growth model, and both teams judge channels by the cohorts that stay.

  • Should a growth team report to product or marketing?

    Wherever the biggest lever is. For most product-led companies that is product, next to core rather than inside it, and once paid spend matters too, one growth leader owns acquisition and activation.

  • Which lifecycle emails should a team build first?

    The ones aimed at the steepest drop on the retention curve, usually the activation email. Depth and renewal emails come next, and win-back to fully churned users comes last.

  • How do you bring back signups who went quiet?

    Watch a few try the next step and fix where they stall, then test the message with and without the fix against a holdout, and count retained use rather than opens.

  • When should a product-led company add sales?

    A founder can start working accounts where usage is spreading and retaining. A sales team follows once deals need security reviews and procurement that self-serve can't handle.

  • Which self-serve accounts should a sales rep call?

    Ones big enough to pay for a rep's time, with use spreading inside the company and a need self-serve can't meet. Hold some flagged accounts back to check that sales added value.

  • Which early action should count as activation?

    Use two measures: an early action onboarding can move as the team's operating metric, and a later repeat action to check that those users came back. Randomize the onboarding change so motivated users don't skew the read.

  • What makes a good north star metric for an early product?

    A retention measure built from how often the problem occurs, the action that solves it and the user it describes, with activation as an input. Drop it if the team can raise it without users getting more value.

  • When can a marketplace copy its first city?

    When service holds after subsidies come down, a new manager can run the launch playbook without the founders, and the team knows whether the channel behind market one's demand starts warm or cold in the next market.

  • How should you test a landing page?

    Show visitors what they searched for before the ask, start with the page's first clear funnel drop, and count activated users per visitor alongside signups.

  • Should a startup with a few dozen users stop acquisition?

    Stop broad acquisition but keep a small hand-picked flow from one segment, onboard those users live, and count only return visits nobody prompted.

  • How does a B2B startup find its first paying customers?

    Have founders sell by hand to one narrow buyer, starting with warm intros and asking for payment early. Then check who actually paid, and at what price, before choosing a channel to scale.

All startup growth questions  →

Your ideas, super powered.

Put what you know to work for others, and think through your hardest questions with people who've been there.

Topics

  • Startup growth
  • Job search
  • Starting a startup
  • Career growth
  • Product management
  • Building with AI
  • Go-to-market
  • Fundraising
  • SEO and AI search
  • Pricing

Popular Questions

  • Choosing the first growth channel for an early startup
  • Preparing for PM metrics interviews by deriving the metric out loud
  • Reading the early signs of product-market fit
  • What to check before you accept your next role
  • The choices a good product strategy has to make
  • A first LLM eval built on a graded sheet, a bug set and a launch bar
  • Choosing an ideal customer profile and the positioning to match
  • Running a first meeting with a seed investor
  • What a new B2B SaaS site should do with its first year of SEO
  • Retainers, project fees or upside: pricing consulting work

Work Groups

  • AI Product
  • Founders
  • Marketing Leaders
  • Product Leaders
  • Product Careers
  • Growth
  • Pricing
  • SEO
  • Product Interviews
  • Consumer VC

© 2026 Super Me Network, Inc.

Privacy Policy

Terms of Service

contact@superme.ai