Index of every page on this site: llms.txt
All skills
deanpeters avatar

/sales-value-narrative

@476ae12
Run it yourself

Build 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.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/sales-value-narrative

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

examplessample-industrial.md

≈794 tokens on demand. Your agent reads this file only when SKILL.md points to it.

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.


## 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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts7d3 checks · Risk SAFE
  • Gen Agent Trust Hub7d

    The skill is a sales enablement tool that helps build value narratives. It is functionally safe and uses good practices like provenance tagging for AI-generated content. Its only concern is the inherent risk of indirect prompt injection from processing user-supplied sales and competitor data.

  • Socket7d

    No alerts

  • Snyk7d

    Risk: LOW · No issues

Signed by skilld at 476ae12. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
argument-hint
[offering, who you sell to, and the alternative you most often lose to]
type
component
theme
strategy-positioning
Other metadata
intent
Give Sales and partners a short story the customer can retell inside their own company, from the cost of staying put to a better outcome, with proof for every claim and a prepared answer for the objections reps actually hear. Hands the one-page competitive card to battle-card-builder.
best_for
[
  "Enabling Sales or partners to explain value to a group of buyers, not one champion",
  "Starting with why change and why now instead of a feature tour",
  "Preparing objection answers from what reps really hear",
  "Giving reps a do-not-say list that protects deals and credibility"
]
scenarios
[
  "Reps open with features and lose to 'we'll just keep what we have'. Build the narrative",
  "Our resellers need a story they can tell in ten minutes. What goes in it?",
  "Write the objection handling for 'too expensive' and 'we'll wait until next budget'",
  "Review our sales deck. I think it's a product tour"
]
estimated_time
30-45 min

README badge

README badge for deanpeters/product-manager-skills/sales-value-narrative