Applications · 12 min read

How to Write a YC Application for a Two-Sided Marketplace

Short answer

Two-sided marketplaces face a structural challenge that no other YC application category deals with in quite the same way: you must demonstrate traction on two distinct populations simultaneously — supply and demand — and partners specifically probe whether you have solved the harder side first. The marketplace applications that get interviews are the ones that show evidence of having cracked the genuinely difficult side of their market, not just metrics that look impressive when supply and demand are conflated into a single growth number.

The Core Marketplace Question Every Application Must Answer

This page covers exactly how to frame each application field for a marketplace business, the specific liquidity and density metrics that matter, and the marketplace-specific traps that sink otherwise promising applications.

Before writing a single field, identify the answer to this question: which side of your marketplace is harder to acquire, and what have you done specifically to solve that harder side?

In nearly every marketplace, one side is significantly harder to acquire and retain than the other. For a freelance marketplace, supply (qualified freelancers) is usually the harder side. For a niche B2B marketplace connecting buyers to specialized suppliers, the buyers might be harder to acquire if the suppliers are eager but buyers are skeptical of a new platform. For a marketplace serving an established profession (doctors, lawyers, contractors), the professional supply side often requires more deliberate, manual relationship-building than the demand side.

Your entire application should be organized around demonstrating that you have identified your hard side correctly and have a credible, evidenced plan for solving it — not a generic "we'll grow both sides together" narrative.

The Answer Layer: Marketplace-Specific Field Framework

50-Character Description

Name both sides explicitly if space allows, or name the harder side specifically if it does not.

Strong examples:

  • "Marketplace connecting pharmacy owners and verified distributors"
  • "On-demand marketplace for verified home repair contractors"
  • "B2B marketplace for surplus industrial equipment"

Avoid generic marketplace language ("Uber for X," "Airbnb for Y") unless the analogy genuinely clarifies the mechanic for an unfamiliar reader — and even then, follow it immediately with the specific supply and demand sides.

Product Description — The Liquidity Story

Structure: [Supply side] + [Demand side] + [The matching mechanic] + [Current liquidity evidence]

"We connect independent home repair contractors (supply) with homeowners needing repairs verified through licensing and insurance checks (demand). Homeowners post a job description with photos; we match them with 3 verified contractors within 2 hours based on specialty and location. We currently have 340 verified contractors across 4 Indian cities and have facilitated 1,200 completed jobs in the last 90 days, with a 94% job completion rate."

That description names both sides specifically, explains the matching mechanic in one sentence, and provides liquidity evidence (completed jobs, completion rate) rather than vanity metrics like total signups.

The Traction Field — Reporting Both Sides Honestly

The single biggest marketplace application mistake is reporting only demand-side metrics (more visible, easier to inflate with marketing spend) while obscuring supply-side health. Report both sides explicitly:

Supply side: "340 verified contractors onboarded. 180 (53%) have completed at least one job in the last 30 days — our measure of active supply."

Demand side: "1,450 homeowners have posted at least one job. 1,200 jobs completed, 94% completion rate."

The match rate — the metric that matters most: "78% of posted jobs receive at least one contractor response within 2 hours. This match rate has improved from 52% three months ago as we've concentrated contractor density in our top 2 cities rather than spreading thin across all 4."

The match rate (or fill rate, depending on your marketplace type) is the single most important marketplace-specific metric and should appear prominently in your traction section. It is the number that tells partners whether your marketplace actually works as a marketplace, independent of how many people have signed up on either side.

The Insight Field — What You Know About Your Hard Side

Your insight should focus specifically on the harder side of your marketplace and what you understand about acquiring or retaining it that competitors do not.

"Every existing contractor marketplace in India requires contractors to bid against each other for jobs, driving prices down and pushing the best contractors away from the platform within months. We pay contractors a fixed referral fee per completed job regardless of job price, which means our best, most in-demand contractors stay active on our platform rather than treating us as a last-resort lead source. Our contractor retention at 90 days is 71%, compared to an estimated 25-30% for bid-based competitor platforms based on contractor interviews."

The Unfair Advantage Field — Supply-Side Relationships

For most marketplaces, the unfair advantage that matters is supply-side access or relationships, since supply is more frequently the harder side to acquire and the side competitors struggle most to replicate.

"Our cofounder spent 4 years running operations for a contractor cooperative covering 200+ contractors across Pune. Those existing relationships gave us our first 80 contractors in 6 weeks — a cold-start problem that would take a competitor 6-12 months to solve through generic recruiting."

The Data Layer: Marketplace Metrics YC Partners Specifically Look For

Liquidity Metrics

Match/fill rate: Percentage of demand-side requests that successfully connect with supply. The single most important marketplace health metric.

Time to match: How long it takes from a demand-side request to a successful supply-side connection. Faster is generally better, but the right benchmark depends on your category — a same-day home repair match is different from an appropriate timeline for a high-value B2B equipment match.

Repeat usage rate: Percentage of demand-side users who return for a second transaction within a defined window. This is your best signal of genuine product-market fit versus one-time curiosity usage.

Density Metrics

Geographic or category density: Marketplaces typically need a minimum density threshold within a specific geography or category before liquidity becomes self-sustaining. State your current density and your strategy for reaching the threshold: "We have 340 contractors across 4 cities, but our liquidity data shows match rates above 70% only in our top 2 cities where contractor density exceeds 80 per city. We are deliberately concentrating new contractor acquisition in 2 additional cities rather than spreading across 10, based on this density threshold finding."

Supply utilization rate: What percentage of your supply side is actively transacting versus dormant. Low utilization (a large number of registered suppliers with few actually completing transactions) is a red flag partners specifically probe.

Take Rate and Unit Economics

Take rate: Your percentage or fixed fee per transaction, and how it compares to alternatives in your category. Be specific about whether your take rate is sustainable at scale or whether you are currently subsidizing one side to build liquidity.

Contribution margin per transaction: After accounting for any subsidies, incentives, or acquisition costs tied to a specific transaction, what is your actual margin? Marketplaces sometimes show impressive gross transaction volume while losing money on every individual transaction during a subsidized growth phase — be honest about which phase you are in.

The Context Layer: Marketplace-Specific Traps in YC Applications

Trap 1: Reporting GMV (gross merchandise value) as if it were revenue

GMV is the total value of transactions flowing through your platform. Your actual revenue is your take rate applied to that GMV. Conflating the two — or worse, hoping partners won't ask the difference — is one of the most common marketplace application mistakes. State both explicitly: "GMV of ₹18 lakh over the last 90 days, with a 12% take rate generating ₹2.16 lakh in platform revenue."

Trap 2: Demonstrating growth on the easy side while obscuring stagnation on the hard side

If your demand side is growing 20% month-over-month but your supply side is flat, do not lead with the demand growth number alone. Partners will ask about the other side specifically, and an application that omits this context reads as either naive about marketplace dynamics or deliberately obscuring a weakness.

Trap 3: Treating "chicken and egg" as a problem you'll solve later rather than one you've already solved

Every marketplace founder knows about the chicken-and-egg cold-start problem. What differentiates a strong application is evidence that you have already solved it at small scale — even if that scale is just one neighborhood, one city, or one narrow category — rather than a plan for how you intend to solve it.

Trap 4: Ignoring disintermediation risk

If your marketplace's two sides could plausibly transact directly once they find each other (a common risk for service marketplaces where the contractor and homeowner could simply exchange phone numbers and skip the platform on future jobs), address this directly. What is your specific mechanism for retaining the transaction on-platform — payment processing, ongoing dispute resolution value, insurance/verification you provide, or other genuine value that justifies continued platform usage?

Keep reading

More on Applications

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.

FAQ

Frequently asked questions

Which side of a marketplace should I focus on first when applying to YC?
Whichever side is structurally harder to acquire and retain for your specific category — this varies by marketplace type. For most service marketplaces (contractors, freelancers, healthcare providers), supply is typically the harder side because qualified suppliers have alternative ways to find work and are skeptical of unproven platforms. For some B2B and niche marketplaces, demand can be the harder side if buyers are risk-averse about an unproven new channel. Identify your specific hard side honestly and organize your entire application around evidence that you have solved it.
What is a good match rate or fill rate for an early-stage marketplace?
There is no universal benchmark — it depends heavily on category and the urgency of the demand-side request. A same-day service marketplace (home repair, on-demand delivery) might target match rates above 70-80% to be viable, since users abandon the platform quickly if requests go unfulfilled. A higher-value, lower-frequency B2B marketplace (industrial equipment, specialized professional services) might have acceptable match rates in the 30-50% range if the transaction value justifies a longer matching window. What matters in your application is showing the trend — is your match rate improving as you concentrate density, and do you understand why?
Should a YC marketplace application report GMV or revenue as the primary traction metric?
Report both explicitly, but lead with revenue if you have meaningful revenue, since GMV alone can overstate the actual business value, especially at a low take rate. If your business is pre-revenue or revenue is not yet a meaningful signal (common in early-stage marketplaces still building liquidity), GMV combined with take rate and a clear path to monetization is acceptable, but state this combination explicitly rather than letting GMV stand alone as if it represented revenue.
How do you handle the chicken-and-egg problem in a YC application?
By showing you have already solved it at a small scale rather than describing it as a future plan. Identify the specific narrow segment — one city, one category, one customer type — where you first achieved liquidity, and describe exactly how you did it: manual sourcing of initial supply, a single-player mode that provided value before the marketplace had two-sided liquidity, or a concentrated geographic launch strategy. Partners want evidence of execution against this known problem, not awareness that the problem exists.
What if my marketplace's supply and demand sides could disintermediate and transact off-platform?
Address this directly and specifically in your application rather than hoping it doesn't come up. Describe the specific mechanism that retains transactions on your platform: payment processing convenience, insurance or verification you provide that off-platform transactions would lose, ongoing dispute resolution, or repeat-matching algorithms that make staying on-platform more valuable over time than any single transaction. If you do not have a clear answer to this question, it is a genuine business risk worth addressing before applying, not just before the interview.
How important is geographic density for a marketplace YC application?
Very important for most local or service marketplaces, less critical for marketplaces with fully digital, location-independent transactions. If your marketplace requires geographic density to function (most service marketplaces do), state your current density specifically and show that you understand the threshold required for sustainable liquidity in your category. A marketplace that has spread thin across many cities with low density everywhere is a weaker application than one with strong, demonstrated liquidity in one or two concentrated markets.
What insight should a marketplace founder highlight in their YC application?
An insight specific to your harder side — what you understand about why that side is hard to acquire or retain that your competitors have gotten wrong. Generic insights about market size or general digital transformation are weak. A specific insight about supplier behavior, buyer trust dynamics, or a structural flaw in how competitors structure their take rate or incentives is strong, especially when paired with evidence (retention data, acquisition cost comparison) that proves the insight is correct.
How should marketplace founders describe their take rate in a YC application?
State the exact percentage or fee structure, explain how it compares to alternatives in your category, and be honest about whether your current take rate is sustainable or whether you are subsidizing growth. "Our take rate is 12%, compared to 20-25% for traditional contractor lead-generation services — we can sustain this lower rate because our matching algorithm reduces the customer acquisition cost we'd otherwise pass through to contractors" is a strong, specific answer that ties the take rate to your competitive positioning.
Do YC partners expect marketplace startups to be profitable at the application stage?
No, especially at early stage, but they do expect founders to understand their unit economics precisely, including whether current operations are subsidized and what the path to sustainable take rate economics looks like. A marketplace that is currently subsidizing one side to build liquidity is acceptable if the founder can explain the subsidy clearly, state its cost, and describe the specific conditions under which the subsidy will be reduced or removed.
What is the most common reason marketplace YC applications get rejected?
Failing to demonstrate genuine liquidity on the harder side of the marketplace. Applications that show impressive growth on the easier side (often demand, sometimes supply depending on category) while the harder side remains thin or stagnant read as evidence that the founder has not yet solved the core marketplace challenge. The second most common reason is conflating GMV with revenue in a way that overstates the actual business traction once a partner does the take-rate math.
How should a B2B marketplace application differ from a consumer marketplace application?
B2B marketplace applications should emphasize transaction value and relationship depth over raw transaction volume, since B2B marketplaces typically have fewer, higher-value transactions compared to consumer marketplaces. Sales cycle length, the specific decision-maker on each side, and contract or repeat-purchase commitments matter more in B2B marketplace traction than the high-frequency repeat usage metrics that matter most for consumer marketplaces. State your specific B2B sales motion and average transaction value explicitly rather than applying consumer marketplace metrics frameworks to a fundamentally different transaction pattern.
Should marketplace founders address marketplace-specific risks proactively in their application?
Yes, particularly disintermediation risk and liquidity concentration risk. Proactively naming these risks and describing your specific mitigation is more credible than hoping partners don't think of them — partners who have evaluated many marketplace applications will think of them regardless, and an application that has already addressed the obvious risk demonstrates more sophisticated marketplace thinking than one that ignores it.

An independent resource · Not affiliated with Y Combinator · Last updated 2026-08-04