How to Describe Your Progress Section in the YC Application

Partners read hundreds of progress sections per batch. The ones they remember answer a single question with maximum specificity: what has actually happened since you started building this company?

The YC application asks: "How far along are you? Do you have a product? Any users? Any revenue?"

What partners are actually evaluating through this field:

Is this company real or hypothetical? The most important signal. A company with specific, dated evidence of activity — customers acquired on a specific date, a specific version of the product shipped, a specific conversation with a named user type — is real. A company described entirely in future tense is hypothetical.

Is this founder moving fast enough? Partners compare what you have built against how long you have been building. 14 months with 3 users is a slow pace. 6 weeks with 23 paying customers is a fast one. The absolute numbers matter less than the ratio of evidence to time elapsed.

What is the quality of the evidence? There is a hierarchy of evidence in the progress section: paying customers (strongest), unpaid active users with strong retention, signed LOIs or pilots, prototype tested with real users, prototype built but not yet tested, concept with no prototype (weakest). Know where you sit on this hierarchy and write accordingly.

If You Have Paying Customers

This is the strongest possible progress section. State the following in this exact order:

1. Number of paying customers (exact, as of a specific date)
2. Monthly recurring revenue (exact number)
3. Retention rate (exact metric, exact window)
4. How you acquired them (the specific channel, not "through marketing")
5. What they pay and what they use the product for
6. The earliest and most recent customer acquisition date

Example:

"23 paying customers as of October 14, 2024. ₹64,400 MRR. Month-2 revenue retention: 89%. All 23 came from direct outreach in 12 pharmacy owner WhatsApp groups across Maharashtra. Average contract: ₹2,800/month for inventory tracking and expiry alerts. First customer: August 3. Most recent: October 11."

That is 60 words. It contains 7 specific data points. A partner reading it can reconstruct your acquisition motion, evaluate your retention, assess your pricing, and verify the timeline.

If You Have Free Users But No Revenue

State the strongest behavioral evidence you have — not just signup numbers, but evidence of genuine engagement and value:

1. Number of active users (distinguish total signups from monthly actives)
2. Retention (Day-7 or Day-30 — be specific about the window)
3. The specific behavior that signals value (not just "users love it")
4. Any monetization signal (users who asked to pay, who gave payment information, who upgraded from free)
5. When you launched and how you acquired these users

Example:

"340 monthly active users, 11 weeks after launch. Day-7 organic retention: 61%. Top usage behavior: users generate an average of 4.2 inventory reports per week — our hypothesis was 1-2 per week. 6 users have asked how to pay; 3 have given us credit card information for when we launch paid tiers. Acquired entirely through founder's personal network of 47 pharmacy owner WhatsApp groups."

If You Have a Working Prototype But No Users

State specifically what the product does, who has seen it, what their reaction was, and what specific evidence of demand you have gathered:

1. What the product does today (not what it will do)
2. Who has used or seen it (number, user type)
3. What they said or did that constitutes demand evidence
4. Any pre-commitment evidence (waitlist with payment, signed LOI, deposit paid)
5. When you built it and how long it took

Example:

"Working prototype of our WhatsApp-native inventory system built over 8 weeks. Tested with 14 pharmacy owners across 3 cities — 11 said they would pay ₹500-1,500/month for the current version. 3 have agreed to pay on launch and given us their WhatsApp numbers to be the first to receive the link. One distributor has agreed to pilot our returns integration when we launch. No live users yet — launching in 3 weeks."

If You Are Pre-Prototype (Idea Stage)

This is the hardest stage to write a strong progress section. The temptation is to describe what you are going to build. Resist it entirely. Write only about evidence of demand and team activity:

1. Number of user interviews conducted (must be substantial — 20+ to carry weight)
2. The specific, non-obvious thing you learned that justifies building this
3. Any behavioral evidence of demand (someone who offered to pay, who changed their behavior because of a conversation with you)
4. What the team has built in adjacent areas or what specifically qualifies the team to build this quickly
5. What you have done in the last 30 days that proves you are moving

Example:

"No product yet. 67 user interviews with independent pharmacy owners across Maharashtra and Gujarat over 8 weeks. The non-obvious finding: 72% of respondents identify stock loss to expiry as their most painful operational problem — more painful than theft, payment delays, or distributor issues. We did not expect this ranking. We asked them to rank 7 pain points; expiry loss won unprompted in 72% of cases. 4 owners offered to pay before we mentioned pricing. We are building the prototype this week."

Partners weight progress evidence on an implicit hierarchy. Know where your evidence sits:

What "Progress" Is Not

Partners are explicit about this: the following do not count as progress evidence:

• Media coverage or press mentions
• Academic publications or research citations
• Advisor or investor names
• Contest wins or accelerator acceptances (other than YC itself)
• App store downloads without active user data
• Social media followers without conversion evidence

These items can appear as supporting context but should never be the primary content of your progress section.

Mistake 1: Mixing past progress with future plans

The progress section should describe only what has happened, not what you plan to do. "We have 14 customers and plan to reach 50 by Q1" — the second half of that sentence belongs in the growth plan field, not the progress section. Keep the progress section entirely in the past tense.

Mistake 2: Reporting vanity metrics instead of retention metrics

"10,000 app downloads" without active user data is a vanity metric. "2,400 monthly active users" is a real metric. "61% Day-7 organic retention" is a retention metric. Downloads, page views, and social shares are not progress evidence. Active users with retention data are.

Mistake 3: Understating progress out of modesty

Founders frequently write "we have some early customers" when they mean "we have 23 paying customers at ₹64,400 MRR." The modesty is counterproductive — it produces less impact than the specific numbers would. Partners cannot be impressed by numbers you do not name. Write the number. Say it confidently.

Mistake 4: Reporting aggregate progress without a timeline

"We have 23 customers" is weaker than "we have 23 customers acquired over 10 weeks, with the first customer on August 3 and the most recent on October 11." The timeline tells partners your pace — which is information about your execution velocity that the aggregate number alone cannot convey.