Individual skill

usage-to-value-map

Method for translating product telemetry into ROI narratives and expansion triggers.

plugins/b2b-saas/skills/usage-to-value-map/SKILL.md

Read pinned source

Source commit 78e0419f4440bcb43bc80127e174ecf5adef1753

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
438
Repository last updated
Apr 3, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Usage-to-Value Map Skill

## When to Use
- Preparing exec readouts showing how product usage ties to business outcomes.
- Prioritizing adoption plays based on feature depth, collaboration, or workflow coverage.
- Equipping sales/CS with quantified value proof for renewal/expansion cycles.

## Framework
1. **Telemetry Layer** – identify key events, feature usage, seat adoption, and integration data.
2. **Value Drivers** – map telemetry to business KPIs (time saved, revenue uplift, compliance risk).
3. **Benchmarking** – compare against cohort medians, champions, or best-in-class customers.
4. **Signal→Play Mapping** – tie usage patterns to recommended plays (exec briefing, enablement, upsell).
5. **Narrative Template** – structure story: context → usage signal → value proof → action.
Back to top