Product management

How to write a product roadmap with Claude: structure the priorities, write the narrative, align the stakeholders.

A product roadmap is a communication document as much as a planning tool. Claude helps with the communication layer: structuring the narrative, writing the rationale, aligning the format to your audience.

THE SHORT VERSION

Claude does not set your product priorities. What it does well is structure those priorities into a readable roadmap document and write the narrative that explains why this sequence makes sense. The prioritization is yours; the document is Claude.

Bill Colbert

Treetop Growth Strategy — Updated May 2026

What Claude needs

Inputs for a useful product roadmap

Before you prompt Claude for a roadmap, you need your priorities roughly sorted. Claude can help you document and communicate your roadmap; it cannot discover what your customers need or what is technically feasible.

Bring to the session:

Your product vision: where the product is going in 2-3 years
Your near-term priorities for the next two quarters with rationale
The customer problems each initiative addresses
Your key constraints: team size, technical dependencies, business priorities
Your audience for this roadmap document

The prompt

How to draft a product roadmap with Claude

Roadmap narrative prompt

I need to write a product roadmap document for [audience: internal team / board / customer-facing]. Context: Product vision: [describe where the product is going] Q3 priorities: [list initiatives with one-line rationale each] Q4 priorities: [list initiatives with one-line rationale each] H2 and beyond (themes only): [list 2-3 themes] Key customer problems this roadmap addresses: [list] Key constraints shaping sequencing: [list] Write a product roadmap document with: (1) an executive summary of our product direction, (2) a narrative explanation of our Q3-Q4 priorities and why this sequence, (3) a brief on what we are intentionally not doing and why, (4) a forward-looking vision section for H2 and beyond.

Common variations

Different roadmap formats for different audiences

For boards and investors: "Write this so each initiative is described in terms of the business metric it moves, not the feature it adds."

For sales teams: "Write a version that a salesperson can use in a customer conversation: focus on the problems we are solving and when customers can expect them addressed."

For engineering teams: "Add a section on technical dependencies and sequencing rationale for each initiative."

Time estimate: Full roadmap document draft: 20-30 minutes with prepared inputs. Editing: 30-45 minutes. Audience-specific versions: 15 minutes each.

Want AI embedded in your actual workflow?

Book a 30-minute AI Audit. We identify your highest-leverage opportunities and hand you a deployment plan.

Book the AI Audit →Audit your AI stack