He Uses 7 Claude Code Agents to Build Apps with 0 Employees

Gabor Mayer is a PM at Google who runs a 21-agent Claude Code development team. In this episode, he walks through a live demo building a production mobile app from zero to TestFlight - Confluence for specs, JIRA for tickets, Figma for design, and Claude Code for development. Full Writeup: https://www.news.aakashg.com/p/how-to-build-a-full-ai-dev-team Transcript: [VERIFY - transcript URL] --- Timestamps: 00:00 AI agents can now run a startup workflow 01:23 Subscribe and AI tools bundle 01:55 Claude Code as your designer, developer, and systems analyst 02:43 Gabor’s 21-agent startup team inside Claude Code 04:57 Inside the system analyst agent 05:52 Live demo: zero to TestFlight 08:42 Prompting Claude to define a good system analyst 10:02 Ads 11:53 Building the system analyst workflow 12:24 Why documentation matters: Confluence, Jira, and MCPs 15:38 Why classic PM skills make you a better AI builder 19:22 The scaffolding that prevents AI spaghetti code 22:23 Setting up project-specific agents in Claude Code 26:26 Dictating the full product spec for the hockey rules app 32:26 Ads 35:36 Why dictation changes the quality of AI specs 47:38 Creating the visual direction in Figma Make 56:00 The idea-to-prompt-to-design-to-app workflow 1:06:21 Claude Code starts building the Figma screens 1:24:06 Frontend epics and Figma-linked tickets appear in Jira 1:48:57 The hockey rules AI app is live 1:53:56 Full recap: Claude, Confluence, Figma, Jira, Simulator, TestFlight 2:03:20 Should PMs get AI PM certificates? 2:08:21 How to create a PM portfolio that helps you land top jobs 2:13:32 How to get started building with AI agents --- 🏆 Thanks to our sponsors: 1. Maven Custom: Go from PM to AI builder with Cloud Code - https://maven.com/gabor/productbuilder 2. Amplitude: The market-leader in product analytics - https://amplitude.com/session-replay?utm_campaign=session-replay-launch-2025&utm_source=linkedin&utm_medium=organic-social&utm_content=productgrowthpodcast 3. Testkube: Leading test orchestration platform - http://testkube.io/ 4. Land PM Job: 12-week experience to master getting a PM job - https://www.landpmjob.com/ 5. Product Faculty: Get $550 off their #1 AI PM Certification with code AAKASH550C7 - https://maven.com/product-faculty/ai-product-management-certification?promoCode=AAKASH550C7 --- Key Takeaways: 1. One-prompt vibe coding fails because of context compression - When you give one agent one massive specification, the model silently drops details it considers lower priority. Your color palette, edge cases, and security requirements disappear. Break work into smaller scoped tasks with dedicated agents. 2. The system analyst agent is the most important agent in any AI dev team - It asks clarifying questions one at a time, documents decisions in Confluence, and maps dependencies before code is written. Without it, every agent operates on partial context. 3. Dictation produces 5x more specification detail than typing - Use voice tools like Super Whisper to describe your app requirements. Even imperfect dictation captures more nuance than careful typing. The AI handles the interpretation. 4. Reusable agents encode institutional knowledge - Every painful lesson, API workaround, and MCP quirk gets saved in the agent markdown file. The next project starts from a position of strength rather than from zero. 5. Attach screenshots to every front-end development ticket - Without visual references, coding agents default to generic AI aesthetics. The Figma link or screenshot is what ensures your brand design actually shows up in the code. 6. Build a Spaghetti Agent for code quality - A dedicated code maintainability agent checks naming conventions, circular references, and comment quality after every sprint. It catches structural problems a PM would never spot. 7. The coding phase is the fastest part of building - Specification, documentation, design, ticket creation, and team review take longer than the actual code generation. Do not skip the front-end work. 8. Sprint organization with dependency mapping is essential - Use tags as a workaround for Atlassian MCP limitations. Map dependencies between tickets so agents build features in the right order. Without sprints, agents build on top of code that does not exist yet. --- 👨‍💻 Where to find Gabor Mayer: LinkedIn: https://www.linkedin.com/in/mayergabor/ Maven Course: https://maven.com/gabor/productbuilder X: https://x.com/gabor_pm 👨‍💻 Where to find Aakash: Twitter: https://www.x.com/aakashg0 LinkedIn: https://www.linkedin.com/in/aakashgupta/ Newsletter: https://www.news.aakashg.com #claudecode #aipm --- 🧠 About Product Growth: The world's largest podcast focused solely on product + growth, with over 200K+ listeners. 🔔 Subscribe and turn on notifications to get more videos like this.

Aakash GuptahostGabor Mayerguest

Apr 28, 20262h 15mWatch on YouTube ↗

EPISODE INFO

Released: April 28, 2026
Duration: 2h 15m
Channel: Aakash Gupta
Watch on YouTube: ▶ Open ↗

EPISODE DESCRIPTION

Gabor Mayer is a PM at Google who runs a 21-agent Claude Code development team. In this episode, he walks through a live demo building a production mobile app from zero to TestFlight - Confluence for specs, JIRA for tickets, Figma for design, and Claude Code for development. Full Writeup: https://www.news.aakashg.com/p/how-to-build-a-full-ai-dev-team Transcript: [VERIFY - transcript URL] --- Timestamps: 00:00 AI agents can now run a startup workflow 01:23 Subscribe and AI tools bundle 01:55 Claude Code as your designer, developer, and systems analyst 02:43 Gabor’s 21-agent startup team inside Claude Code 04:57 Inside the system analyst agent 05:52 Live demo: zero to TestFlight 08:42 Prompting Claude to define a good system analyst 10:02 Ads 11:53 Building the system analyst workflow 12:24 Why documentation matters: Confluence, Jira, and MCPs 15:38 Why classic PM skills make you a better AI builder 19:22 The scaffolding that prevents AI spaghetti code 22:23 Setting up project-specific agents in Claude Code 26:26 Dictating the full product spec for the hockey rules app 32:26 Ads 35:36 Why dictation changes the quality of AI specs 47:38 Creating the visual direction in Figma Make 56:00 The idea-to-prompt-to-design-to-app workflow 1:06:21 Claude Code starts building the Figma screens 1:24:06 Frontend epics and Figma-linked tickets appear in Jira 1:48:57 The hockey rules AI app is live 1:53:56 Full recap: Claude, Confluence, Figma, Jira, Simulator, TestFlight 2:03:20 Should PMs get AI PM certificates? 2:08:21 How to create a PM portfolio that helps you land top jobs 2:13:32 How to get started building with AI agents --- 🏆 Thanks to our sponsors:
Maven Custom: Go from PM to AI builder with Cloud Code - https://maven.com/gabor/productbuilder
Amplitude: The market-leader in product analytics - https://amplitude.com/session-replay?utm_campaign=session-replay-launch-2025&utm_source=linkedin&utm_medium=organic-social&utm_content=productgrowthpodcast
Testkube: Leading test orchestration platform - http://testkube.io/
Land PM Job: 12-week experience to master getting a PM job - https://www.landpmjob.com/
Product Faculty: Get $550 off their #1 AI PM Certification with code AAKASH550C7 - https://maven.com/product-faculty/ai-product-management-certification?promoCode=AAKASH550C7
--- Key Takeaways:
1. One-prompt vibe coding fails because of context compression - When you give one agent one massive specification, the model silently drops details it considers lower priority. Your color palette, edge cases, and security requirements disappear. Break work into smaller scoped tasks with dedicated agents.
1. The system analyst agent is the most important agent in any AI dev team - It asks clarifying questions one at a time, documents decisions in Confluence, and maps dependencies before code is written. Without it, every agent operates on partial context.
1. Dictation produces 5x more specification detail than typing - Use voice tools like Super Whisper to describe your app requirements. Even imperfect dictation captures more nuance than careful typing. The AI handles the interpretation.
1. Reusable agents encode institutional knowledge - Every painful lesson, API workaround, and MCP quirk gets saved in the agent markdown file. The next project starts from a position of strength rather than from zero.
1. Attach screenshots to every front-end development ticket - Without visual references, coding agents default to generic AI aesthetics. The Figma link or screenshot is what ensures your brand design actually shows up in the code.
1. Build a Spaghetti Agent for code quality - A dedicated code maintainability agent checks naming conventions, circular references, and comment quality after every sprint. It catches structural problems a PM would never spot.
1. The coding phase is the fastest part of building - Specification, documentation, design, ticket creation, and team review take longer than the actual code generation. Do not skip the front-end work.
1. Sprint organization with dependency mapping is essential - Use tags as a workaround for Atlassian MCP limitations. Map dependencies between tickets so agents build features in the right order. Without sprints, agents build on top of code that does not exist yet. --- 👨‍💻 Where to find Gabor Mayer: LinkedIn: https://www.linkedin.com/in/mayergabor/ Maven Course: https://maven.com/gabor/productbuilder X: https://x.com/gabor_pm 👨‍💻 Where to find Aakash: Twitter: https://www.x.com/aakashg0 LinkedIn: https://www.linkedin.com/in/aakashgupta/ Newsletter: https://www.news.aakashg.com #claudecode #aipm --- 🧠 About Product Growth: The world's largest podcast focused solely on product + growth, with over 200K+ listeners. 🔔 Subscribe and turn on notifications to get more videos like this.

SPEAKERS

Aakash Gupta
host
Host of the Aakash Gupta podcast/channel covering AI, product, and software-building workflows.
Gabor Mayer
guest
Product manager at Google who has been building AI-powered apps using multi-agent Claude Code workflows.

EPISODE SUMMARY

In this episode of Aakash Gupta, featuring Aakash Gupta and Gabor Mayer, He Uses 7 Claude Code Agents to Build Apps with 0 Employees explores how to ship an iOS app using Claude Code agents Gabor shows how he structures Claude Code as a “startup OS” with ~21 specialized agents (system analyst, CTO, designer, test architect, maintainability reviewer, privacy/data council) to mimic a real product team’s division of labor.

RELATED EPISODES