How to Fill the YC Application If You Have No Traction Yet

When you have no traction, every other dimension of your application has to carry more weight. YC partners reading a pre-traction application are looking for a different set of signals — not evidence that the product works, but evidence that you have the depth, insight, and proximity to the problem to figure out what will work.

The four things that compensate for no traction, in order of strength:

1. Founder-problem fit that is visceral and specific The clearest substitute for product evidence is the quality of the founder's relationship with the problem. A founder who experienced this problem personally and can describe it with granular specificity — the exact workflow that fails, the exact moment they felt the pain, the specific cost they personally incurred — is more credible than a founder who identified the problem through market research.

2. Depth of user research with non-obvious output 40-80 user interviews that produced a genuinely non-obvious insight about the problem — something you could only have learned by doing those interviews — is the closest substitute to product traction. The key is that the insight must be genuinely non-obvious: something that contradicts the conventional understanding of the problem or reveals a user truth that competitors have missed.

3. Pre-commitment signals from potential users People who have taken an action — not just expressed interest — before your product exists. Signed LOIs, paid deposits, users who asked when they can pay, people who gave you their phone number and said to call them when you launch. These actions cost the user something and are therefore meaningful signals.

4. A working prototype, even if no one has used it yet A prototype that no one has used is weaker than a prototype with users, but it is meaningfully stronger than no prototype at all. It proves the founding team can execute and makes the product concept concrete rather than theoretical.

50-CHARACTER DESCRIPTION

Write this field exactly as you would with traction. Your user and your product description do not depend on your traction state. "Inventory management for Indian pharmacies" is as correct with zero users as it is with 50 users.

PRODUCT DESCRIPTION

Same format as with traction: user + problem + workflow + outcome. The difference is that you cannot cite current customers or retention data. Keep it clean and specific about what the product does — do not add hedging language like "we plan to build" or "our product will." Describe the product as it is designed, not as it will be.

HOW FAR ALONG ARE YOU (TRACTION FIELD)

This is the field where you need to reframe completely. Do not write this as a traction field. Write it as a progress field.

Progress is everything you have done that is not traction:

• Prototype built (describe what it does specifically)

• User interviews conducted (name the number and what you learned)

• Industry research completed (specific findings, not general context)

• Partnerships or pilot agreements in progress (name the stage)

• Pre-orders or LOIs collected (name the number and amount)

• Technical milestones achieved (for hard tech)

Strong no-traction progress answer: "We have no revenue or users yet. What we have: a working prototype that handles the core expiry alert workflow on WhatsApp. 67 user interviews with independent pharmacy owners across 3 cities, through which we discovered that the person managing inventory in 80% of pharmacies is not the pharmacist but a family member — a finding that shaped our WhatsApp-first design. 3 pharmacies have agreed to use our beta and give weekly feedback starting next month. 2 signed LOIs from pharmacy owners who asked to pay before we have a payment system."

This answer has no traction. It is still credible.

HOW DO YOU KNOW PEOPLE WANT THIS

Without paying customers, lead with the strongest pre-commitment signals you have, then add the most specific thing you learned from user research.

"We have no paying customers. However: 2 pharmacy owners independently sent us a UPI payment request before we told them how to pay. In our 67 interviews, we heard the same unprompted statement from 34 owners: 'I find out about expired stock when I'm throwing it away.' That statement — describing lost money that was invisible until it was too late — is why we believe the product will convert when we launch."

YOUR INSIGHT

Without traction, this field carries disproportionate weight. It is the place where you can demonstrate depth that the absence of traction cannot provide. Write the sharpest, most specific insight you have. Make it something that could only be known by someone who has spent months inside this problem.

A pre-traction application with a genuinely exceptional insight can be more fundable than a post-traction application with mediocre insight. The insight is what tells YC partners whether you understand the problem deeply enough to solve it — with or without current customers.

DISTRIBUTION

Without customers, describe your plan with as much specificity as possible, and anchor it to anything you have already tested.

"We will acquire our first customers through pharmacy owner WhatsApp groups in Maharashtra. We have already joined 47 such groups with 100-500 members each. We have not yet posted our product — we have been observing and building relationships. We plan to begin outreach next week to the 5 groups where we have had the most engagement."

The phrase "we have already joined" is past tense and specific. It is not traction but it is motion.

Based on publicly available accounts from pre-traction founders who received YC interviews:

They all had a working prototype. Not necessarily a coded MVP — but something. A WhatsApp bot, a spreadsheet, a Glide app, a manual service. Nothing purely theoretical.

They all had a specific non-obvious insight. The insight was always something that could only be known from direct contact with users. None of them cited market reports as the source of their insight.

They all had at least one pre-commitment signal. One signed LOI, one person who asked to pay, one user who gave their phone number to be called at launch. Something that required action from a potential user.

They all had specific numbers in every field. Even without traction, they had numbers: interview counts, prototype usage sessions, WhatsApp group sizes, LOI amounts. Specificity in the absence of traction signals that the founder is grounded in reality rather than working from theory.

Pre-traction applications are viable when the compensating factors are genuinely strong. They are not viable as a shortcut to apply before you are ready.

You should wait before applying if:

• You have not yet done user interviews — 40+ are the minimum before your insight is credible

• You have no prototype of any kind — even a manual or no-code version

• Your founder-problem fit story is generic rather than specific and personal

• Your insight is something anyone could derive from reading about the market

• You cannot name a single potential customer who has taken any action

If you cannot check at least three of the four compensating factors — founder-problem fit depth, user research insight, pre-commitment signal, working prototype — spend 4-6 more weeks building those before applying. The cost of one more month of preparation is much lower than the cost of using your application on a version of your company that is not yet ready.

You have an idea but no interviews yet: Do not apply. Spend the next 4 weeks doing 40-60 user interviews. Come back when you have an insight that could only be known from those conversations.

You have 20 interviews but no prototype: Build a minimal prototype — even manual — before applying. The combination of 20+ interviews and a working prototype is meaningfully stronger than interviews alone.

You have a prototype but no users: Get 5 users to try it before applying. One week of effort, potentially transformative impact on your application. The difference between "we built X" and "we built X and 5 people have been using it for 2 weeks" is larger than the effort required.

You have interviews, a prototype, and 2-3 pilot users but no revenue: Apply now. This is the minimum viable pre-traction application. You have all four compensating factors in at least minimal form.

You have strong founder-problem fit but none of the above: Start with user interviews this week. The strongest asset you have is your personal connection to the problem — interviews will help you translate that into a fundable insight faster than anything else.