Episode Summary
Executive Summary: The episode follows Emergent founders Mukund and Madhav Jha as they explain how they pivoted from coding/testing agents for engineers to a platform that lets non-technical users build production-ready software. They argue that AI is expanding software creation, not just replacing jobs, by enabling domain experts and solo founders to launch customized tools, internal apps, and even agentic workflows at scale.
Main Topics: From software testing to full-stack coding agents (Priority: 5/5): The founders trace Emergent’s origin to automating software testing, then realizing verification loops could support broader software engineering automation. Pivot to non-technical users and production apps (Priority: 5/5): They explain shifting away from enterprise/technical users toward ordinary users who need real deployed software, not just prototypes. Engineering architecture for production and long-horizon tasks (Priority: 5/5): Emergent’s stack combines its own infra, multi-agent orchestration, memory, and deployment systems to make apps both buildable and shippable. Distribution, competition, and first-mover dynamics in AI (Priority: 4/5): They discuss how model advances reset the market, how they competed against early coding tool entrants, and how influencer marketing helped accelerate adoption. AI’s impact on SaaS and software labor (Priority: 5/5): The conversation frames AI as changing SaaS from static workflows to agentic, customizable systems while increasing demand for software output rather than eliminating it. Personal software and domain-expert entrepreneurship (Priority: 5/5): A major theme is empowerment: people closest to a problem can now build bespoke apps without translation loss, lowering the barrier to starting businesses. Team culture, hiring, and global operating model (Priority: 4/5): They describe a lean team split between Bangalore and San Francisco, with strong customer empathy and high-ownership hiring standards.
Key Arguments: Verification is the key loop that allows agents to continue working; solving testing/verification can unlock broader software engineering automation. Starting second in AI can be an advantage because each new model generation changes what is possible and lets teams reimagine the product from a better starting point. Most existing AI app builders were optimized for front-end prototyping; Emergent differentiated by focusing on end-to-end production readiness, including deployment and backend support. Building its own infrastructure gave Emergent better feedback loops, smoother deployment, and fewer build-to-prod failures than relying on third-party sandboxes. Non-technical users are the real growth audience; 80% of users reportedly have zero programming knowledge and are building serious applications. A large share of the product’s value comes from user proximity: domain experts can build directly, avoiding the translation loss of working through a dev shop. AI is expanding the market for software and reshaping roles, enabling PMs, designers, and engineers to converge into smaller, more productive teams. SaaS companies must become agent-first or risk obsolescence as more workflows are consumed by autonomous agents. Model companies are not the immediate existential threat because application quality depends on understanding user needs, orchestration, and verification layers on top of foundation models.
Data Points: Apps built with Emergent: 7 million - Total apps built in eight months since launch Time to reach Sui Bench #1: 2 months - Their coding agent became world number one on the benchmark in two months User mix who are non-technical: 80% - Majority of platform users have zero programming knowledge Geographic reach: 190 countries - Users are spread globally across the platform Regional user concentration: 70% to 80% in US and Europe - They described most users as coming from Western markets Internal team size when customer support was split: 12 people - They were a very small engineering team early on Potential traditional development cost: $500,000 - Estimate for building the kind of software users now build on Emergent Current build cost on Emergent: $5,000 - Approximate cost for users to build the same software themselves Monthly savings from replacing Asana: $3,000-$4,000 - Internal tool built on Emergent reduced subscription costs Internal app shipping cadence: 3 times a day - They ship morning, evening, and night
Pivotal Quotes: "if you have like some agency of interest and you want to start your own business and have autonomy over your life, like you are empowered. that at scale." — Mukund Jha: Explaining the broader social value of Emergent beyond job displacement fears "the real user need was actually to ship the product, not just the front-end prototyping." — Madhav/Mukund Jha: Describing the pivot from prototype-focused app builders to production software "the current way the SaaS is existing today needs to change." — Mukund Jha: Arguing that agentic workflows and customizable internal software will reshape SaaS
Implications: AI app builders are moving from novelty/prototyping tools to serious production platforms. For users, this means more autonomy and lower cost; for SaaS vendors, it means pressure to become customizable and agent-native.
About Y Combinator Startup Podcast
We help founders make something people want. The Y Combinator Podcast is where builders talk about building. From the earliest days of an idea to scaling a company that changes the world, YC partners and founders share real stories, lessons, and tactics from the frontlines.