Marc Baselga

Overview

Marc Baselga appears in the newsletter ecosystem as a recurring commentator on practical AI adoption, agentic tooling, and the operating changes AI Product Managers need to make inside real organizations. Across the cited mentions, he is less presented as a builder of a single product and more as an interpreter of what tools like Claude Code, Cursor, MCPs, and copilots mean for product teams, internal workflows, and company decision-making.

For AI Product Managers, Baselga matters because his commentary repeatedly shifts attention from surface-level AI metrics to operational reality: whether teams can prototype faster, access code and context safely, measure outcomes instead of token counts, and remove organizational blockers to adoption. He is also specifically cited for surfacing Fiona Fung’s “latent demand” insight from Anthropic’s Claude Code and Cowork teams, making him a useful signal source for PMs trying to understand second-order product lessons from emerging AI tools.

Key Developments

• 2026-03-03: Marc Baselga notes that product leaders increasingly see lack of Claude Code access to repositories as a red flag when evaluating employers, arguing that repo-connected AI tools give PMs faster, more structured answers than long engineering back-and-forth.
• 2026-03-13: He recommends quantifying the cost of slow AI adoption—such as missed markets, lost deals, and compliance delays—and finding a senior IT or C-suite sponsor to safely expand tool access beyond default options like Copilot.
• 2026-03-22: He warns that many teams measure AI adoption using token counts, connector activity, or gamified usage metrics instead of business outcomes, pushing for outcome-based evaluation.
• 2026-03-26: He shares reading recommendations for product leaders, including Benedict Evans on OpenAI’s moat and Gokul Rajaram on AI-native firms potentially collapsing traditional product, design, and engineering boundaries.
• 2026-04-04: He argues PMs should have agentic coding tools such as Claude Code and Cursor for prototyping, codebase querying, and converting specs into artifacts, while noting that direct production access is a separate governance question.
• 2026-04-08: He highlights a case where an Adobe product lead with no coding background used Claude Code to turn a markdown folder into an “AI chief of staff,” illustrating practical non-engineer leverage.
• 2026-04-22: He warns that even if tools compress prototype-to-staging cycles dramatically, organizational decisions still depend on status and confidence, which can create costly mistakes and churn if judgment does not improve alongside speed.
• 2026-05-11: He observes uneven AI adoption across 400+ senior product leaders in Supra, arguing that strong adoption comes from leadership usage, easy infrastructure, and clear safety policies rather than participation theater.
• 2026-05-13: He says companies often ignore their internal AI “factory”—the workflow layer created by Claude Code, Cursor, MCPs, and copilots—and over-focus on tool adoption or token usage.
• 2026-06-29: He is cited for highlighting Fiona Fung’s “latent demand” insight from Anthropic’s Claude Code and Cowork teams, emphasizing that strong AI products can reveal needs users could not easily articulate beforehand.

Relevance to AI PMs

1. Adoption should be measured by outcomes, not activity. Baselga consistently argues against using token counts or raw usage as success metrics. AI PMs can apply this by tying AI rollouts to cycle time, conversion, support deflection, quality, revenue impact, or decision throughput.

2. PM leverage expands with agentic coding access. His examples suggest PMs should use tools like Claude Code and Cursor to prototype, inspect codebases, and turn specifications into testable artifacts without waiting on full engineering cycles. Tactically, this can shorten discovery, improve handoffs, and sharpen product judgment.

3. Org design and governance matter as much as tools. Baselga repeatedly points to executive sponsorship, safe approval paths, infrastructure, and policy clarity as the real determinants of AI adoption. For AI PMs, this means building rollout plans that include security, IT, and leadership alignment—not just prompt libraries or training sessions.

Related

• Claude Code: The most frequent anchor in Baselga’s mentions; central to his observations about PM leverage, repo access, prototyping speed, and internal workflows.
• Cursor: Often paired with Claude Code as an agentic coding tool PMs should use for prototyping and codebase interaction.
• Agentic coding: A core theme in his commentary, especially around PM autonomy and faster artifact creation.
• MCPs: Referenced as part of the internal AI workflow stack companies under-measure when they focus only on usage statistics.
• AI adoption: One of his main topics, especially the gap between participation metrics and real organizational outcomes.
• Token counts: Used in his commentary as an example of a misleading proxy metric for AI success.
• Copilot: Mentioned as a default enterprise tool that may be insufficient if organizations block broader AI capabilities.
• Adobe: Featured in a practical example of a non-technical product lead using Claude Code effectively.
• Supra: The context for his observations on uneven AI adoption among senior product leaders.
• Fiona Fung: Baselga is explicitly cited for surfacing her “latent demand” insight.
• Latent demand: A key product concept linked to his June 2026 mention, relevant for PMs evaluating AI-native behavior and unmet user needs.
• Benedict Evans and Gokul Rajaram: Included in Baselga’s shared reading list, reflecting his interest in strategic shifts to product org structure and AI competition.
• Product CABs, Sales CABs, investor-selection filters: Related organizational and decision-making themes that connect to his broader focus on how companies evaluate AI opportunities and readiness.