YC Application for Pre-Revenue Startups — What to Focus On

When you have no revenue, every other form of evidence has to work harder. YC partners reading a pre-revenue application are asking a single underlying question: does this founder have enough contact with the real problem to build something people will pay for?

Revenue is the cleanest answer to that question. In its absence, the next best answers — in descending order of strength — are:

Signed letters of intent or pre-orders. Money that is not yet revenue but is committed. Even ₹5,000 collected from 5 people who want the product before it exists is a stronger signal than 500 people who said they would pay.

Paying waitlist or deposit. Users who have given you something to secure a spot — money, time, personal information they would not share casually. A 200-person waitlist where 40 people gave you their phone number and asked to be called when you launch is different from a passive email signup.

Intensive user research with specific outputs. 60-80 user interviews with documented findings, named interviewees (industries and roles, not personal details), and specific insights that emerged from the research. This signals that the founder has done the equivalent of customer development work even without a product.

Active pilot users. Users who are using a prototype, a manual version, or even a Google Sheet version of your product in their real workflow. Free pilots with real usage are meaningfully different from demo sign-ups.

Domain-specific founder credentials. A founder who ran a pharmacy for 8 years applying for a pharmacy software startup has a form of evidence that is not about the product at all — it is about the problem. That credential is fundable even without revenue when it is specific and deep enough.

THE TRACTION FIELD

This is the field where pre-revenue founders feel most exposed. The instinct is to either apologize for having no revenue or to pad the answer with market size data. Both are wrong.

The right approach: state what you have specifically, then frame it as the evidence you have chosen to gather before building.

Wrong version: "We are pre-revenue but the global pharmacy software market is $4.2B and growing. We plan to begin customer acquisition after product launch in Q3."

Right version: "We have no revenue yet. We have spent the last 3 months doing customer development: 67 interviews with independent pharmacy owners across Pune, Nashik, and Aurangabad. 43 of them said they currently track inventory in paper or Excel. 11 agreed to use a beta version of our product for free and give us weekly feedback. 3 of them have asked when they can pay us. Our first paid pilot starts in 2 weeks."

The right version has no revenue but it has motion, specificity, and the most important signal for a pre-revenue application: people who asked when they could pay.

THE INSIGHT FIELD

For pre-revenue founders, the insight field is often the strongest field available. An insight that comes from deep immersion in a problem — from doing the interviews, living in the industry, or experiencing the problem personally — is genuinely hard to fake and genuinely valuable to partners reading it.

Make your insight specific and non-obvious. It should name something about your user or your market that is true, that competitors have missed, and that you know because of direct contact — not because you read it in a report.

Weak insight (no revenue, no real depth): "Independent pharmacies are underserved by current software solutions because existing products are too expensive and too complex."

Strong insight (no revenue, real depth): "In 67 interviews, I found that the person who manages stock in 80% of independent pharmacies is not the pharmacist — it's a family member, usually a spouse or adult child, who has never used a computer for work. Every existing pharmacy software product assumes desktop literacy. None of them work on WhatsApp. That is the gap we are filling."

The strong version could only come from actually doing 67 interviews. Partners reading it know this. That specificity is what makes it fundable at pre-revenue stage.

THE FOUNDER-PROBLEM FIT FIELD

At pre-revenue stage, this field carries more weight than it does for companies with traction. Partners are trying to evaluate: if this company has no revenue yet, why should I believe this founder will figure it out?

The answer comes from one of three sources:

Personal experience with the problem. You or someone close to you experienced this problem directly. The more visceral and specific the story, the more credible the fit.

Professional immersion in the problem. You spent years working in this industry before starting the company. You have seen this problem from the inside, you know the workarounds people use, and you know why every attempted solution has failed.

Intensive research-driven obsession. You have spent 6+ months doing nothing but talking to users in this space and you know more about their day-to-day reality than most people who have worked in the industry for years.

State which one applies to you, then prove it with the most specific detail you have. A pharmacy founder who can name 3 specific suppliers, describe the exact workflow a pharmacy owner goes through when receiving a delivery, and articulate the precise moment in that workflow where the biggest losses happen is demonstrating domain depth that is fundable without revenue.

Do not use market size as a substitute for user evidence. "The market is $4B" tells a partner nothing about whether real users want your specific product. Market size belongs as brief supporting context, not as the primary evidence of demand.

Do not describe a product you have not built as if it already exists. "Our product does X, Y, and Z" when your product is a Figma mockup is misleading and will unravel in the interview when partners ask for a product demo. Be honest: "We have a working prototype that handles X. Y and Z are on our next sprint."

Do not apologize for being pre-revenue. Apologetic language — "we know we don't have revenue yet but..." — signals defensiveness. Just state where you are and what you have. Confidence about your current state is more credible than apology.

Do not lead with future projections. "We plan to reach $100K MRR within 6 months of launch" with no current evidence is not compelling. It is a guess dressed as a plan. Every pre-revenue application has projections. The ones that get interviews have evidence.

Based on patterns across applications that received interviews without revenue, the minimum viable pre-revenue application tends to have:

• A working prototype or MVP — even if minimal

• 30+ documented user interviews with specific findings

• At least 5 users actively using the prototype in any form

• At least 2-3 users who have explicitly asked when they can pay

• A non-obvious insight that could only come from the above research

• A founder-problem fit story that is specific and personal

If your current situation includes all six of these, a pre-revenue application has a real chance. If you are missing more than two, the strongest move is to spend 4-6 more weeks building the evidence before applying.

Indian founders often have access to a research advantage that is underused: proximity to the market they are building for. If you are building pharmacy software and pharmacies are your neighbors, or building for kirana stores and you grew up in a family that runs one — that proximity is evidence. Name it explicitly. The ability to do 60 user interviews in 3 weeks because your market is physically accessible to you is a real advantage over a founder who would need to fly across the country to talk to the same users.

Use your geographic and cultural proximity to your user as a founder-problem fit argument. It is legitimate and often compelling.