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

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

Sales Value Narrative Example: SaaS

Offering: Route Optimizer (Fieldlight add-on) Sold to: service companies with 50-300 technicians; direct sales plus resellers Alternative that wins most: "Our dispatchers manage fine in spreadsheets and a whiteboard."

Why this example exists: the first draft opens with features. The rebuild opens with the cost of staying put, and shows that for a SaaS add-on "why now" is often a renewal date or a busy season.


## Draft critique (first)
Opens with "Fieldlight is the leading field service platform with 11 years..." and a feature tour.
No status quo, no why-now, one value statement for everyone.

## Narrative: Route Optimizer

**Why change**
Every time a job runs long or a rush call comes in, a dispatcher rebuilds the day by hand. The
cost is hours of dispatcher time and the jobs that slip. Calculation to repeat with their numbers:
reschedules per day x minutes each x working days = dispatcher hours per month. `[NEEDS SOURCE]`
for any benchmark; the customer supplies their own.

**Why now**
Triggers a rep can spot: peak season starting in 8-10 weeks; adding technicians (the board gets
harder to hold in one head); a dispatcher leaving; a missed-SLA complaint. Ask: "When did you last
rebuild the whole day, and who was on the phone?"

**Why us**
Pillars from the message house: rush calls fit without wrecking the day; right tech first time; tomorrow's plan tonight. Proof: 14-account pilot, `[NEEDS SOURCE]` until results are pulled.

## Value by role
| Role | Cares about | Value | Proof |
|---|---|---|---|
| Dispatcher | Not dreading rush calls | Reschedule in seconds | Pilot reschedule time `[NEEDS SOURCE]` |
| Ops manager | Jobs per tech per day | Fewer repeat visits | First-visit fix rate `[NEEDS SOURCE]` |
| CFO | Payback | Hours saved vs add-on price | Repeatable calculation |
| IT / security | Data handling | Technician location data handled under the existing DPA | DPA addendum (Legal, in review) |
| Reseller | Margin, easy demo | Five-minute demo, add-on margin | Margin sheet |

## Objections
| Objection | Behind it | Answer | Proof |
|---|---|---|---|
| "Spreadsheets work fine" | They don't see the cost | "Fair. How many times last week did you rebuild the day? Let's price it with your numbers." | Calculation |
| "Too expensive" | Over budget / no belief in savings | Clarify which, then show their hours saved vs price | Calculation |
| "We'll wait until next budget" | No trigger | "Peak season starts in 9 weeks. What does one bad week cost you?" | Their numbers |
| "Is technician GPS data safe?" | Privacy fear | Walk through the DPA addendum | Legal-approved text |

## Do-not-say (dated Jun 1)
- "Smartest scheduler on the market" (no basis)
- "Reduces drive time by X%" (pilot not pulled; do not quote until it is)

## Cards needed
Status quo (spreadsheets) first; then the one competitor that appears in 4 of the last 10 deals.

What to learn from this

  • The first card is for "do nothing," because that is who wins most deals.
  • A do-not-say entry protects a claim that isn't ready. The pilot number is a promise to keep, not a number to quote.
  • The calculation hands the customer the math, so the champion can defend it to their CFO.

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