| name | product-launch-enablement |
| description | Build launch readiness plans and field-ready launch assets for revenue teams. Use when the user asks for launch enablement, seller FAQs, talk-track updates, training, go/no-go checks, or post-launch adoption review. Route quarter-wide prioritization to quarterly-enablement-planner. |
Product Launch Enablement
Turn product changes into launch readiness, seller guidance, and post-launch follow-through.
Confirm Inputs First
Confirm:
- Whether a current
revenue-enablement-context exists; if yes, use it as baseline assumptions, if no, capture only the highest-impact missing context.
- What changed and why it matters to the field
- Target audience and impacted teams
- Launch date, rollout model, and required approvals
- Cross-functional owner model (PMM, Enablement, Sales, CS, RevOps, Support)
- Commercial implications, risks, and non-goals
- Required behavior changes for field teams
If details are incomplete, request missing blockers or proceed with assumptions labeled by risk.
Read The Right Reference
Read references/launch-readiness-framework.md before planning.
Read references/source-system-guide.md when launch inputs or distribution depend on docs, Slack, enablement platforms, or project trackers.
Default Workflow
- Classify the launch by field impact and rollout scope.
- Define what each team needs to know, do, and stop doing.
- Write the field message: what changed, why it matters, when to use it, and what not to say.
- Build the launch kit: FAQ, talk track, objection notes, and any rep-facing proof points.
- Set training, practice, and manager inspection checkpoints.
- Define go/no-go criteria and the owners who sign off.
- Map handoffs and escalation paths across PMM, enablement, sales, CS, RevOps, and support.
- Add a 30-day review loop for adoption, friction, and message drift.
- Produce a launch timeline and owner matrix.
Tool Notes
- Keep deliverables tool-agnostic.
- Use references/source-system-guide.md for source-of-truth, destination mapping, and safe writeback boundaries.
- If requested, map outputs into the user's docs, slides, or project tracker stack.
Output Contract
Default output includes:
- Launch tier and readiness matrix
- Cross-functional owner and handoff matrix
- Field message summary and FAQ
- Talk-track and objection updates
- Training and practice plan
- Go/no-go readiness checklist
- 30-day post-launch signal review plan
Quality Bar
- Launch guidance is role-specific and action-oriented.
- Field teams can explain the change, when to use it, and what not to say.
- Cross-functional ownership and escalation paths are unambiguous.
- Risks and readiness gates are explicit.
- The review loop catches message drift and adoption issues early.
