Guide

How product managers can use Claude

Product work is mostly reading, deciding and writing things down. This guide shows how to set Claude up around one product and use it for research synthesis, roadmap notes, market questions and, if you have repo access, Claude Code.

Updated 30 October 2026

Quick answer: make a Claude Project for your product with the strategy, personas and current roadmap in its knowledge. Use chats there to synthesise interview notes and draft roadmap updates, turn on Research (paid plans) for market questions, and, if you have access to the codebase, use Claude Code to ask how a feature actually works before you write about it.

Menu names below were checked against Claude's help center and Claude Code docs as of October 2026. For writing the spec itself, see how to write a PRD with AI; this guide covers the work around it.

Set up a product Project

Open Projects in the sidebar and click + New Project.
In the knowledge area, click + and add the product strategy, persona notes, the current roadmap and your PRD template.
Click Set project instructions. Tell Claude who reads your documents (engineers, leadership), the format you use, and to flag assumptions instead of filling gaps. Click Save instructions.

Chats in a Project don't see each other. When a decision is final, add a short note of it to the knowledge so the next chat starts from it.

Synthesise user research

Start a new chat in the Project and attach the interview notes or survey export (remove personal details you don't need).
Ask for recurring problems, each with how many sources mention it and a short quote as evidence.
Ask what the notes don't answer, so you know what to test next.
Spot-check a few quotes against the originals, then add the final summary to Project knowledge.

Write roadmap notes and updates

In the Project, paste what shipped, what slipped and what's next.
Ask for two versions: a detailed note for the team and a short update for leadership that ties each item to the strategy in the knowledge.
Ask Claude to list risks and open questions separately, so they don't get buried in prose.

Answer market questions with Research

With web search on, click + at the bottom left of the chat and choose Research.
Ask a bounded question, such as how competitors handle a specific feature and on which plans.
Research searches the web and your connected apps over several steps on its own; it uses more of your limit than a normal chat.

To let Claude search your docs or tickets too, add connectors under Customize > Connectors. Anthropic's examples include Google Drive and Linear; Claude only sees what your own account can access.

Use Claude Code to understand the product

If you can open the repository, Claude Code can read it and explain it in plain language, which helps before you write requirements for an existing feature.

Open the desktop app's Code tab and pick the project folder, or run claude in that folder in a terminal.
Switch to Plan mode, where Claude explores and proposes without editing code.
Ask questions such as where a setting is stored, or what happens when a payment fails.
Leave changes to your engineers unless that's agreed; Claude Code can edit files, commit and open pull requests.

Not sure which tool fits a task? See Claude Code vs Claude chat.

Good to know

Plans: Projects are on every plan (five on Free). Research needs a paid plan. Claude Code needs Pro, Max, Team, Enterprise or a Console account, and the desktop Code tab needs a paid subscription.
Limits: on Pro and Max, usage limits are shared between Claude and Claude Code.
Team sharing: on Team and Enterprise, projects can be shared with members, and an Owner must enable connectors first.

If it doesn't work

Synthesis invents themes: ask for a source and quote per theme, and drop any it can't support.
Claude forgets the strategy: check you're inside the Project and the document is in its knowledge.
No Research button: turn on web search first; Research is paid plans only.
Claude Code uses API billing: run /login with your subscription and make sure ANTHROPIC_API_KEY isn't set.

Keeping decisions from getting lost

See Workbranch for product managers for the full picture. With the Workbranch connector, saying "save this to Workbranch" in a Claude chat files its tasks, decisions and open questions into a project, by topic.

Sources

What are projects? (Claude Help Center, checked 30 October 2026)
How can I create and manage projects? (Claude Help Center, checked 30 October 2026)
Use Research on Claude (Claude Help Center, checked 30 October 2026)
Use connectors to extend Claude's capabilities (Claude Help Center, checked 30 October 2026)
Use Claude Code Desktop (Claude Code docs, checked 30 October 2026)
Using Claude Code with your Pro or Max plan (Claude Help Center, checked 30 October 2026)

Frequently asked questions

Should I paste raw customer interview transcripts into Claude?

Check your company's policy first, and remove names and personal details you don't need. On Team and Enterprise plans your admins control the workspace settings.

Can engineers and PMs share the same Claude Project?

On Team and Enterprise plans projects can be shared with members as Can view or Can edit, so a product Project can be shared with the squad.

Do I need to code to use Claude Code?

No, you describe tasks in plain language, but it works on files and can run commands, so keep the default mode, which asks before editing files or running commands.