On June 8, 2026, Salesforce signed a definitive agreement to acquire m3ter, the London-based metering-and-rating platform built for consumption-based billing. Salesforce is folding m3ter's high-volume mediation, metering, and rating into Agentforce Revenue Management so enterprises can launch and bill usage- and outcome-based pricing natively. The deal is expected to close in Q2 of Salesforce's fiscal 2027.
Taken alone, it is a sensible tuck-in. Taken together with the last few weeks, it is a pattern you should price into your build-vs-buy decision: the standalone usage-metering category is being absorbed into bigger platforms.
Three metering acquisitions, one direction
- Stripe → Metronome - the payments-infrastructure giant pulled usage billing in-house (what it means + alternatives).
- Adyen → Orb - on June 11, 2026, the payments processor bought Orb (Vercel, Replit, Supabase, Glean) for $335M, framing it as unifying billing with payment performance and fraud risk (the absorption thesis).
- Salesforce → m3ter - now the CRM/revenue-cloud giant takes the third independent metering specialist, this time to power agent monetization.
Three different acquirers (payments infra, payments processing, CRM) all reached the same conclusion within weeks: metering is strategic, and they would rather own it than integrate it. When the buyers are this varied and the timing this tight, that is not coincidence - it is a category being consolidated.
Why metering specifically
AI pricing is the forcing function. Per-seat subscriptions are giving way to per-token, per-call, per-outcome models, and that pricing is only as good as the meter underneath it. Metering is high-volume, correctness-critical, and hard to retrofit - exactly the kind of capability platforms buy rather than build. m3ter going to Salesforce-for-Agentforce is the tell: the unit being monetized is now an agent's work, and you cannot bill for it without a meter.
What it changes for teams choosing how to meter
If you are picking a metering or usage-billing vendor right now, the consolidation wave reshapes the risk:
- "Buy" now carries acquisition risk. The independent vendor you adopt this quarter may be inside a payments or CRM giant next quarter - with a new roadmap, new pricing, and new strategic priorities that are not yours. Three of the category's names just got bought.
- Owning the metering core got more defensible. The meter is where pricing, billing, and product analytics meet. If a giant owns it, they own your pricing flexibility. Keeping that core under your control is now a strategic choice, not a NIH reflex.
- Portability is the load-bearing requirement. Whatever you choose, the question to ask before signing is: can I get my raw usage events out, in full, whenever I want? If the answer is "via a migration project," you are not portable - you are captured.
The hedge: own the meter, stay portable
You do not have to choose between building a metering database from scratch and renting one that might get acquired out from under you. The durable position is a metering layer you control, with your raw events always exportable - so a vendor's acquisition is an inconvenience, not a migration crisis.
That is what UsageBox is built to be: a purpose-built, idempotent, auditable metering store that you own the data in, with export on demand. If you want the deeper version of why this layer is hard enough that giants keep buying it, read why usage metering needs its own database - and on the original m3ter product, our m3ter review.
The metering category is consolidating into payments and CRM platforms. The teams that come out ahead are the ones who treated their meter as something they own and can carry, not something they rent and hope keeps existing.