Roadmap synthesis

Across the meetings provided (customer research calls, strategy
discussions, engineering capacity reviews, sales/CS calls, competitive
intelligence), produce a strategic product roadmap.

The roadmap should:
- Reflect actual customer signal — quote verbatim where useful, cite
  frequency of requests
- Align with strategic direction articulated in leadership meetings
- Be grounded in realistic capacity from engineering reviews
- Surface trade-offs explicitly, not hide them
- Distinguish "what we'll build" from "why we'll build it" from "when"

Do not invent customer signal or strategic direction that wasn't in
the source meetings. If something is thin or contested, write
"Limited signal — confirm with {source}" or "Contested in source —
decision needed."

No emojis. Length 2000–4000 words depending on portfolio scope.

Format:

# Product Roadmap — {Area / Product / Portfolio Name}
**Status:** Draft v1.0
**Owner:** {Name}
**Reviewers:** {Required for sign-off}
**Period covered:** {date range}
**Source discussions:** {List of source meetings}
**Last updated:** {date}
**Next review:** {date}

## Strategic context
Two to three paragraphs. The strategic direction the roadmap operates
within. What's the company trying to accomplish? What customers are
we focused on? What positions are we taking? Cite from leadership /
strategy discussions where useful.

## Themes
The three to six strategic themes the roadmap operates against.
Themes are broader than features; they're the categories of investment.

### Theme 1: {Name}
- **What it covers:** scope
- **Why it matters strategically:** reasoning from source
- **Customer signal:** evidence from research that this theme
  addresses real pain
- **Success looks like:** outcome
- **Investment level:** Heavy | Moderate | Selective

[Repeat for each theme]

## Now (in progress or starting imminently)
For each item:
### {Item name}
- **What it is:** one to two sentences
- **Theme:** which theme this belongs to
- **Why now:** the specific reasoning for this timing
- **Customer signal:** evidence — quote if useful, frequency if relevant
- **Strategic fit:** how this aligns with strategic direction
- **Owner:** PM / team
- **Engineering team:** team
- **Target ship:** date or "this quarter"
- **Success criteria:** how we'll measure
- **Status:** In discovery | In build | In test
- **Dependencies:** list
- **Risks:** list

## Next (committed to start within ~3 months)
For each item:
### {Item name}
- **What it is:** description
- **Theme:** which theme
- **Why this is Next and not Now:** reasoning
- **Customer signal:** evidence
- **Strategic fit:** alignment
- **Owner-to-be:** tentative
- **Target start:** period
- **Open questions:** things needing resolution before this becomes Now

## Later (on the radar; will be considered next planning cycle)
Items in Later are NOT commitments. They're signals being tracked.

For each:
- **Item:** brief
- **Theme:** which theme, or "doesn't fit current themes"
- **What we're tracking:** the signal that put this on the radar
- **What would need to be true to move this to Next:** the trigger
- **Source:** source meeting if applicable

## Considered and not pursuing (currently)
Items that came up in source meetings but that we're deliberately not
prioritizing. This is the most underrated section.

For each:
- **Item:** description
- **Why considered:** the signal that surfaced it
- **Why not pursuing:** the specific reasoning — strategic fit,
  capacity, timing
- **What would change our mind:** the conditions for reconsideration

## Customer signal summary
Quantified view of what customers have been asking for:
- **{Pain point / request}:** mentioned in {N} customer calls —
  segment pattern: {which customers} — quote: "{verbatim}"

## Strategic signal summary
Key strategic decisions and direction from leadership / strategy
discussions:
- {Strategic point} — articulated in {meeting} — quote if useful

## Capacity reality
What engineering capacity looks like for the period:
- Teams and their committed capacity
- Major debt items consuming capacity
- Realistic shipping volume in the period

## Risks and watch-outs
- **Risk:** description — **Mitigation:** approach

## Open questions to resolve before next refresh
- {Question}

## Cross-references
- Related PRDs
- Related ADRs
- Source customer corpus
- Source strategy discussions

Based on the comprehensive roadmap synthesis, produce a lightweight
Now / Next / Later roadmap. Audience can be internal team members,
leadership, or close partners. Communicates direction without
overcommitting.

Constraints:
- Under 1000 words
- Scannable — bullets, not paragraphs
- Each item has a brief "why" so the prioritization is legible
- No internal-only or confidential content
- Clear hedging on Later (this is not a commitment)

Format:

# {Area / Product} Roadmap — Now / Next / Later
**Updated:** {date}
**Owner:** {Name}

## What we're focused on right now
The strategic frame for this period — two to three sentences.

## Now (active work, expected to ship in {period})
- **{Item name}:** one-line description
  - **Why now:** one-phrase reasoning
  - **Target:** when

## Next (planned to start within ~3 months)
- **{Item name}:** one-line description
  - **Why next:** one phrase
  - **Expected start:** period

## Later (on our radar; not yet committed)
- **{Item name}:** one line
  - **What we're tracking:** brief context

Items here are signals, not commitments.

## Themes shaping this roadmap
- **{Theme}:** one line on what this theme is and why it matters

## What we're explicitly NOT doing right now
- **{Item}:** brief reason for non-pursuit
- **{Item}:** brief reason

Naming non-pursuit explicitly prevents these items from being
relitigated repeatedly.

Based on the strategic roadmap synthesis, produce a customer-facing
roadmap. The audience is external — customers, prospects, partners.
The communication must be honest, useful for their planning, and
appropriately hedged.

Constraints:
- Under 800 words
- Lead with themes and outcomes, not feature names
- Be specific where you can be reliable; be vague where you can't
  yet commit
- Never use phrasing that creates a commitment you can't deliver
- No internal jargon, no code names, no strategic confidential content
- Tone: confident about direction, honest about timing uncertainty

Format:

# {Product Name} Product Direction — Updated {date}

## What we're building toward
Two to three sentences on the direction of the product.

## Recently shipped
- **{Capability name}:** what it does for them, in their language

## Currently building
- **{Capability name}:** what it will do for them, why we're building it
  - **When:** conservative target — "later this quarter" / "by end of
    year" / "early next year"

Avoid specific date promises unless very confident. Customers remember
missed dates.

## Planned for next period
- **{Capability name}:** what it will do for them
  - **When:** period or "next few months"

## On the horizon
Areas we're investing in but not yet ready to specify timing for.
- **{Theme or capability area}:** what we're exploring and why

## Themes for this period
- **{Theme}:** what this means for our customers

## What we're not doing right now
(Optional, but builds trust when included.)

We're regularly asked about {topics}. Here's our honest read on each:
- **{Topic}:** honest framing — "we hear this; not in our near-term
  plans because {brief reasoning}" or "this is on our radar but won't
  come in this period"

## Our process
- We update this roadmap {cadence}
- It's informed by {customer research / advisory board / product council}
- If you want to influence it: {process}

---

**Important:** This roadmap reflects our current direction and is
subject to change as we learn more from customers and as priorities
evolve. Specific dates are targets, not commitments, unless explicitly
indicated.

This prompt updates the roadmap based on new source material — recent
customer calls, recent strategy discussions, recent engineering
reviews, any other developments since the last roadmap version.

Inputs:
- The current roadmap (paste below)
- New source meetings since the last update (paste artifacts
  below)

Produce an updated version of the roadmap that:
- Preserves the structure of the current roadmap
- Incorporates new customer signal (with frequency updates if items
  have come up again)
- Reflects strategic direction shifts if any
- Updates Now / Next / Later assignments based on what's changed
- Adds items that have emerged
- Moves or removes items based on what's been learned
- Flags what changed in this update so reviewers can see deltas

Format:

[Output the updated roadmap using the same structure as Template A]

## Change log — {Date}
**Source:** New meetings since {previous update date}

**What moved from Next to Now:**
- {Item} — why it moved

**What moved from Later to Next:**
- {Item} — why it moved

**What's newly added:**
- {Item} — to which bucket — source

**What moved backward (Now to Next, Next to Later):**
- {Item} — why it moved back

**What was removed:**
- {Item} — why removed (deprioritized / completed / no longer relevant)

**Strategic shifts:**
- {Shift} — what discussion prompted it

**New customer signal:**
- {Signal} — frequency change or new pattern

**Capacity changes:**
- {Change} — how it affects the roadmap

**Items still being debated (not yet decided):**
- {Item} — what's open