Marc Baselga
A source cited for studying PM interviews across eight companies. He is mentioned in relation to an Anthropic culture interview and a Supra Insider episode.
Key Highlights
- Marc Baselga is cited as a curator of practical AI product insights spanning adoption, tooling, governance, and pricing.
- He consistently argues that AI teams should measure business outcomes rather than token counts or superficial usage metrics.
- His commentary supports giving PMs access to agentic coding tools like Claude Code and Cursor with clear governance boundaries.
- He surfaced pricing research showing enterprise buyers value predictable total AI cost more than the absolute lowest price.
- His mentions frequently connect organizational behavior, infrastructure readiness, and safety policy to successful AI adoption.
Marc Baselga
Overview
Marc Baselga appears in the newsletter as a curator and synthesizer of practical AI product insights, especially around adoption, agentic workflows, tooling access, organizational change, and pricing. Rather than being cited for a single product or company role, he is relevant because he consistently surfaces operational lessons that AI product managers can act on immediately—from how PMs should use agentic coding tools, to how teams should measure AI success, to how buyers think about pricing.For AI Product Managers, Baselga matters as a signal amplifier for emerging best practices. His mentions connect frontline product work with broader strategic questions: how to equip PMs with tools like Claude Code and Cursor, how to avoid vanity adoption metrics such as token counts, how to drive safe enterprise rollout beyond narrow copilots, and how to design AI pricing around predictability rather than headline cheapness. In that sense, he functions as a useful interpreter of what high-performing AI product organizations are learning in real time.
Key Developments
- 2026-03-13 — Recommended 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 approved AI tooling beyond just Copilot.
- 2026-03-22 — Warned that many teams measure AI adoption with usage proxies like token counts, connector hits, or demo activity instead of tracking real business outcomes.
- 2026-03-26 — Shared a set of readings for product leaders, including Benedict Evans’ argument that OpenAI lacks a durable moat and Gokul Rajaram’s view that AI-native companies may collapse traditional product, design, and engineering boundaries.
- 2026-04-04 — Argued that PMs should have access to agentic coding tools such as Claude Code and Cursor for prototyping, codebase queries, and turning specs into artifacts, while noting that direct production access is a separate governance question.
- 2026-04-08 — Highlighted how an Adobe product lead with no coding background used Claude Code to convert a markdown folder into an “AI chief of staff,” illustrating practical non-engineer leverage from agentic tooling.
- 2026-04-22 — Warned that even as tools accelerate prototyping and shipping, organizational decision-making still depends on status and confidence, which can delay detection of mistakes and increase churn.
- 2026-05-11 — Observed uneven AI adoption across 400+ senior product leaders in Supra, noting that strong performers pair leadership usage with easy infrastructure and clear safety policies rather than optimizing only for participation.
- 2026-05-13 — Argued that companies often overlook their internal AI “factory”—the agent-driven workflows built with Claude Code, Cursor, MCPs, and copilots—and instead overfocus on tool adoption or token usage.
- 2026-06-29 — Highlighted Fiona Fung’s “latent demand” insight from Anthropic’s Claude Code and Cowork teams, pointing to hidden user demand that emerges once strong AI workflows become available.
- 2026-08-10 — Recapped Marcos Rivera’s Supra session findings that software buyers prioritize predictable total AI cost over lowest price; Pricing I/O survey data showed 68% ranked predictability among their top three priorities.
Relevance to AI PMs
1. Measure outcomes, not AI theater. Baselga repeatedly emphasizes that token counts, usage stats, and participation metrics are weak proxies for success. AI PMs should define business outcome measures upfront—faster cycle time, conversion lift, support deflection, win rate, or reduced compliance delay—and use those to evaluate AI initiatives.2. Equip PMs with agentic tools, but separate enablement from governance. His commentary suggests PMs gain meaningful leverage from tools like Claude Code and Cursor for prototyping, requirements translation, and codebase understanding. Tactically, AI PMs should push for sandboxed access, documented workflows, and review guardrails rather than treating tool access and production permissions as the same decision.
3. Design pricing for predictability. Baselga’s pricing recap is highly actionable for AI PMs shipping paid AI features. Product teams should present typical and heavy-usage cost scenarios, make bill escalators legible, and clarify what happens when usage thresholds are crossed so enterprise buyers can forecast spend with confidence.
Related
- Adobe — Connected through the example of an Adobe product lead using Claude Code as an “AI chief of staff,” showing non-technical PM leverage.
- Claude Code / Cursor / agentic-coding — Central to Baselga’s commentary on PM enablement, rapid prototyping, and internal AI workflow creation.
- MCPs and copilots — Referenced as part of the internal AI “factory” that companies often fail to measure properly.
- AI adoption / token counts / latent demand — Recurring themes in his insights: adoption should be measured by outcomes, not raw usage, while unmet demand may become visible only after strong tooling is introduced.
- Supra — A recurring context for observations on senior product leaders, adoption patterns, and pricing discussions.
- Marcos Rivera / Pricing I/O — Linked through the August 2026 pricing findings on enterprise buyer preferences for predictable total cost.
- Fiona Fung — Related through the June 2026 note on latent demand in Anthropic’s Claude Code and Cowork teams.
- Benedict Evans / Gokul Rajaram — Connected via Baselga’s curated reads on AI moats and changing product leadership structures.
Newsletter Mentions (14)
“in Marc Baselga says he and Ben Erez studied PM interviews across eight companies, highlighting Anthropic’s culture interview for every candidate, which reportedly asks 10 to 15 questions in about 45 minutes to assess decision-making and alignment with company values.”
in Marc Baselga says he and Ben Erez studied PM interviews across eight companies, highlighting Anthropic’s culture interview for every candidate, which reportedly asks 10 to 15 questions in about 45 minutes to assess decision-making and alignment with company values. He also says a Supra Insider episode examining the interview was released.
“#5 in Marc Baselga recapped findings shared by Marcos Rivera in a recent Supra session: Pricing I/O surveyed 296 software buyers, and 68% ranked predictable total cost among their top three AI pricing priorities, while lowest price ranked last.”
#5 in Marc Baselga recapped findings shared by Marcos Rivera in a recent Supra session: Pricing I/O surveyed 296 software buyers, and 68% ranked predictable total cost among their top three AI pricing priorities, while lowest price ranked last. AI product builders should show typical and heavier-adoption costs, bill-increasing factors, and the consequences of crossing limits before sending a quote.
“#10 in Marc Baselga highlights Fiona Fung’s “latent demand” insight from Anthropic’s Claude Code and Cowork teams.”
A short item summarizing Marc Baselga's note about latent demand in Anthropic tools.
“#14 in Marc Baselga says companies often ignore their internal AI “factory”—the agent-driven workflows from Claude Code, Cursor, MCPs and copilots—and instead measure token usage or tool adoption.”
#14 in Marc Baselga says companies often ignore their internal AI “factory”—the agent-driven workflows from Claude Code, Cursor, MCPs and copilots—and instead measure token usage or tool adoption.
“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.
Related
An AI coding assistant environment used for running evaluation skills and agentic workflows. In this issue it is mentioned as a runtime for ai-evals-course material and as an agent in an OpenRouter-like system.
An AI company best known for Claude. It is referenced implicitly through Claude’s memory and Cowork features.
An AI coding tool referenced as providing data used to evaluate Grok 4.6. It is also named later as a target environment for running AI eval skills.
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.
A person mentioned alongside Marc Baselga in a study of PM interviews across eight companies. He is part of the context around Anthropic’s hiring interview process.
A technology analyst known for strategic takes on the AI industry and distribution dynamics. The newsletter cites him in a deep-dive discussion with Lenny Rachitsky about AI’s future.
Stay updated on Marc Baselga
Get curated AI PM insights delivered daily — covering this and 1,000+ other sources.
Subscribe Free