top of page

Sample AI-native Product Manager Stack, 2026

  • Writer: Harshal
    Harshal
  • Mar 30
  • 4 min read

Updated: May 1

Mapping AI tools to the Product Lifecycle

I enjoy discussing with product peers how AI is changing product management. I also enjoy using AI in a structured way through reusable workflows, prompts, and templates. Here I share how AI helps me across product lifecycle stages, with examples from day-to-day work.

AI has improved my PM leverage most when I map it to the product lifecycle and use explicit guardrails for quality.

AI PM workflow including research, analysis, documents, planning, and launch
AI PM workflow including research, analysis, documents, planning, and launch

Related:

Product Lifecycle Map

Problem Discovery -> PRD -> Prototyping -> Communication

Product lifecycle map
Product lifecycle map

1) Problem Discovery

This stage gives me faster, better context before and after customer conversations.

UX Research

I use AI-enabled user research tools when talking to users or customers. HeyMarvin and Dovetail both have AI capabilities to speed up insight synthesis from interviews and usability studies. I have used Granola, Fathom-video, and NotyAI to handle meeting notes and insights. They record meetings, create summaries, and organize notes.

Data Analysis

I use AI to write SQL queries based on what I want to analyze. For example, I use Cursor (Composer + Claude Sonnet), the BigQuery extension, and BigQuery MCP to inspect schema and draft queries from clear instructions. This setup also checks linting. I can run small queries in Cursor, but I usually copy queries into Metabase or DataStudio.

I maintain a labeled SQL repository so each new analysis gets faster through reusable query patterns.

I also use PostHog, which has a really good AI assistant to understand users' behavior on web pages.

Competitive Research

I use Perplexity Deep Research for competitive research. I use a template to keep analysis consistent.

In one role, I used up to 27 competitor products directly and brought that evidence to engineering discussions. That helped prove feasibility and segment-level demand faster than customer quotes alone.

Market and AI News

I use n8n to keep track of competitive, market, and AI news. For example, I have a workflow to extract value from newsletters and blogs and convert them to a private podcast feed. This saves time and improves learning consistency.

Perplexity and ChatGPT help explain other concepts. I use NotebookLM to understand a topic from many angles, especially complex AI research papers.

Product Manager stack, AI-narratives
Product Manager stack, AI-narratives

2) PRD

This stage improves the quality and speed of written thinking before team review.

Product Requirements Docs and User Stories

I use Notion with Notion AI to write product requirement documents and JTBDs.

I also use Cursor with a directory of organized markdown files when I need tighter context control across multiple documents. This works very well, with a trade-off in readability and shareability.

I use pushback prompts in these workflows so AI challenges assumptions instead of only agreeing. I validate critical claims against primary sources and recent customer evidence before socializing a draft.

Customer Journey Mapping

I use Mermaid diagrams to create customer journey maps. Mermaid is not perfect for CJM depth, but it is fast and reliable for early alignment.

Product Roadmap

I use Notion to track the product roadmap. It is not purpose-built for roadmaps, but the database features and Notion AI make it effective for roadmapping.

3) Prototyping

This stage reduces abstract debate and improves alignment by making ideas tangible early.

I use Lovable, Cursor, and a few more coding agents to prototype products or experiences.

This pattern helped in multiple contexts: I pushed context-engineering changes to production for better generation quality, used model-swap evals to de-risk engineering investment, and built a full webapp mock to support prospect conversations.

a product lifecycle
a product lifecycle

4) Communication

This stage helps me keep teams aligned while reducing operational overhead.

Task Management

I use n8n, Cursor, Notion MCP, and Linear MCP to create and update user stories. I use n8n to maintain a higher-quality database in Notion. My n8n workflows read human-updated rows and trigger database updates.

I have n8n workflows to clean up older tickets or update some status fields in completed tickets.

I use Trello for side projects or homework. I built an integration with Trello community MCP and an n8n workflow that I can trigger from anywhere, including my phone, to create or update tasks. Having an AI assistant is a must-have for project management.

Stakeholder and Customer Communication

I use Loom to tell the user's story to my team, customers, or stakeholders. Loom and Descript both have AI features to help edit videos.

Early Customer Onboarding

Along with colleagues, I integrated an AI assistant with Grafana, which helped analyze user failures and support a white-glove onboarding service. This was most useful for early customers.

Missing Tools and Adoption Criteria

I have not used Gamma AI yet. Documents are usually enough for my current communication style, so presentation-first workflows are a lower priority. I have not used Claude Code yet, but I use coding agents through IDE, web browser, and CLI daily. I have heard Hex is strong, but I have not needed it yet for my current data analysis workflows. I prefer vibe-coded solutions for some tasks, like Opportunity Solution Trees, so I have used less of Figma and Miro AI so far.

I adopt a new tool only when it improves decision quality, reduces cycle time, or removes repeated manual work in my current stack.

Related:


bottom of page