Core & Strategy
Revenue Enablement Context
Create or update a canonical revenue enablement context used by other enablement skills. Use when the user needs to document ICP, personas, sales stages, qualification rules, pricing and packaging, core objections, competitors, and current initiatives, or when downstream skill outputs are weak because shared context is missing. Route multi-skill sequencing requests to enablement-router.
Revenue Enablement Context
Build one reliable context baseline that other enablement skills can reuse.
Confirm Inputs First
Confirm these items before drafting:
- Company and product summary
- ICP segments and buyer personas
- Sales stages and qualification definitions
- Pricing and packaging basics
- Top objections and common competitive alternatives
- Current quarter initiatives and key risks
- Existing context artifact location and last-updated date (if it exists)
If key items are missing, ask only for the highest-impact gaps. If the user wants speed, proceed with clearly labeled assumptions.
Read The Right Reference
Read references/context-schema.md before drafting or updating the context artifact. Read references/context-schema.yaml when the user wants a machine-readable context pack for downstream reuse.
Default Workflow
- Collect provided source material and normalize terms.
- Fill the context schema section by section.
- Mark unknowns as assumptions, not facts.
- Flag contradictions across sources and propose one canonical version.
- Add a short dependency block listing which downstream skills depend on each section.
- Create a compact context handshake block: source location, version date, owner, and confidence rating.
- Add a missing-information checklist for future refinement.
- Return the updated context plus the top unresolved decisions.
What To Avoid
- Generic context that cannot drive role-specific outputs.
- Hidden contradictions between sales-stage definitions and qualification guidance.
- Missing freshness markers that cause downstream skills to reuse stale assumptions.
- Overwriting uncertain data as facts instead of preserving assumptions.
Output Contract
Default output includes:
- A canonical revenue enablement context document with all schema sections populated
- A compact context handshake block (owner, freshness, confidence, and source)
- A machine-readable context object when requested
- A labeled assumptions list
- A missing-information checklist prioritized by downstream impact
Quality Bar
- Context is specific enough to drive role-based outputs, not generic market language.
- Definitions are unambiguous for stages, qualification, and personas.
- Assumptions are explicit and easy to replace with confirmed data.
- Freshness and confidence are visible so downstream users can judge reliability.
- Another skill can consume this context without asking foundational questions again.
Open source
This playbook is part of 37 open-source enablement workflows. Read, copy, and adapt — attribution welcome but not required.
Run this playbook with your team
Pointer's workspace lets you assign playbooks to people, track progress, and pair them with role blueprints and ramp plans.
More from Core & Strategy
All playbooks →Enablement Router
Route revenue enablement requests to the best-fit skill or sequence of skills. Use when the user asks which enablement skill to use, combines multiple enablement asks in one prompt, or needs a staged workflow across planning, messaging, coaching, delivery, and measurement. Route single-artifact requests directly to the corresponding specialist skill instead of this router.
Executive Briefing Builder
Build executive-facing briefing materials for strategic customer meetings, internal leadership prep, and high-stakes decision discussions. Use when asked to prepare an executive briefing, align leadership on meeting goals, or craft concise decision-oriented talking points. For recurring business review cadence decks, use qbr-ebr-builder.