28 metering and usage-event data statistics that define modern revenue design


Market data and pricing benchmarks revealing how AI agents are transforming billing models, cost structures, and revenue design for software companies
AI agents have moved from experimental pilots to permanent line items in enterprise software budgets, and pricing them has become one of the most complex challenges in modern software monetization. Unlike traditional SaaS products with predictable seat-based models, AI agents consume variable compute resources, process unpredictable token volumes, and increasingly bill against outcomes that resist simple per-unit measurement. Companies building AI-powered products need usage-based billing infrastructure capable of handling this complexity while maintaining the financial accuracy that enterprise customers demand.
The clearest picture of current practice comes from Orb's 2026 study of 80 AI agent companies, supplemented by Deloitte's 2026 SaaS predictions and Stripe's 2025 pricing research. Orb analyzed 80 AI agent companies at a 90% confidence level. Together the sources show a market that has already consolidated around hybrid monetization, with the year-over-year numbers now moving only incrementally.
Orb's 2026 research found that 95% of the 80 AI agent companies studied combine multiple pricing mechanisms rather than relying on a single model. Hybrid is no longer an emerging strategy; it is the operating norm, and single-model billing systems are now the constraint rather than the simplification.
Usage-based pricing appears in 91.3% of the companies in Orb's 2026 sample, up from 83.3% in 2025. Consumption has effectively become the default variable component of AI agent monetization, which makes accurate, real-time usage metering a prerequisite rather than an optimization.
Subscriptions have not disappeared. 71.3% of the companies studied retain a subscription element, up from 62.1% in 2025, typically as a platform or access fee that anchors predictable revenue underneath variable consumption.
Among companies that use subscriptions, 94.7% pair them with usage-based pricing. The standalone seat subscription is close to extinct in the AI agent category, replaced by a base plus consumption structure.
Despite the volume of commentary, outcome-based pricing sits at just 3.8% in Orb's 2026 sample, down slightly from 4.5% in 2025. Orb attributes the gap to instrumentation rather than appetite: defining, measuring, and attributing outcomes reliably is hard, and most legacy billing infrastructure was not built for it.
Within Orb's own year-over-year series, hybrid pricing moved from 92.4% in 2025 to 95% in 2026, a small step because the model was already near saturation. Stripe's 2025 research found 56% of AI company leaders blending subscription and usage-based fees across a broader population of AI companies, so the two figures are not points on one line, and the 56% number should no longer be cited as the current AI agent benchmark.
Deloitte's 2026 technology predictions cite survey data showing that 83% of AI-native SaaS companies offered usage-based pricing. Companies born after the shift are not retrofitting consumption billing; they start with it.
Deloitte, citing Gartner, projects that by 2030 at least 40% of enterprise SaaS spending could move toward usage-based, agent-based, or outcome-based models. This is the single most consequential number for revenue design teams, because it reprices a large share of the addressable budget.
The hardest question in AI agent pricing is not how much to charge but what to charge for. The market has converged on a wider set of billable units than traditional SaaS ever required.
Deloitte documents that AI monetization now spans actions and tasks, compute, API calls, tokens, duration, or combinations of those measures. A single vendor may run several of these simultaneously across different products and customer tiers.
Orb's 2025 analysis of AI agent pricing notes that agent activity is naturally represented by events such as calls, tokens, jobs, documents, or leads. Choosing the event is the pricing decision; everything downstream, from rate cards to invoices, inherits that choice.
Orb's 2026 research identifies effort-based pricing, where compute time, number of steps, or task complexity become the value and usage measure. This sits between raw consumption and pure outcomes, and it fits agentic workloads where a single request may trigger long, variable execution chains.
Gorgias states that its AI Agent is not billed by seats, messages, or tokens, but by fully resolved interactions. Naming the metrics it does not bill is itself a positioning move, signaling that the customer pays only for completed work.
Salesforce sells Flex Credits at $500 per 100,000 credits, with one Agentforce action consuming 20 credits, or $0.10. Credits let a vendor price wildly different actions on one scale, which is why prepaid credit and token packages have become standard components of AI rate cards.
Deloitte documents flat-fee, per-agent, or digital worker pricing as one of several emerging models. It has not disappeared, but it now typically appears as one rail in a hybrid structure rather than as the whole commercial model, though no market-wide monthly benchmark range for it is well established.
Where outcome pricing does exist, the published mechanics are more precise than the summary coverage suggests. These figures come from vendor documentation rather than secondary aggregation.
Intercom's Fin documentation prices a resolution at $0.99, alongside procedure handoffs and disqualifications, for Fin over chat and email. The unit is the outcome, not the conversation, the message, or the token.
Intercom does not price all outcomes identically. Its documentation lists $0.99 for several outcome types and $9.99 for qualification, a roughly tenfold spread that reflects differing commercial value. Outcome pricing is therefore a rate card, not a single number.
Intercom charges at most one outcome per conversation. Caps of this kind protect customers from compounding charges inside a single interaction, and they have to be enforced at the metering layer rather than at invoice time.
Intercom does not charge when an eligible outcome is not achieved. That single rule is what makes outcome pricing commercially credible, and it forces the vendor to define success precisely enough to be auditable.
Gorgias prices its AI Agent at $0.90 per resolved interaction on most plans and $1 on Starter. The billable unit is a resolved interaction rather than a conversation, and that distinction matters for how usage is metered.
Zendesk introduced automated resolution tiers on May 18, 2026. Automated resolutions are the unit used to calculate and bill AI agent usage, accounts are credited with a resolution allowance that those resolutions draw down, and the tiers are designed so customers do not overpay for straightforward tasks. This is a shift from the earlier framing of a flat overage bolted onto seat pricing.
Under Zendesk's tiers, an assisted escalation and a contained resolution do not count against the resolution allowance. A verified resolution is counted only after a 72-hour window with no customer follow-up, once a large language model evaluates the conversation and confirms the request was satisfactorily resolved. Billing gated on automated verification is a meaningful step beyond charging for any contained conversation.
Salesforce's $2 per conversation metric remains available, but its 2025 packaging update introduced Flex Credits and multiple consumption and buying models. The trend is not the $2 price point; it is the deliberate move from one metric to a portfolio of consumption rails within a single product.
Outcome and resolution pricing only works if the underlying cost curve cooperates. Analyst projections suggest it may not, indefinitely.
Gartner predicts that generative AI cost per resolution for customer service will exceed offshore human agent costs by 2030, with cost per resolution exceeding $3, higher than many B2C offshore human agents. Vendors publishing sub-$1 resolution prices today are pricing against a cost base that may not stay where it is.
Gartner cautions that returns on AI customer service investments are far from guaranteed and that full automation will be prohibitively expensive for most organizations, expecting leading organizations to use AI to drive customer engagement rather than to cut costs. For vendors, that erodes deflection-and-savings as the anchor for a price and shifts the justification toward engagement, retention, and lifetime value.
The evidence is consistent across sources: AI pricing set at launch does not survive contact with real usage.
Stripe found that among AI businesses charging for usage, 92% subsequently changed their pricing. Repricing is the expected case, not the exception, which makes the cost and latency of a pricing change a competitive variable.
Stripe's pricing framework treats post-launch iteration as a structural feature of AI products rather than a sign of a mistake, because early usage data is the strongest input available for calibrating rates against real consumption patterns.
Orb's 2026 research frames AI agent pricing as an ongoing system rather than a single packaging exercise. Companies that can version, simulate, and roll out pricing changes continuously hold a structural advantage over those that treat pricing as a launch artifact.
Orb's 2026 study identifies technical complexity, operational friction, and pricing knowledge gaps as the practical limits on pricing execution. The bottleneck is rarely the strategy; it is the systems and workflows required to run it.
Orb's 2025 analysis emphasizes testing pricing against actual usage data before rollout. Simulating a proposed rate card against historical events turns repricing from a revenue gamble into a modeled decision.
Variable consumption creates variable bills, and enterprise buyers will not accept unbounded exposure. Guardrails have become part of the pricing model itself.
Orb identifies caps, pooling across teams, seasonal overage protections, and credit bundles that roll over as the mechanisms that make consumption pricing acceptable to buyers. These are commercial terms with billing consequences, and each one adds an aggregation rule the billing system must enforce.
The dominant structure combines a base platform fee with variable usage charges. The base fee funds predictable delivery and gives finance a revenue floor; the variable component captures expansion as consumption grows.
Orb stresses defining billable outcomes and attribution rules precisely enough for customers to verify them. When the invoice line is an outcome rather than a unit of input, the customer's ability to reconstruct the charge from event history becomes a commercial requirement.
Prepaid credits and token packages let buyers commit budget in advance and give vendors cash and forecastability. Managing drawdown, expiry, and top-ups correctly is a billing engineering problem, not a spreadsheet exercise.
Spend controls with real-time monitoring, configurable thresholds, alerts, and workflow triggers address a leading buyer objection to consumption pricing: bill shock. Vendors that cannot show a customer their spend in real time struggle to sell variable pricing into procurement.
Threshold billing invoices when accrued usage crosses a defined level rather than waiting for a calendar boundary. For high-velocity AI consumption, this reduces credit exposure and smooths cash collection.
AI rate cards increasingly vary by dimension: model version, region, and feature set. Dimensional pricing is what allows a vendor to pass through materially different underlying costs without maintaining a separate product for each combination.
Pricing strategy is only as good as the system that executes it. In AI agent monetization, the metering and finance layer has become part of the pricing model rather than a downstream reporting concern.
A preserved raw usage event layer is what makes outcome billing defensible. Event-level history can support auditability, corrections, and finance workflows, and it is what lets a vendor reconstruct why a specific outcome was billed.
Orb documents backdating price changes and backfilling missing events, with invoices and credit ledgers recalculating automatically rather than through manual correction events. In agentic systems where events arrive late or contracts are renegotiated after a service period, retroactive correction is a routine operation rather than an edge case.
Defining usage metrics in SQL over raw usage events, with versioned pricing and logs, means a new billable metric can often be defined without a fresh instrumentation project. This is what turns the 92% repricing statistic from a crisis into a workflow.
Finance workflows covering ASC 606-aligned reporting, enterprise contract handling, and ERP integrations such as NetSuite close the loop between metered consumption and recognized revenue. Usage data that cannot reach the ledger cleanly is a month-end problem waiting to happen.
Deloitte's June 2026 analysis notes that outcome-based pricing introduces new ASC 606 judgments for SaaS companies, including how performance obligations and variable consideration are identified and measured. Pricing model selection is now an accounting decision as well as a commercial one.
Pricing versioning with auditable change history and simulation reduces engineering dependence when testing and operationalizing pricing changes. As pricing shifts from a static decision to a continuously iterated system, the ability of finance and pricing teams to act without a deployment cycle becomes a durable advantage.
These trends converge on a small number of concrete requirements for companies building AI-powered products.
Hybrid pricing demands flexible infrastructure
With 95% of the AI agent companies in Orb's 2026 study using hybrid pricing and 94.7% of subscription users pairing subscriptions with usage, billing systems must support layered structures natively:
Outcome-based billing requires event-level tracking
Pricing per resolution, per resolved interaction, or per task depends on granular event history. Event-level records can support:
Enterprise adoption accelerates billing complexity
As AI agents move from departmental tools to enterprise infrastructure, billing requirements expand:
Companies building AI solutions need billing infrastructure that evolves with pricing strategy rather than constraining it. When 92% of usage-charging AI businesses have already repriced, the ability to test new models, apply retroactive changes, and maintain financial accuracy across complex scenarios is not a back-office concern. It determines how fast a company can respond to a market that is still repricing itself.
Hybrid pricing dominates. Orb's 2026 study of 80 AI agent companies found 95% use hybrid pricing, 91.3% use usage-based pricing, and 71.3% use subscriptions, with 94.7% of the subscription users pairing subscriptions with usage charges. Pure outcome-based pricing appears in only 3.8% of the sample, down slightly from 4.5% in 2025, which makes it the most discussed and least adopted model in the category.
Deloitte documents billing across actions and tasks, compute, API calls, tokens, duration, or combinations. In practice, published examples include resolutions at $0.99 from Intercom, resolved interactions at $0.90 from Gorgias, verified automated resolutions at Zendesk, for which no list rate is published, and credit-denominated actions from Salesforce, where a standard 20-credit action equates to $0.10.
AI agent billing requires real-time usage metering over a preserved raw usage event layer, support for layered subscription plus usage structures, dimensional pricing across models and regions, credit systems for prepaid consumption, spend thresholds and alerts, and finance workflows that connect metered usage to ASC 606-aligned reporting and the ERP. Because pricing changes frequently, the system also needs versioning, simulation against historical usage, and backdating so corrections can be applied without manual reconstruction.
Traditional SaaS relies on predictable seat-based or flat subscription pricing. AI agents introduce variable consumption driven by tokens, API calls, task complexity, and compute, and rates may differ by model version, region, or feature set. Orb's 2026 research also identifies effort-based pricing, where compute time, steps, or task complexity become the usage measure. Outcome models add a further layer by charging for results rather than resources, which requires attribution rules, per-conversation caps, and the ability to not charge when an outcome is not achieved.
Frequently. Stripe found that 92% of AI businesses charging for usage subsequently changed their pricing, and Orb's 2026 research describes AI agent pricing as a continuously iterated system rather than a one-time packaging decision. Cost pressure reinforces this: Gartner projects that generative AI cost per resolution for customer service will exceed offshore human agent costs by 2030. Teams should plan for repricing as a recurring operation and build the tooling to support it.



See how AI companies are removing the friction from invoicing, billing and revenue.