Digital technologies, connected assets, and data-rich customer relationships have made a new generation of pricing models practical in B2B. Instead of charging only for ownership or simple units sold, you can now charge for usage, access, outcomes, or a mix of all three. Done well, these models better align what customers pay with the value they receive and create more predictable recurring revenue. Done poorly, they confuse customers, overwhelm sales, and create billing disputes.
This chapter focuses on three related families of models: dynamic pricing, usage-based pricing, and performance- or outcome-based pricing. We will define each, discuss when they are appropriate, outline the data they require, walk through a step-by-step design and pilot process, and close with guidance on managing customer adoption, complexity, and perceived fairness.
10.1 Defining Dynamic, Usage-Based, and Outcome-Based Pricing
Although these models are often discussed together, it is helpful to distinguish them clearly.
Dynamic pricing in B2B means that the price for a given product or service can change over time or across transactions based on predefined rules and changing conditions. Typical drivers include:
- Demand and capacity utilization (e.g., higher prices when capacity is tight)
- Time and lead time (e.g., rush orders vs. standard orders)
- Customer behavior (e.g., better terms for digital self-service)
- Market signals (e.g., commodity prices, spot rates, competitive benchmarks)
The key is that prices are not fixed; they are responsive to conditions and governed by explicit logic, not arbitrary negotiation. In B2B, dynamic pricing is common in freight and logistics, advertising inventory, industrial gases and utilities, and other capacity-based or spot markets.
Usage-based pricing means charging customers based on how much they use a product or service. Instead of paying a fixed fee regardless of consumption, customers pay per transaction, per user, per device, per GB, per API call, per machine hour, or some other usage metric. There is often a minimum fee or base subscription, but variable usage is the primary driver of revenue.
Outcome-based (or performance-based) pricing ties part of your revenue to the outcomes you help the customer achieve. Examples include:
- A share of cost savings (e.g., energy efficiency solutions priced as a percentage of energy cost reduced)
- A share of revenue uplift (e.g., marketing services tied to incremental sales)
- Payment contingent on uptime or performance (e.g., availability guarantees with penalties and bonuses)
Most real-world implementations mix these ideas. A common structure is “fixed plus variable”: a base fee for access or readiness, plus a usage-based or performance-based component. Dynamic elements may then adjust prices or thresholds based on demand, cost, or contract conditions.
Two characteristics distinguish these models from traditional fixed-price approaches:
- Revenue scales more directly with customer activity and realized value.
- Risk is shared differently between supplier and customer; you may take on more volume or performance risk in exchange for upside potential and stickier relationships.
10.2 When These Models Are Used (SaaS, Services, Assets, Platforms)
Dynamic, usage-based, and performance-based models are most attractive when four conditions hold: value varies significantly across customers, usage can be measured, ongoing relationships matter, and customers can understand the link between what they pay and what they get.
They are particularly common in several B2B environments.
Software-as-a-Service (SaaS) and digital platforms.
SaaS providers frequently charge per user, per seat, per transaction, per active account, or per capacity metric (e.g., data volume, compute units). Platforms may charge per listing, per booking, per shipment, or per transaction value. These structures let small customers start small and scale, while larger customers pay in line with the value they extract.
Services and managed solutions.
In consulting, business process outsourcing, IT services, and managed operations, outcome-based elements such as SLAs with bonuses and penalties or gainshare on savings are often layered on top of base fees. Usage-based elements (per ticket, per incident, per device managed) help align price with workload.
Asset-intensive businesses and “as-a-service” models.
Equipment manufacturers and industrial firms increasingly explore “equipment as a service,” charging per hour of operation, per ton processed, or per part produced rather than only for upfront capital sales. Maintenance contracts may be tied to uptime or throughput. These models can reduce customers’ capital expenditure and create recurring revenue streams.
Networked and capacity-constrained businesses.
In logistics, air cargo, container shipping, warehousing, and energy, dynamic pricing is used to manage demand and capacity. Prices can vary by time, lane, load factor, or flexibility of service. When combined with contractual floors and ceilings, these mechanisms help both sides manage volatility and plan more effectively.
Data, analytics, and API businesses.
Providers of data, analytics, or API-based services often charge based on the number of calls, queries, or data volume consumed. This enables small customers to start at low spend and grow over time, while larger customers pay more in line with their usage and derived value.
However, these models are not universally appropriate. They tend to be less effective when:
- Usage is hard to measure, audit, or agree on
- The economic value of usage is unclear or very low
- Transaction sizes are tiny and the cost of metering and billing exceeds the benefit
- Customers prioritize simplicity and budget predictability over precise value alignment
In those cases, simpler tiered subscriptions or fixed-fee contracts, perhaps with periodic review, may be better options.
A useful filter is to ask, by offering and segment: does a variable or performance-based structure significantly improve alignment of price to value and expand the feasible “win–win” zone, after accounting for added complexity? If not, resist the temptation to add sophistication for its own sake.
10.3 Data Required: Usage Telemetry, Performance Metrics, SLAs
All three model types depend on credible, timely data. Without it, you cannot bill accurately, defend your invoices, or improve your design. Three data domains matter most: usage telemetry, performance metrics, and contract or SLA definitions.
Usage telemetry is the record of how customers consume your product or service. Depending on the business, this might be:
- API calls, page views, logins, or events in a SaaS or platform environment
- Machine hours, cycles, or throughput from connected equipment
- Tickets, incidents, or cases processed in a managed service
- Shipments, kilometers, or container moves in logistics
Effective telemetry has a few characteristics:
- It is automatically captured, not manually compiled.
- It is tied to specific customers, contracts, or billing accounts.
- It is stored at sufficient granularity to support audits and dispute resolution.
- It can be summarized into the metrics you plan to bill on (e.g., “billable API calls” as a subset of all calls).
Performance metrics capture the outcomes you are promising. Depending on your model, these could include:
- Uptime or availability percentages for systems or equipment
- Response times or resolution times for service tickets
- Energy consumption per unit of output
- Defect rates, yield, or scrap
- Conversion rates, leads generated, or revenue uplift
For outcome-based pricing, it is critical to agree on:
- Baselines: what performance would have been without your solution
- Measurement methods and data sources
- Attribution rules: how to disentangle your impact from other factors
- Time windows for measurement and payout
Contract and SLA data tie telemetry and performance to commercial terms. You need structured records of:
- Contracted price metrics and levels (per-unit rates, thresholds, tiers)
- Included vs. billable usage (base allowances, overage rules)
- Performance targets, bonuses, and penalties
- Caps, floors, and sharing rules for outcomes (e.g., maximum variable payout)
From a systems perspective, this typically means integrating:
- Operational systems that generate usage and performance data
- Contract repositories or CPQ systems that store commercial terms
- Billing systems that calculate charges and generate invoices
- Analytics tools that monitor model performance and unit economics
If you do not yet have perfect data, you can still move forward in stages: start with simpler metrics, manual samples, or conservative approximations, while building more automated telemetry and contract integration over time.
10.4 Step-by-Step Guide to Designing and Piloting New Pricing Models
Designing dynamic, usage-based, or outcome-based models is as much about change management as it is about math. A structured process reduces risk and increases the odds that your new model will stick.
Step 1: Select the right scope.
Identify a manageable scope where the benefits are likely to be high and internal resistance manageable. Typical candidates include a new product or service rather than your entire legacy portfolio, a clearly defined segment (e.g., mid-market SaaS customers, a specific equipment line), or a subset of new customers or renewals, not all existing contracts at once.
Step 2: Clarify the value story and objectives.
For the chosen scope, articulate how customers create value using your solution, why a variable or performance-linked model is more appropriate than a fixed one, and what you want to achieve: higher adoption, better alignment, more recurring revenue, differentiation, or share gain.
Step 3: Choose candidate pricing metrics.
Brainstorm potential metrics for usage or outcomes, then evaluate them against four tests:
- Alignment: Does the metric correlate strongly with value for the customer?
- Measurability: Can you measure it reliably and at reasonable cost?
- Controllability: Do you influence it meaningfully, especially for outcome metrics?
- Simplicity: Can customers and sales easily understand and forecast it?
Narrow down to one primary metric and, at most, a small number of secondary metrics.
Step 4: Design price structures and scenarios.
Using your chosen metric, decide on the mix of fixed and variable components (for example, a base subscription plus per-unit fee). Consider volume tiers, thresholds, or committed minimums. For dynamic elements, define how prices vary with load, time, or other drivers.
Then model economics under realistic scenarios, for customers at different sizes and usage patterns and under adverse conditions such as lower-than-expected usage or higher-than-expected performance payouts. Check for both customer ROI and your own unit economics.
Step 5: Translate into concrete offers and contracts.
Convert structures into clear offer configurations and commercial packages (such as good–better–best plans), standard contract language including definitions, baselines, and dispute mechanisms, and CPQ and billing rules that can actually be implemented.
Step 6: Prepare sales and customer-facing materials.
Before you go to market, build simple calculators that let sales show “what you pay” under different usage scenarios. Create visual comparisons with old models (for example, “under typical usage, your spend would be within this range”) and draft talking points for common objections: “we want budget certainty,” “we do not want to be penalized for success,” “this seems complex.”
Step 7: Pilot with selected customers.
Choose a limited set of customers (or a region, channel, or product variant) for a controlled pilot. Prefer customers who are open to innovation and where you have strong relationships. Collect both quantitative data (usage, revenue, margin) and qualitative feedback (perceived fairness, understanding, satisfaction). Monitor internal experience: sales comfort, billing accuracy, and operational load.
Step 8: Iterate and refine.
Based on pilot results, adjust metrics, thresholds, and price levels where outcomes were out of range. Simplify structures that caused confusion or billing errors. Clarify contract language and sales messaging. Only after you see stable, acceptable performance in the pilot should you scale up to broader segments and legacy migrations.
10.5 Managing Customer Adoption, Complexity, and Perceived Fairness
The technical design of a new pricing model is only half the battle. Customer adoption depends on whether the model feels understandable, predictable, and fair.
Managing perceived complexity.
Customers and sales teams have limited bandwidth. They will resist models that feel opaque or hard to forecast, even if those models are theoretically superior. To keep complexity in check:
- Limit the number of price metrics and tiers.
- Use intuitive metrics closely tied to how customers already think about their business.
- Provide simple tools and examples that show typical bills under different usage levels.
- Avoid frequent parameter changes; if you adjust, do it in structured, predictable ways.
Addressing budget predictability.
Many customers, especially in larger organizations, need to plan budgets annually and dislike open-ended variable charges. You can mitigate this by:
- Offering hybrid models: a base committed spend with variable overage, or a “cap and collar” on total spend.
- Providing forecast ranges and budget planning support based on historical or benchmark usage.
- Allowing customers to choose between more variable but potentially cheaper options and more fixed, predictable options.
Ensuring fairness and trust.
Outcome-based and highly dynamic models can trigger concerns about being “gamed” or exploited. To build trust:
- Be transparent about formulas, indices, and measurement methods; avoid black-box algorithms where possible.
- Use conservative baselines and attribution rules that err on the side of the customer when causality is ambiguous.
- Share data regularly so customers can verify that calculations match agreed rules.
- Design sharing rules that feel reasonable: customers should clearly gain more net value than they pay you, even when you earn well.
Managing transition for existing customers.
Shifting installed customers from traditional pricing to new models is often more sensitive than launching them with new customers. Good practices include starting with new customers and new use cases, building a track record before proposing changes to the base; offering side-by-side comparisons (“if you stayed on the old model vs. moving to the new model, here is the expected impact given your usage”); using migration incentives that make the switch attractive while protecting long-term economics; and allowing some customers to remain on legacy models where change costs and relationship risks outweigh the benefits.
Aligning internal incentives and metrics.
Finally, internal alignment matters as much as customer acceptance. Adapt sales compensation so that reps are not penalized for selling models where revenue ramps over time instead of being front-loaded. Update performance dashboards to focus on annual recurring revenue, net revenue retention, and unit economics, not just upfront bookings. Train finance, operations, and customer success teams to understand and support the new model, including how to monitor churn risk and upsell opportunities.
Dynamic, usage-based, and performance-based pricing models are powerful tools in the B2B pricing toolkit. They are not right for every situation. But when thoughtfully designed, grounded in data, and introduced with careful change management, they can create stronger alignment between you and your customers and unlock new sources of profitable growth.
