Purpose
Produce an executive-ready enablement communication — update, business case, or forum summary — that leads with business outcomes, ties enablement work directly to revenue and productivity metrics, and gives senior GTM leaders a clear decision or takeaway. Solves the recurring problem of enablement work being reported as activity ("we ran 12 sessions") instead of impact ("we cut ramp time by 3 weeks, adding $X in earlier quota attainment").
When to Use
Invoke this skill when the user asks to:
- Draft an enablement program update for a QBR or leadership review
- Build a business case to justify enablement headcount, tooling, or budget
- Summarize an enablement initiative's impact for the CRO, VP of Sales, or exec team
- Prepare talking points or a one-pager for an executive GTM forum
- Translate enablement metrics (completion rates, session counts) into business terms
- Report on a launch, certification, or ramp program's contribution to pipeline or revenue
Inputs Required
Before starting, collect:
- Communication type: Program update / business case / forum summary / launch recap
- Audience: Who's reading — CRO, VP Sales, exec team, GTM leadership group
- Program/initiative: What enablement work is being reported on or proposed
- Outcomes and metrics available: Any results — ramp time, quota attainment, win rate, adoption, completion, deal cycle, productivity per rep
- Business goal it ties to: The revenue or GTM objective this program supports (pipeline, retention, new-logo velocity, upsell)
- The ask or decision: What you want the audience to approve, know, or do next
- Timeframe: Reporting period or projection window
If specific dollar figures aren't available, use rep-level and cycle-level metrics as proxies and flag where a business-owned number would strengthen the case.
Instructions
Step 1: Establish the Business Frame
Open by anchoring to what leadership already cares about, not to enablement activity.
- Identify the GTM metric this program moves: ramp-to-productivity, win rate, average deal size, sales cycle length, forecast accuracy, or net revenue retention
- State the "so what" in the first two sentences — the outcome, not the effort
- If this is a business case, frame the problem as a revenue cost: "Reps take 6 months to ramp; each month of delay is roughly [X] in unrealized quota."
Step 2: Build the Metrics Bridge
Translate every enablement metric into a business consequence. Use this mapping:
- Completion / certification rates → readiness → shorter ramp → earlier quota attainment
- Ramp time reduction → additional productive selling weeks per hire → incremental pipeline/revenue
- Content/message adoption → consistency in deals → win rate or deal-size lift
- Program participation → behavior change → measurable pipeline or conversion movement For each claim, show the chain: activity → capability → behavior → business result. Never present an activity metric without its downstream business meaning.
Step 3: Quantify Impact (or Frame the Estimate Honestly)
- Where hard numbers exist, present them with the baseline for contrast (before/after or vs. target)
- Where numbers are directional, state the assumption openly: "Assuming a conservative 2-week ramp reduction across 20 hires at [quota/week]..."
- Distinguish attributed impact (directly measured) from influenced impact (contributed to) — executives distrust over-claiming
- Include one credibility check: the single number a skeptical CRO would push back on, and how you'd defend it
Step 4: Structure the Narrative by Communication Type
Program Update — Outcome headline → 3 key results (metrics bridged) → what's working → what's at risk → next period focus → any ask.
Business Case — Problem framed as revenue cost → proposed solution → projected impact with assumptions → investment required → expected ROI or payback → decision requested.
Forum Summary / One-Pager — Single outcome statement → 3-4 scannable proof points → one clear recommendation. Built to be read in under 90 seconds.
Launch Recap — Adoption vs. target → behavior/deal evidence → early business signal → what changes next.
Step 5: Sharpen the Ask
End every communication with a single, unambiguous next step:
- What decision, approval, or awareness you need
- Who owns the next action and by when
- Remove hedging — one recommendation, stated plainly
Output Format
- Structure: Executive-first — outcome headline, then supporting evidence, then the ask; ordered by decision relevance not chronology
- Length: 400–700 words for updates and recaps; 600–900 for business cases; one-pagers under 350 words
- Format: Structured document with bolded section headers; metrics presented as bullets or a compact before/after table; prose kept tight
- Sections: Outcome headline → business context → results with metrics bridge → risks or assumptions → recommendation/ask
- Tone: Senior operator addressing peers — confident, revenue-fluent, concise. No enablement jargon that requires translation, no false modesty, no activity-dumping.
Quality Checklist
Before delivering output, verify:
- [ ] The first two sentences state a business outcome, not enablement activity
- [ ] Every enablement metric is bridged to a revenue, pipeline, or productivity consequence
- [ ] At least one quantified impact figure (or an explicitly flagged estimate with its assumption) is present
- [ ] Attributed vs. influenced impact is distinguished — no unsupported over-claiming
- [ ] The communication ends with exactly one clear ask, decision, or next step with an owner
- [ ] Length matches the communication type and could be read in the target forum's time window
Notes
- The most common failure mode is reporting effort ("sessions delivered") instead of impact — always force the metrics bridge in Step 2
- When no dollar figures exist, ramp-time reduction and win-rate movement are the two most credible proxies for revenue impact with GTM leaders
- Business cases win on payback period and conservative assumptions, not on the largest possible projection — a defensible smaller number beats an aggressive one that invites pushback
- For recurring updates (QBRs), keep the metric definitions consistent quarter over quarter so leaders can track a trend line rather than re-learn the story each time
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills