Home/Answers/Value metric
PRICING LAB / Value metric

How to Choose Value metric

Choose Value metric by use case and compatibility first, specs second; test locally when possible.

Updated 2026-11-01About 3 minLocal test
Quick answer

Choose Value metric by use case and compatibility first, specs second; test locally when possible. A value metric should grow with customer value; common ones are seats, usage, API calls, storage or outcomes.

Why it matters

Stacked specs do not guarantee fit for your use case.

Tied to value.

Step by step

  1. Define the outcome customers pay for and choose a value metric that grows with value.
  2. Use real usage data for packaging and price points; do not copy competitors first.
  3. Include payment fees, sales commission, infrastructure and support in margin.
  4. Raise prices in cohorts with exit and grandfather terms.

Common mistakes

  • Cost-plus pricing instead of value.
  • A value metric unrelated to customer value.
  • Free plan gives too much, killing conversion.
  • One-off big price increase without grandfathering/communication.

Checklist

  • Value metric scales with customer value.
  • Package differences are clear and explainable.
  • Margin includes payments/commission/infra/support.
  • Price increases have grandfathering and communication.
  • Pilot and cancel/downgrade data are tracked.

Key facts

  • Tied to value.
  • Predictable/explainable.
  • Scales with customer.

FAQ

How do I choose Value metric?

Choose Value metric by use case and compatibility first, specs second; test locally when possible. A value metric should grow with customer value; common ones are seats, usage, API calls, storage or outcomes.

How long does it take?

Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.

Is data uploaded?

Runs locally and does not upload video/audio; extensions may still read the page.

Source: SaaSPriceLab