What happened to m3ter after Salesforce bought it

A product manager hears that Salesforce bought a metering company and asks, in the same meeting, what to charge per API call. Someone writes a number on the whiteboard because the silence is uncomfortable. The room agrees the number is close enough to proceed. That agreement is the problem. The number is not in the announcement. It is not in a contract. It is now in a photo of the whiteboard, which is how a fictional price becomes internal policy.

The sentence worth reading instead is the completion record: "Salesforce completed its acquisition of m3ter on July 1, 2026." The deal is done. m3ter is metering and rating for usage-based pricing, aimed at Agentforce Revenue Management. Metering is how usage is counted. Rating is how a count becomes a charge under a rule someone wrote. Usage-based pricing is the commercial shape those two activities serve. The aim is a direction. It is not a statement that every revenue org gained a meter on the day of the close. Rating without a rule is a calculator with no buttons labelled. The buttons are the work, and they are not in the notice.

What follows separates a finished acquisition from a price. A good answer names a person, a rule, or a date. A number with no owner is what gets copied into a quote template.

#What did the 1 July 2026 close actually settle?

The question is not whether Salesforce bought m3ter. It did. The question is what a completion is allowed to put on a product slide. Check the edition and the order form before finance is told the feature is already theirs. A completion date is about the companies. Entitlement is about the contract. Keep those files apart.

The spelling is m3ter, with a digit. Searches will try "meter", a capital M, and the digit left out. The company in the completion sentence is the one this decision is about. It is not every meter an organisation already runs in a product it built. If a product already emits a count, that count was not acquired on 1 July 2026. Do not brief it as if it were.

A good answer sounds like the completion sentence dated 1 July 2026, m3ter described as metering and rating for usage-based pricing, aimed at Agentforce Revenue Management, and a named person who will not tell finance the meter is already in the org. Aimed at stays a direction. The order form is what says whether the product is held.

A bad answer sounds like the price list arrived with the code, so the whiteboard number can stay until legal tidies it. The price list did not arrive. Why Salesforce acquired m3ter stops at the description on the cited page. There is no longer strategy essay. Do not add one. Why m3ter sold is not here. A profile or a clip is not a source, and a motive taken from one is a motive to refuse.

#Who is allowed to set the price a customer pays?

Salesforce owns m3ter. "Is m3ter owned by Salesforce", "did Salesforce buy m3ter", and "who owns m3ter" are one question, and the completion answers it. Owning a metering company does not own the price. The price a customer pays for usage is a commercial decision the selling company makes, per product, often per edition, with a start date. Salesforce buying the company that counts and rates does not write that decision. A partner should not write it in the margin of a technical proposal either.

Impact on the customers who are billed is not a new rate inferred from the close. Their invoices change when a rule is changed by someone willing to sign it. The acquisition does not amend their contract. Do not tell them it did.

A good answer sounds like a named person in commercial or finance who can refuse a rate, a named product the rate would apply to, and a start date that is not 1 July 2026 unless that person has chosen it for a reason that is not the close. The rule's shape can be stated without a currency amount: included quantity, what happens past it, whether the period is a month or a contract year, whether unused quantity expires, and who may change the rule.

A bad answer sounds like pricing is shared, so the sample in the sidebar can stand in until the committee meets. Shared means nobody. "For illustration" inside a proposal is how a sample rate escapes. Illustrations get copied. If a worked example is needed before the commercial owner has signed, use a symbol, not a currency amount. A rate from a previous company, a rival's public card, or a blog is the same fiction with a different footnote.

There is no price per API call in the announcement. There is no price per agent action and no price per thousand events. The close gives a place a rule can sit. It does not write the rule, and it does not pick the number. If finance asks what the acquisition set as the price of a call, the answer is that it did not set one.

#Which date may start an invoice?

The date is 1 July 2026. The vendor writes July 1, 2026. Same day. "When did Salesforce acquire m3ter" is that day. A timeline is that day. There is no shutdown, rename, or billing cutover to add. Do not treat the close as the first day usage may be invoiced. Invoicing waits on a meter that is trusted, a unit, a rating rule, and a person who owns the invoice. None of those arrived as a date inside the notice.

A good answer sounds like 1 July 2026 kept as the corporate completion, and a separate first billed period labelled as a finance decision, with the person who can explain the count named beside it. "Went live" is split in two. Live as a completed purchase: yes. Live as an org that now rates API calls: the source does not say that.

A bad answer sounds like billing starts on 1 July because that is the close. The plan has confused a corporate day with a revenue process. A second date people try to attach is the day a sample rate was written on a whiteboard. That date is not an acquisition date. It is the day a fictional number escaped. Strike it from the timeline. Leave 1 July 2026, and leave the commercial start date labelled as internal.

"Went live" in the sense of a release inside an edition is the phrase to test. Aimed at Agentforce Revenue Management is a direction. The order form says whether the product is held. A news date does not.

#Which price is missing, the deal or the rate?

Two different prices get mixed. Separate them before either one is allowed into a document that leaves the room.

The first is what Salesforce paid for the company. The cited page does not publish a purchase price or a licence fee. How much Salesforce paid for m3ter, how much m3ter was sold for, and the acquisition price are not answered here. Do not remember a number into the gap. A clip is not a source. There is no m3ter licence fee on the cited page, and no free trial established by the completion sentence.

The second price is what a customer is charged per API call, per thousand events, or per any other unit. The announcement does not contain that either. A price that is invented will be copied into a quote template. A customer will eventually see it. Then someone will have to explain a number nobody agreed.

A good answer sounds like procurement stating that the deal price was not published, and the commercial owner stating that the customer rate has not been signed. Both cells stay empty. The shape of the rule, written on the implementation side, is what gives the rate somewhere honest to sit afterwards, in a decision legal and finance make.

A bad answer sounds like one number offered for both questions, because the room was tired of blanks. A DVD, a Reddit thread, a YouTube video, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown. A course that names a price per call is still not the announcement. Spending, in a short clip, is the same unpublished number.

#Is there a shutdown, or a meter that already exists?

There is no end date for m3ter in the cited page. Do not invent one because a meter cannot be seen in an org in the week of the close. Missing from an edition is not retirement. A sunset would be its own notice. There is not one here. Product decline cannot be read from a completion sentence. The sentence is not a changelog and not a satisfaction score. If a tenant was held before the close, the people who hold the login can say whether it still opens. The announcement cannot remember the login.

A good answer sounds like no shutdown date, and a clear statement of which situation is true. If m3ter history already exists, keeping enough grain to explain a disputed count is the work. If it does not, the work is defining meters, not migrating them. The person proposing the project can say which of those is true before a proposal keeps the word migration out of habit. Missing usage, when it is reached, is a business rule: delay, zero, or a human hold. An estimate is not a quiet fourth option.

A bad answer sounds like users are forced onto a new rate so an invoice can run, and the absence of a screen means the product was retired. The source does not order billing onto a named screen, and it does not order customers onto a new rate. Forcing a rate so an invoice runs is the failure mode. It is not an instruction in the notice. Worth, after the purchase, is not a price per call and not a verdict. The record supports ownership, the date, the kind of work, a missing deal price, and a missing end date.

A quote that opens with a price per call has skipped the record. Send the number back. Blanks on the meter, the unit, the rating sentence, and the invoice owner are acceptable. Fake numbers are not. Run the first period, when it exists, as a reconciliation, with a person in front of the invoice. That discipline comes after the whiteboard has been wiped. The whiteboard is the decision in this room.

#What to do with the answers

Read the five as a set. Specific answers mean the room can tell a corporate close from a rate. General answers mean the decision rests on a shared feeling that a metering company arrives with a price, which the notice does not say.

The meter, the unit, the rating sentence, and the invoice owner, still with no invented rate, are set out in m3ter, usage pricing, and Agentforce Revenue Management.