the application
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, verbatim from the application. The name pulled its weight too. Pryse for price, .dev for devtool. Noticeable, not cute.
What got us the interview.
- A sharp, specific framing of the problem
- A founding team with real, relevant scars
- An honest account of a hard problem we'd actually lived
The invite came November 19. Interview date, December 1.
the collapse
By December 1, the idea was dead. User research had already killed it, the market was too small for a real company. By the time the interview was scheduled, the founding team had split too, with no plan to keep building together. Eleven days out. No progress on what we'd submitted. No replacement idea.
We decided to be honest about the collapse, but that honesty had a limit we didn't see at the time. We called a friend who'd been through YC and told him the real situation. We told the partner we were hunting for a new idea and starting fresh. We left out that there was no "we" left to start anything.
the interview
The partner liked the problem. We had nothing to show him. The interview ran ten to fifteen minutes, with a panel that had clearly done nothing but this for days. He had built pricing infrastructure himself, at a company he used to run, so the problem landed instantly. He called it worth solving. Genuinely hard. Real defensibility, if someone built it right. Then he asked what we'd built.
We knew before the interview ended that we'd lost it. The rejection landed the same day. The problem wasn't weak. The team didn't look wrong on paper. A YC interview runs on momentum since the application. We had none.
conclusion
The real mistake happened earlier. We stayed in the process after we'd stopped believing in the idea we submitted, instead of withdrawing, or being fully upfront, 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.
A YC interview tests momentum, not how well you can explain an idea. Walk in with nothing moved since you applied, and no explanation buys it back. However honest.
Get new essays and theses by email
More essays
- Pricing AI Products When the Cost per Task Keeps Falling Oct 27, 2026
- The Liability Wall Stopped Being Hypothetical Oct 4, 2026
- The Personal Assistant Landscape, Right Now Sep 30, 2026
- The Home Doesn't Have One User, So Its Assistant Shouldn't Either Sep 26, 2026
- Qualities of Great AI Coding Agents Sep 22, 2026
- The AI Bubble Deflates, The Technology Doesn't Sep 22, 2026
- The Boring Levers That Actually Run A Boutique Agency Sep 15, 2026
- India's Seed Stage Is Missing Its Powerhouse Sep 13, 2026
- Code Review Was Never The Bottleneck Sep 7, 2026
- An AI Assistant That I Actually Want Sep 1, 2026
- The Small Things I Keep for Myself Aug 31, 2026
- What Changes When You Go From Operator to Investor Aug 10, 2026
- The Wow Moment Shouldn't Take Two Weeks Apr 21, 2026
- The Three Moments That Will Make or Break Littlebird Apr 14, 2026
- Voice at Work, Why It's Harder Than It Looks Mar 31, 2026
- Top of Funnel for Voice-First Tools Is Not Signups. It's Someone Else's Product Mar 27, 2026
- When Thinking Outruns Writing Mar 26, 2026
- Why Voice-First Tools Struggle in India Mar 23, 2026
- When AI Disappears, Value Appears Mar 20, 2026
- The Tiny Feature That Saves Your Users and Your Metrics Feb 5, 2026
- Anatomy of a CLI-Based Code Assistant Jan 20, 2026