The AI-Native PM Operating System [Live Demo]

Mike Bal (Head of Product at David's Bridal) shows his complete AI native PM operating system. MCP integrations explained, live demos, and how to stop drowning in 20 different tools. Full Writeup: https://www.news.aakashg.com/p/mike-bal-podcast Transcript: https://www.aakashg.com/the-ai-native-pm-operating-system-how-to-connect-all-your-tools/ --- Timestamps: 0:00 - Intro 1:44 - What Makes an AI Native PM 2:43 - Operating System vs Tool Stack 4:52 - Cursor and MCP Demo 12:14 - Connecting Tools Through MCP 15:23 - Design with Figma Make 20:14 - Google AI Studio 24:01 - Confluence and Figma Integration 30:51 - Research with Manus 37:11 - Manus vs Claude Research 41:47 - Email and Communications 47:19 - Licenses and IT 55:42 - PM Lifecycle and Mistakes 1:00:23 - Outro --- 🏆 Thanks to our sponsor: Linear: Plan and build products like the best - https://linear.app/partners/aakash --- Key Takeaways: 1. Operating systems beat tool stacks - Stop logging into 20 different UIs. Build one central interface through Cursor and Claude Desktop that connects to everything. The composable mindset adapts to your needs. 2. MCP changes PM workflows forever - Model Context Protocol lets you connect JIRA, Figma, GitHub, Notion, Confluence through natural language. Check ticket status without opening JIRA. Compare designs without manual cross-reference. 3. Design validation takes 30 seconds now - "Find my Confluence doc about Feature X, load this Figma design, compare them and tell me what I missed." Used to take 1-2 hours of manual comparison work. 4. Manus dominates heavy research - Gives you multiple file outputs: sample CSVs, combined datasets, data sources report, quick start guide, markdown summary. All traceable back to sources. ChatGPT just gives responses. 5. Research must stay external until vetted - The "conspiracy theorist LLM" problem is real. If you automatically feed everything into your system, AI anchors to wrong information. Vet research separately, then bring validated context in. 6. PMs can build what required engineers - Mike built a colorization app for e-commerce in one morning. Migrated content to Sanity CMS in a few hours. All from natural language prompts in Cursor. 7. Context switching kills productivity - Every time you open a new tab, you lose flow state. The operating system keeps you in one interface. The AI handles the context switching for you. 8. Corporate IT restrictions become irrelevant - You already have Cursor or Claude Desktop. You already use JIRA, Figma, GitHub. Connect them through a better interface. No new tool approvals needed. 9. Analytics workflows save massive time - Export Clarity data, upload to Cursor, prompt "analyze drop-offs and create visualizations." Takes 10 minutes vs hours of manual Excel work. 10. AI native PMs think in prompts - "What do I need to do? What are the steps? What tools will help?" Treat AI as an extension of yourself, not a separate tool to learn. --- 👨‍💻 Where to find Mike Bal: LinkedIn: https://www.linkedin.com/in/mikebal/ YouTube: @thatmikebal Website: https://mikebal.com/ 👨‍💻 Where to find Aakash: Twitter: https://www.x.com/aakashg0 LinkedIn: https://www.linkedin.com/in/aagupta/ Newsletter: https://www.news.aakashg.com #aipm #cursor --- 🧠 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 GuptahostMike Balguest

Feb 3, 20261h 1mWatch on YouTube ↗

EPISODE INFO

Released: February 3, 2026
Duration: 1h 1m
Channel: Aakash Gupta
Watch on YouTube: ▶ Open ↗

EPISODE DESCRIPTION

Mike Bal (Head of Product at David's Bridal) shows his complete AI native PM operating system. MCP integrations explained, live demos, and how to stop drowning in 20 different tools. Full Writeup: https://www.news.aakashg.com/p/mike-bal-podcast Transcript: https://www.aakashg.com/the-ai-native-pm-operating-system-how-to-connect-all-your-tools/ --- Timestamps: 0:00 - Intro 1:44 - What Makes an AI Native PM 2:43 - Operating System vs Tool Stack 4:52 - Cursor and MCP Demo 12:14 - Connecting Tools Through MCP 15:23 - Design with Figma Make 20:14 - Google AI Studio 24:01 - Confluence and Figma Integration 30:51 - Research with Manus 37:11 - Manus vs Claude Research 41:47 - Email and Communications 47:19 - Licenses and IT 55:42 - PM Lifecycle and Mistakes 1:00:23 - Outro --- 🏆 Thanks to our sponsor: Linear: Plan and build products like the best - https://linear.app/partners/aakash --- Key Takeaways:
1. Operating systems beat tool stacks - Stop logging into 20 different UIs. Build one central interface through Cursor and Claude Desktop that connects to everything. The composable mindset adapts to your needs.
1. MCP changes PM workflows forever - Model Context Protocol lets you connect JIRA, Figma, GitHub, Notion, Confluence through natural language. Check ticket status without opening JIRA. Compare designs without manual cross-reference.
1. Design validation takes 30 seconds now - "Find my Confluence doc about Feature X, load this Figma design, compare them and tell me what I missed." Used to take 1-2 hours of manual comparison work.
1. Manus dominates heavy research - Gives you multiple file outputs: sample CSVs, combined datasets, data sources report, quick start guide, markdown summary. All traceable back to sources. ChatGPT just gives responses.
1. Research must stay external until vetted - The "conspiracy theorist LLM" problem is real. If you automatically feed everything into your system, AI anchors to wrong information. Vet research separately, then bring validated context in.
1. PMs can build what required engineers - Mike built a colorization app for e-commerce in one morning. Migrated content to Sanity CMS in a few hours. All from natural language prompts in Cursor.
1. Context switching kills productivity - Every time you open a new tab, you lose flow state. The operating system keeps you in one interface. The AI handles the context switching for you.
1. Corporate IT restrictions become irrelevant - You already have Cursor or Claude Desktop. You already use JIRA, Figma, GitHub. Connect them through a better interface. No new tool approvals needed.
1. Analytics workflows save massive time - Export Clarity data, upload to Cursor, prompt "analyze drop-offs and create visualizations." Takes 10 minutes vs hours of manual Excel work.
1. AI native PMs think in prompts - "What do I need to do? What are the steps? What tools will help?" Treat AI as an extension of yourself, not a separate tool to learn. --- 👨‍💻 Where to find Mike Bal: LinkedIn: https://www.linkedin.com/in/mikebal/ YouTube: @thatmikebal Website: https://mikebal.com/ 👨‍💻 Where to find Aakash: Twitter: https://www.x.com/aakashg0 LinkedIn: https://www.linkedin.com/in/aagupta/ Newsletter: https://www.news.aakashg.com #aipm #cursor --- 🧠 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
Product leader and creator/host of the Aakash Gupta channel, interviewing guests about product management and AI workflows.
Mike Bal
guest
Product leader (introduced as leading product at David’s Bridal) focused on AI-native PM workflows and tooling demos.

EPISODE SUMMARY

In this episode of Aakash Gupta, featuring Aakash Gupta and Mike Bal, The AI-Native PM Operating System [Live Demo] explores building an AI-native PM OS with MCP-connected tools and workflows AI-native PMs “think in prompts,” translating outcomes into steps and selecting the best AI+tool combination to execute them.

RELATED EPISODES