Salesforce buys m3ter to bake consumption billing into Agentforce Revenue Management

Salesforce has signed a definitive agreement to acquire m3ter, a London-based metering and rating platform built for consumption-based billing. m3ter’s platform is designed to handle the messiness that sits between “customers used it” and “we get paid for it,” which is exactly why this integration matters: it targets billing mechanics, not just a dashboard.

The specific consequence is that m3ter’s infrastructure will be integrated natively into Agentforce Revenue Management. That means Salesforce customers can launch, track, and bill usage-based and outcome-based pricing models directly within Agentforce, without leaving the platform. Financial terms were not disclosed.

So what is Salesforce really buying here? In plain English, consumption-based billing needs metering and rating. Metering is the collection of usage signals. Rating is the logic that turns those signals into billable amounts under whatever plan a company designs. That is hard enough when you control the product and the telemetry. It gets even harder when you need to do it in a way that supports multiple pricing models, changing price rules, and auditability across contracts.

This acquisition also lands in a moment when “usage” is no longer a niche pricing experiment. Many software vendors have spent the last few years experimenting with consumption and outcome-linked models because they promise a smoother fit between value delivered and value captured. For buyers, those models can feel more fair. For sellers, they can reduce churn, improve expansion, and align incentives. The catch is operational: billing has to be correct, timely, and consistent enough that finance trusts it, support can explain it, and customers do not end up in endless disputes.

That is where m3ter’s positioning becomes strategically relevant. The Next Web describes m3ter as “built for consumption-based billing,” and the integration target is Agentforce Revenue Management. Revenue Management is the natural home for the policies and workflows that turn customer activity into revenue numbers. By embedding m3ter infrastructure natively, Salesforce is effectively trying to remove the usual integration pain between a CRM or customer workflow layer and the metering and rating layer where billing decisions are made.

There is also a platform incentive baked into the move. If Salesforce customers can “launch, track, and bill” usage-based and outcome-based pricing models without leaving Agentforce, Salesforce reduces friction across the entire commercial loop. That loop typically sprawls across tools: CRM for selling, billing platforms elsewhere for billing execution, spreadsheets or data pipelines for metering transforms, and analytics tools for tracking. Each handoff is an opportunity for errors, delays, and version drift. A native integration is Salesforce’s way of tightening that loop so the revenue process feels like one system.

Regulatory and compliance considerations add another layer of stakes, even when the source does not spell them out. Billing correctness is operationally similar to financial reporting quality, and consumption and outcome-based models can create additional scrutiny because charges may depend on event-level measurement and contractual definitions of “outcome.” In practice, regulators, auditors, and enterprise finance teams care about traceability: what data drove the charge, what rules applied, and whether the billing can be reconstructed. A metering and rating platform integrated into a revenue management workflow is positioned to support that kind of explainability better than a patchwork of disconnected systems.

For peers, the second-order implication is clear. Salesforce is signaling that consumption-based and outcome-based monetization is not just a feature request, it is a core capability the platform needs to own end-to-end. If this integration lands well, it could raise customer expectations that revenue management vendors should provide more than invoicing, they should provide the billing intelligence and execution foundation for variable pricing.

Board members and senior operators at other revenue platform companies should treat this as a competitive benchmark. When Salesforce integrates a specialized metering and rating infrastructure directly into Agentforce Revenue Management, the bar moves from “can you support usage billing” to “can you do it natively, across launch to billing, with minimal system hopping.” In a market where pricing innovation is fast and implementation complexity is the silent killer, this is the kind of move that can shift who wins the next round of enterprise deals.