m3ter licence cost after the Salesforce acquisition

Billing a customer for what they use is a different commercial problem from billing a customer for a seat, and that difference is the whole story of an m3ter licence. The company is a metering and rating platform. Its price has always been shaped by volume. Salesforce's published price for the product it is joining, Revenue Cloud, is shaped by people. A buyer who reads one and expects the other will be surprised.

The completion record is one dated sentence: "Salesforce completed its acquisition of m3ter on July 1, 2026." Salesforce's announcement describes m3ter as "a leading metering and rating platform purpose-built for consumption-based monetization" and says the acquisition will bring "high-volume mediation, metering and rating capabilities natively to Agentforce Revenue Management". When we opened m3ter.com on 13 October 2026, its footer already read "m3ter from Salesforce". The brand lives on. What is missing is a Salesforce price for it.

#How m3ter itself prices

m3ter's pricing page, which was still live on 13 October 2026, says its pricing is "designed for the needs of mid-size and large B2B SaaS companies" and invites you to talk to the company. It sets out four building blocks, and they are the best guide to what a quote will contain.

Source: m3ter pricing, read 13 October 2026. m3ter sells by quote.

The sentence to hold on to is this one: "A monthly fee based on the size of your needs, which includes allowances for usage data ingested and bill calculations performed." It tells you the unit. You are not paying per user. You are paying for a size of need with two measured allowances, and exceeding them means buying more. That is the opposite of a seat licence, and it is why a seat price from Salesforce's side will not tell you what m3ter costs.

#What Salesforce publishes beside it

The Salesforce product m3ter is meant to join is Revenue Cloud, which Salesforce prices on a published page. It lists two editions billed annually in US dollars per user per month, with the Australian dollar view alongside.

Source: Salesforce Revenue Cloud pricing, read 13 October 2026. The page says one edition requires an annual contract and that the figures are for information and subject to change.

Two lines on that page matter here. The first is that the upper edition lists "Consumption & Invoicing", and the feature grid has a "Usage Selling" row, so Salesforce already sells some usage capability inside Revenue Cloud. The second is the FAQ answer that Revenue Cloud is a paid add-on, because "It is a separate product that you purchase in addition to your standard Sales Cloud subscription." There is no free trial.

The grid also shows Dynamic Revenue Orchestration and Invoice Management as "Available for purchase*", with a footnote saying freemium access is available. We would not read that as covering m3ter. Salesforce has not said what m3ter volume, if any, is bundled. It said m3ter is expected to bring native consumption billing "alongside our existing models", and we found no price attached to that.

#Seats versus volume

Take a concrete picture. Twenty-five people in sales operations and finance use quote and order screens. On the upper edition at list, that is 25 times $200 times 12, or $60,000 a year, or AU$84,000 at the Australian list. On Growth it is $45,000. Those numbers are a function of how many people log in.

Now your product generates usage events, perhaps API calls, compute hours or messages sent. Whether that is ten thousand a month or ten billion has no bearing on the seat count, but it decides the work a metering platform does and, on m3ter's published model, the allowance you need. The two meters are independent. A small team can bill an enormous usage base, and a large team can bill a small one. When you see a proposal that prices both with one figure, ask for it to be split into seats, usage allowance and services so you can check each.

#What to find out before a quote arrives

Salesforce has not published how m3ter capabilities will be packaged. So the first set of questions is about the contract, not the feature list.

Is m3ter being sold as a separate line, an add-on to Revenue Cloud, or part of the upper edition? Is the unit the platform fee with allowances, as m3ter described it, or something new such as credits, events or billed revenue? Are the usage allowances measured on usage records ingested, on bill calculations, or both? What is the rate beyond the allowance, and is it fixed for the term? Which connectors are included, given that m3ter listed CRM and ERP integrations as add-ons? Does standard support still come with the platform fee? Is there a minimum term, and does it match your Revenue Cloud term?

#Estimating your volume honestly

The allowance is the number that surprises people, so estimate it before you negotiate. Take a typical month and count the usage records your products emit that you would want to price: events per customer per day, multiplied by customers, multiplied by days. Separately count the bill calculations you expect, which is roughly customers times invoice runs times any recalculation you allow for corrections. Then add growth for the contract term, since you are buying capacity for a year or more, and a clean forecast of the first quarter may be half your final-quarter volume.

Do not invent a per-event price to fill the gap. A figure you derive yourself is your price to your own customers, which is a different document from what you pay the vendor. The m3ter, usage pricing and Agentforce Revenue Management page covers that design work.

#Overage and true-up traps

The risks in a usage-priced licence are specific. A fast-growing product can exhaust an allowance mid-term, and the question is whether you buy a block at the contract rate or pay an unplanned overage. A bill-calculation allowance can be consumed faster than expected if you rerun invoices for corrections or simulations, so ask whether test runs and sandbox activity count. If your data arrives in bursts, ask whether the allowance is annual, monthly or peak-based. And if you are billed on size of need rather than raw volume, ask exactly how that size is measured and who can re-measure it at renewal.

#Support and services as separate lines

m3ter's page says standard support is included and most customers pay extra for enhanced support. That is worth costing as its own line, because a billing platform that produces invoices is a service you will want help with at month end. Implementation is a third line. m3ter says an implementation is typically part of a challenging quote-to-cash transformation, which suggests the licence will often be the smaller part of the first-year cost, but we have no published figure to put against that and will not invent one.

#Comparing two offers

If you are weighing an m3ter quote against another metering or billing product, list the same fields for each: unit of charge, allowance, overage rate, included integrations, support level, term, renewal cap and exit terms. Include the cost of the CRM and ERP connections, since m3ter treats them as add-ons. Then estimate year-one and year-three totals for the same volume forecast. The cheapest platform fee is not the cheapest licence if the allowance is small.

#Three buyer positions

If you already run Revenue Cloud, ask first whether m3ter capability is part of your edition, a purchasable extension or a later release. Salesforce said it will bring metering and rating natively to Agentforce Revenue Management, and your current order form will not mention that until a product line exists. Keep your renewal flexible so you can adopt the new packaging without paying for the old one twice.

If you are an existing m3ter customer, your licence is the contract you signed with m3ter. The footer now says m3ter from Salesforce, but the acquisition does not change your order form by itself. Ask how and when contracts will move, whether pricing is held for the term, and whether support terms stay the same.

If you are choosing a metering platform now, you have a harder comparison. m3ter's published structure is a platform fee with allowances, while Salesforce's published Revenue Cloud structure is per user. A fair evaluation prices your forecast usage under each and shows the seats you would need alongside it, with the services required to connect the CRM, ERP and invoicing systems.

#What to put in the order form

Whatever the packaging turns out to be, insist that the order form states the unit of charge and how it is measured, the allowance included in the platform fee, the rate for additional allowance, the term over which that rate holds, whether sandbox and test activity counts, which integrations are included, the support level and its response times, and the renewal uplift cap. A licence that names only a platform fee leaves the most expensive questions to be settled after you have committed.

Also ask how your data is exported if you leave. Usage records and rated charges are the evidence behind your invoices, and you will want them in a form you can reload elsewhere.

#A word on currency and tax

The Revenue Cloud page shows both US and Australian dollar views, which suggests Salesforce expects to bill in either. m3ter's page shows no currency. Confirm the billing currency, who the contracting entity is, and how tax is applied before you compare totals from two vendors, since a difference of that kind can outweigh a modest gap in list price.

#A worked example of the split

Suppose a software company has 12 finance and revenue operations users who need quote, order and invoice screens, and a product that generates a large and growing stream of usage events. On the upper Revenue Cloud edition at list, the seat licence is 12 times $200 times 12, or $28,800 a year, a figure that barely moves as usage grows. The metering side is entirely different. Its cost is driven by the allowances in the platform fee, which m3ter ties to the size of need, with incremental allowances bought as events and bill calculations rise.

The useful insight from that split is that one side of the invoice is stable and the other is the part that scales with the success of your product. Finance should model them separately, with the usage line as a range across low, expected and high growth. Presenting a single total hides the line most likely to be revised at renewal.

#Timing and the Revenue Cloud term

Because the Revenue Cloud page says one edition requires an annual contract, line up the metering term with the Revenue Cloud term where you can. A metering agreement that expires six months before the quoting agreement forces you to renegotiate half of your quote-to-cash stack in isolation, which weakens your position on both. If the terms cannot match, ask for a co-termination clause.

#Where this page stops

This is the licence view. For the deal see what happened to m3ter. For how usage and invoices connect to Salesforce see integrating m3ter with Salesforce. For leaving see should you migrate from m3ter. Meter and rating design is on the m3ter and Agentforce Revenue Management page.

#The short version for procurement

Salesforce completed the m3ter acquisition on 1 July 2026. m3ter prices by quote from a platform fee with usage allowances, add-ons, support and services. Revenue Cloud lists at $150 and $200 per user per month on annual billing, as at 13 October 2026, and prices seats, not usage. Get the packaging, the unit, the allowances, the overage rate and the term in writing.