Applications · 12 min read

YC Application for B2B SaaS — The Exact Framework

Short answer

B2B SaaS is the most common category in the YC portfolio. It is also the category where the average application quality is highest — which means the bar for standing out is higher than in most other sectors. A generic B2B SaaS application that describes a large market, a workflow problem, and a team with relevant experience will not get an interview. The applications that do get interviews are specific about the exact user, the exact workflow, the exact reason every existing solution fails that user, and the exact evidence that people will pay.

What YC Specifically Looks for in B2B SaaS Applications

YC partners reading a B2B SaaS application are trying to answer five questions:

1. Is the ICP (ideal customer profile) specific enough to be real? "SMBs" is not an ICP. "Independent pharmacy owners in tier 2 Indian cities with 1-3 staff" is an ICP. The specificity of the customer description is the first signal of how deeply the founder knows their market.

2. Is the pain acute enough that customers will pay to fix it? Workflow inefficiency that costs 20 minutes a day is annoying. Workflow inefficiency that costs ₹2 lakh a year in expired inventory is painful. YC funds solutions to acute pain, not mild inconvenience.

3. Why have existing solutions failed this specific customer? This is the insight question. The answer should name specific competitors, explain exactly what they do well, and identify the precise reason they fail for your specific user — not in general, but for the exact person you are building for.

4. What is the distribution motion? B2B SaaS distribution is not viral. It is either direct sales, channel partnerships, or bottom-up product-led growth. YC wants to know which motion you are using and why it works for your specific buyer.

5. What does the revenue model look like and is it sustainable? MRR, churn, CAC, LTV. Even at early stage, having one or two of these numbers with real data is more credible than projections.

The Answer Layer: Field-by-Field B2B SaaS Framework

50-CHARACTER DESCRIPTION

Formula for B2B SaaS: [Workflow category] for [specific business type]

Strong examples:

  • "Accounts payable software for Indian MSMEs"
  • "Fleet management for last-mile logistics companies"
  • "HR compliance tool for Indian garment factories"

What to avoid: any use of "platform," "solution," "AI-powered" as the lead descriptor. These words occupy characters without communicating what the product does.

PRODUCT DESCRIPTION (~150 WORDS)

Structure: User → Problem → Workflow → Outcome → Scale signal

"[User type] currently [describe painful manual process]. This costs them [specific measurable cost — time, money, risk]. Our product enables [user] to [specific action] through [brief product description], resulting in [specific measurable outcome]. We currently have [X] customers who [evidence of adoption]."

Example: "Independent pharmacy owners in tier 2 India currently track medicine inventory in notebooks or Excel. A typical 500-SKU pharmacy loses ₹1.5-2.5 lakh per year to expired stock they did not track in time. Our WhatsApp-native inventory system lets pharmacy owners log stock levels in 3 minutes daily and automatically flags near-expiry items 10 days in advance. We have 23 paying customers at ₹2,800/month average, with month-2 retention of 89%."

THE INSIGHT FIELD

The B2B SaaS insight field must answer: what do existing solutions get wrong about this buyer, and how did you discover that?

Strong insight structure: 1. What existing solutions assume about the buyer (the wrong assumption) 2. What is actually true about the buyer (what you discovered from user research) 3. Why your approach is built around the actual truth rather than the assumption

"Every pharmacy software vendor assumes the buyer is a pharmacist with a desktop computer and IT literacy. In 80% of independent pharmacies we interviewed, the person who manages daily stock is a family member — spouse or adult child — who uses WhatsApp exclusively and has never opened a desktop application for work. We built for that person, not the pharmacist. No competitor has done this."

THE COMPETITION FIELD

B2B SaaS competition answers should follow this structure:

  • Name 2-3 specific competitors
  • State what they do well (one sentence each)
  • State the specific reason they fail for your exact user (one sentence each)
  • State what you do differently (one sentence)

Never claim there is no competition in B2B SaaS. Every B2B workflow problem that is worth solving has either direct software competitors or an indirect incumbent (Excel, WhatsApp, paper) that you are displacing.

THE DISTRIBUTION FIELD

B2B SaaS distribution in the YC application should answer: how do you get your first 100 customers, through what specific channel, and what evidence do you have that this channel works?

WEAK

We will acquire customers through digital marketing and word of mouth.

STRONG

We acquire customers through WhatsApp pharmacy owner groups. There are 340+ active pharmacy owner groups in Maharashtra with 100-500 members each. We have joined 47 of them and converted 23 paying customers at an average CAC of ₹1,200. Our best-performing group had a 12% conversion rate from a single message.

THE REVENUE MODEL FIELD

State your pricing, your billing cycle, your current MRR, and your churn rate. If you have only one or two of these numbers, state what you have. Do not project numbers you do not have.

"We charge ₹2,800/month per pharmacy on a monthly subscription. Current MRR: ₹64,400 from 23 customers. Month-2 retention: 89%. We have not yet measured month-6 retention because our oldest customers are 4 months old."

The last sentence — acknowledging what you don't know yet — is more credible than not mentioning it.

The Data Layer: B2B SaaS Benchmarks YC Uses

These are the metrics YC partners reference when evaluating early-stage B2B SaaS:

MoM revenue growth: 15-20% is good at early stage. Above 20% is strong.

Logo retention (monthly): 90%+ is the benchmark. Below 85% at early stage raises questions about product-market fit.

Net Revenue Retention: Above 100% (expansion revenue) is the goal. Below 90% signals churn that is not being compensated by expansion.

CAC payback period: Under 12 months at early stage. Under 6 months is exceptional for SMB SaaS.

Sales cycle: For SMB B2B SaaS, under 2 weeks is typical. Enterprise sales cycles of 3-6+ months are normal for enterprise — but need to be disclosed because they affect how quickly you can grow.

If you have any of these metrics with real data, include them. If you have none, prioritize getting your first 5 paying customers before applying.

The Context Layer: Why Most B2B SaaS Applications Fail

The most common failure mode for B2B SaaS YC applications is building from the category down rather than from the user up.

Category-down thinking: "Pharmacy software is a large market → we should build pharmacy software."

User-up thinking: "Independent pharmacy owners in Maharashtra lose ₹2 lakh/year to expired stock → we should build an expiry tracking system for them."

The first approach produces applications that describe a market and a product category. The second produces applications that describe a specific user with a specific acute problem. Partners fund the second type.

The secondary failure mode is treating distribution as an afterthought. B2B SaaS does not grow virally. Every paying customer requires someone to acquire them. If your application describes a compelling product but says nothing specific about how you will acquire customers, partners will ask in the interview and your credibility will depend entirely on how well you have thought about it.

Vertical SaaS vs Horizontal SaaS — Which to Apply With

Vertical SaaS (built for one specific industry): Easier to apply with because the user, the problem, and the solution are all highly specific. Easier to acquire early customers because you can go deep in one industry. Harder to pitch as a large opportunity because the market appears narrow. Solve this by being precise about the size of the vertical — "8 lakh independent pharmacies in India at ₹2,800/month is a ₹2,400 Cr TAM" is a fundable vertical.

Horizontal SaaS (built for many industries): Harder to apply with because the ICP is inherently broader and the "why us for this specific user" question is harder to answer specifically. If you are building horizontal SaaS, pick a beachhead vertical for your application and build your entire application around that vertical. Do not try to describe all potential use cases — pick the one you are starting with and go deep.

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 B2B SaaS YC application?
Retention. Revenue matters, but retention tells partners whether your product has real value. A $5K MRR company with 95% monthly retention is more fundable than a $15K MRR company with 75% monthly retention. Retention is the signal that customers who tried your product found it worth keeping. Revenue growth without retention is a leaky bucket — it tells partners you can acquire customers but not keep them. If you have strong retention numbers, lead with them.
How much revenue do you need to apply to YC as a B2B SaaS company?
There is no minimum. YC has funded B2B SaaS companies at zero revenue when the founder-problem fit, the insight, and the early user validation were sufficiently strong. However, the bar for pre-revenue B2B SaaS applications is high. The practical answer: if you have any paying customers at all — even one paying customer at any price — include that number. It changes the application from theoretical to real. If you have no paying customers but have 5 signed LOIs or paid pilots, include those.
Should a B2B SaaS YC application describe the roadmap or just the current product?
Focus 90% on the current product and current evidence. One sentence on immediate next priority is sufficient. "We are currently building the distributor integration that will automate purchase orders — our top customer request." That is the appropriate level of roadmap detail. Founders who spend significant application space describing future features they have not built are signaling that their current product is not compelling enough to carry the application. If your current product is not the focus of your application, strengthen the current product before applying.
How do you handle the competition question for B2B SaaS when there are many competitors?
Pick the 2-3 that your actual customers compare you to most frequently. Not the biggest names in the category — the ones your users mention when you ask them "what did you use before us?" or "what else did you consider?" Those are your real competitors. Describing the competitive landscape in terms of what your actual users consider alternatives is more credible than a comprehensive market map that names every company in the category.
What pricing model should B2B SaaS founders use when applying to YC?
Use whatever pricing you have actually tested with real customers. Do not present aspirational pricing that you have not validated. If you are charging ₹2,800/month per seat, state that. If you are charging $49/month with annual option, state that. If you are still figuring out pricing and have customers on free pilots, state the pilot price (even if free) and note when you plan to convert to paid. Partners evaluate whether your pricing makes sense relative to your user's willingness to pay — which requires knowing what you are actually charging.
Should B2B SaaS founders mention enterprise customers in their YC application?
Yes, if you have them or have a clear path to them. A single enterprise customer — even at a small contract value — signals that your product is credible enough for a sophisticated buyer to commit to. If you have enterprise conversations in progress, mention them as "1 enterprise pilot agreement signed, expected live in 6 weeks." Enterprise traction is high-signal even at early stage because enterprise procurement processes are demanding enough that a signed agreement represents significant validation.
How important is the founding team's domain expertise for B2B SaaS applications?
Very important. YC partners know that B2B SaaS distribution requires deep understanding of the buyer — their workflow, their budget cycles, their decision-making process, their language. A founding team with no experience in the target industry selling into that industry faces a steeper climb than one that has lived in it. If you have direct domain experience, lead with it. If you don't, compensate with an unusually high volume of user interviews — 60+ interviews with your target buyer is a credible substitute for lived experience when the research is deep and the insights are real.
What is the difference between a B2B SaaS application that gets an interview and one that doesn't?
The clearest differentiator is the specificity of the ICP combined with the evidence of acute pain. Applications that get interviews describe a user so specifically that you could draw a picture of them — name, job, daily workflow, what they use now, how they feel about it, what they would pay to fix it. Applications that don't get interviews describe a user category ("SMBs," "enterprises," "healthcare companies") without the specificity that makes the opportunity feel real. Pair that specific ICP with a measurable pain — time lost, money lost, compliance risk — and you have the foundation of a fundable B2B SaaS application.
Should you apply to YC with a B2B SaaS product that has a long enterprise sales cycle?
Yes, but address the sales cycle explicitly. Partners will ask about it. A 6-month enterprise sales cycle means you can only add a small number of customers per quarter — which affects your growth rate narrative. Address this proactively: "Our sales cycle is 3-4 months. We currently have 3 customers and 4 in final negotiation. We are deliberately targeting mid-market accounts — 50-500 employees — where the cycle is shorter than enterprise while the ACV is 10x our SMB customers." That framing is honest about the constraint and shows you have thought about the right trade-off.
How should B2B SaaS founders think about the India vs US market question for YC?
Indian B2B SaaS founders should be explicit about where their current customers are and where they plan to go. A B2B SaaS company with 20 Indian SMB customers and a plan to move to US enterprise in 18 months should say that directly — and explain why the India validation phase produces insights and unit economics that directly transfer to the US market. The India SaaS market is increasingly respected by YC; Freshworks, Zoho, and Chargebee — all India-origin SaaS companies — have demonstrated that the path from India to global enterprise SaaS is real and well-travelled.
What should a B2B SaaS application say about customer success and churn prevention?
If you have any churn data, include it. If you have no churn yet because your customers are less than 3 months old, say that. If you have implemented any proactive retention measures — a customer success check-in, an onboarding call, an in-product prompt — mention them briefly as evidence that you are thinking about retention systematically. For very early stage, even one example of a customer who almost churned and why they stayed is a credible data point that shows you are paying attention to retention signals.
Can a B2B SaaS product without any integration or API be fundable at YC?
Yes, at early stage. YC funds the earliest version of many B2B SaaS products that are effectively manual workflows with a thin software layer. The question is not whether you have integrations — it is whether customers are getting value from what you have built. A WhatsApp-based inventory system that requires manual data entry but produces valuable expiry alerts is fundable if customers pay for it and retain. Integrations and automation are product roadmap items. Customer value is the application criteria.
← all YC Q&A

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