From pricing-monetization
Choose the value metric — what you charge per (seats, usage units, records, transactions, outcomes) — the single highest-leverage pricing decision. Reach for this when a product's metric caps growth, when expansion isn't automatic, or before setting any price number. Scores candidate metrics on value-alignment, expansion-with-success, and budget-predictability.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pricing-monetization:value-metric-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The value metric is *what you charge per*. It is the highest-leverage decision in
The value metric is what you charge per. It is the highest-leverage decision in pricing — a right metric makes expansion automatic; a wrong one caps the company forever. Decide it before the number.
A strong value metric is simultaneously:
These trade off. The most value-aligned metric is often the least predictable.
List every plausible per-unit: seats, active users, API calls, GB stored/processed, records/contacts, transactions, monetary volume processed, outcomes (resolved tickets, qualified leads), workspaces/projects. Don't pre-filter yet.
Run each candidate through ../../knowledge/pricing-decision-trees.md §2.
Reject cost proxies. Flag the bill-shock risks. Note which metrics the customer can
game down (e.g. deactivating "active users") — those leak revenue.
The usual resolution: a steady metric for the base + a value-aligned metric for expansion. E.g. price the platform on seats/workspaces (predictable) and the consumption on usage (aligned) — the hybrid pattern. Don't force one metric to do both jobs if they conflict.
"If this product becomes 10× more valuable, does our revenue grow with it?" A metric that answers no caps the business — discard it however convenient it is to bill.
Hand the chosen metric to willingness-to-pay-research to find the price points, then
to packaging-and-tiering to fence the tiers along the metric.
A value-metric recommendation with: each candidate's three-test score, the gaming/bill-shock risks, how the alignment-vs-predictability tension was resolved, and the failure-question result. Name the one metric (or the base+expansion pair) you'd bet the business on.
npx claudepluginhub mcorbett51090/ravenclaude --plugin pricing-monetizationGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.