Can I Send a YC Founder Update Before the Interview Decision? Here's What to Send

YC Summer 2026 applications closed May 4. As of today, May 13, 2026, S26 founders are sitting in the longest 12 days of their year, waiting for interview invites that start landing May 18 to May 26. The single question we get asked most at YC Roaster during this window is: can I send YC a founder update while my application is being reviewed?

Short answer: yes. YC partners do read the founder updates that come in via the application portal between submission and the interview decision. They have said this on the record, multiple times, including on the official YC podcast and in partner office hours.

The longer answer is the part founders get wrong, and the reason most updates do more harm than good. This post walks through what to send, what to skip, and how to format the update so a partner actually reads it.

What is the YC founder update field?

When you submit your YC application, the application portal stays open. There is a field, sometimes labeled "Founder Update" and sometimes embedded as a free-text reply within your application thread, that lets you add new information after submission. Partners can see these updates when they review your application a second time, which typically happens between day 7 and day 14 after the deadline.

For S26 applicants, that second-read window is happening right now, between roughly May 11 and May 18. Anything you submit before May 18 has the highest chance of being seen by the partner reviewing your application. Anything you send after the invite emails go out matters mostly if you did not get an invite and are being re-reviewed for the "borderline pile" that gets a second look before June 5.

When should I send a founder update?

Send one update if, and only if, something materially changed since you submitted. The bar is genuinely high. Material means:

A real new customer. Not "interested customer," not "had a great call." A signed contract or a paying customer.

A real revenue number. Going from $4K MRR to $7K MRR in a week is material. Going from "we have not charged yet" to "first paid customer" is very material.

A real shipped feature that changes the demo. Not "we refactored the auth flow." A new capability that, if shown in your one-minute demo, would have changed how a partner reacted.

A real new team member. A senior engineer or designer who quit a strong job to join. Not "we hired a part-time contractor."

A real piece of external validation. Press in a credible publication, a competitor acquisition that proves the market, an investor commitment.

If you do not have one of these, do not send anything. The most common YC founder update mistake is sending an update because you feel anxious, not because anything changed. Partners pattern match on this fast.

What does a good YC founder update look like?

Three lines. Maybe four. Here is the structure that works:

Line 1: What changed, with the number. Line 2: Why it is meaningful. Line 3: What it implies for the next 30 days.

Example, generalized from a W26 founder we worked with at YC Roaster who got an interview:

"Update since submission: signed our first enterprise pilot at $12K/month, starting May 9. This was our first paid customer in the defense vertical and validates the thesis that procurement teams will pay for our workflow product. We now have 3 paid customers ($31K total MRR) and expect to close two more by end of May."

That is it. No greeting. No "I hope you are well." No closing. Partners read 40 of these a day during invite week. Lead with the news.

What does a bad YC founder update look like?

The bad updates pattern into four buckets, and we see all four every batch:

The recap. Founders re-explain what their company does, what the application said, what the team looks like. The partner already read this 11 days ago. They did not forget. They forgot you, but they did not forget the application.

The polish. Founders mention they redesigned the landing page, hired a brand consultant, refined the pitch deck, or rewrote the about page. None of this is material. Partners do not invest in landing pages.

The pivot. Founders use the update to announce they have changed direction, ICP, or product. This almost always reads as instability. If you genuinely need to pivot, wait for the rejection (if it comes) and apply to W27 with the new thesis fully baked.

The drama. Founders explain why their cofounder left, why funding fell through, why the launch was delayed. Partners do not need the saga. Just the new state, in one sentence.

Should I send more than one founder update?

No. One update during the May 5 to May 26 window. If you somehow have two separate pieces of material news in two weeks, batch them into one update at the end of the window. Multiple updates train the partner to skim or skip.

The only exception: if you sent an update and a genuinely massive new thing happens (Series A term sheet, acquisition offer, a launch that hit Hacker News front page), a second update is acceptable. But "genuinely massive" is the bar.

What if nothing material has changed since I submitted?

This is the situation 80% of S26 applicants are in right now. The honest answer: do not send anything, and use the next 5 days to create something worth updating about.

That probably looks like one of:

Close one new paying customer this week. Discount aggressively if you have to. The price you charge matters less than the data point that someone paid.

Ship one new feature that improves your demo video. Re-record the demo. If you get the interview, the partners will watch the new version.

Get one credible reference call lined up. A YC alum, a notable angel, or a known operator who will pick up the phone if a partner calls.

Then send the update when one of those lands.

How does this connect to getting an interview?

It is one of the few levers you still have. The application is locked. The team is what it is. The product roadmap is fixed for the next two weeks. The only thing you control between May 4 and May 18 is whether one more material data point is in front of the partner when they make the call.

If your application was borderline, one strong update can move you from the maybe pile to the interview pile. We have seen it happen on every batch we have worked.

If your application was a clear yes already, the update will not change the decision but it will set you up for a stronger interview. The partner walks in remembering the most recent data point about your company, not the version of you that existed on May 4.

How do I know if my application was borderline?

You do not. The partners do not tell you, even when they reject. The only reliable signal is the read from someone who has been in the partner seat. That is the entire reason YC Roaster exists. If you want a YC alumnus to read your application and tell you where it falls (clear yes, borderline, clear no) and what one founder update would do the most to move it up, we can route you to one. That is the highest leverage thing you can spend an hour on this week.

The wait is almost over. Send the right update, or send nothing, and prepare to be one of the 800 to 1,200 invites that go out next week.