AI Prompts for Product Managers: Copy and Paste for ChatGPT

In a small business, the product manager is often the founder, a developer who drew the short straw, or someone in marketing who cares a lot about customers. Nobody gave them a playbook. They just have a list of ideas, a pile of feedback and not enough hours.

These prompts cover the work a product owner does week to week: talking to customers, writing stories and specs, choosing what to build, and telling people about it. Fill in the [brackets], paste in your own notes, and you'll have a solid first draft in minutes. If you also run delivery, my prompt library for running projects picks up where this one stops.

Customer discovery and interview guides

Interview guide for a new idea

Copy this prompt

I'm exploring an idea for [product or feature] aimed at [type of customer].
Write an interview guide with open questions about their current habits, frustrations and workarounds. Avoid leading questions and anything that pitches the idea.

Screener for the right interviewees

Copy this prompt

Write a short screener of five questions to find the right people to interview about [problem area].
I want to reach [describe ideal customer] and rule out [who to exclude].

Invite customers to a chat

Copy this prompt

Write a friendly email inviting [type of customer] to a [length] chat about how they handle [task].
Make it clear I'm not selling anything, and offer [thank-you gesture, for example early access].

Summarise one interview

Copy this prompt

Here's a transcript from a customer interview, with names removed: [paste transcript].
Summarise the person's goals, pains and current workarounds, and list the exact phrases they used that we should remember.

List the assumptions to test

Copy this prompt

Here's our product idea: [describe idea].
List the riskiest assumptions behind it, from most to least dangerous, and suggest a quick, low-effort way to test each one with real customers before we build anything.

Problem statements and user stories

A sharp problem statement

Copy this prompt

Using these notes [paste notes], write a problem statement in one or two sentences covering who has the problem, what they're trying to do, what gets in the way and why it matters to them.

User stories from a feature idea

Copy this prompt

Turn this feature idea [describe feature] into user stories in the format: as a [type of user], I want [goal] so that [reason].
Write one for each type of user who'd touch it.

Acceptance criteria

Copy this prompt

Write acceptance criteria for this user story: [paste story].
Use plain given, when, then statements and include the edge cases a developer is likely to ask about, such as empty states and errors.

Jobs customers hire us for

Copy this prompt

Based on this feedback [paste feedback], describe the jobs our customers are hiring [product] to do.
Separate the practical, emotional and social jobs, with one example quote for each.

Split a story that's too big

Copy this prompt

This user story is too big for one sprint: [paste story].
Split it into smaller stories that each deliver something a customer could use on its own, and explain the order you'd build them in.

Choosing what to build and telling the roadmap story

Prioritise a wish list

Copy this prompt

Here's our feature wish list: [paste list].
Score each item for customer impact, effort and confidence on a simple scale, explain your reasoning briefly, and suggest the top three to build next.

A now, next, later roadmap

Copy this prompt

Turn these priorities [paste list] into a now, next, later roadmap for a small team.
For each item, add one sentence on the customer problem it solves rather than describing the feature itself.

Explain the roadmap to the team

Copy this prompt

Write a short narrative explaining our roadmap for [period] to the team.
Connect each theme to a customer problem, and say what we're deliberately not doing and why.

Say no to a feature request

Copy this prompt

A customer has asked for [feature]. We've decided not to build it for now because [reason].
Write a warm, honest reply that thanks them, explains the decision and suggests a workaround if there is one.

Challenge my priorities

Copy this prompt

Here's my top priority for the coming months and my reasoning: [paste].
Argue against it as a sceptical co-founder would, then tell me which of your objections I should take seriously.

Drafting specs and product requirement documents

First draft PRD

Copy this prompt

Write a first draft product requirements document for [feature] with sections for problem, goals, users, user stories, requirements, out of scope, open questions and how we'll know it worked.
Use these notes: [paste notes].

Work with me

Want AI doing the heavy lifting in your marketing?

I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.

Book a free 30-minute callOr grab the free resources →

One-page spec for a small change

Copy this prompt

Write a one-page spec for this small change: [describe change].
Keep it to what a developer and designer need: the problem, the expected behaviour, edge cases and anything that mustn't change.

Find the gaps in a spec

Copy this prompt

Review this spec [paste spec] as an experienced developer, designer and support lead would.
List the questions each of them would ask, and anything missing that could cause rework later.

Decide how you'll judge success

Copy this prompt

Suggest how we'd know whether [feature] is working for customers.
Give me two or three simple signals we can track, what good would look like, and what result would make us rethink it.

Launch notes and release messaging

When a launch needs a page of its own, these landing page copy prompts are the natural next step.

Release notes customers will read

Copy this prompt

Turn this list of changes [paste changes] into release notes for customers.
Lead with what they can now do, use plain language, skip internal jargon and keep each item to one or two sentences.

Launch announcement email

Copy this prompt

Write a launch email for [feature] aimed at [type of customer].
Open with the problem it solves, show one example of it in use, and finish with a single clear next step.

Internal launch brief

Copy this prompt

Write an internal launch brief for [feature] so support, marketing and the rest of the team know what's changing, who it's for, the key messages, likely customer questions and who to ask for help.

Answers to likely customer questions

Copy this prompt

List the questions customers are most likely to ask about [new feature or change], including the awkward ones.
Draft a short, plain answer for each that our support team can use.

Short in-app announcement

Copy this prompt

Write three versions of a short in-app message announcing [feature] to existing users.
Each should explain the benefit in one sentence and invite them to try it.

Making sense of customer feedback

Theme a pile of feedback

Copy this prompt

Here's customer feedback from [source, for example support emails or reviews], with names removed: [paste feedback].
Group it into themes, show how often each comes up, and quote one typical comment per theme.

Separate requests from problems

Copy this prompt

From this feedback [paste feedback], separate what customers are asking for from the underlying problems they're describing.
For each problem, suggest whether a fix, a feature or better guidance would help most.

Follow-up survey

Copy this prompt

Write a short survey of no more than six questions to follow up on [theme from feedback].
Mix one or two rating questions with open questions, and avoid anything that nudges people towards an answer.

Feedback round-up for the team

Copy this prompt

Turn these feedback notes [paste notes] into a one-page summary for the team: top themes, what's new, what's getting worse, notable quotes and the two things you'd look into first.

Close the loop with customers

Copy this prompt

Write a short, warm message to customers who asked for [feature], letting them know it's now live, thanking them for the idea and showing how to use it in a couple of steps.

How to get better answers from your product prompts

• Feed it the customer's own words. Paste real feedback and interview notes. Summaries of summaries lose the detail that matters.
• Strip out names first. Remove customer names, emails and anything that identifies a person before you paste.
• Ask for the counter-argument. ChatGPT tends to agree with you. Ask it to argue the other side before you commit.
• Keep your product context together. ChatGPT has projects, so you can keep your product description, personas and past decisions in one place.
• Treat output as a draft. It doesn't know your customers. You do, so edit for what you know is true.

If you're not sure where AI fits into your product work, here's what an AI consultant does for a small business.

Frequently asked questions

What are good AI prompts for product managers?

The most useful ones cover the jobs you repeat: interview guides, problem statements, user stories, prioritisation, specs, release notes and feedback summaries. Give the prompt your real notes and it'll give you a first draft you can sharpen.

Can ChatGPT write a product requirements document?

It can write a solid first draft if you give it the problem, the users and your notes. You'll still need to check the requirements with your developers and fill in what only your team knows.

Is it safe to paste customer interviews into ChatGPT?

Remove names, email addresses and anything that identifies a person first, and check your own privacy promises to customers. Describe sensitive details in general terms.

Do product owners in small businesses need different prompts?

Usually yes. Small teams skip the heavy process, so the prompts here focus on quick, practical outputs: a one-page spec rather than a long document, and a simple now, next, later roadmap.

Can I use these product manager prompts in Claude or Gemini?

Yes. They're plain-language prompts, so they work in ChatGPT, Claude or Gemini. Fill in the brackets the same way in any of them.