Closing & follow-ups

~7 min read

Background

Why it matters

The interview is usually decided before your clever question, and a YC slot often ends with no time for one. This page is still worth twenty minutes of prep because the failure modes are cheap to avoid: a question you could have Googled, a follow-up email that rewrites the company, or a number you promised and never sent. Do the boring version well.

Core concepts

  • If they ask “what questions do you have?”, ask one that changes your behavior. Timeline and process (“what happens after this, and when?”). What would make this a no. How they think about a risk you actually have (the wedge, the cycle time, a student team). Skip “what do you look for in founders?” You can read that. Skip a question whose only job is to sound smart.
  • Don’t pitch again inside the question. “Have you seen how big this market is?” is a speech. One question, then listen. If the clock is gone, “I’m good, thank you” is a complete close. Forcing a question into a partner’s next interview helps no one.
  • The follow-up is the thing they asked for, sent quickly. A metric definition. A one-page cohort. An intro to the customer you mentioned, after you asked that customer. Same day if you can, next day if you can’t. A new twelve-slide narrative is not a follow-up. It tells them the interview version wasn’t the real one.
  • Don’t invent urgency or a new story. “We’re closing Friday” belongs in the email only if it was true in the room. A fact you failed to say can be one sentence (“recurring is $7.5k, not $9k, after pulling the setup fee”), especially if it corrects the record. A second company strategy does not belong in the thread.
  • Room difference. After a YC interview, the application and the ten minutes are the artifact. A short thank-you is enough unless they asked for something. After a seed meeting, the follow-up is part of diligence. The partner’s associate will notice whether the number in the email matches the number you said. See Traction and Fundraising.
  • Between the interview and the next one. Fix the sentence that broke. Don’t add a new market to “sound bigger” because one partner frowned. If the frown was about a real gap (no user, no price test), spend the week on that gap, not on the email’s adjectives.

Mental model

flowchart TD
  R["In the room: one useful question, or none"] --> A["After: send exactly what you promised, and any correction"]
  A --> D["Don't: a new pitch, a fake deadline, a different number"]

The close is a handoff. The company does not get reinvented in the handoff.

Interview questions

  1. They say “any questions?” with two minutes left. What do you ask? Answer: One process or risk question. “What would you need to see in the next month for this to be a yes?” or “Is the thing you’re least sure about the wedge or the cycle time?” Then stop talking. Not a market monologue, and not a question about their personal brand.

  2. The YC interview ends abruptly and you never asked anything. Did you fail the close? Answer: No. Use the minutes on their questions. Send a short note only if they asked for a fact or if you need to correct one. A long thank-you that re-pitches the company spends their reading time on something they already heard.

  3. You promised a cohort breakdown and also want to attach a new deck with a bigger TAM. What do you send? Answer: The cohort, with the definition in two lines, and nothing else that changes the story. If the TAM in the room was wrong, one correcting sentence. A new market narrative in the attachment is a signal that the interview answer was disposable.

  4. A partner goes cold after a good meeting. What do you do? Answer: One bump with something new that is real (a paid user, a correction, the intro you offered), then go back to the company. A sequence of “just checking in” emails doesn’t create a decision. Fundraising advice from Ralston and Flora is consistent on this: the raise is a process you run while the work continues, not a thread you refresh every morning.

Watch

Further reading


Back to top

Copyright © 2026. Distributed under the MIT License.

This site uses Just the Docs, a documentation theme for Jekyll.