How to Build Superintelligence Inside Your Company

The episode features YC General Partner Pete Kumman discussing how Y Combinator transformed itself into an AI-native organization by building internal agent infrastructure from scratch. The journey began about a year prior when Pete and a small engineering team worked with YC's finance team, noticing an inefficient loop where software engineers had to manually translate complex financial workflows into deterministic software. The realization that agentic coding tools could empower non-technical employees to encode their own workflows in plain English prompted a broader infrastructure project.

The foundational breakthrough came when agents were given read-only SQL access to YC's single PostgreSQL database, which houses all critical company context — funded companies, founders, financial transactions, CRM notes, and more. This single-database architecture proved enormously powerful because it allowed agents to answer arbitrary, complex questions instantly, dramatically increasing both the volume and complexity of questions employees would dare to ask — an instance of Jevons' paradox applied to organizational intelligence.

The team built a shared internal tool registry that has grown from roughly 20 tools to over 350, covering finance workflows, office hours management, event planning, and more. Skills — abstraction layers over tools — emerged as a key primitive, and the system evolved toward self-improvement: a nightly agent reads all employee agent conversations, identifies gaps, and automatically improves skills. A concrete example is YC's 'two-sentence description' skill, which was refined by feeding it transcripts of partner office hours sessions, ultimately making the AI better at this task than any individual partner.

A critical organizational design choice was making all agent conversations publicly viewable by full-time YC employees via a Slack broadcast channel. This transparency served multiple purposes: it allowed employees to learn from each other's agent usage, it acted as a social control mechanism to keep sensitive information private without heavy technical restrictions, and it enabled a high-trust, egalitarian environment that the hosts argue is prerequisite for this type of AI-native organization.

The hosts draw broader lessons about the nature of AI adoption in organizations. They argue that the 'horseless carriage' problem — slotting AI as a small feature inside deterministic software rather than building agent-first — still dominates commercial software. They advocate for minimal, agent-wrapping architectures ('just-in-time software') over large deterministic codebases, citing Gary's experience rewriting a half-million-line Rails app into a far smaller, more flexible agentic system. The conversation concludes with a philosophical argument about centralization versus decentralization in AI: the hosts warn against a 'mainframe era' scenario where a few large companies control AI and user prompts, and advocate for a personal computing-style revolution where individuals own and program their own AI systems.