m3ter pricing uses a custom model combining a monthly platform fee with allowances for usage data ingestion and bill calculations. Additional costs can apply for expanded processing capacity, CRM and ERP integrations, enhanced support, and implementation services. m3ter publishes these pricing components but does not disclose standardized monthly rates.
For SaaS, AI, and cloud infrastructure companies, billing costs depend on usage volume, pricing complexity, and connected financial systems. Linking usage and cost data with business activity helps establish the operating requirements behind usage-based billing. Salesforce completed its acquisition of m3ter on July 1, 2026, incorporating its metering and rating technology into the company's revenue management portfolio.
Key takeaways
- m3ter uses custom pricing with a monthly core platform fee that includes allowances for usage data ingestion and bill calculations
- Additional processing capacity, CRM and ERP integrations, enhanced support, and implementation services can affect total costs
- m3ter supports usage-based and hybrid pricing, configurable billable metrics, enterprise commitments, prepaid balances, and unaggregated usage measurements
- Salesforce completed its acquisition of m3ter on July 1, 2026, adding usage metering and rating technology to its revenue management portfolio
- Total cost of ownership depends on platform fees, processing volumes, integrations, implementation scope, and ongoing finance workflows
Understanding m3ter's pricing structure
Core platform fee
m3ter charges a monthly platform fee based on the requirements of the deployment. The fee includes allowances for two activities:
- Usage data ingestion: Collecting and processing product activity used in billing calculations
- Bill calculations: Computing customer charges using configured pricing rules and usage measurements
Standard support is included in the core platform fee.
The company does not publish a universal monthly rate or fixed allowances for every deployment. Contracted pricing reflects the expected processing workload and commercial requirements.
Usage ingestion and bill calculations are separate measurements. A business can generate millions of usage records while producing a substantially smaller number of customer bills.
These differences influence how the billing infrastructure is configured and priced.
Additional processing and integration costs
m3ter offers optional components beyond its core platform package.
These include:
- Additional usage ingestion: Expanded processing allowances for higher event volumes
- Additional bill calculations: Increased capacity for billing computations
- CRM integrations: Connections supporting customer, contract, and commercial data
- ERP integrations: Connections with financial systems and invoicing workflows
- Enhanced support: Additional service levels beyond standard support
- Implementation services: Solution design, project management, and platform configuration
The total cost depends on which components are included in the deployment.
For example, a company using m3ter to calculate usage charges across several products may have different integration and processing requirements from a company managing customer-specific enterprise agreements.
How billing complexity affects pricing
Usage-based billing platforms process two related but distinct types of information: the product activity being measured and the commercial rules used to calculate charges.
An AI application may generate substantial token usage data, while an enterprise software company may process fewer events but manage numerous commitments, credits, and customized contract terms.
Both environments can require detailed billing calculations.
Factors influencing the commercial scope include the number of billable metrics, pricing configurations, accounts, products, and downstream integrations.
What m3ter provides for usage-based billing
Usage ingestion and metering
m3ter provides infrastructure for ingesting, transforming, storing, and aggregating product usage measurements.
Its metering capabilities include:
- Usage measurement ingestion
- Data enrichment and transformation
- Configurable aggregations
- Compound calculations
- Usage segmentation
- Billable metric configuration
- Historical usage reporting
- Data exports
These capabilities allow companies to calculate charges using product activity such as API calls, compute usage, storage consumption, or transactions.
m3ter also supports retaining processed, unaggregated measurements for historical billing analysis.
Its service description specifies retention of processed, unaggregated usage measurements for at least 24 months during the applicable contract period. Original raw usage and cost inputs are subject to a separate default retention period of 60 days unless the agreement provides otherwise.
This distinction separates the retained, processed measurements used for billing analysis from the original input records.
Pricing models and enterprise contracts
m3ter supports several commercial structures.
These include:
- Usage-based pricing: Charges linked to measurable product activity
- Subscription pricing: Recurring fees associated with a plan or service period
- Hybrid pricing: A combination of fixed recurring charges and usage-based components
- Credit-based pricing: Prepaid balances applied against eligible charges
- Enterprise commitments: Contracted minimum spend or usage arrangements
- Multi-attribute pricing: Rates determined by multiple usage characteristics
- Account hierarchies: Billing relationships between parent and child accounts
Each model creates different billing requirements.
Usage-based pricing measures consumption, while subscriptions charge for a recurring entitlement or period. Combining recurring platform fees with metered charges creates a hybrid pricing model, with each component calculated according to configured pricing rules.
Prepaid credits provide a balance that can be applied against specified charges. Outcome-based pricing is another distinct model, linking charges to defined results rather than consumption alone.
Enterprise agreements may combine several of these components with customer-specific commercial terms.
Bill calculation and financial integrations
m3ter's calculation engine applies configured pricing rules to usage measurements and generates billing outputs.
The platform connects with external systems for downstream commercial and finance workflows.
Supported activities include:
- Customer and contract synchronization
- Usage-based charge calculations
- Prepayment and balance tracking
- Billing output generation
- Automated data transfers
- ERP and invoicing integrations
- Financial reporting data exports
m3ter provides connectors and APIs for integrating with CRM, invoicing, and ERP platforms.
The configured architecture determines how calculated charges become customer invoices and how payment collection, accounts receivable, and revenue recognition are managed.
Salesforce's acquisition of m3ter
Acquisition completed in July 2026
Salesforce announced its agreement to acquire m3ter on June 8, 2026, and completed the acquisition on July 1, 2026.
The transaction brings m3ter's mediation, metering, and rating technology into Salesforce's revenue management portfolio.
The acquisition supports Salesforce's broader strategy around usage-based and outcome-based monetization through Agentforce Revenue Management.
Usage-based billing calculates charges from measurable activity. Outcome-based pricing connects commercial charges to defined results, making the measurement and rating of those results relevant to billing infrastructure.
Connections with Salesforce revenue management
m3ter provides integration capabilities for Salesforce environments, including commercial and billing workflows.
These integrations support activities involving:
- Customer information
- Contract data
- Product usage measurements
- Billing calculations
- Revenue management
- CRM synchronization
Salesforce's ownership establishes a closer relationship between m3ter's usage metering technology and the company's revenue management products.
Specific capabilities depend on the configured integration and product deployment.
Factors affecting m3ter's total cost of ownership
Usage ingestion and bill calculation volume
m3ter's pricing separates ingestion activity from bill calculations.
Usage ingestion represents the product measurements processed by the platform. Bill calculations represent the operations required to apply pricing configurations and determine customer charges.
A software company may generate a high volume of events while billing customers monthly. Another may calculate charges frequently across multiple products, customer accounts, or commercial structures.
These workloads involve different processing profiles.
Total processing requirements depend on event frequency, metering configuration, billing schedules, and commercial complexity.
Integration and implementation requirements
m3ter can operate as part of a broader revenue technology environment.
A deployment may include:
- CRM systems
- ERP platforms
- Invoicing applications
- Payment-processing services
- Customer account management
- Revenue recognition software
- Data warehouses
- Reporting tools
The number and depth of integrations influence implementation and maintenance work.
m3ter provides implementation services covering solution design, configuration, and project management. These services can form part of a broader quote-to-cash transformation.
Implementation requirements vary according to the existing system architecture and billing workflows.
Understanding unit economics
Platform fees form one component of the total cost of operating usage-based software.
A broader cost model considers both billing infrastructure expenses and the costs associated with delivering the underlying product or service.
Relevant unit economics may include:
- Cost per API request
- Cost per transaction
- Cost per token
- Cost per customer
- Cost per workload
- Revenue per billable unit
For example, an AI company can compare the revenue collected for model usage with the computing costs associated with delivering that usage.
Billing platform charges represent a separate operating component within that calculation.
These measurements help distinguish the cost of delivering a service from the cost of measuring, pricing, and billing for it.
Price evolution and historical billing adjustments
Processing historical usage
Usage-based billing must account for data and commercial changes that occur after activity is recorded.
Examples include:
- Late-arriving usage measurements
- Corrected usage information
- Updated pricing rules
- Contract amendments
- Changes to billing periods
- Revised aggregation configurations
m3ter supports stored usage measurements and recalculation workflows that can be used for historical billing analysis and corrections.
The relevant process depends on the affected billing period, configured pricing rules, and the state of downstream financial records.
Maintaining billing accuracy also requires a clear process for correcting delayed usage records and reflecting eligible adjustments in invoices.
Finalized invoices may require corresponding adjustments within connected invoicing and finance systems.
Analyzing proposed pricing models
Historical billing adjustments and pricing analysis serve different purposes.
Corrections update the treatment of recorded activity, while pricing analysis estimates the effects of alternative commercial configurations.
A pricing model assessment can consider:
- Customer-level revenue differences
- Effects of revised usage tiers
- Changes to unit prices
- Credit consumption
- Committed spend utilization
- Revenue distribution across customer segments
Historical information can provide a basis for modeled pricing scenarios.
Projected results remain estimates based on the underlying usage data and assumptions rather than guaranteed future outcomes.
Customer transparency and billing operations
Usage visibility
Usage-based pricing can produce different charges across billing periods as product activity changes.
Customer-facing usage information can make those charges easier to understand. Dashboards can incorporate spend controls to provide visibility into usage thresholds, balances, and automated alerts.
Relevant information includes usage quantities, applicable pricing, credit balances, and accumulated charges.
m3ter provides usage and billing data that can support reporting and connected customer-facing systems.
Account-level visibility and billing notifications depend on the configured product and integration environment.
Security and access controls
Usage-based billing platforms process customer information, pricing configurations, contract details, and usage measurements.
Relevant enterprise capabilities include:
- Role-based access controls
- Activity logging
- Data protection
- Authentication
- Audit records
- Incident management
- System availability
A structured approach to security governance covers the identification, protection, detection, response, and recovery activities associated with cybersecurity risks.
These controls are relevant to the governance of commercial and financial systems.
Finance workflows and revenue recognition
Connecting usage with financial records
Usage-based and hybrid pricing connect product activity with contractual charges and financial reporting.
A typical revenue workflow involves several stages:
- Recording customer usage
- Applying pricing and contract terms
- Calculating billable amounts
- Generating invoices
- Recording payments
- Managing customer balances
- Recognizing revenue
Connected contract-to-cash workflows bring together commercial terms, billing calculations, invoicing, and collection.
m3ter supports usage calculations and transfers billing information into connected finance systems.
The downstream software configuration determines how invoicing, payment collection, and revenue accounting are performed.
Revenue recognition requirements
Enterprise software contracts may involve recurring subscriptions, variable usage charges, prepaid balances, and commitments.
These arrangements can require different revenue recognition treatments depending on the contractual obligations.
Under US GAAP, ASC 606 governs revenue recognition from customer contracts. Internationally, revenue recognition requirements are addressed through IFRS 15.
Billing infrastructure can provide the transaction records, usage information, and contract data used in these finance workflows.
The applicable accounting treatment depends on the contract and reporting framework.
How Orb supports usage-based billing and price evolution
Orb provides revenue infrastructure connecting metering, pricing, billing, invoicing, and finance workflows for SaaS, AI, and cloud infrastructure companies.
Its platform supports usage-based, hybrid, subscription, and credit-based pricing within a connected revenue management environment.
Raw usage events and flexible pricing
Orb's usage-based billing engine uses raw usage events to calculate billable metrics.
Its standard metering architecture retains granular usage information, supporting historical analysis, eligible backfills, and price evolution workflows. Hosted Rollups provides aggregation during ingestion for configured high-volume streams.
Core capabilities include:
- Custom SQL metrics: Define billable quantities using configurable calculations over usage data
- Hybrid pricing: Combine recurring fees, seats, and usage-based charges
- Dimensional price groups: Support pricing across multiple usage dimensions, such as region, instance type, and environment, using a single pricing configuration for dimension combinations
- Prepaid credits: Manage purchased credit balances, configured drawdowns, and expiration
- Billing adjustments: Support eligible historical corrections and invoice recalculation workflows
Orb's prepaid credits capabilities connect credit allocations and usage consumption with the underlying billing calculations.
These features support multiple products, custom contracts, and evolving commercial models.
Historical pricing simulations
Orb Simulations allows product and finance teams to evaluate proposed pricing against real historical usage before production rollout.
The platform supports comparisons between alternative pricing configurations, including projected revenue effects and customer-level impacts.
These simulations provide modeled results based on historical data rather than guaranteed future performance.
Orb's price evolution capabilities also support customer-specific configurations, scheduled commercial updates, and subscription migrations.
This connects pricing analysis with the workflows used to manage and implement new pricing structures.
Invoicing and finance workflows
Orb connects usage-based billing with invoicing, accounts receivable, collections, and financial reporting through its finance workflows.
Its NetSuite integration creates standard financial transaction objects, including invoices, credit memos, and customer deposits.
Orb's Experience Kit supports customer-facing billing experiences, including usage dashboards and configurable pricing interfaces.
Customer-specific results illustrate these capabilities in production:
- Vercel: Reported an 80% reduction in the time required to build and launch billing for new products after implementing Orb, as documented in its customer story
- Stytch: Reported a 75% reduction in time spent processing bills and invoicing after implementing Orb
Both results reflect the companies' individual implementations and are not guaranteed outcomes for other customers.
Orb pricing structure
Orb pricing is customized across Core, Advanced, and Enterprise plans.
- Core: Real-time usage ingestion, hybrid and usage-based billing, automated price updates, invoicing, and finance and tax integrations
- Advanced: Adds data warehouse synchronization, Salesforce and NetSuite integrations, customer hierarchies, and premium support
- Enterprise: Adds enterprise-grade service-level agreements and dedicated support
Orb's commercial model is based primarily on billings and event volume, with additional platform fees for Advanced and Enterprise.
The platform also connects with payment-processing systems, including Stripe Payments, supporting billing execution alongside configured payment collection workflows.
Orb brings usage metering, pricing configuration, historical simulations, invoicing, and finance workflows together within its revenue infrastructure.
Frequently asked questions
Does m3ter publish its pricing?
m3ter publishes its pricing structure but does not provide standardized monthly rates. Its commercial model includes a core platform fee with allowances for usage ingestion and bill calculations. Additional processing capacity, integrations, support, and implementation services can affect the final agreement.
What determines m3ter's total cost?
The primary factors include usage ingestion volume, bill calculations, selected integrations, support requirements, and implementation scope. Connected invoicing and finance systems also contribute to total operating costs.
Does m3ter generate customer invoices?
m3ter calculates customer billing amounts and supports transferring billing outputs to connected invoicing and financial systems. Invoice generation, payment collection, and revenue reporting depend on the configured integrations and downstream applications.
When did Salesforce acquire m3ter?
Salesforce announced its agreement to acquire m3ter on June 8, 2026, and completed the acquisition on July 1, 2026. The transaction brought m3ter's usage metering and rating technology into Salesforce's revenue management portfolio.
How does Orb support price evolution?
Orb supports price evolution through raw usage events, configurable SQL metrics, historical pricing simulations, scheduled updates, and customer-specific pricing configurations. These capabilities connect pricing analysis with metering, billing, invoicing, and finance workflows.