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

/buying-journey-enablement

@476ae12
Run it yourself

Map how a buying group buys, then assign the enablement asset for each stage and role, for direct sales and partners. Use when Sales has a pile of assets and customers still stall.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/buying-journey-enablement

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

examplessample-industrial.md

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

Buying Journey Enablement Example: Industrial

Offering: NFA-500 retrofit controller (Northfield Automation) Motions: direct to large plants; 8 partners (distributors and one integrator) Evidence: win/loss on 8 lost deals; interviews with 3 partners

Why this example exists: the group is larger, the specification is often written by an outside integrator, and partners do most of the selling. The gap sits at requirements building, where the spec is written around a competitor.


## Journey map

| Buying job | Roles active | Needs to move forward | Stall (checked / hypothesis) | Asset |
|---|---|---|---|---|
| Problem identification | Maintenance engineer, plant manager | See the cost of the aging controller | Hypothesis | Status-quo checklist (build) |
| Solution exploration | Maintenance engineer, integrator | Learn that a shift-long retrofit exists | 3 of 8: never considered retrofit | Application note, partner explainer |
| Requirements | **Integrator**, technical evaluator | Spec text and standards summary | **5 of 8 lost: spec named a competitor** | **Spec text + standards summary (missing)** |
| Supplier selection | Procurement, plant manager | Comparable offer, TCO | 2 of 8: unlike-for-like comparison | TCO sheet, battle card |
| Validation | Maintenance engineer | Reference at a similar plant | 3 of 8: no reference in their industry | Reference case (one, permission pending) |
| Consensus | Plant manager, finance | Payback and shutdown risk | Hypothesis | Business-case template (build) |

## Direct vs partner
Distributors: short sales guide, demo unit access, bracket-kit stocking plan, margin sheet.
Integrators: spec text, I/O mapping guide, program import tool, early access to firmware. Direct
team: full narrative, site survey process, battle cards.

## Training and certification
Sales level (half a day: narrative, top objections). Technical level (two days: configure,
install with the bracket kit, commission; **tested on a demo rig**). Service level for partners who
commission. Certified partners are listed, get lead sharing, and a demo unit. Recertify at each
major firmware release.

## Feedback loop
Partner managers log objections and hotline questions; monthly review for six months with Sales,
Service, and product; assets updated; a short "what changed" note to partners.

## Missing assets (ranked)
1. Spec text and standards summary for integrators (5 of 8 lost deals)
2. Business-case template for the plant manager and finance
3. Second and third reference cases (permission needed)

## Stall hypotheses to check
1. Is "no reference in their industry" a real blocker or an excuse? Call two lost accounts.

What to learn from this

  • The biggest gap is a role the team doesn't sell to. The integrator wrote the spec; no asset served them.
  • Partners get a different toolkit, not a shorter one. Distributors need stocking and margin; integrators need spec text.
  • Certification is tested on a demo rig. Attendance alone doesn't commission a controller.

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

    This skill provides a structured workflow and templates for mapping customer buying journeys and aligning sales assets. It consists entirely of Markdown instructions and examples with no executable code, network operations, or access to sensitive system resources.

  • 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 buys it, and how you sell: direct, partners, self-serve]
type
workflow
theme
strategy-positioning
Other metadata
intent
Enable the buying, not only the selling: map the buying jobs a group must complete, what each role needs at each stage, and the one asset that meets it, then set what partners need, how they are trained and certified, and how field feedback keeps the toolkit current. Fewer, better assets.
best_for
[
  "Building a sales enablement toolkit around how customers actually buy",
  "Finding where target accounts stall and which asset is missing",
  "Separating what direct sales, resellers, and integrators each need",
  "Cutting a library of assets nobody uses"
]
scenarios
[
  "Deals stall after the demo. Where in the buying process are we losing them?",
  "We have 60 sales assets. Which stage and role does each serve?",
  "What do our distributors need that our direct reps don't?",
  "Set up partner training and certification for the NFA-500 launch"
]
estimated_time
45-90 min

README badge

README badge for deanpeters/product-manager-skills/buying-journey-enablement