Applications · 12 min read

YC Application for Marketplaces — What to Emphasize

Short answer

Marketplaces are one of the hardest business models to apply to YC with and one of the highest-value when they work. The reason applications fail: the chicken-and-egg problem is real and visible in every marketplace application, and most founders address it poorly. YC partners have seen hundreds of marketplace applications. The ones that get interviews are specific about which side of the market they are seeding first, how they are doing it manually, and what the supply-demand balance looks like right now — not at scale.

What YC Specifically Evaluates in Marketplace Applications

1. Which side of the market have you solved first — and how? Every marketplace starts lopsided. You either have supply without demand, or demand without supply. YC wants to know which side you started with, why you started there, and what you have done to build it before the other side existed.

2. What is your current liquidity? Liquidity in a marketplace means the probability that a buyer finds a seller (or vice versa) quickly. A marketplace with 1,000 suppliers and 5 buyers has terrible liquidity. A marketplace with 20 suppliers and 40 buyers in the same geography might have excellent liquidity. State your current liquidity metric — not just GMV or user counts.

3. What is your take rate and is it defensible? Your take rate (the percentage of each transaction you keep) is a unit economics question and a competitive defensibility question. State it specifically and explain why suppliers and buyers accept it.

4. Have you done things that don't scale to bootstrap supply or demand? The best marketplace applications describe founder-driven supply or demand generation that most companies would not do. Manually calling every pharmacy in Maharashtra. Personally onboarding the first 20 suppliers. Guaranteeing demand to early suppliers to reduce their risk. These signals tell partners that you are willing to do the hard work before the flywheel spins.

5. What is your GMV and growth rate? GMV (gross merchandise value — total transaction value flowing through the marketplace) is the primary marketplace revenue metric. State it specifically: "We processed ₹8.4 lakh in GMV last month, up from ₹3.2 lakh two months ago."

The Answer Layer: Field-by-Field Marketplace Framework

50-CHARACTER DESCRIPTION

Formula for marketplaces: [Transaction type] marketplace for [specific user pair]

Strong examples:

  • "Used medical equipment marketplace for Indian clinics"
  • "Freelance CA marketplace for Indian startups"
  • "Agricultural produce marketplace for Maharashtra farmers"

What to avoid: "connecting X and Y" — this is too abstract. Name the transaction, not the connection.

PRODUCT DESCRIPTION

Structure: Supply side + demand side + transaction + take rate + current scale

"[Supply side user] uses our platform to [list/sell/offer]. [Demand side user] uses it to [find/buy/book]. We charge [take rate]% on each transaction. Current GMV: [number]. We currently have [X] active suppliers and [Y] active buyers in [geography]."

Example: "Independent pharmacy owners use our platform to return near-expiry medicines to distributors and get credit. Distributors use it to manage returns at scale instead of handling them manually through WhatsApp. We charge 8% on each return transaction. Current monthly GMV: ₹12.4 lakh across 23 pharmacy sellers and 4 distributors in Maharashtra."

THE CHICKEN-AND-EGG FIELD (INSIGHT / HOW FAR ALONG)

This is the field where marketplace applications most commonly fail. Most founders either avoid the chicken-and-egg question entirely or describe it at a level that reveals they have not yet solved it.

The strongest marketplace applications describe specifically how they solved the cold start problem:

The constrained geography approach: "We launched in one area of Pune — Hadapsar — and did not expand until we had 15 active suppliers and 30 active buyers in that single zone. We drove all supply and demand ourselves through direct outreach for the first 6 weeks."

The guaranteed demand approach: "We guaranteed our first 8 suppliers that we would buy their unsold inventory at cost if they joined the platform and no buyers appeared within 2 weeks. We never had to honor that guarantee — but removing the supply-side risk got us our first 8 suppliers in 10 days."

The single-player mode approach: "Our product is useful to one side of the marketplace even without the other side. Pharmacies use our expiry tracking tool for free. The return marketplace is an optional layer that becomes available when a distributor is in our network. We built the single-player product first and the marketplace layer second."

State which approach you used, what the result was, and where you are now.

THE TRACTION FIELD

Marketplaces have unique traction metrics. Include as many of these as you have:

  • GMV: Total transaction value in the last 30 days
  • Take rate: Your percentage of each transaction
  • Net revenue: GMV × take rate
  • Supply count: Active suppliers in the last 30 days
  • Demand count: Active buyers in the last 30 days
  • Liquidity rate: % of listed items/services that transact within 7 days
  • Repeat transaction rate: % of buyers who transact more than once per month
  • Supply-demand ratio: The balance between available inventory and buyer demand

A marketplace application with all 8 of these metrics filled with real numbers is in the top 5% of what YC receives. Even 4 or 5 of them with real data is strong.

THE DISTRIBUTION FIELD

Marketplace distribution means how you grow both sides. Address each separately:

"We grow supply through direct outreach to pharmacy owner WhatsApp groups — we have joined 47 groups in Maharashtra and converted 23 pharmacy sellers at a CAC of ₹1,200. We grow demand by approaching pharmaceutical distributors directly — we have 4 active distributors and are in conversations with 3 more. Our target is 10 distributors covering 60% of Maharashtra's pharmaceutical supply chain within 6 months."

The Data Layer: Marketplace Benchmarks YC Uses

Early-stage GMV growth: 20%+ MoM is a strong signal for an early marketplace.

Liquidity rate: For a healthy early-stage marketplace, 60%+ of listed items/services should transact within 30 days.

Repeat transaction rate: 40%+ of buyers transacting more than once per month signals that the marketplace is delivering consistent value.

Take rate range: Consumer marketplaces typically charge 10-30%. B2B marketplaces 3-15%. Your take rate should be defensible relative to the value you are creating — not the maximum you can extract.

Supply-demand ratio: The optimal ratio varies by marketplace type. The signal YC looks for is whether the ratio is improving over time and whether you understand what drives it.

The Context Layer: Why Most Marketplace Applications Fail

The three most common marketplace application failure modes:

Failure 1: Both sides described equally without showing which side is the bottleneck Every marketplace has a bottleneck side — the side that is harder to acquire and that limits growth. Applications that describe both sides without identifying the bottleneck signal that the founder has not yet run into the core constraint of their marketplace. Name the harder side and describe what you are doing specifically to solve it.

Failure 2: GMV cited without take rate GMV without take rate is a vanity metric. ₹50 lakh GMV at a 2% take rate is ₹1 lakh in revenue. ₹10 lakh GMV at a 20% take rate is ₹2 lakh in revenue. Partners evaluate marketplace economics on net revenue, not GMV. Always state both.

Failure 3: No description of the manual work done to bootstrap the marketplace YC explicitly values founders who do things that don't scale. A marketplace application that describes software features but does not describe the manual founder-driven work done to acquire early supply and demand is a missed opportunity. Every successful marketplace started with a founder who did things manually that the platform would eventually automate. Describe that work specifically.

Types of Marketplaces and Their Specific Challenges

Geographic marketplaces (services, logistics, on-demand): Liquidity is hyper-local. Your application should show that you have achieved liquidity in one specific geography before describing expansion plans.

B2B marketplaces (procurement, wholesale, distribution): Sales cycles are longer and relationship-driven. Your application should name specific buyers and sellers and show the transaction history between them.

Vertical SaaS + marketplace hybrids: Many successful marketplaces start as vertical SaaS tools and add marketplace features as a second revenue layer. If your model is this hybrid, describe the SaaS layer and the marketplace layer separately and explain how they reinforce each other.

Aggregator marketplaces (service providers, talent): Quality control is the core product challenge. Your application should describe how you ensure quality on the supply side — your vetting process, your rating system, and your evidence that quality is consistent.

Keep reading

More on Applications

Founder Stories

Want the real version of these answers? Read long-form, source-linked stories from actual YC founders — how they got in, what broke, what scaled.

Read Founder Stories →

Go deeper

Want the full data behind this answer?

Our YC database tracks 5,000+ companies, every batch, with application patterns, founder backgrounds, and pivot stories — the raw material we built this answer on.

Open the database →

FAQ

Frequently asked questions

What is the most important metric for a marketplace YC application?
GMV growth rate combined with take rate is the most important combined metric. GMV growth shows that transaction volume is increasing. Take rate shows that you are capturing a sustainable percentage of that value. Together they produce net revenue growth — the metric that tells partners whether the marketplace is building a real business rather than just facilitating transactions at cost. If you only have one of these numbers, GMV growth with a specific take rate stated is more useful than GMV alone.
How do you address the chicken-and-egg problem in a YC application?
Name it explicitly and describe specifically how you have attacked it. The most credible approaches: constraining the geography to achieve density in one area first, guaranteeing supply-side demand to reduce early risk, building a single-player mode that creates value for one side before the other side exists, or manually seeding the scarce side yourself. The worst approach is to not address it and hope partners do not ask — they will always ask, and founders who have not thought carefully about this will have weak answers.
What take rate should a marketplace charge in a YC application?
Whatever you have validated with real transactions. Do not present an aspirational take rate — present the one your users have already accepted. If you are still experimenting with pricing, name the range you have tested and what you have learned. Partners evaluate whether your take rate is defensible relative to the value you are creating. A 15% take rate that saves each seller ₹50,000 per transaction is defensible. A 5% take rate that provides minimal value beyond connectivity is harder to defend.
Should a marketplace YC application focus on GMV or revenue?
Both, but lead with net revenue (GMV × take rate) because it is the metric that tells partners whether the marketplace is a real business. GMV alone is frequently cited by marketplace founders to make scale appear larger than it is. Partners immediately convert GMV to net revenue in their evaluation. Save yourself the credibility issue by doing that conversion in your application and presenting both numbers.
How should a marketplace handle the liquidity question in its application?
State your current liquidity metric specifically: "Of the 340 pharmacy return requests posted on our platform in the last 30 days, 71% were matched with a distributor within 48 hours." That is a liquidity metric with a specific number, a specific timeframe, and a specific context. Liquidity described abstractly — "our marketplace has good liquidity in our core geography" — tells partners nothing specific. A number always outperforms a description.
Is it better to apply to YC as a marketplace or as a SaaS with marketplace features?
If your current revenue is primarily from software subscriptions and the marketplace is a future layer, apply as SaaS with a marketplace roadmap. If your current revenue is primarily from transaction fees, apply as a marketplace. The framing should match where your value creation and revenue actually come from today. Presenting yourself as a marketplace when you are primarily a SaaS tool — or vice versa — creates a misalignment that partners will surface in the interview.
How many suppliers and buyers do you need before applying to YC as a marketplace?
There is no minimum, but the most credible early-stage marketplace applications tend to have at least 10-20 active suppliers and a similar number of active buyers with documented transaction history between them. Below this threshold, the marketplace has not yet demonstrated that transactions happen — only that two sides exist. The key insight is that 20 active suppliers and 20 active buyers with real transaction history is more fundable than 500 suppliers and 500 buyers who have never transacted.
How should a marketplace describe its defensibility in a YC application?
Name the specific moats that make your marketplace hard to replicate: data network effects (transaction history that improves matching), supply-side exclusivity (agreements that prevent suppliers from listing elsewhere), geographic density that makes a new entrant uncompetitive in your core market, or vertical-specific compliance requirements that competitors would need 12-18 months to navigate. Generic claims of network effects without a specific description of how they manifest in your marketplace are not credible at early stage.
What is the right geographic scope for a marketplace YC application?
As narrow as your current liquidity supports. A marketplace that claims to serve all of India with thin supply and demand distributed across dozens of cities is less credible than a marketplace that has achieved genuine density in one city or region. The right answer is your current actual geography — even if it is one neighborhood in one city — with a clear argument for why that density creates a replicable pattern.
Should marketplace founders apply to YC before or after proving liquidity?
After proving at least basic liquidity in one geography. The specific threshold: at least 50% of listed transactions successfully completing within a reasonable timeframe in your core geography. Below this threshold, the marketplace has not yet proved the core product hypothesis — that supply and demand will actually transact when brought together on your platform. Applying before proving this leaves the application's core question unanswered.
How should a marketplace describe its unit economics in the application?
With three specific numbers: average transaction value, take rate percentage, and net revenue per transaction. Then connect those to customer acquisition cost for each side. "Average transaction value: ₹54,000. Take rate: 8%. Net revenue per transaction: ₹4,320. Pharmacy seller CAC: ₹1,200. Distributor CAC: ₹8,000. A single closed transaction covers our pharmacy acquisition cost 3.6x." That calculation tells partners whether the business can grow profitably — which is the core unit economics question for any marketplace.
Can a marketplace apply to YC with a 0% take rate?
Yes, if you have a credible path to monetization and can explain why building with a 0% take rate first creates a defensible position. Some of the most successful marketplace businesses started with 0% take rate to achieve supply and demand density before introducing fees. The key is being explicit about this strategy: "We are currently charging 0% to maximize supply-side participation in our first year. We will introduce a 5% take rate in month 13 when we have density in 3 Maharashtra cities. We have disclosed this plan to all current suppliers and 94% said they would remain on the platform at that take rate."
← all YC Q&A

An independent resource · Not affiliated with Y Combinator · Last updated 2026-02-01