pricing-value-metric
Pick the right value metric (price unit) for B2B pricing — per-seat, per-API-call, per-active-record, per-outcome, per-revenue-processed, hybrid. Diagnoses the operator's current metric vs the unit that scales with customer success, identifies gaming + misalignment failure modes, and outputs a recommended metric switch with the metric-shift case study reservoir. Loaded by the main pricing skill when the operator asks about per-seat vs per-X, value metric, price unit, or "should I change how I charge?"
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- pricing-value-metric
- license
- MIT
- description
- Pick the right value metric (price unit) for B2B pricing — per-seat, per-API-call, per-active-record, per-outcome, per-revenue-processed, hybrid. Diagnoses the operator's current metric vs the unit that scales with customer success, identifies gaming + misalignment failure modes, and outputs a recommended metric switch with the metric-shift case study reservoir. Loaded by the main pricing skill when the operator asks about per-seat vs per-X, value metric, price unit, or "should I change how I charge?"
- allowed-tools
- Read - Write
- user-invocable
- false
02 资源文件 1
- 参考文档skill-report.json22.1 KB
03 SKILL.md 正文
Pricing Value Metric — sub-skill
The price-unit engine. The right value metric scales naturally with customer success — your revenue grows with their growth, automatically, without re-negotiation.
Activation
Routed here when operator says:
- "Per-seat vs per-X"
- "Should I change my value metric?"
- "Should I switch to outcome pricing?"
- "Customers are gaming our metric"
- "Our top customer pays the same as our median customer"
The metric catalog
| Metric | Best for | Failure modes |
|---|---|---|
| Per-seat | Tools used continuously by named users (project mgmt, design, CRM) | Login sharing if value-per-seat is low; doesn't scale with usage |
| Per-API-call | Programmatic infrastructure (data APIs, search APIs, AI APIs) | Noisy call counts; buyer can't predict bill; rate-limiting tension |
| Per-active-record | Data platforms (contacts, customers, deals, leads) | "Active" definition disputes; archived records leak revenue |
| Per-event / per-transaction | Notification, payment, messaging | Bill volatility; bursty traffic = bursty bills |
| Per-MAU / per-MTU | End-user-facing analytics, CDPs | Passive users inflate; bot-user definition disputes |
| Per-outcome | Services + outcome-driven SaaS (closed deals, hired candidates) | Attribution disputes; bounded-liability complexity |
| Per-revenue-processed | Embedded fintech, marketplaces | Customer-revenue volatility; pricing-to-bill cadence mismatch |
| Per-environment / per-workspace | DevOps, infra | Doesn't scale with team; encourages multi-tenant abuse |
| Hybrid (base + variable) | Mixed-mode SaaS (CRM with seats + automation runs) | Two metrics to communicate; pricing page complexity |
The right-metric rubric
A value metric is RIGHT if it satisfies all 4:
- Scales naturally with customer success — their growth in what-they-care-about = their bill grows automatically.
- Is easy to count + verify — no audit disputes, no quarterly "what counts as X" debates.
- Aligns with how the buyer talks internally — matches their P&L line item or their team's reporting language.
- Doesn't create a volume-vs-revenue tension for their team — they don't have to fight you to use you more.
If any fail, the metric leaks margin (or churn).
The metric-shift case study reservoir
Common shifts and their typical outcomes:
| Shift | Typical outcome | Risk |
|---|---|---|
| Per-seat → per-active-record | 30-100% ACV expansion on top decile, lower churn | Mid-tier customers may shrink at first |
| Per-API-call → per-outcome | 50-200% ACV expansion on top decile | Outcome definition + attribution complexity |
| Per-seat → per-event | Better volume scaling, more predictable | Bursty traffic = bursty bills |
| Flat → consumption | Stronger product-market alignment | Loss of revenue predictability |
| Consumption → flat | Predictable revenue | Caps top-customer expansion |
| Single-metric → hybrid | Captures both seat + usage | Doubles communication complexity |
When recommending a shift, always cite which of the 4 right-metric criteria is currently failing and which the new metric satisfies.
Workflow
1. Load inputs
From brand-config.json:
pricing.valueMetric.unit— current metricpricing.currentTiers— current tier structurecustomer.psps[]
Also gather (ask if not in config):
- Top-10% customer billing vs median (do they pay 5x? 15x? 50x?)
- Documented gaming behaviors (shared logins, single API key for the org, etc.)
- Quarterly revenue volatility (predictable / cyclical / spiky)
2. Diagnose current metric
Run the 4-criterion check:
Criterion 1 — Scales with success?
Current: {pass / fail with example}
Criterion 2 — Easy to count + verify?
Current: {pass / fail}
Criterion 3 — Matches buyer's internal language?
Current: {pass / fail}
Criterion 4 — No volume-vs-revenue tension?
Current: {pass / fail}
Failures: {N of 4}
3. If all 4 pass — recommend HOLD
The metric is right. Don't tune the metric; tune tier prices or
packaging instead. Route to pricing-contrast-set or
pricing-pocket-waterfall.
4. If 1+ fail — diagnose shift candidates
For each failed criterion, identify a candidate metric that addresses it:
- Failed criterion 1 + value scales with usage → consumption metric
- Failed criterion 1 + value scales with outcomes → outcome metric
- Failed criterion 2 + gaming present → metric with cleaner counter
- Failed criterion 3 + buyer talks in dollars-processed → revenue-processed
- Failed criterion 4 + buyer fights to use less → fixed-base + variable cap
5. Output the recommendation
Value-Metric Diagnosis — {company}
─────────────────────────────────────────────────────────────────
CURRENT METRIC: {unit + price}
4-CRITERION CHECK:
1. Scales with success: {pass/fail + reason}
2. Easy to count: {pass/fail}
3. Matches buyer language: {pass/fail}
4. No volume-vs-revenue tension: {pass/fail}
TOP CUSTOMER vs MEDIAN: {Nx}
GAMING OBSERVED: {description or "none documented"}
RECOMMENDATION: {HOLD / SHIFT to {new metric}}
IF SHIFT:
New metric: {unit}
Reason: {which criteria it satisfies that current fails}
Predicted top-decile ACV impact: {range from case-study reservoir}
Risk: {what could go wrong}
Migration path: {grandfather existing / new logos only / pilot}
Test design: route to pricing-tribunal (value-metric shifts are
Strategic-tier under the risk taxonomy — never ship blind)
Self-check
- [ ] 4-criterion check completed for current metric
- [ ] Top-decile vs median ratio captured (or flagged as data gap)
- [ ] Gaming behaviors named specifically (not "we think they game it")
- [ ] Recommendation is HOLD or SHIFT — not "try a few"
- [ ] If SHIFT: case-study reservoir cited for predicted impact range
- [ ] If SHIFT: routed to pricing-tribunal for test design
Reference
../../pricing/references/value-metric-catalog.md— full metric catalog../../pricing/references/pricing-framework.md— value-metric in context../pricing-tribunal/SKILL.md— value-metric shifts are Strategic-tier; must tribunal
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.