Nadia: What the Yes or No Actually Bought Her

Miles: I read it four times, and I still, I still don't know what it means. Grant: That's Nadia. Tuesday night, an inbox, one email from YC Combinator. Miles: Ninety seconds of dead air after she read it. That's where today starts. Grant: Welcome back, everyone, to year one. Miles: Good to be back. So we're spending this whole episode inside Nadia's month, the customer she chased- Grant: Mm. Miles: The feature she killed, the hire she put off. Grant: And the fundraise she shut down on her own, quietly, without telling half her team. Miles: Which we'll get into why that choice runs against what a lot of founders are hearing this cycle. Grant: To widen the lens, a YC partner's read on how they pattern-match founders sitting exactly where Nadia's sitting right now. Miles: What actually changes the morning you get a yes- Grant: Right Miles: ... or a no? Grant: And by the end, Miles and I each land on one thing, one number, one honest answer we're holding Nadia to in September, no matter what YC decides. Miles: August twenty-eighth, that's the date circled on her calendar. Grant: So let's go back to Tuesday night. Miles: The email. I mean, she's read this email four times, and she still can't tell you what it actually says. Grant: That's kind of the whole story right there, isn't it? Miles: The line she keeps circling, "Your application has advanced to the next stage of review." That's it. No yes, no no. Grant: And look, that's the pattern I've seen a hundred times. Founders read advanced as, "We want you," because that's what they need it to mean in that moment. Miles: She did, but nowhere in that sentence does it say interview. Grant: So what's she actually holding in her hand? Miles: A status update. Grant: Mm. Miles: Nothing more. Grant: Okay, so let's get the actual dates pinned down. Miles: Right. She submitted before the on-time cutoff. Y Combinator's own applications page puts that at July twenty-seventh, eight PM Pacific. Grant: And when is the verdict actually locked? Miles: August twenty-eighth, seventeen days out from where we're sitting right now. Grant: So when did this email land? Miles: Tuesday night, late, eleven fifty-two PM. Grant: So she's sitting there at midnight, still hitting refresh, not even tired? Miles: She was awake, waiting. I mean, really waiting, the kind where you're checking your phone every few minutes. And Y Combinator's own process notes say most interviews happen by video through August and September, so a message showing up mid-August isn't a verdict. It's a placeholder in line. Grant: Which she knows intellectually. Miles: Sure. Doesn't stop you reading it four times anyway. Grant: Here's what got me, though, what she did in the ninety seconds right after she read it. Miles: What'd she do? Grant: She didn't call her co-founder, didn't text anyone. She opened her bill log and wrote- Miles: Wow Grant: ... down the exact minute she got it. Miles: She timestamped it? Grant: Down to the minute. That's not relief. That's someone bracing for something. Miles: Or someone who's been burned by ambiguity before and knows that a record of exactly what was said in that exact moment matters later. Grant: Maybe both, but that ninety seconds tells you more than whatever shows up on the twenty-eighth will. Miles: Which raises the obvious question, what was she actually doing in the weeks leading up to that email landing in her inbox? Okay, so forget the email for a second. What did she actually do with that month? Grant: That's the real question. Miles: Right. So week one, she's still building. She signs a pilot with a regional produce distributor, I wanna say fourteen stores, and she's manually reconciling their inventory feed by hand every night. Grant: By hand? Miles: By hand. No automation yet. That's the thing about early traction. It's ugly before it's real. Week two is where it gets interesting. She kills a feature, a supplier matching tool she burned six weeks on because the customer never touched it once. Grant: Six weeks gone? Miles: Gone. And in the same week, she postpones a hire, an ops lead she'd basically promised an offer to because payroll would have wiped her runway to under two months. Grant: Would she defend that call if the answer's no? Miles: She told me yes without blinking. Said the alternative was hiring someone into a company that might not exist by October. Grant: Hard to argue with the math. Miles: And then there's the customer she chased, a wholesale bakery chain bigger than the produce account that had gone quiet for three weeks. She got them back on a call, and they signed a paid pilot the following Monday. That's not waiting. That's grinding. Grant: So the month wasn't dead time. It was a second sprint. Miles: Yeah, and that's the framing I've heard from YC partners directly. They treat what you build between submission and interview as some of the strongest signal in the whole process. Grant: So the form isn't the pitch, the month is. Miles: That's the read. And founders are allowed to send updates after they've applied, so silence on your end doesn't mean silence on YC's end. Grant: Did she send anything? Miles: Two updates, one after the bakery contract, one after a small local news mention. Grant: Mm-hmm. Smart. Miles: And here's the other piece. From what I've seen this cycle, applications for fall twenty twenty-six get read rolling, not all dumped at the deadline. Grant: Which means the calendar she's staring at might not even reflect when her file actually got looked at. Miles: Exactly. Somebody could have read her application in week one and be sitting on it or read it last Tuesday. Grant: So none of this, the bakery, the feature she killed, the hire she held off, none of it was really about waiting. Miles: No. It was about not being the same company by anyone opens the file. That's the difference between waiting and positioning. Grant: Except every one of those calls, the customer, the feature, the hire, assumes she gets the yes. Miles: Yeah. I hadn't really sat with that until you said it. Grant: So what does she build for the other outcome? Because there's a second thing she started this month and quietly stopped. Miles: The parallel raise. Grant: The parallel raise. So there's a thread I wanna pull that Nadia hasn't touched, the raise she started then just stopped running. Miles: The... Right, the parallel round. She had three meetings booked back in July. Grant: Three meetings, one soft yes on terms, and then nothing. No follow-up for seventeen days. Miles: Seventeen days. That's not too busy. That's a decision. Grant: That's what I asked her. Who told you to stop? Miles: Hmm. Grant: She said nobody told her. She just didn't wanna look like she was hedging. Miles: Hedging against what, though? Grant: That's the word she wouldn't say out loud, so I asked her directly, "What happens to your co-founder's confidence if the answer's no?" She deflected. Twice. Miles: Whatd she say the second time? Grant: Something about, "We'll figure it out." Then she pivoted straight back to the ops hire. Miles: Yeah. That's a real silence, actually. Grant: It sat there a while, yeah. Miles: So flip it around. Is stopping the raise the mistake, or does it just look that way from outside? Grant: Round funded put out a guide for this exact Fall Twenty Twenty-Six window arguing you keep outreach running in parallel, so a rejection- Miles: Mm-hmm Grant: ... costs you a no, not the whole company. Miles: A single no, not the whole raise. So the logic is run both engines and one rejection doesn't sink everything. Grant: That's the pitch. She's read it. It's everywhere right now. She's resisted it anyway. Miles: Why, if the math's that clean? Grant: I don't think it's math for her. Stopping the raise was the one place she could control the story. Keeping two processes alive means admitting the yes isn't guaranteed. Miles: And running just the one means she never has to say that out loud, not even to her co-founder. Grant: Maybe not even to herself. So what actually happens to the co-founder if it's a no? She never answered that. Somebody's watched hundreds of founders sit in this exact window, though. Miles: Let's hear how a partner reads it. Zoom out for a second. YC partners have watched hundreds of founders sit in exactly this window Nadia's in right now. Grant: And the pattern's not subtle if you're watching closely enough. Founders who keep shipping during the wait are fine either way. The ones who go quiet and start refreshing their inbox every ten minutes, that's your behavioral tell. Those are the ones who crack on a no. Miles: Which is the tell, right? Motion versus paralysis. Grant: Exactly. It's not about confidence. It's about whether you can hold two outcomes at once and keep working anyway. Miles: So say the call comes and it's a yes. What actually changes the next morning? Grant: Money moves first. One widely cited YC interview guide, Round Funded, I think it was, described the standard 500K deal funding the moment you're accepted, not when the batch starts. Miles: Not weeks later. Immediately. Grant: Immediately. And the batch itself runs in person in San Francisco through the fall. Miles: Which means if Nadia gets the yes, she's relocating a company, not just updating a calendar. Grant: Right. That's the part founders underestimate. The operational scramble starts before the excitement wears off. Miles: Now flip it. Say it's a no. Grant: Here's what nobody talks about enough. Interview teams, regardless of outcome, get written feedback, detailed, specific from the partners who sat on that call. Miles: Even the rejections? Grant: Even the rejections. And multiple guides covering this cycle frame that feedback as the single most underused asset a rejected founder walks away with. Most people read it once, feel bad, and never open it again. Miles: Instead of treating it like a scouting report. Grant: Exactly. Two or three partners, ten minutes, telling you precisely what they weren't convinced of. Miles: That reframes the no. It's not a verdict, it's a punch list. Grant: There's a bigger reframe too. One founder guy that came across, Flowjams, put out a number worth sitting with, something like forty percent of accepted companies each batch are still idea stage, no revenue. Miles: Forty percent? Grant: That's their read, and I'd hold it loosely since it's one outside account, not YC's own filing. But if it's even close to right, it means traction isn't the filter everyone assumes it is. Miles: So the feature Nadia killed, the customer she chased, that might matter less to the decision than she thinks. Grant: Might, or might be exactly why she got an interview at all. That's the part you can't know from outside. Miles: Which is almost worse. You can't game a filter you can't see. Grant: No, you can't. Miles: So the partner's looking for movement, not proof, and the money and the feedback both land the same day as the answer, whichever way it goes. Grant: Same day. No lag. Miles: Seventeen days from right now, Nadia finds out which version of tomorrow she's building. Grant: And whatever the letter says, there's a second document sitting right behind it. Miles: Yeah. So here's my number for September. Whichever way the email goes, I wanna know if she calls that pilot customer back. Grant: Not the investors? Miles: No, the customer, the one who never touched the feature she killed. If she's still chasing that relationship after a no, that tells me more than any term sheet. Grant: I see. Mine's smaller. I wanna know if she names a co-founder. Doesn't have to be the current one, just does she stop dodging the question? Miles: That's the one she wouldn't answer twice. Grant: Right. And silence on that after a yes or no is still an answer. Miles: Seventeen days until the twenty-eighth. Grant: Seventeen days, August twenty-eighth. Miles: Mm-hmm. Grant: That's the date on the email, and nothing before it changes anything. Miles: No amount of pattern matching gets her there early. Grant: Nope. She just waits it out. Keeps working the way she has been. Miles: Or doesn't. That's the thing. We don't know which version of her shows up on the twenty-eighth. Grant: We don't. Miles: August twenty-eighth. Grant: We'll have her answer either way. Miles: Tough play. We keep coming back to that ninety seconds after the email landed. Grant: Yeah. She opens her build log, writes down the exact minute. That's someone treating a status update like data. Miles: And that's where we're leaving it. Honestly, everyone's just waiting. Grant: Seventeen days. August twenty-eighth is when the decision lands, and that waiting period, that's when what she does tells you more than anything she says. Miles: We don't know which way it goes. Grant: Nope. Not yet. Miles: Know a first year founder with a story like Nadia's? Send them our way. yearone@heymato.com. Grant: And if this stuck with you, leave a review. Founders listen to those more than you think, especially when they're still in the waiting. Miles: Thanks for being here for this one. Grant: We'll be back the moment she hears. Miles: Yes or no. Grant: Either way, we're telling you what happens next. Miles: See you then.