deanpeters/Product-Manager-Skills / plugins/pm-deliver/skills/sales-value-narrative
sales-value-narrative
VerifiedBuild a sales value narrative: why change, why now, why us, value by buying-group role, objections, and a do-not-say list. Use when Sales or partners must explain value with claims they can defend.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.8 KB |
| examples/sample-industrial.md | markdown | 3.1 KB |
| examples/sample.md | markdown | 3.2 KB |
| template.md | markdown | 1.7 KB |
template.md
View on GitHub# Sales Value Narrative Template
Unsupported proof stays `[NEEDS SOURCE]`. Quality checks at the bottom.
---
## 1. Scope
**Offering:** · **Sales motion:** · **Alternatives that win (include the status quo):**
**Message house (link or note absence):**
## 2. The story
**Why change** (cost of the status quo, in their terms): · Proof or `[NEEDS SOURCE]`:
**Calculation they can repeat:** [inputs x formula]
**Why now** (trigger events, and how a rep spots them):
**Why us** (from the pillars, with proof):
## 3. Value by role
| Role | Cares about | Value in their terms | Proof they trust | Risk to defuse |
|---|---|---|---|---|
| User | | | | |
| Buyer | | | | |
| Technical evaluator | | | | |
| Finance | | | | |
| Sponsor | | | | |
| Partner (if any) | | | | |
## 4. Objections (collected from reps, partners, win/loss)
| Objection | What may be behind it | Answer (acknowledge, clarify, respond, confirm) | Proof |
|---|---|---|---|
## 5. Trap questions (only where evidence is held)
| Question | Weakness it surfaces | Evidence |
|---|---|---|
## 6. Do-not-say (dated)
| Do not say | Why |
|---|---|
## 7. Cards needed
| Alternative | Card built with battle-card-builder? | As-of date |
|---|---|---|
## 8. Committed copy extras
**Proof to Gather (ranked):** 1. · **Questions to Ask Reps:** 1.
---
## Quality checks
- [ ] Opens with why change, then why now, then why us
- [ ] The status quo is named and priced
- [ ] Value is written per role
- [ ] Every claim is sourced or flagged; nothing invented
- [ ] Objections came from reps, not the product team
- [ ] Traps rest on documented evidence
- [ ] A do-not-say list exists, with a date
- [ ] Tested with two or three reps on real accounts
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |