Aakash GuptaThe Claude Code Analytics Workflow Top AI PMs Don’t Want You to Know
CHAPTERS
Why Claude Code + MCP is a “10x” analytics workflow for PMs
Aakash and Frank open by framing the core idea: run your entire product analytics-to-spec workflow inside Claude Code/Cursor by connecting your product context and tools through MCP. They preview the end-to-end arc—chart analysis, reporting automation, feedback synthesis, PRDs, and even shipping prototypes/tickets.
Meet Frank Lee (Amplitude AIPM lead) and what he’s optimizing for
Frank introduces his role at Amplitude working on agents and MCP products. The conversation sets up a practical, PM-focused tutorial: how to “surface product context” into an AI agent so it can reason over your metrics and product artifacts.
Claude Code, Cursor, Skills, MCP—plain-English breakdown
Frank explains what Claude Code is (terminal-based coding agent) and what MCP is (Model Context Protocol for connecting models to external tools/data/actions). He also introduces Skills as reusable prompt/tool bundles that standardize repeated workflows.
Initial setup: build a “product repo” as your context source of truth
Frank demos his setup in Cursor: a dedicated repo with folders per product line and markdown context (roadmaps, specs, vocabulary). This repo becomes the shared substrate that Claude Code/Cursor can reference to brainstorm, analyze, and draft documents consistently.
Creating an Auto-Insights Skill: teaching the agent how to analyze charts
Frank walks through a real Skill definition: metadata (name/description), a structured prompt, heuristics (spikes, seasonality, anomalies), and tool selection via MCP. The Skill replicates hours of manual exploratory slicing by having the agent fetch related charts and form hypotheses.
Context management realities: tool descriptions, compaction, and session resets
Aakash and Frank dig into how much context is “too much,” and what actually consumes the context window (often MCP tool schemas/instructions). They cover practical tactics: starting new sessions/tabs, Claude Code’s /compact, and writing progress to a markdown file before compaction fails.
Ingesting meeting notes without a native MCP: the Granola script workaround
Frank shows how he uses Claude Code to create scripts that pull meeting notes (e.g., from Granola) into his repo by date-based folders. Once notes are local files, the agent can reference entire folders for summaries, action items, and downstream PRD inputs.
Parallel agent orchestration: where Conductor and Git worktrees matter (and when they don’t)
Frank explains Conductor’s value for running many coding agents in parallel without branch conflicts, using Git worktrees. He notes that most PM tasks don’t require heavy parallel orchestration, but it becomes crucial for multi-agent coding work.
The “Top 5” PM analytics use cases (the full loop)
Frank lays out the five repeatable workflows: anomaly investigation, automated weekly reporting, qualitative feedback synthesis, converting insights to PRDs/actions, and finally routing work to Linear or prototyping in code. This becomes the blueprint for the rest of the demos.
Demo 1: Deep chart analysis—investigating a metric spike via Amplitude MCP
Frank demonstrates dropping an Amplitude chart link into Claude Code and triggering an ‘analyze chart’ Skill. The agent parses the URL, queries underlying data, explores properties and related charts, and produces a structured explanation with hypotheses (e.g., feature flags, data quality, power users).
Demo 2: Dashboard reporting automation—TL;DRing a dashboard and scheduling agents
They switch to dashboard-level synthesis: an ‘analyze dashboard’ Skill fetches charts in batches to manage context limits and summarizes key movements. Frank then shows Amplitude’s scheduled dashboard agents that push insights to Slack/email, reducing the need for recurring WBR slide prep.
Demo 3: Customer feedback analysis—unifying Zendesk/Intercom/Salesforce/G2 into one view
Frank demonstrates using an ‘analyze feedback’ Skill over Amplitude’s AI Feedback product to pull recent themes, issues, bugs, and delights. The key value is centralized ingestion plus flexible, queryable analysis (e.g., focus only on praise, competitors, or urgent issues).
Demo 4–5: From insights to PRDs, then to Linear or prototypes (Cursor/Claude Code)
They generate draft PRDs/specs directly into markdown files, then iterate to improve quality (reduce verbosity, prioritize acceptance criteria). Finally, they discuss routing: push tickets to Linear via MCP, message engineers, or even prototype changes in code using Cursor/Claude Code agents.
Common MCP mistakes and the real critiques (context bloat, auth pain, configuration)
Frank outlines two major user errors: expecting MCP to do everything, and connecting too many irrelevant MCP servers/tools. He then addresses broader criticisms—hype, context waste, auth friction, and configuration—arguing the ecosystem is rapidly improving (managed connectors, dynamic tool calling, Skills).
What Amplitude is shipping next: embedded global agent, sub-agents, and Slack-first access
Frank previews Amplitude’s broader agents launch: a global embedded agent across the platform, plus specialized sub-agents (dashboard, session replay, feedback, website optimization). MCP underpins both internal agent capabilities and external workflows in Claude/Cursor/ChatGPT, with strong emphasis on “agents where you work,” especially Slack.
Closing: “Vibe PMing” as the future operating model
Aakash wraps by positioning this as the new default for PM effectiveness: integrate analytics + qual data + spec writing + execution through agents. He encourages viewers to request access (Claude Code, Cursor, GitHub, MCP-enabled tools) and points to follow-up resources and the newsletter walkthrough.
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