Skip to content
Aakash GuptaAakash Gupta

The Claude Code Setup for Non-Technical PMs That Nobody Shows You

Most PMs are still bureaucrats stuck in Jira, Linear, and PowerPoints. The best PMs have stopped waiting on engineering and started shipping code themselves. In this episode, Andre Albuquerque (founder of Builders Camp, Europe's largest product builder school with 4,000+ students) walks through his exact 4-level builder PM stack live - Lovable, Claude Code, Cursor, Vercel, and a multi-agent CLAUDE.md setup that AI-native teams actually run. Full Writeup: https://www.news.aakashg.com/p/claude-code-for-non-technical-pms Transcript: https://www.aakashg.com/albuquerque-podcast/ --- Timestamps: 00:00 - Intro 02:27 - The biggest problem non-technical PMs face today 04:50 - The 4-level builder PM framework 05:28 - Level 1 - Why you start with Lovable 08:04 - Level 2 - The Lovable + Claude Code bridge 10:21 - Ads 12:14 - Live demo: connecting Lovable to Claude Code via GitHub 28:37 - Level 3 - Cursor + Vercel for real production 31:02 - Ads 33:22 - Why Andre prefers Cursor over Claude Code desktop 35:40 - Mental model: Lovable vs Cursor vs Vercel 41:17 - Level 4 - Agents, skills, and CLAUDE.md 42:50 - The CLAUDE.md memory file explained 45:24 - The PM orchestrator agent pattern 53:26 - How AI-native teams spend 50% of their time 01:01:33 - Why 90% of European PMs are still non-technical 01:07:45 - The Monday morning move 01:09:07 - Outro --- 🏆 Thanks to our sponsors: 1. Customer.io: Send smarter messages using your product data - http://customer.io/productgrowth 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. Bolt: Ship AI-powered products 10x faster - https://bolt.new/solutions/product-manager?utm_source=Promoted&utm_medium=email&utm_campaign=aakash-product-growth 4. Ariso: Ariso: Your AI chief of staff for meetings, follow-ups, and coaching - https://ariso.ai/aakash 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. Non-technical PMs are stuck in Jira, Linear, and PowerPoints - Most European PMs are still product owners in disguise, paper-shuffling between strategy and engineering teams. The way out is to actually start building, not to lobby for more autonomy. 2. Start with Lovable on a personal project - Build something for your family, your friends, yourself. The codebase does not need to be pretty. The point is the safety to make mistakes without breaking anything that matters. 3. The Lovable + Claude Code bridge nobody documents - Connect both tools to the same GitHub repo. Write code in Claude Code with all its depth. QA visually in Lovable with its hosted preview. Publish from Lovable's button. The perfect transition layer. 4. Lovable, Cursor, and Vercel are not competitors - Lovable bundles the IDE, the hosting, and the deployment in one product. Vercel exposes the hosting layer so you can run real branches with real preview URLs. Cursor is just an IDE with a generous free tier. 5. Cursor has a free debugging agent - When Claude Code breaks, open a Cursor agent and paste the error. The free agent unsticks you instead of leaving you stuck at step zero. 6. CLAUDE.md is your team's culture - Loaded automatically every session. The first rule should be "for every task, call the PM agent." When you notice yourself fixing the same issue twice, update CLAUDE.md so it never happens again. 7. The PM agent never writes code - The PM orchestrator's only job is to decide which other agent should handle the work. The researcher investigates. The designer proposes. The engineer architects. The implementer writes. 8. Do not copy famous people's skills wholesale - Going on LinkedIn and downloading 100 skills from product celebrities creates more confusion than value. Look at how your real team works. Write each role down as an agent. 9. Fix the agent, not the feature - When something ships wrong, do not patch the output. Identify which agent in the pipeline failed, update its instructions, and run the pipeline again. The next session inherits the fix. 10. The Monday morning move is exactly three steps - Get added as a collaborator on a low-risk repo. Pick the oldest ticket in the backlog. Push a branch and demo by Friday. --- 👨‍💻 Where to find Andre Albuquerque: LinkedIn: https://www.linkedin.com/in/andre-albuquerque/ Builders Camp: https://builderscamp.com Newsletter: https://www.andrealbuquerque.com 👨‍💻 Where to find Aakash: Twitter: https://x.com/aakashgupta LinkedIn: https://www.linkedin.com/in/aagupta/ Newsletter: https://www.news.aakashg.com #BuilderPM #ClaudeCode #AIPM --- 🧠 About Product Growth: The world's largest podcast focused solely on product + growth, with over 200K+ listeners. 🔔 Subscribe and turn on notifications.

Andre AlbuquerqueguestAakash Guptahost
May 18, 20261h 10mWatch on YouTube ↗

CHAPTERS

  1. Why non-technical PMs are becoming “bureaucrats” (and why that’s dangerous now)

    Andre argues many non-technical PMs are trapped in Jira/Linear/decks and can’t directly contribute to shipping, creating dependency on engineering. He contrasts that with AI-native teams where even CEOs and PMs commit code and ship faster with smaller teams.

  2. The 4-level “Builder PM” framework: from safe prototypes to automation

    Andre lays out a four-step progression designed to reduce fear while increasing capability. The journey starts with low-risk prototyping and ends with multi-agent automation and team-level standards.

  3. Level 1 — Start with Lovable to build confidence (personal projects first)

    Lovable is presented as the least intimidating entry point because you see the product as you build and don’t need to understand infra. Andre recommends starting with a personal use case to remove risk and pressure.

  4. Level 2 — The Lovable + Claude Code “bridge” (keep Lovable as QA + hosting)

    Andre describes an ‘accidental’ but powerful workflow: use Claude Code to edit code in a GitHub repo while Lovable remains the visual testing environment and deployment host. This creates a smoother transition from prototype to code-first without immediately learning hosting/deploy.

  5. Live demo — Connecting Lovable to Claude Code via GitHub (step-by-step)

    They build a small app in Lovable, connect it to GitHub, then open that repo in Claude Code. Andre makes changes (theme + header redesign) in Claude Code, merges them, and shows the updates appear back in Lovable for testing and publishing.

  6. A PM-friendly Git primer: branches, pull requests, and why this demo skips reviews

    Aakash provides a simplified explanation of Git fundamentals to reduce intimidation. Andre emphasizes this is fine for personal work, but company workflows will reintroduce review gates and stricter processes.

  7. Level 3 — Moving to production: Cursor/Claude Code + Vercel previews

    Andre explains why he eventually leaves Lovable as infrastructure: to work faster with multiple branches and safer parallel work. Vercel becomes the standard ‘bridge’ from GitHub to users, generating preview deployments per branch for testing before merging to production.

  8. Cursor vs Claude Code desktop: comfort, debugging, and GitHub ergonomics

    Andre prefers Cursor’s UI layout (vertical session navigation) and uses it primarily as a comfortable interface for Claude Code rather than hand-editing files. Aakash adds practical reasons: Cursor’s free agent can help debug setup issues and its GitHub syncing is smooth.

  9. Level 4 — Avoiding “slop”: agents, skills, and the CLAUDE.md memory system

    Andre introduces his quality-and-speed scaling system: a CLAUDE.md that encodes rules/values plus an agents/skills structure that enforces good workflows. The goal is to reduce low-quality, overly complex AI-generated code by improving the process that generates code.

  10. The PM orchestrator agent pattern: one agent routes work to specialists

    Andre explains that his PM agent doesn’t do the work—it orchestrates other agents better suited for research, design, architecture, and implementation. A key mechanism: CLAUDE.md includes a rule to always call the PM agent first, ensuring consistent process.

  11. How AI-native teams actually spend time: build features + improve the machine

    Andre claims elite teams devote a large share of effort to improving their agent/skill infrastructure rather than endlessly tweaking individual outputs. This compounds velocity: better agents lead to better future features across the whole team.

  12. “Only four jobs” and the slop tradeoff: speed needs infra + discovery rigor

    Andre connects the future org structure to early-stage founder archetypes and argues strong infra/security makes non-technical building safe. To avoid shipping slop, teams add friction at the beginning (discovery rigor) and the end (checks), not during execution dependencies.

  13. Europe vs US product culture: why so many European PMs stay non-technical

    Andre argues European orgs over-index on the ‘product owner’ delivery-manager pattern, leaving PMs as translators rather than empowered builders. This structure can disempower squads and reduce participation in discovery and go-to-market.

  14. The Monday morning move: how a PM starts becoming a builder inside a company

    Andre proposes a practical first step: ask an engineer to add you as a collaborator to a low-risk repo or carve out a safe area to experiment. Then pick the oldest backlog item and try building it with Claude Code on a branch to demonstrate value without risking production.

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.

Add to Chrome