Value metrics and metering
The value metric is the unit of value that makes Subscription & As-a-Service pricing scalable - if it is measurable, trusted, and aligned to customer value.
500+ cases•35+ industrial clients•Execution-led operating partner
What this page gives you
How to pick a value metric that customers accept and finance teams approve.
How to avoid metrics that look good but fail in real operations.
A practical metering and verification checklist for industrial OEMs.
How to build pricing bands, floors, and caps around the metric.
The most common 'dispute triggers' and how to remove them upfront.
Core concepts
Practical decision logic
Start from customer value - what do they optimise for (uptime, throughput, quality, energy)?
List 3 candidate metrics - include one 'simple' option, not just the perfect one.
Test measurability - can you measure it consistently across customer sites?
Test trust - will the customer accept the measurement method without constant disputes?
Test controllability - can you influence the drivers of the metric?
Choose a primary metric and a secondary 'safety metric' for edge cases.
Define metering method - data source, frequency, failure mode, fallback.
Define verification rules - responsibilities, baselines, exclusions, auditability.
Build pricing structure - bands/tiering, floors, caps, indexation.
Pilot and validate - compare measured vs expected, adjust before scaling.
Common pitfalls
Picking a metric that cannot be measured reliably at customer sites.
Choosing a metric customers do not link to value (procurement blocks it).
Metering that depends on manual reporting - disputes become inevitable.
No fallback rule when data fails - revenue leakage or relationship damage.
Outcome metrics used without control of usage conditions.
Pricing without floors/caps - downside becomes systemic at scale.
Verification rules written too late (legal friction delays deals).
Practical templates and checklists
Value metric quality test
- Is it measurable with high reliability?
- Does it map to customer value and internal KPIs?
- Is it hard to game?
- Is it scalable across sites?
- Can you control enough drivers to stand behind it?
- Can finance model downside exposure?
Metering and verification spec (minimum)
- Metric definition and unit
- Data source(s) and ownership
- Frequency and aggregation rule
- Baseline and normalisation (if needed)
- Exclusions and responsibility boundaries
- Data failure fallback rule
- Audit rights and dispute resolution
Where this shows up in deals
Pay-per-cycle
Cycles captured via controller logs with monthly reconciliation.
Subscription + usage
Base fee plus variable per unit processed with caps.
Uptime SLA
Uptime measured via remote monitoring with defined exclusions for customer misuse.
Related content
Frequently asked questions
Q: What makes a good value metric for industrial As-a-Service pricing?
A: A good value metric has three properties: the customer already tracks and values it (e.g., uptime hours, units produced, cycles completed), you can measure it reliably with existing or affordable instrumentation, and it scales with the value your equipment creates. If the customer does not recognise the metric as meaningful, pricing will always feel arbitrary.
Q: What are the most common value metrics used in industrial subscriptions?
A: The most common are: operating hours (for equipment where availability matters), units produced or processed (for production lines), cycles completed (for discrete manufacturing), and uptime percentage (for critical infrastructure). Some advanced models use composite metrics like cost-per-good-part or energy efficiency ratios.
Q: How do you verify a value metric before putting it in a contract?
A: Run a measurement pilot: install metering, collect data for 60-90 days, and check three things - does the data match the customer's own records, is there enough granularity to resolve disputes, and does variability stay within a range that makes pricing predictable? If any of these fail, simplify the metric or add a floor-and-cap structure.
Q: What triggers disputes over value metrics and how do you prevent them?
A: The most common dispute triggers are: disagreement on measurement method, downtime caused by factors outside the OEM's control being counted against performance, and invoicing based on data the customer cannot independently verify. Prevent these by defining the measurement source, exclusion rules, and a reconciliation process in the contract before signing.
Want to choose a value metric that scales?
Assess fit, execution risks, and the fastest path forward.