Marc Baselga
An observer or author discussing uneven AI adoption among senior product leaders. The item emphasizes infrastructure and policy as drivers of effective adoption.
Key Highlights
- Marc Baselga emphasizes that effective AI adoption depends more on infrastructure, leadership behavior, and safety policy than on raw participation.
- He argues PMs should have access to agentic coding tools like Claude Code and Cursor, while treating production access as a separate governance issue.
- Baselga warns that token counts and similar usage stats are weak measures of AI success unless tied to business outcomes.
- He highlights that rapid prototyping with AI does not fix poor decision-making cultures driven by status and confidence.
- His observations from 400+ senior product leaders suggest top-performing companies combine executive AI usage with low-friction enablement.
Overview
Marc Baselga appears in the newsletter as a product leadership observer and author focused on how AI is actually being adopted inside product organizations. Across multiple mentions, he consistently argues that successful AI adoption is not mainly about enthusiasm, tool access, or vanity usage metrics. Instead, it depends on whether leaders themselves use AI, whether teams have practical infrastructure that makes adoption easy, and whether clear safety and approval policies reduce friction.For AI Product Managers, Baselga matters because his commentary sits at the intersection of tooling, org design, governance, and operating cadence. He highlights recurring execution gaps: companies measuring token counts instead of outcomes, teams shipping fast with tools like Claude Code while still making status-driven decisions, and organizations limiting access to useful tools without a business case for broader enablement. His advice is especially relevant for PMs trying to move from AI experimentation to durable, measurable operating change.
Key Developments
- 2026-01-11: Marc Baselga outlines three investor-selection filters for first-time founders: diversify angel checks to build a stronger network, pick early investors who create positive signaling for later rounds, and avoid harmful backers through founder backchanneling.
- 2026-01-17: He shares best practices for running Product Customer Advisory Boards, stressing that Product CABs should gather unfiltered customer input rather than function like Sales CABs or roadmap showcases.
- 2026-03-03: Baselga notes that lack of Claude Code access to repositories is becoming a red flag for product leaders evaluating companies, because repo-connected AI tools can answer deep code questions quickly and reduce dependency on long engineering explanations.
- 2026-03-13: He recommends quantifying the business cost of slow AI adoption—such as missed markets, lost deals, and compliance delays—and finding a senior IT or C-suite sponsor to help safely expand access beyond limited defaults like Copilot.
- 2026-03-22: He warns that many teams are measuring AI adoption through proxy metrics like token counts, connector hits, or internal demo rituals rather than true business outcomes.
- 2026-03-26: Baselga shares five recommended reads for product leaders, including Benedict Evans on OpenAI’s moat and Gokul Rajaram on AI-native organizations potentially collapsing traditional boundaries between product, design, and engineering.
- 2026-04-04: He argues PMs should absolutely have agentic coding tools such as Claude Code and Cursor for prototyping, querying codebases, and converting specs into working artifacts, while cautioning that direct production push access is a much harder governance question.
- 2026-04-08: Baselga highlights an Adobe product lead with no coding background who used Claude Code and a folder of markdown files to create an AI chief of staff, illustrating practical no-code or low-code leverage for PMs.
- 2026-04-22: He warns that even though AI tools now let teams prototype in hours and ship to staging rapidly, decision-making often still follows status and confidence rather than evidence, creating expensive errors that are discovered too late.
- 2026-05-11: Drawing on observations from 400+ senior product leaders in Supra, Baselga says AI adoption is highly uneven because many firms optimize for participation instead of outcomes; the strongest performers pair leadership usage with easy infrastructure and explicit safety policies.
Relevance to AI PMs
1. Use outcome metrics, not activity metrics. Baselga repeatedly pushes PMs to measure business impact rather than AI usage proxies. Tactically, that means tying AI initiatives to cycle time, win rate, support deflection, revenue lift, quality, or compliance outcomes instead of reporting token counts or tool logins.2. Design adoption systems, not just tool rollouts. His observations suggest AI uptake improves when leaders model usage, infrastructure is easy to access, and guardrails are clear. For AI PMs, this means building enablement around permissions, approved workflows, repo access, data policies, and examples of good usage—not simply buying licenses.
3. Expand PM leverage with agentic coding safely. Baselga’s stance is practical: PMs should use tools like Claude Code and Cursor to prototype, inspect codebases, and turn specs into artifacts faster. But AI PMs should separate experimentation access from production authority, with staged approvals, review processes, and role-based controls.
Related
- Adobe: Referenced in an example where an Adobe product lead used Claude Code to build an AI chief of staff despite having no coding background.
- Claude Code: One of the tools most closely associated with Baselga’s commentary on PM leverage, codebase access, and rapid prototyping.
- Cursor: Mentioned alongside Claude Code as an agentic coding tool PMs should have access to for practical development work.
- Agentic coding: A core theme in Baselga’s perspective, especially around PM prototyping, code querying, and converting specs into working outputs.
- Benedict Evans: Appears in Baselga’s curated reading list, reflecting his broader interest in strategic AI market analysis.
- Gokul Rajaram: Also featured in Baselga’s recommended reads, particularly on how AI-native firms may reshape product leadership structures.
- AI adoption: The central theme connecting many of Baselga’s mentions, especially his emphasis on uneven adoption and the need for infrastructure and policy.
- Token counts: Used by Baselga as an example of a misleading adoption metric when not tied to outcomes.
- Copilot: Referenced as a baseline enterprise AI tool that may be too restrictive if organizations fail to safely broaden access to more capable workflows.
- Product CABs: Connected to Baselga’s advice on gathering real customer input through well-structured advisory boards.
- Sales CABs: Used as a contrast case to clarify that Product CABs should prioritize learning over showcasing.
- Investor-selection filters: A separate but notable topic Baselga addressed for founders, focused on strategic investor choice.
- Supra: The source context for his observation that AI adoption is uneven among 400+ senior product leaders.
Newsletter Mentions (10)
“Marc Baselga observes that AI adoption is uneven among 400+ senior product leaders in Supra as companies optimize for participation over outcomes; top performers combine leadership AI usage with easy-to-use infrastructure and clear safety policies.”
#6 in Marc Baselga observes that AI adoption is uneven among 400+ senior product leaders in Supra as companies optimize for participation over outcomes; top performers combine leadership AI usage with easy-to-use infrastructure and clear safety policies.
“in Marc Baselga warns that although tools like Claude Code let teams prototype in an afternoon and ship to staging before lunch, decision-making still hinges on status and confidence, leading to costly, late-detected mistakes and higher churn.”
#17 in Marc Baselga warns that although tools like Claude Code let teams prototype in an afternoon and ship to staging before lunch, decision-making still hinges on status and confidence, leading to costly, late-detected mistakes and higher churn.
“Marc Baselga shows how an Adobe product lead with zero coding skills set up Claude Code to turn a folder of markdown files into an AI chief of staff.”
#21 in Marc Baselga shows how an Adobe product lead with zero coding skills set up Claude Code to turn a folder of markdown files into an AI chief of staff.
“#12 in Marc Baselga argues PMs should absolutely have agentic coding tools (e.g., Claude Code, Cursor) to prototype, query the codebase, and turn specs into working artifacts—yet granting them direct push access to production remains a far more complex debate.”
GenAI PM Daily April 04, 2026 GenAI PM Daily 🎧 Listen to this brief 3 min listen Today's top 17 insights for PM Builders, ranked by relevance from X, Blogs, and LinkedIn. Claude subscriptions will no longer cover usage on third-party tools like OpenClaw. #12 in Marc Baselga argues PMs should absolutely have agentic coding tools (e.g., Claude Code, Cursor) to prototype, query the codebase, and turn specs into working artifacts—yet granting them direct push access to production remains a far more complex debate.
“#17 in Marc Baselga shares 5 sharp reads for product leaders this month. Highlights include Benedict Evans’ case that OpenAI lacks a durable moat and Gokul Rajaram’s prediction that AI-native firms will eliminate the traditional CPO role by merging product, design, and engineering.”
#17 in Marc Baselga shares 5 sharp reads for product leaders this month. Highlights include Benedict Evans’ case that OpenAI lacks a durable moat and Gokul Rajaram’s prediction that AI-native firms will eliminate the traditional CPO role by merging product, design, and engineering. #18 in Dharmesh Shah echoes Reid Hoffman’s insight that AI-powered agents open vast new opportunities for software companies, proving software is far from dead.
“#10 in Marc Baselga warns that many product teams are gauging AI adoption through usage stats—token counts, connector hits or even weekly “demo spinner” games—rather than tracking real business outcomes.”
A product measurement insight emphasizes outcome-based AI adoption tracking. #10 in Marc Baselga warns that many product teams are gauging AI adoption through usage stats—token counts, connector hits or even weekly “demo spinner” games—rather than tracking real business outcomes.
“Marc Baselga recommends quantifying the cost of slow AI adoption (missed markets, lost deals, compliance delays) and enlisting a senior IT- or C-suite sponsor to push for safe approval of broader AI tools beyond just Copilot.”
#15 in Marc Baselga recommends quantifying the cost of slow AI adoption (missed markets, lost deals, compliance delays) and enlisting a senior IT- or C-suite sponsor to push for safe approval of broader AI tools beyond just Copilot.
“#21 in Marc Baselga notes product leaders now see lack of Claude Code access to repos as a red flag when choosing a company.”
#21 in Marc Baselga notes product leaders now see lack of Claude Code access to repos as a red flag when choosing a company. Connecting Claude Code lets PMs get instant, structured answers to deep code queries instead of lengthy engineer discussions. #22 in Greg Isenberg urges PMs to rebuild every SaaS tool—Notion, Slack, Stripe, etc.—as agent-native (payments, communication, memory) because the coming machine-to-machine economy will feature billions of software agents as customers.
“Running Effective Customer Advisory Boards: Marc Baselga shared best practices for Product CABs (Customer Advisory Boards). He advises distinguishing Product CABs from Sales CABs—Product CABs exist to gather unfiltered input, not to showcase your roadmap.”
From LinkedIn • Deeper Insights Product Management Insights & Strategies Framework for AI Agent Success: Dharmesh Shah introduced a clear formula—Agent Success = IQ × EQ × CQ—to evaluate AI agents. IQ measures reasoning ability, EQ measures collaboration skills, and CQ (Context Quotient) reflects how well the agent knows your business context. Dharmesh emphasizes that a model’s raw intelligence is useless without context and advises feeding agents with your top rep’s call recordings, NPS comments, renewal notes, and other internal signals to drive real impact. ( Dharmesh Shah ) Running Effective Customer Advisory Boards: Marc Baselga shared best practices for Product CABs (Customer Advisory Boards). He advises distinguishing Product CABs from Sales CABs—Product CABs exist to gather unfiltered input, not to showcase your roadmap. Key tips include requiring members to commit to at least one pilot per year, selecting forward-thinking customers (not just your largest accounts), and using CAB sessions to debate real strategic bets like pricing and new directions. ( Marc Baselga ) AI Tools & Applications Automating Project Memory: Peter Yang offered a simple yet powerful prompt: after a long chat with your AI agent, ask “Update project memory with the takeaways from this chat.” This approach automates the persistence of context—no more manual copy-and-paste—and keeps your projects aligned as they evolve. ( Peter Yang ) AI Industry Developments & News One-Click AWS Databases in Vercel for Agent-Driven Development: Guillermo Rauch announced that Vercel now enables one-click provisioning of AWS databases—RDS, DynamoDB, and Aurora DSQL—directly from the platform. This integration removes manual setup of environment variables, secrets, and network configuration, paving the way for seamless, production-grade agentic coding where AI handles backend infrastructure for you. ( Guillermo Rauch )
“Product Management Insights & Strategies Marc Baselga outlines three investor-selection filters for first-time founders: diversify checks among angels to build a supportive network; choose early backers who create positive signals for later rounds; and avoid detractors by backchanneling with founders of failed ventures—ensuring investors add strategic value beyond capital.”
Read Tal Raviv’s post . Paweł Huryn offers a free YouTube course and an “Ultimate Guide to n8n for PMs” on building AI agents without code. He covers multi-agent workflows, intent management, 1,000+ integrations, best practices, common mistakes, and cost-saving strategies—equipping PMs to prototype and automate complex tasks. Explore the n8n deep dive . Product Management Insights & Strategies Marc Baselga outlines three investor-selection filters for first-time founders: diversify checks among angels to build a supportive network; choose early backers who create positive signals for later rounds; and avoid detractors by backchanneling with founders of failed ventures—ensuring investors add strategic value beyond capital.
Related
An AI coding assistant and agentic development tool used for code generation, debugging, planning, and workflow automation. It appears here as part of a personal OS and also for token usage debugging and plan limits.
Cursor is an AI coding editor used by builders and teams. In this newsletter it is part of the progression from vibe coding prototypes toward a team AI operating model.
An AI development pattern where models act more like autonomous coding agents. The newsletter uses it to describe both NVIDIA Dynamo’s target workload and GPT-5.5/Codex improvements.
Stay updated on Marc Baselga
Get curated AI PM insights delivered daily — covering this and 1,000+ other sources.
Subscribe Free