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 |
examples/sample-industrial.md
View on GitHub# Sales Value Narrative Example: Industrial
**Offering:** NFA-500 retrofit controller (Northfield Automation)
**Sold to:** plant engineering and maintenance; buyers are procurement and the plant manager; 8 partners
**Alternatives that win:** "our current supplier is fine," and keeping the NFA-200 running
**Why this example exists:** the status quo here is a *working machine*, so the why-now is a
supportability cliff, and the narrative must reach procurement and finance, not just engineers.
---
```markdown
## Narrative: NFA-500
**Why change**
The NFA-200 works. The cost is what happens when it stops: replacement parts in six to eight
weeks as stock thins, and the people who can program it are retiring. Cost of staying put =
hours of downtime per failure x cost per hour x expected failures per year (customer's numbers).
`[NEEDS SOURCE]` for failure rates; use the customer's maintenance logs.
**Why now**
Triggers: spare-parts coverage and service contracts for the NFA-200 base run to 2028; a
planned shutdown window this year; a retirement of the one engineer who knows the program; a
customer audit asking for a support plan.
**Why us**
Upgrade the line without stopping it: a shift, not a shutdown; connected fault warning; your
programs come with you (import tested, report T-114). Other pillar proof `[NEEDS SOURCE]`.
## Value by role
| Role | Cares about | Value | Proof |
|---|---|---|---|
| Maintenance engineer | Programs and wiring they trust | Imports existing programs | T-114 |
| Plant manager | Output, no lost weekends | Swap in a shift | Pilot install times `[NEEDS SOURCE]` |
| Procurement | Supplier risk, terms | Parts and service in six countries; service through 2028 | Service agreement terms |
| Finance | Payback | Avoided downtime vs project cost | Repeatable calculation |
| Distributor | Margin, stocking | Bracket kit keeps installs predictable | Partner terms |
## Objections
| Objection | Behind it | Answer |
|---|---|---|
| "Our current supplier is fine" | No trigger to move | "Is parts coverage on your current unit confirmed past 2028? Let's check together." |
| "Price" | Over budget, or a competitor's lower quote | Clarify; compare total cost of ownership, including downtime avoided |
| "Will it integrate with what we have?" | Technical evaluator's fear | Walk through program import and the bracket kit; offer a site survey |
| "Is the connected tier a cybersecurity risk?" | IT/OT security | Share architecture note (`[NEEDS SOURCE]`: security review in progress) |
## Do-not-say (dated Apr 15)
- "Drop-in replacement" (it needs a different bracket)
- "Most reliable retrofit controller" (no comparative data)
## Cards needed
Status quo (keep the NFA-200 running) first; then the competitor named in 3 of 8 lost deals.
```
## What to learn from this
- **"Drop-in replacement" is on the do-not-say list** because the bracket differs. One careless
phrase would turn an installation visit into a complaint.
- **The security objection has no answer yet,** and the narrative says so instead of improvising.
- **Procurement and finance each get their own value block.** They decide, and they never see the demo.
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 |