May 23, 2025 · 30m · y-combinator
How To Design Better AI Apps · Y Combinator
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this episode of Y Combinator's 'The Breakdown,' General Partner Pete Koomen joins hosts Tom Blomfield and David Lieb to discuss why modern AI applications fail when constrained by legacy software paradigms and how developers can build true AI-native experiences through custom system prompts, background agent workflows, and unconstrained user interfaces.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. How this is scored →
speaking balance: gold is the partners, purple is the guest (3 minute bins)
Pete counters Tom's suggestion that users won't touch system prompts by citing real YC internal agent usage proving people will actively write and modify prompts daily.
Hardest push from the partners ▶ 21:00 Tom rejects raw system prompt writingTom explicitly challenges Pete's model by comparing manual prompt drafting to expecting an executive to write a 30-page manual for a new assistant instead of iterative onboarding.
Biggest teaching moment ▶ 5:29 Pete deconstructs developer gatekeepingPete breaks down why modern AI interfaces fail, showing that engineers are inappropriately applying decades-old code-hiding paradigms to natural-language system prompts.
The partners hold their own ▶ 11:49 David's technological wave breakdownDavid enriches Pete's thesis by citing concrete historical precedent, detailing how early internet directories and early mobile web-wrappers took years to find their native paradigms.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The partners as informed peer | Guest teaching | Guest disagreement | The partners pushing back | Why |
|---|---|---|---|---|---|---|
| Welcoming Pete Koomen and Introducing 'AI Horseless Carriages' | 3 | 2 | 2 | 1 | The hosts introduce Pete Koeman and discuss his viral essay critiquing corporate AI agent design. Pete explains the contrast between powerful developer tools like Cursor and frustrating, repetitive integrations like Gmail's Gemini drafting tool. | |
| Ideal AI Workflows vs. Defensive Corporate Software Design | 5 | 3 | 2 | 1 | The panel discusses why large tech companies ship bland AI tools, citing risk aversion, PR concerns, and legacy development mentalities. The hosts actively contribute context regarding Google's early transformer models and corporate caution. | |
| Custom System Prompts: Personalizing AI Output Tone | 3 | 4 | 2 | 1 | Pete demonstrates how personalizing a system prompt with user context produces natural email responses rather than lowest-common-denominator corporate prose. He explains how developers traditionally gatekeep software logic. | |
| The 'AI Horseless Carriage' Analogy and Technological Shifts | 6 | 3 | 1 | 1 | David Lieb draws historical parallels between horseless carriages and early tech paradigms, like digitized Yellow Pages directories and mobile web-wrapper apps. Pete showcases his inbox automation agent using natural language rules. | |
| Interactive Demo, Vibe Coding, and the 'Cursor Moment' | 5 | 3 | 2 | 1 | The conversation shifts to vibe coding and why developer tools are outpacing domain-specific tools in legal and accounting. Pete attributes this to dev tools granting raw access without patronizing guardrails. | |
| Will Everyday Users Write System Prompts? | 4 | 2 | 3 | 5 | Tom Blomfield and David Lieb push back on Pete's assumption that everyday users will comfortably write system prompts, citing non-technical users like their parents. Pete defends his view by comparing prompt writing to general computer literacy. | |
| Iterative System Prompting and AI-Assisted Configuration | 5 | 3 | 3 | 5 | Tom Blomfield argues for a layer of abstraction where AI auto-updates system prompts based on iterative feedback rather than users raw-dogging text files. Pete agrees with tooling improvements but maintains prompt visibility is essential. | |
| Moving Beyond Chatbots: Tool Use, MCP, and True Automation | 5 | 3 | 1 | 1 | The panel explores tool use, MCP servers, and transitioning away from conversational chatbot interfaces toward background automation that completes real-world tasks across multiple apps. |