Aakash GuptaThe Claude Code Analytics Workflow Top AI PMs Don’t Want You to Know
At a glance
WHAT IT’S REALLY ABOUT
Claude Code + MCP turns analytics into end-to-end PM automation
- Frank Lee demonstrates a “vibe PMing” workflow where Claude Code/Cursor connected via MCP pulls product context and analytics data to answer questions and generate deliverables end-to-end.
- The setup centers on organizing durable product context (plans, specs, templates, meeting notes) in a GitHub-backed repo that Claude Code and Cursor can reference and update.
- Custom “Skills” (structured prompts + tool permissions) operationalize repeatable tasks like chart anomaly analysis, dashboard summaries, and feedback synthesis with consistent output formats.
- The workflow expands from quantitative analysis (charts/dashboards) to qualitative synthesis (Zendesk/Slack/surveys) and then into execution by drafting PRDs and pushing tickets or prototypes into Linear/code.
- They discuss common MCP pitfalls (too many irrelevant tools, wrong expectations) and rebut criticisms by highlighting tool optimization, improving auth/managed connectors, and dynamic tool calling to reduce context waste.
IDEAS WORTH REMEMBERING
5 ideasTreat MCP as the data/action bridge, not the whole workflow.
MCP primarily lets models interact with external tools and data; the workflow power comes from layering Skills, good prompts, and curated toolsets on top of MCP connections.
Build a “product repo” as your persistent context layer.
Store roadmap notes, initiative folders, PRD templates, and terminology in markdown inside a GitHub repo so agents can reliably reference and generate consistent outputs across sessions and devices.
Codify recurring PM tasks as Skills with heuristics and output formats.
Lee’s chart/dashboard Skills specify what patterns to look for (spikes, seasonality, anomalies), how to query (e.g., charts three-at-a-time), and a standard narrative structure for business-ready summaries.
Automate weekly reporting by scheduling dashboard agents into where teams work.
Instead of building WBR slides manually, schedule agents to synthesize dashboards and push insights into Slack/email so meetings focus on decisions and solutions rather than reporting.
Connect quant changes to qual evidence in the same agent run.
After dashboard/chart analysis, the agent can pull related feedback, release notes/annotations, experiments, or session replay signals to form hypotheses about why metrics moved.
WORDS WORTH SAVING
5 quotes“The most powerful thing is managing my product process in Claude Code and Cursor using a bunch of MCPs.”
— Frank Lee
“MCP… is the easiest way to connect your AI models with any external tools, action, and data.”
— Frank Lee
“At Amazon, I used to spend all of my Sundays… Now… Monday morning… [dashboards are] automatically synthesized.”
— Frank Lee
“They’re… correct. They’re too verbose. So I can go back to my prompt and say, ‘Hey, dramatically cut down the words.’”
— Frank Lee
“Sometimes people think that MCPs can do everything… [but] MCPs are easy ways for your AI to interact with external systems.”
— Frank Lee
High quality AI-generated summary created from speaker-labeled transcript.
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