What Not To Do In A YC Interview

We applied to YC's Winter 2023 batch on the last possible day, for a product called Pryse.dev, pricing infrastructure for usage-based SaaS companies, the same words we used in the application itself. The name did some work too, Pryse for price, .dev for devtool, small enough to notice, not so cute it got in the way.

What actually got us the interview, in hindsight: a specific, ambitious framing of the problem, a founding team with real, relevant background, and an honest account of a hard problem we'd hit ourselves. We got the invite on November 19, with the interview date set for December 1.

What we didn't have by December 1 was the idea anymore. User research had shown us the market was too small to build a real company on, and by the time the interview was scheduled, the founding team had also quietly split, with no shared intention to keep building together. We had eleven days, no progress on what we'd submitted, and no replacement idea.

We talked to a friend who'd gone through YC, told him the actual situation, and decided to show up anyway and be honest about it. That honesty had a limit we didn't notice at the time. We told the partner we were hunting for a new idea and would start fresh. We left out that there was no longer a "we" in any committed sense.

The interview itself was short, ten to fifteen minutes, with a panel that had clearly been running these back to back for days. The partner had built pricing infrastructure himself at a company he used to run, so the problem landed instantly, he'd felt exactly the pain we were describing. He called it worth solving, genuinely hard, with real defensibility if someone built it right. Then he asked what we'd built. We had nothing to show him.

We knew before the interview ended that it probably wasn't going our way, and the rejection came by the end of the same day. Not because the problem was weak, and not because the team looked wrong on paper. Because a YC interview is built around momentum since the application landed, and we walked in with none.

The mistake wasn't the pivot, and it wasn't telling them about it. The mistake was staying in the process at all once the idea we'd submitted was one we no longer believed in, without either withdrawing or being fully upfront about where things actually stood, team included, before the interview was even scheduled. Partial honesty read exactly like what it was, a good story about the past covering for the absence of anything current.

If there's one thing worth taking from this, it's that a YC interview isn't really testing whether you can explain your idea well. It's testing whether something is still moving. Walk in with nothing that's moved since you applied, and no explanation, however honest, buys that back.