sidchaudhary/gtm-skills / skills/gtm-engineer/sales-enablement
sales-enablement
VerifiedProduces sales collateral: one-pagers, ROI calculators, proposal templates, and playbooks, mapped to buyer persona and deal stage. Use when a rep needs a specific asset to hand a prospect. Boundary: for objection-handling responses specifically, use objection-handling: that skill already owns the objection library in this pack. This skill covers every other enablement asset type.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.0 KB |
| references/house-rules.md | markdown | 13.3 KB |
| references/outbound-copy-standards.md | markdown | 15.5 KB |
| references/sales-enablement-assets.md | markdown | 9.8 KB |
references/sales-enablement-assets.md
View on GitHub# Sales Enablement Asset Templates
Reference for the `sales-enablement` skill: the sales deck framework, case study brief format, and buyer persona card template. One-pager, ROI calculator, and proposal structures live in the main SKILL.md, this file covers the two asset types that need more room.
---
## Sales Deck, 10-12 Slide Framework
1. **Current-world problem**, the pain the buyer lives with today
2. **Cost of the problem**, what inaction costs, in time/money/risk
3. **The shift happening**, market or technology change creating urgency
4. **Your approach**, how you solve it differently
5. **Product walkthrough**, 3-4 key workflows, not a full feature tour
6. **Proof points**, metrics, logos, third-party recognition
7. **Case study**, one customer story told well, not a logo wall
8. **Implementation/timeline**, how they get from signed to live
9. **ROI/value**, expected return and payback period
10. **Pricing overview**, transparent, tiered if applicable
11. **Next steps/CTA**, a clear action with a timeline
### Principles
- Story arc, not feature tour: the world has a problem → there's a better way → here's proof → here's how to get there
- One idea per slide, if a slide needs two points, split it into two slides
- Design for presenting, not reading, slides support the conversation, they don't replace it
### Customization by buyer type
| Buyer | Emphasize | De-emphasize |
|---|---|---|
| Technical buyer | Architecture, security, integrations, API | ROI math, business metrics |
| Economic buyer | ROI, payback period, total cost, risk | Technical implementation detail |
| Champion | Internal selling points, quick wins, peer proof | Deep technical/financial detail |
---
## Case Study Briefs (Sales Format)
Sales case studies differ from marketing case studies: marketing tells a story, sales needs fast-access proof mid-call. Keep it short, outcome-focused, and tagged for retrieval.
**Structure:**
1. Customer profile, industry, company size, buyer role
2. Challenge, 2-3 sentences on what they struggled with
3. Solution, 1-2 sentences on what they implemented
4. Results, 3 specific before/after metrics
5. Pull quote, one sentence from the customer, verbatim if available
6. Tags, industry, use case, company size, persona (so a rep can pull "show me a healthcare example" instantly)
---
## Buyer Persona Card
| Field | Description |
|---|---|
| Role/title | Common titles and reporting structure |
| Goals | What success looks like for them specifically |
| Pains | What frustrates them day to day |
| Top objections | The 3-5 objections this role raises most (cross-reference `objection-handling` output) |
| Evaluation criteria | How they judge solutions |
| Buying process role | Decision-maker, influencer, blocker, or champion |
| Messaging angle | The single sentence that resonates most with this persona |
### Persona archetypes
- **Economic buyer**, signs the check, cares about ROI and risk
- **Technical buyer**, evaluates the product, cares about capability and integration
- **End user**, uses it daily, cares about ease and workflow fit
- **Champion**, advocates internally, needs ammunition to sell on your behalf
- **Blocker**, opposes the purchase; understand the concern to neutralize it, don't ignore it
---
## Demo Script / Talk Track
The asset a rep uses live, so it is written to be spoken, not read.
**Structure**
1. **Frame** - one sentence on what you are about to show and which of their stated problems it
addresses. Never open in the product.
2. **The one thing** - the single capability that matters most to this persona, shown first. A demo
that saves the best part for last loses the room before it arrives.
3. **Their data, or their scenario** - use the prospect's own numbers, names, and workflow. A demo
in a generic sandbox is a product tour, not a demo.
4. **Two supporting beats** - no more. Every extra feature shown dilutes the one thing.
5. **Land it** - restate the outcome in their words, then ask what they would want to see next.
**Talk track types**
| Type | Use when | Length |
|---|---|---|
| Cold-call opener | First voice contact, no context | Under 30 seconds |
| Discovery-to-demo bridge | Moving from questions to showing | Two sentences |
| Feature-to-outcome translation | A rep keeps describing mechanics | One line per feature |
| Competitive displacement | A named competitor is in play | Under a minute, no disparagement |
| Pricing walk-through | Presenting the number | Say the number, then stop |
**Rules for spoken copy**
- Write in the rep's spoken register. If they would not say it out loud, rewrite it.
- Mark where to stop talking. The most common demo failure is narrating past the point where the
prospect wanted to speak.
- No feature named without the outcome attached in the same breath.
- One question at the end, not three.
- Never script a claim the rep cannot defend when asked how they know it.
---
## Will a Rep Actually Use This
Most enablement collateral is made once and never used again. An asset reps do not trust or cannot
find is not an asset, and producing it has a cost: it displaces the version they were already
improvising, which at least fit the conversation.
Every asset ships with:
- **What it replaces.** If it does not replace something, say what it is added to and when in the
cycle it gets used. An asset with no slot in an existing motion will not acquire one.
- **Where it lives.** A path, a link, or a named place. An asset a rep has to ask for is an asset
they will not use on a live call.
- **Who owns it.** A named person, because the next question a rep has about it goes to someone.
- **The trust test.** Would a rep put their own name behind every claim in it? Reps drop collateral
the moment one number gets challenged and they cannot defend it. A single indefensible claim
discredits the whole document.
Diagnostic: if the rep would rather send a short email they wrote themselves than this asset, the
asset is wrong. Ask why, and fix that instead of polishing the layout.
---
## Every Asset Has an Expiry
Enablement assets rot silently, and a stale asset is worse than a missing one because it gets used
with confidence.
| What goes stale | Why it matters | Review trigger |
|---|---|---|
| Pricing on a one-pager or proposal | A rep quotes a price that no longer exists | Any pricing change |
| A named customer in a proof point | The customer may have churned, or never agreed to be named | Quarterly, and on any churn |
| Competitive positioning | Competitors ship and reprice | Quarterly, and on a competitor launch |
| Integration and security claims | The product changed underneath the claim | Any relevant release |
| ROI benchmark inputs | Wage, tool cost, and team-size assumptions drift | Annually |
Each asset carries a **last verified date** and the trigger that forces the next review. Undated
collateral cannot be audited, so it never gets retired.
**Permission to cite is separate from having the number.** Before a customer name appears in
anything a prospect sees, confirm the reference is approved and current. A churned customer used as
a proof point is a live liability: a prospect who checks will find out, and the rep will not know
why the deal cooled.
---
## Common Mistakes Across Asset Types
- Proposals and decks that lead with features instead of the buyer's own stated pain
- ROI calculators with the formula hidden, a rep can't defend math they can't see
- One-pagers that try to cover everything instead of the 3 differentiators that actually matter for this buyer
- Playbooks nobody owns, assign an owner and review quarterly, or it goes stale within two quarters
---
## The Usage Problem, With Numbers
The adoption section above says an asset reps do not use is not an asset. The scale of that is worth
stating, because it reframes what producing collateral is actually for.
| Finding | Figure |
|---|---|
| Marketing content that goes unused by sales | **~65%**, stable for over a decade; some audits above 80% |
| Untouched specifically because reps cannot find it | **~60-70%** |
| Content recreated because nobody could find the original | **~40%** |
| Sellers reporting no easy access to what they need | **~78%** |
| Seller time spent hunting, comparing or revising content | **~10 hours per week** |
**The dominant failure is findability, not quality.** Roughly two thirds of content goes untouched
because it cannot be located, which means the "where it lives" line in the adoption block is not
administrative detail, it is the highest-leverage field on the whole asset. A good one-pager nobody can
find loses to a mediocre one in the rep's own downloads folder, every time.
It also means **the default answer to "we need better collateral" is usually not a new asset.** Before
producing anything, ask what already exists, whether reps can find it, and whether the gap is creation
or retrieval. Producing a new asset into an unfindable library adds to the 65%.
### The 10% that does the work
**Around 50% of all prospect engagement comes from about 10% of enablement content.**
That distribution changes the job from *producing* to *identifying*:
- **Find the 10% before commissioning the next asset.** Ask which pieces reps actually send, unprompted,
and which ones prospects respond to. Those are the templates for everything else.
- **A rep sending the same asset repeatedly is a signal, not a habit.** It is the closest thing to a
usage metric most teams have.
- **Retire aggressively.** An asset nobody has sent in a quarter is not neutral: it dilutes search, adds
to the pile reps are failing to navigate, and makes the 10% harder to find.
- **Ask what the rep currently improvises instead.** The gap between what exists and what they type from
scratch every time is the highest-value asset nobody has built.
Where the user cannot answer which assets get sent, say that measuring it is the first deliverable, ahead
of producing anything new.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |