Pay for what you use: what the m3ter acquisition reveals about the future of Salesforce licensing

On June 8, 2026, Salesforce signed a definitive agreement to acquire m3ter, a UK-based platform specializing in metering and consumption-based billing. At first glance, it looks like a technical announcement with little impact outside the finance department. It isn't.

This acquisition is Salesforce's answer to a question already being asked in plenty of boardrooms: if AI is changing how software creates value, why are we still paying by user seat?

What m3ter is, and where it fits into the Salesforce ecosystem

m3ter is a high-volume metering and rating platform built to support consumption-based monetization models. In practice, it captures in real time how much a customer is using of a given product or service, and automatically turns that into billing.

Salesforce will integrate this technology directly into Agentforce Revenue Management (formerly Revenue Cloud), its revenue cycle management hub. The stated goal is to let any company launch, track, and bill flexible pricing models, usage-based or outcome-based, without leaving the Salesforce ecosystem or relying on external billing systems.

Why this is happening now

The answer is tied directly to the rise of Agentforce. AI products rarely fit neatly into the traditional "per user, per month" model: an AI agent can work around the clock, complete hundreds of tasks with no human account attached, and the value it creates doesn't map cleanly onto a headcount of licenses.

Salesforce has already been feeling this tension. As more companies shift from fixed subscriptions to AI-driven, variable-usage products, per-seat billing infrastructure stops making sense. m3ter closes exactly that gap.

This is the same shift already visible in the : the more Salesforce automates tasks with AI, the less sense it makes to charge by user-account headcount.

What this means in practice for your company's budget

• More variable pricing models: expect more Salesforce AI features to come with usage- or outcome-based pricing instead of a fixed license

• A different kind of budget predictability: finance teams will need to track usage metrics, not just license counts

• A chance to scale without renegotiating contracts: in theory, you can increase an AI agent's usage without buying more "seats"

• A need for real-time visibility: without reliable usage data, it's hard to forecast the real cost of a variable billing model

We've written before about how a . This shift reinforces that argument: value stops living in the tool alone and becomes directly tied to how much your company actually uses it.

What to ask before adopting variable-priced AI modules

• How is usage measured and reported, and how often

• Is there a cap or alert before costs spike unexpectedly

• How does cost-per-outcome compare with traditional licensing

• What visibility does the management dashboard offer into real-time usage

That last question ties directly back to what we've explored about Salesforce as the : without real-time visibility into cost and usage, any AI investment decision is made blind.

Licensing decisions deserve data, not assumptions

At Azimute, we help companies figure out which Salesforce modules and licensing models actually make sense for their reality, not adopt technology just because it's trending. and make the call based on data, not assumptions.