🍁 Canada's AI PM Resource Hub

The home for
AI Product Management
in Canada

Whether you're breaking into AI PM or using AI to level up as a PM — you're in the right place.

What brings you here today?

🧭
AI PM Career Guide
I want to break into AI Product Management

You're a PM, aspiring PM, or career-switcher who wants to understand AI PM roles, build the right skills, and land a job in Canada's AI product market.

  • Explore 6 AI PM career tracks
  • Browse curated courses & free resources
  • Get a 6-month roadmap to your first AI PM role
  • See which Canadian companies are hiring
Explore Career Guide →
⚡
PM as Builder
I want to use AI to become a better PM

You're already a PM — AI PM or not — and you want to prototype faster, ship smarter, and stop being the bottleneck. This is your toolkit.

  • Build working prototypes without writing code
  • Set up a PM Knowledge Bot your whole team can use
  • Convert prototypes into BDD user stories instantly
  • Ship a launch support preset before go-live
Explore PM as Builder →

Not sure? Start with the Career Guide or jump into Builder tools

🍁 Canada's AI PM Resource Hub

Break into
AI Product Management

Career tracks, core skills, the best courses, and free resources — everything you need to land an AI PM role in Canada.

🤖 Generative AI PM 🔬 ML Product Manager 🛠 AI Platform PM 📊 Data Product Manager ⚙️ AI Infrastructure PM 🧭 AI Strategy Lead

The Basics

What is AI Product Management?

AI Product Management is the discipline of defining, building, and launching AI-powered products. It blends classic product thinking — user research, prioritisation, roadmapping, stakeholder management — with a working understanding of machine learning, large language models, and responsible AI.

Where a traditional PM translates user needs into features, an AI PM must also navigate the probabilistic nature of AI outputs, understand model trade-offs, design evaluation frameworks, and make confident decisions about when AI is the right solution.

As AI shifts from a feature into a product category of its own, companies are hiring PMs who can bridge the gap between engineering teams and business stakeholders who need reliable results.

AI PM vs. traditional PM: The core job is the same — ship things users love. The difference is understanding a new kind of technical uncertainty, defining success differently (evals, not just metrics), and managing user trust in ways deterministic software doesn't require.

$245KAvg. AI PM salary (US, 2026)
$145KAvg. AI PM salary (Canada, CAD)
929Open AI PM roles globally (LinkedIn)
2×Salary premium vs. traditional PM

Sources: Product Compass, Aakash Gupta (Product Growth), LinkedIn — April 2026.

🍁 Made in Canada

Canada's AI PM landscape

Canada punches above its weight in AI. The country is home to three globally recognised AI research clusters, a world-class ML talent pipeline, and a growing number of AI-native companies hiring product talent.

🍁 Toronto / GTA
Canada's largest AI PM market. Dense cluster of fintech, health tech, and enterprise SaaS companies with active AI product teams. Home to Vector Institute and proximity to Waterloo's ML talent pipeline.
ShopifyRBCTD BankCohereLayer6AdaBenevity
🍁 Montreal
Deep academic AI roots (Mila, McGill, Université de Montréal). Strong in AI research, gaming AI, and health AI. Bilingual market — French is an asset.
UbisoftElement AI alumniServiceNowNuance
🍁 Vancouver
Growing hub for AI infrastructure and developer tools companies. Strong remote-first culture — many global AI companies hire Canadian PMs from here.
HootsuiteFinger FoodBBTVClio

⚖️ AIDA — Canada's AI Act

The Artificial Intelligence and Data Act (AIDA) is Canada's proposed federal AI regulation, part of Bill C-27. It would require companies to assess and mitigate risks from "high-impact" AI systems. As an AI PM in Canada, regulatory literacy around AIDA is increasingly expected — especially in fintech, health tech, and any consumer-facing AI.

🏛️ Canada's AI research edge

Vector Institute — Toronto's applied AI research hub, partnered with 40+ companies actively hiring AI talent
Mila — Montreal's world-renowned deep learning institute, founded by Yoshua Bengio (Turing Award)
Amii — Edmonton's AI institute, strong in reinforcement learning and industrial AI applications
Canadian companies actively hiring AI PMs
Shopify· Cohere· RBC· TD Bank· Layer6 AI· Ada· Faire· Benevity· Clio· Hootsuite· Ubisoft· ServiceNow Canada· Wattpad· Lightspeed· Veeva Systems· AppDirect· FreshBooks· Top Hat· Shopify· Cohere· RBC· TD Bank· Layer6 AI· Ada· Faire· Benevity· Clio· Hootsuite· Ubisoft· ServiceNow Canada· Wattpad· Lightspeed· Veeva Systems· AppDirect· FreshBooks· Top Hat·

Career Tracks

Types of AI PM roles

AI PM isn't one job — it's a family of specialisations. Knowing which track fits your background is the most important first decision.

🤖

Generative AI PM

Owns products built on LLMs — copilots, AI assistants, content tools. Requires deep understanding of prompt engineering, model evals, and UX for probabilistic outputs.

Highest demand in 2026
Common path: Traditional PM who ships one LLM feature → becomes the team's AI PM
🔬

ML Product Manager

Works directly with ML engineers on model development — defining datasets, success metrics, and evaluation criteria. More technical; often requires understanding training pipelines.

Strong in big tech & infra
Common path: Data analyst / data scientist → transitions into product
🛠

AI Platform PM

Builds internal tools and infrastructure that other product teams use to ship AI features. Customers are internal developers and ML engineers. Requires strong technical depth.

Scales with team size
Common path: Software engineer or TPM → moves into internal platform product
📊

Data Product Manager

Owns the data assets that power AI products — pipelines, feature stores, labelling workflows, and data quality. Critical at companies where data is the core competitive advantage.

Underrated entry point
Common path: Data engineer or analytics PM → specialises in data as product
🧭

AI Strategy Lead

Senior role focused on how AI fits into overall product and company strategy. Defines the AI roadmap, manages AI risk, coordinates across teams. More about judgment than execution.

Senior / 7+ years
Common path: Experienced GPM or Director → takes on AI portfolio ownership
⚖️

Responsible AI PM

Focuses on safety, fairness, transparency, and regulatory compliance. Growing fast as regulation catches up — especially relevant in Canada with AIDA on the horizon.

Emerging specialisation
Common path: Policy, ethics research, or senior PM with compliance background

What to Learn

Skills that get you hired

Two categories: technical foundations to earn credibility with engineering, and the product craft that remains the core of the job.

Technical Foundations
LLM & Generative AI fundamentals
Transformers, context windows, temperature, fine-tuning vs. RAG, prompt engineering — conceptual fluency, not coding.
AI evals & model evaluation
Defining success for AI outputs, building golden datasets, setting ship/no-ship thresholds. Growing fast as a distinct skill.
RAG & agentic systems
Retrieval-augmented generation and multi-step agent architectures — critical knowledge for 2026 product roles.
Data literacy & ML pipelines
Reading model cards, understanding training data, and the difference between offline and online metrics.
Responsible AI & governance
Bias, fairness, transparency, and regulatory literacy — especially relevant in Canada under AIDA.
Product Craft
AI product strategy & roadmapping
Deciding when to build vs. buy AI, sequencing investments, and defining what "done" means for a model-powered feature.
User research for AI products
Understanding how users interpret AI outputs, designing for uncertainty, and building trust through transparent AI UX.
Cross-functional leadership
Working effectively with ML engineers, data scientists, and safety researchers — translating between technical and business language.
Metrics & experimentation for AI
A/B testing AI features, understanding the limits of standard metrics for probabilistic systems, setting up post-launch monitoring.
Stakeholder communication
Explaining AI risk, capability, and uncertainty to executives and legal teams without overselling or underselling.

Learn

Best AI PM courses in 2026

Curated and reviewed — free options, structured certifications, and practitioner-led bootcamps.

Free to audit
AI Product Management Specialization
Duke University · Coursera

4-course specialization covering ML fundamentals, data strategy, and building AI products end-to-end. The most structured free-to-audit option available.

⏱ Self-paced🎓 4 courses👶 Beginner–mid
View on Coursera ↗
Cohort · Paid
AI Product Management Certification
Maven · Rohan Varma & Henry Shi (Anthropic)

Hands-on — you ship a real AI product as your capstone with an assigned engineer. Henry Shi is technical staff at Anthropic. Best for career-switchers wanting real depth.

⏱ Cohort-based🛠 Capstone📈 Mid–senior
View on Maven ↗
Certification
AI Product Management Program
Pragmatic Institute

Well-regarded in enterprise environments. Combines Pragmatic PM frameworks with a practical AI track. Recognised by mid-to-large Canadian employers.

⏱ Flexible🏢 Enterprise focus📈 Mid–senior
View at Pragmatic ↗
Cohort · Paid
AI Product Academy
Dr. Marily Nika · Gen AI PM Lead, Google

Led by one of the highest-profile AI PM educators globally. Strong on AI strategy, executive communication, and translating ML capability into product decisions.

⏱ Cohort-based📍 Harvard Fellow
View on Maven ↗
Membership
AI/ML Product Management
Reforge

The gold standard for experienced PMs. Dense, practitioner-led, peer-cohort discussion. Built for people already shipping products. Not for beginners.

⏱ Self-paced + cohort🔒 Membership req.📈 Senior
View at Reforge ↗
Self-paced
AI Product Manager Nanodegree
Udacity (part of Accenture)

Structured 18-hour nanodegree covering AI product lifecycle from concept to launch, including GenAI strategy and LLM product design. Updated August 2026.

⏱ ~18 hours🎓 Certificate👶 Intermediate
View at Udacity ↗

🔗 Some links above are affiliate links — we earn a small commission if you enrol, at no extra cost to you. We only list courses we've reviewed and believe deliver genuine value.

Free Learning

YouTube channels worth your time

Ranked by skill per hour — channels that actually teach you something, not just narrate AI headlines.

▶
Andrej Karpathy
The single best free AI education available. "Neural Networks: Zero to Hero" and "Intro to Large Language Models" are essential for any AI PM wanting real depth.
🎯 Best for: LLM fundamentals from first principles
▶
DeepLearning.AI
Andrew Ng's channel. Free short courses on LLMs, RAG, agentic AI, and prompt engineering — concise and taught by frontier practitioners.
🎯 Best for: Structured AI courses · 676K subscribers
▶
AI Explained
Fewer videos, longer format, deeper analysis. Counters hype by rigorously examining AI papers and claims. Best for genuine AI literacy.
🎯 Best for: Critical thinking about AI capability
▶
Lenny's Podcast
The go-to for product practitioners. Recurring conversations with AI builders, founders, and PMs shipping real AI products.
🎯 Best for: Product + AI strategy thinking
▶
Matthew Berman
Frequent model and product analysis — 621K subscribers. Best for staying current on new model releases and LLM benchmarks week to week.
🎯 Best for: Staying current on model developments
▶
Skill Leap AI
Structured walkthroughs of popular AI products. Useful for understanding the UX of AI tools your users already use — 332K subscribers.
🎯 Best for: Complete AI product tutorials
▶
AI Engineer (Conference Talks)
Production talks from the AI Engineer Summit — 260K+ subscribers, 10M+ views. This is where you learn what real teams are building and how.
🎯 Best for: What's actually in production at AI companies
▶
Tina Huang
Ex-Meta data scientist turned educator — 1M+ subscribers. Accessible AI education alongside data and career content, great for PMs from analytics backgrounds.
🎯 Best for: Accessible entry into AI/data topics

Get Started

Your 6-month AI PM roadmap

A realistic path from "curious about AI PM" to "actively interviewing" — whether you're a PM already or coming from an adjacent role.

1

Build your AI foundation (Months 1–2)

Start with conceptual literacy, not code. Watch Karpathy's "Intro to LLMs," take DeepLearning.AI's free RAG and prompt engineering short courses. Target: explain LLMs, RAG, and agents to a non-technical colleague.

  • Audit Duke AI PM Specialization on Coursera
  • Watch Karpathy + DeepLearning.AI free courses
  • Read Lenny's Newsletter AI PM interviews
2

Apply it to real product problems (Month 3)

Pick one AI product you use and write a teardown: what's the model doing, how is success measured, what would you change and why? Share it on LinkedIn. This is your proof of thinking, not a portfolio project.

3

Get structured and credentialed (Months 3–5)

Pick one paid course based on your goal — Reforge if you're senior, Maven if you want to ship something real, Pragmatic if your employer cares about recognisable certifications.

4

Interview prep + network (Months 5–6)

AI PM interviews test your ability to scope AI products, define evals, and reason about model risk. Practice with real job descriptions and join communities where AI PMs already work.

  • Practice AI PM case frameworks
  • Network on LinkedIn and Lenny's Slack
  • Target roles with "LLM," "GenAI," or "AI features" in the JD

Common questions

Do I need to know how to code?
No — but you need conceptual fluency: being able to have a real technical conversation with engineers, read a model card, and understand why a system behaves the way it does. Coding is rarely required for PM roles, though it helps for ML platform or data PM tracks.
Can I transition from a non-PM background?
Yes, especially from data analysis, engineering, UX research, or business analysis. The path usually means getting PM fundamentals first, then layering AI specialisation on top. Most roles expect 3–5+ years of core product work before you'd be considered for an AI PM title.
What's the Canadian job market like?
Strong and growing. Toronto, Vancouver, and Montreal have the deepest AI PM markets, concentrated in fintech, health tech, enterprise SaaS, and AI-native startups. The GTA specifically has a dense cluster supported by Vector Institute and Waterloo's ML talent pipeline.
Which track should I target first?
For most people, Generative AI PM is the highest-demand and most accessible entry point in 2026 — especially if you're already a PM shipping software features. ML PM and AI Platform PM require more technical depth and suit people from engineering or data backgrounds.
Is a certification worth it?
Certificates matter less than demonstrated thinking. A well-written AI product teardown signals more to most hiring managers than a certificate. That said, structured programs (Pragmatic, Maven, Reforge) are worth it for the curriculum and cohort network, not the credential itself.

Stay ahead of the AI PM curve

Monthly: curated course picks, Canadian job market signals, resource roundups, and one genuinely useful AI PM framework. No noise, no hype.

No spam. Unsubscribe anytime. Free forever.

⚡ For every PM, not just AI PMs

Become a
builder with AI

You don't need to become an AI PM to use AI as a PM. Here's how product managers at every level are using AI to prototype faster, think sharper, and do more with less — right now.

Why It Matters

The PM who can build has an unfair advantage

AI has changed what a product manager can do alone. A PM who can spin up a working prototype in an afternoon now commands every room they walk into — with engineering, with executives, with customers.

🚀

Ship ideas in hours, not sprints

Vibe coding tools let you turn a PRD or Figma sketch into a clickable, working prototype without writing code from scratch. Engineering sees the vision instead of imagining it.

🧪

Test before you build

A scrappy AI-built prototype you put in front of real users next week is worth more than three weeks of debate in Confluence. Kill bad ideas fast, prove good ones early.

🧠

Think faster, write better

AI doesn't replace PM thinking — it accelerates it. Use it to sharpen your PRDs, stress-test your reasoning, synthesise user research, and write briefs that actually get read.

🔌

Talk to your tools

Modern PM tools — Jira, Notion, Linear, Figma — all have AI layers now. PMs who know how to orchestrate these don't just save time, they operate at a different level of output.

The Stack

Tools every PM should know in 2026

Organised by what you're trying to do — not by hype. Start with one category, get fluent, then expand.

⚡
v0 by Vercel
Prototype

Describe a UI in plain English and get working React code instantly. The fastest path from "here's what I want the screen to look like" to something you can click through. No coding knowledge needed.

PM use: Spin up user-testable prototypes before engineering touches the ticket. Show stakeholders something real in 20 minutes.
🤖
Claude / ChatGPT
Think + Write

Your always-on thinking partner. Use it to stress-test your strategy, draft and sharpen PRDs, synthesise user research transcripts, and prepare for tough stakeholder questions before the meeting.

PM use: "Here's my problem statement — poke holes in it." Draft a PRD skeleton in 10 minutes, then refine. Summarise 20 user interviews into themes.
💻
Cursor
Build

AI-powered code editor. If you have even basic coding knowledge, Cursor multiplies your speed dramatically. If you don't, pair it with v0 — v0 generates the structure, Cursor helps you tweak and extend it.

PM use: Build lightweight internal tools, data dashboards, or working feature demos without pulling in engineering.
🌐
Replit
Build + Host

Browser-based coding environment with AI built in. Build, run, and share working apps without installing anything. Great for non-technical PMs who want a working prototype they can hand off a link to.

PM use: Build a scrappy data tool or API integration, share a live link in Slack for instant stakeholder feedback.
🎨
Figma + AI plugins
Design

Figma's AI features and plugins (Magician, Genius, Builder.io) let you generate UI components, auto-fill wireframes with realistic content, and translate designs to code. PMs who can sketch in Figma move much faster.

PM use: Create wireframes from a rough description, auto-populate designs with realistic data, generate design variants quickly.
📊
Notion AI
Think + Organise

AI baked directly into your workspace. Summarise long documents, draft spec templates, turn meeting notes into action items, and ask questions across your entire knowledge base without leaving Notion.

PM use: Ask "what did we decide about the onboarding flow?" and get an answer from 6 months of docs instantly. Draft PRDs from bullet points.
🔎
Perplexity
Research

AI search with cited sources. Far better than Google for competitive research, market sizing, and quickly validating assumptions. Every result comes with sources you can check — no hallucination hiding.

PM use: "What are the top 5 competitors to X and how do they price?" in 30 seconds. Market research that used to take hours compressed to minutes.
🎙️
Otter / Fathom
Research

AI meeting transcription and summarisation. Every user interview and stakeholder call is automatically transcribed, summarised, and searchable. You can ask questions like "what did users say about the checkout flow?"

PM use: Turn 10 user interviews into a thematic summary in minutes. Never lose a critical quote or decision from a meeting again.
⚙️
Zapier / Make
Automate

No-code automation platforms that now have AI built in. Connect your PM tools — Jira, Slack, email, Notion, analytics — and automate the repetitive coordination work that eats your calendar.

PM use: Auto-summarise new user feedback into Slack. Trigger Jira ticket creation from a Notion spec. Automate weekly metrics digest emails.

The Process

From idea to working prototype in an afternoon

This is the vibe-coding workflow that PMs are using right now to ship proof-of-concepts before engineering has even estimated the ticket.

01

Write the brief in plain English

Describe what you're building as if you're explaining it to a smart friend. Include: what it does, who it's for, what the main interaction is, what success looks like. Don't worry about tech. Claude or ChatGPT will ask if it needs more.

02

Generate the first version with v0

Paste your brief into v0.dev. In 90 seconds you have working React code. Don't expect it to be perfect — expect it to be 60% of the way there. That's the point. You now have something to react to instead of a blank page.

03

Iterate by conversation

Tell v0 or Cursor what to change in plain English. "Make the button bigger." "Add a search bar at the top." "Change this to a two-column layout." Each iteration takes seconds, not days. You're directing, not coding.

04

Host it instantly, share the link

Replit or Vercel lets you deploy your prototype with one click. You now have a real URL you can send to users, stakeholders, or engineers. "Here's what I'm thinking" + a live link beats any Figma presentation.

05

Put it in front of real users

Schedule 3 user calls with your working prototype. Watch what they click first, where they get confused, what they ignore. Real signal in 48 hours — before a single engineer has written a line of production code.

Steal These

Prompts that actually work for PMs

Copy, adapt, and use. These are the prompts experienced PMs use daily — not demo prompts, real ones.

📋 PRD Drafting
"I'm building [feature] for [user type] who struggles with [problem]. The goal is [outcome]. Draft a PRD skeleton with problem statement, success metrics, user stories, edge cases, and open questions."
→ Gets you a structured PRD draft in 2 minutes. Edit, don't start from scratch.
🔍 Devil's Advocate
"Here's my product strategy: [paste it]. Play devil's advocate — what are the 5 strongest arguments against this approach? What assumptions am I making that could be wrong?"
→ Surfaces blind spots before your exec review does. Use this before every major pitch.
🎤 User Research Synthesis
"Here are transcripts from 8 user interviews: [paste]. Identify the top 5 themes by frequency, pull 2–3 direct quotes per theme, and flag any surprising or contradictory findings."
→ 8 hours of synthesis work in 4 minutes. Review the output critically — it's a starting point, not gospel.
⚡ Build a Prototype
"Build a [type of interface] for [user] who needs to [task]. It should have [key elements]. Make it look clean and modern. Output as a single HTML file I can open in a browser."
→ Paste this into Claude or ChatGPT and get a working HTML file in 30 seconds. No v0 account needed.
📊 Metric Definition
"I'm launching [feature] and my north star is [goal]. Suggest a metrics framework: one primary success metric, 2–3 secondary metrics, and 2 guardrail metrics. Explain why each one matters."
→ Gives you a defensible metrics framework to bring to your data team. Edit the reasoning, keep the structure.
🧩 Competitive Analysis
"Compare how [Competitor A], [Competitor B], and [Competitor C] handle [specific feature/flow]. For each: what's the approach, what's the tradeoff, and what does it signal about their strategy?"
→ Use Perplexity for this — it cites sources. Better than asking a model to recall from training data.

Prototype Ideas

Things PMs are building with AI right now

Real examples of what PMs are shipping in a weekend — not production apps, but powerful proof-of-concepts that change conversations.

🗣️

User interview analyser

Paste in interview transcripts, get back themes, quotes, and sentiment by feature area. Turns a week of synthesis into an afternoon.

Built with: Claude API + simple HTML form
📝

PRD generator

Input your problem statement and key constraints, output a structured PRD draft with user stories, success metrics, and open questions.

Built with: v0 + Claude API
🔄

Feedback triage tool

Connect to your feedback source (CSV export, Intercom export), auto-categorise by theme and priority, and surface the top issues each week.

Built with: Claude API + Notion or Airtable
📊

Metrics dashboard

A simple dashboard that pulls data from a CSV or API and renders charts and weekly commentary automatically. No BI tool required.

Built with: Replit + Claude for commentary
🧭

Competitor monitor

A lightweight tool that checks competitor changelogs, app store reviews, and release notes weekly and sends you a Slack digest of what changed.

Built with: Zapier + Perplexity + Slack
🎯

Roadmap communicator

Input your roadmap items and stakeholder audiences, output tailored one-pagers for engineering, execs, and customers — same content, different framing.

Built with: Claude + Notion template

PM Presets

AI systems every PM should build once

These aren't one-off prompts — they're reusable AI configurations you set up once and reach for every day. Each one buys back hours of your week.

🧠 Preset 1 of 3
Talk to me without talking to me

You've written the PRDs, the decision logs, the Confluence pages. But devs, QA, and business stakeholders still ping you with questions that are already answered somewhere. This preset turns your documentation into an always-on PM proxy — a custom AI that knows your product as well as you do and can answer questions 24/7 without blocking your focus time.

1
Export your key product docs — PRDs, decision logs, Confluence pages, API contracts, known issues — as Markdown or plain text files.
2
Create a Claude Project, custom GPT, or Gemini Gem. Upload all docs as knowledge. Paste the system prompt on the right into the instructions field.
3
Share the link with your dev team, QA, and key business stakeholders. Tell them: "Ask this first before pinging me."
4
Update the docs when decisions change. The bot stays current automatically.
What this buys you: Devs can ask "what's the expected behaviour when X happens?" at midnight. QA can ask "is this a bug or working as intended?" without waiting for standup. Business users can ask "why does this work this way?" without a meeting. You get your focus back.
System Prompt — copy into Claude Project / Custom GPT / Gemini Gem
You are [Product Name] PM Assistant — an always-on knowledge base for the [Product Name] product team. Your role: You have been given the product documentation, PRDs, decision logs, and technical specs for [Product Name]. Your job is to help developers, QA engineers, and business stakeholders find answers to product questions without needing to interrupt the Product Manager. How to answer: — Always cite which document or decision log your answer comes from. — If the answer is clearly in the docs, answer confidently and directly. — If you're uncertain or the docs don't cover it, say so clearly: "This isn't covered in the current documentation — you may need to check with the PM." — Never make up product decisions, feature behaviour, or technical constraints. Only answer from what's in the knowledge base. — Keep answers concise. Developers and QA want direct answers, not essays. Common questions you'll handle: — "What should happen when [edge case]?" — "Why did we decide to build it this way?" — "Is [behaviour] a bug or working as intended?" — "What are the acceptance criteria for [feature]?" — "What's the scope of [feature] — what's in and what's out?" Tone: Direct, clear, technical when needed. You represent the PM's thinking — be precise and honest about what you know and don't know. When to escalate: If a question requires a new product decision, a trade-off call, or involves information not in the docs, clearly flag it: "This requires PM input — the docs don't resolve this."
Claude Projects Custom GPT Gemini Gems Notion AI
🚀 Preset 2 of 3
Launch support that knows the product

New product launches are chaotic. L1 and L2 support agents get flooded with questions they've never seen before, escalate everything to engineering, and you end up in a war room for a week. This preset gives your support team a launch-ready AI trained on your runbook, known issues, FAQ, and expected behaviour — so they can resolve 80% of tickets without escalating.

1
Before launch, compile: feature overview doc, known edge cases, expected error states, FAQ drafted from beta feedback, escalation criteria, and what "working as intended" looks like for each flow.
2
Create a dedicated support preset (separate from your dev-facing PM bot). Upload all launch docs. Tune the tone for customer-facing language, not internal PM language.
3
Share with your support team lead before launch day. Run one dry-run with real support tickets from beta to validate the responses.
4
After launch, add real tickets and resolutions as they come in. The preset improves in real time.
What this buys you: Support agents handle more tickets independently. Escalation rate drops significantly in the first week. You're not on Slack at 11pm explaining what a 422 error means for the fifth time. Engineering stays focused on fixing real bugs, not answering "is this supposed to work like this?"
System Prompt — Launch Support Preset
You are the [Product Name] Launch Support Assistant — a specialist knowledge base for the support team handling tickets during and after the [Feature/Product Name] launch. Your role: You know everything about how [Product Name / Feature] is supposed to work. Your job is to help support agents quickly understand: (1) whether an issue is a bug or working as intended, (2) what the correct resolution or workaround is, and (3) when to escalate to engineering or the PM. Answering tickets: — Start by identifying which part of the product the ticket is about. — Check if the behaviour matches a known issue or edge case from the launch docs. — If it's a known issue: give the support agent the correct explanation and any available workaround. — If it's "working as intended": explain why clearly so the agent can communicate it to the customer. — If it looks like a new bug not in the docs: flag it as "potential new bug — needs engineering review" and suggest what information to capture before escalating. Escalation criteria: Escalate to engineering if: data loss is involved, security or privacy concern, more than [X] users affected, or the error is not in any known issue list. Escalate to PM if: the question is about intended product behaviour that isn't documented, or a decision needs to be made about scope. Tone: Clear and practical. Support agents need fast, accurate answers — not lengthy explanations. Lead with the answer, follow with context. What you know: Feature behaviour, expected user flows, known edge cases and workarounds, error messages and what they mean, FAQ from beta, and escalation criteria. You do NOT make up fixes or workarounds not in the documentation.
Claude Projects Custom GPT Gemini Gems Zendesk AI Intercom Fin
🧪 Preset 3 of 3
Prototype → BDD user stories

The handoff between PM and engineering is where the most product context gets lost. A prototype exists in your head and on a screen — but QA needs Gherkin, engineering needs acceptance criteria, and business needs to sign off. This preset converts your prototype description, wireframe context, and feature intent into fully structured BDD user stories with Given/When/Then scenarios, edge cases, and acceptance criteria — ready for your dev tickets.

1
Describe your prototype: what screens exist, what the user flow is, what the happy path looks like, what inputs and outputs are involved.
2
Add context: who the user is, what they're trying to achieve, what the business rule is, what "done" looks like from QA's perspective.
3
Paste into this preset. Get back structured BDD stories in Gherkin format. Review for accuracy — the AI will cover scenarios you might have missed.
4
Paste the output directly into Jira, Linear, or your dev tickets. QA can start writing automated tests before engineering ships.
What this buys you: Engineering gets unambiguous acceptance criteria. QA can write automated tests from the stories before the feature ships. Business stakeholders can read plain-English scenarios and sign off without a meeting. Fewer "that's not what I meant" moments post-delivery.
Prompt Template — paste into Claude / ChatGPT / Gemini
You are a senior QA engineer and product analyst helping convert a product prototype into structured BDD user stories in Gherkin format. Project context: Product: [Product name and one-line description] User persona: [Who is using this feature — role, context, technical level] Business goal: [What outcome does this feature drive for the business] Tech stack context: [Any relevant constraints — e.g. "React frontend, REST API, no real-time updates"] Prototype description: [Describe your prototype here: what screens or states exist, what the user flow is step by step, what inputs the user provides, what outputs/responses the system gives, what happens on success, what happens on failure] Known business rules: [List any rules the system must enforce — validation rules, permission logic, data constraints, limits, etc.] Your output should include: 1. Feature statement — one sentence describing the feature from the user's perspective ("As a [user], I want to [action] so that [outcome]") 2. Happy path scenario — the primary success flow in Given/When/Then Gherkin format 3. Alternative scenarios — at least 3 variations (different inputs, user types, or conditions) 4. Edge case scenarios — at least 3 boundary conditions, error states, or unexpected inputs 5. Acceptance criteria — a numbered checklist of conditions that must be true for the story to be "done" 6. Out of scope — explicitly list what this story does NOT cover, to prevent scope creep Format each scenario as: Scenario: [name] Given [initial context] When [action taken] Then [expected outcome] And [additional expected outcomes if needed] Be thorough. Surface edge cases the PM may not have considered. Flag any ambiguities in the prototype description that need PM clarification before development begins.
Claude ChatGPT Gemini Cursor GitHub Copilot

The PM Builder newsletter

Monthly: one new AI tool breakdown, one real prompt that works, one prototype idea you can ship this weekend. For PMs who build.

No spam. Unsubscribe anytime. Free forever.