August 2026 Summaries

Modern high-growth software and AI companies increasingly treat revenue as a cross-functional system rather than the responsibility of finance, sales, or any single department. Billing engineers, product leaders, finance teams, and business operations staff now jointly shape pricing, monetization infrastructure, customer billing experiences, revenue recognition, and the ability to adapt commercial models as products evolve. Examples from companies including Supabase, Jasper, Dremio, Factory, Alchemy, Baseten, and Sanity illustrate how billing systems must support accurate invoicing, flexible usage-based pricing, customer spend visibility, and operational scalability. The piece describes this emerging practice as “Revenue Design,” a discipline focused on intentionally coordinating technology, processes, and collaboration so companies can turn customer value into sustainable growth while changing how they monetize as quickly as they develop new products.

Following DealHub’s November 2025 acquisition of Subskribe, the guide compares seven alternatives for SaaS, AI, and infrastructure companies evaluating subscription, hybrid, and usage-based billing systems, while also considering the long-term costs of building billing internally. It presents Orb, acquired by Adyen in July 2026, as the leading option for rapidly evolving consumption pricing because it retains raw usage events, supports SQL-defined metrics, pricing simulations, corrections for late data, high-volume ingestion, and integrated metering, invoicing, accounts receivable, reporting, and ERP connections. Stripe Billing is positioned as a strong choice for organizations using Stripe’s payments ecosystem, especially after its Metronome acquisition expanded enterprise metering and complex contract support, while Chargebee combines mature subscription operations and payment-gateway flexibility with newer usage-billing capabilities. Zuora targets enterprises needing extensive quote-to-cash, compliance, product catalog, and revenue-recognition functionality; Maxio emphasizes SaaS finance reporting and audit readiness; Zenskar focuses on configurable hybrid billing and order-to-cash automation; and Zoho Billing serves organizations invested in the broader Zoho ecosystem. Across the comparison, the main evaluation factors are pricing flexibility, historical usage-data granularity, payment and ERP integration, implementation scope, finance controls, support for complex contracts and multidimensional pricing, and the ability to reduce engineering and reconciliation work.

Consumption-based billing is increasingly used by AI, cloud, and developer-platform companies to align charges with customer usage, although its effectiveness depends on whether the selected metric reflects customer value. The guide compares Orb, Metronome, Chargebee, Lago, Stripe Billing, m3ter, and Maxio based on metering, pricing flexibility, invoicing, finance automation, integrations, enterprise controls, and the choice between buying software and maintaining a homegrown system. It distinguishes usage-native end-to-end platforms from metering-and-rating tools that require downstream invoicing or ERP systems, payments-first products, subscription-first platforms with added usage features, and open-source self-hosted options. Orb is presented as a platform covering raw-event metering through invoicing, accounts receivable, reporting, pricing simulation, backdated corrections, and NetSuite integration, while Metronome, acquired by Stripe in 2026, targets high-volume enterprise usage and complex contracts alongside Stripe’s ecosystem. Chargebee and Maxio combine consumption features with subscription and revenue-operations capabilities, Lago offers open-source and self-hosted flexibility at the cost of greater operational responsibility, Stripe Billing emphasizes payment-native meter-based billing, and m3ter focuses on metering, rating, and orchestration across connected systems. The guide emphasizes that pricing transparency, raw-usage retention, correction workflows, customer usage visibility, auditability, ERP integration, and support for commitments, credits, and multidimensional pricing are important selection factors, particularly as billing complexity grows.

In 2026, organizations evaluating alternatives to Solvimon face a consolidating usage-based billing market shaped by Stripe’s acquisition of Metronome, Adyen’s acquisition of Orb, and Salesforce’s acquisition of m3ter, while homegrown billing remains a common but engineering-intensive option. The comparison emphasizes capabilities such as granular usage-event retention, SQL-based metric definitions, historical pricing simulations, correction workflows, event-ingestion capacity, revenue recognition, integrations, and payment-processor compatibility. Orb is presented as an end-to-end platform for complex usage and hybrid pricing, offering raw-event storage, configurable SQL metrics, simulations, invoicing, accounts receivable, and finance reporting, although the guide is strongly favorable toward it. Metronome targets high-volume enterprise metering and complex commitments within Stripe’s broader ecosystem; Lago provides open-source and self-hosted control; Chargebee combines established subscription workflows with rebuilt usage billing; Maxio focuses on finance-led SaaS operations and revenue recognition; m3ter serves as a metering and pricing layer for organizations retaining existing quote-to-cash systems; and Stripe Billing offers payment-integrated billing with expanding multiprocessor support. The guide advises teams to assess vendors based on their specific pricing complexity, operational ownership, architecture for backfills and late events, finance requirements, integration needs, and tolerance for vendor concentration rather than relying on broad platform categories.

Hybrid billing software is increasingly important for AI, SaaS, and cloud companies that combine subscriptions with usage charges, credits, tiers, commitments, and enterprise-specific terms, creating needs for accurate metering, flexible pricing, compliance, and reduced engineering dependence. The guide compares Orb, Metronome, Chargebee, Lago, Maxio, Stripe Billing, and Zuora, positioning each around different priorities such as enterprise contracts, subscription management, payment integration, open-source self-hosting, finance reporting, or global quote-to-cash operations. It presents Orb as the strongest option for rapidly evolving and complex usage models because its SQL-defined metrics, raw-event retention, pricing simulations, multidimensional pricing, retroactive corrections, customer usage dashboards, and integrated invoicing and receivables are designed to let product, finance, and revenue teams adjust pricing without extensive code changes. The guide also notes market consolidation through Stripe’s acquisition of Metronome and Adyen’s acquisition of Orb, while emphasizing that implementation timelines vary widely by scope and that self-hosted platforms such as Lago trade vendor independence and data control for greater operational responsibility.

Hyperline alternatives for SaaS and AI companies are evaluated primarily on their ability to support usage-based billing, including flexible metric definitions, high-volume event ingestion, retroactive corrections, invoicing, revenue recognition, and ERP integration. The guide compares Orb, Chargebee, Metronome, Stripe Billing, Maxio, Lago, and Zenskar, while emphasizing that building billing internally is also a common but potentially costly option as product and contract complexity grows. Orb is presented as a usage-native platform that retains raw events, supports SQL-based metrics, backfills, dimensional pricing, and integrated billing-to-revenue workflows; it was acquired by Adyen in July 2026 but continues as a standalone product. Chargebee and Maxio are positioned around established subscription and finance operations, Metronome and Stripe Billing around sophisticated usage models and payment infrastructure following Stripe’s acquisition of Metronome, Lago around open-source and self-hosted control, and Zenskar around complex B2B contracts and hybrid pricing. The guide concludes that platform selection should depend on usage volume, pricing complexity, finance and compliance needs, implementation scope, and whether an organization prefers operating billing infrastructure itself or using an integrated managed platform.

Sequence is presented as a CPQ-integrated quote-to-cash platform that supports hybrid subscription, usage, and contract-based billing, while the comparison argues that companies with complex consumption models should assess platforms by practical capabilities such as event ingestion, aggregation, correction workflows, pricing flexibility, simulations, and engineering dependence. It reviews Orb, Metronome, Lago, Chargebee, Maxio, Stripe Billing, Zuora, and in-house development, describing Orb as a usage-focused platform built around retained raw events, SQL-defined metrics, multidimensional pricing, historical simulations, backdating, and high-volume rollups; these features are positioned as useful for AI, cloud infrastructure, and developer-focused businesses. Metronome is characterized as an enterprise-scale usage billing product now within Stripe’s ecosystem, Lago as an open-source and self-hostable option, Chargebee as an established subscription platform expanding its usage capabilities, Maxio as a finance-led system centered on ASC 606 revenue recognition, Stripe Billing as a payments-integrated billing option with expanded metering through Metronome, and Zuora as an enterprise global billing suite broadening into AI monetization. The guide emphasizes that in-house billing can offer initial control but often becomes costly as pricing metrics, credits, commitments, exceptions, compliance, and reconciliation needs grow, while the most suitable choice depends on whether an organization prioritizes CPQ and finance workflows, payments consolidation, infrastructure ownership, global enterprise requirements, or continuous pricing experimentation.

Usage-based billing is becoming increasingly common in SaaS and AI, with the source citing adoption by 74% of software suppliers, growing buyer preference for consumption pricing, and expanded demand from AI workloads measured through tokens, API calls, and compute use. It argues that granular, retained usage-event data is essential for accurate invoicing, retroactive adjustments, pricing simulations, audit trails, revenue recognition, and customer transparency, particularly as organizations manage larger and more complex software portfolios. Although many companies collect usage data and use it for upsell or churn analysis, the cited figures indicate persistent gaps in data quality, analysis, and automated engagement actions. The piece also links robust metering to potential financial benefits such as dynamic-pricing margin improvements, faster collections, and fewer billing disputes, while emphasizing security and compliance risks associated with sensitive usage data. It presents Orb’s raw-event architecture and high-volume ingestion capabilities as a solution designed to preserve event-level records, support flexible pricing changes, and provide traceability from consumption through invoice generation.

Usage-based pricing is becoming a mainstream revenue model across SaaS, AI, cloud infrastructure, telecommunications, and utilities, with market estimates projecting growth from roughly $8–9 billion in 2025 to $18–29 billion by 2034. Surveys cited in the material indicate broad adoption, including 85% of surveyed software companies and 77% of large software firms incorporating consumption-based elements, while hybrid models that combine subscriptions, minimum commitments, or seats with usage charges have become the most common approach among surveyed B2B software and AI companies. Hybrid pricing is associated in cited studies with comparatively strong median growth, although several performance claims regarding retention, conversion, and churn are described as publisher-reported associations rather than proven causal effects. The shift is driven by buyer demand for costs aligned with realized value, particularly amid rising SaaS prices, AI-related variable consumption, and unused software licenses, but it introduces risks such as unpredictable bills, with 78% of surveyed IT leaders reporting unexpected consumption or AI charges. Accurate metering, granular usage records, flexible billing logic, revenue forecasting, and spend controls are presented as essential infrastructure because inadequate systems may cause material revenue leakage and operational reconciliation burdens. North America leads current market revenue, Asia Pacific is projected to grow fastest, and cloud-based platforms dominate deployments, which are reported to be faster to implement than on-premises systems.

Usage-based billing links pricing to measurable customer value and can help businesses protect margins, monetize product adoption, and communicate value more clearly, but the appropriate starting point depends on cost pressures, product maturity, customer preferences, and product type. Companies can price around consumption metrics such as tokens or compute time when variable costs are the priority, action metrics such as workflows or agent runs when expanding capabilities need a revenue path, or outcome metrics such as resolved tickets when success can be consistently measured and trusted. Pricing should be treated as an iterative process rather than a one-time decision, with usage data and customer evidence supporting movement toward more abstract value measures over time. Many businesses combine fixed platform, seat, or tiered fees with usage-based charges in a hybrid “layer cake” model, using separate components to cover baseline access, variable infrastructure costs, feature adoption, and proven customer outcomes. Examples including Snowflake, Octave, Intercom Fin, HubSpot Breeze, and Vercel illustrate how companies apply these approaches through direct metering, credits, subscriptions, and outcome-based charges.

Amberflo has expanded from usage metering into AI governance, cost control, monetization, billing, and FinOps, prompting comparisons with platforms that address different consumption-based pricing needs. The guide evaluates Orb, Metronome by Stripe, Lago, Chargebee, Stripe Billing, Maxio, and Zenskar according to capabilities such as event-scale metering, flexible pricing models, customer-facing usage visibility, payment and accounting integrations, data residency, and finance workflows. Orb is presented as a usage-native platform emphasizing retained raw event data, SQL-defined metrics, pricing simulations, dimensional pricing, customer dashboards, and automated billing adjustments, with customer examples cited to support its scale and operational benefits. Metronome targets high-volume enterprise contracts within Stripe’s ecosystem, while Lago offers an open-source, self-hosted option for organizations prioritizing data sovereignty and engineering control. Chargebee and Maxio focus more broadly on subscription and finance-led operations, Stripe Billing offers simpler native metering for Stripe users alongside Metronome for advanced requirements, and Zenskar positions itself as an AI-native, no-code-oriented billing platform. The comparison concludes that platform selection depends on whether an organization primarily values AI cost governance, pricing experimentation, enterprise contract management, self-hosting, subscription operations, financial reporting, or customer-facing usage transparency.

SaaS pricing is shifting from fixed seat-based subscriptions toward usage-based and hybrid models as vendors raise prices faster than general inflation and seek to link charges more clearly to measurable customer value. The cited benchmarks report that 85% of a 100-company survey had adopted some usage-based pricing by early 2025, while hybrid subscription-plus-usage models showed the highest median growth and net revenue retention in several cohort analyses, though these figures indicate correlation rather than causation. Expansion revenue has become increasingly important, exceeding new-customer revenue for companies above $50 million in annual recurring revenue, making accurate metering, forecasting, billing transparency, and discount governance central operational concerns. AI monetization remains unsettled: 44% of surveyed SaaS companies charge for AI features, but subscriptions remain the most common approach, with hybrid and pure usage models growing and outcome-based pricing still rare. The report also highlights a gap between pricing’s strategic importance and its execution, noting that many leaders rely on intuition while data-led approaches are associated with stronger growth outcomes, and it promotes Orb’s billing infrastructure as a tool for managing complex usage, hybrid, and AI-related pricing models.

Modern B2B billing software increasingly supports usage-based and hybrid pricing for AI, cloud, and developer businesses that charge by tokens, API calls, compute, or other granular consumption measures, requiring high-volume event metering, flexible contracts, and integration with finance systems. The guide compares Orb, Metronome, Lago, Chargebee, Maxio, Stripe Billing, and Recurly, describing Orb as focused on raw usage-event retention, SQL-defined metrics, pricing simulations, dimensional pricing, credits, commitments, and invoicing; Metronome as an enterprise usage-billing product acquired by Stripe in January 2026; Lago as an open-source, self-hosted option; Chargebee and Recurly as subscription-oriented platforms that support usage billing; Maxio as a finance-centered SaaS billing and revenue-recognition platform; and Stripe Billing as an option closely tied to Stripe’s payments ecosystem. It notes that vendors differ in pricing models, integration depth, revenue-recognition capabilities, and operational ownership, while building billing internally can provide early flexibility but may become a long-term engineering and compliance burden. Key evaluation considerations include raw-event handling, rerating and backfills, pricing simulations, ERP and CRM integrations, audit controls, data sovereignty, and support for accounting standards such as ASC 606 and IFRS 15.

AI companies are increasingly moving from traditional seat-based subscriptions toward usage-based and hybrid pricing because their costs and customer value often scale with tokens, API calls, compute time, and other consumption measures. Cited surveys and pricing-page analyses indicate that usage components are common among AI and SaaS products, while hybrid models combine predictable subscription revenue with charges for variable use. The article attributes this shift to rising AI spending, margin pressure from cloud and inference costs, rapid changes in AI unit economics, and difficulties forecasting consumption, with many organizations reporting budget overruns, unexpected charges, and limited visibility into usage data. It also describes a variety of billing approaches, including prepaid credits, pay-per-use, tiered pricing, volume discounts, overages, token-based charges, and category-specific units such as voice minutes or compute resources. Although usage-based pricing is expanding rapidly, the piece notes that effective implementation depends on accurate real-time metering, flexible pricing systems, customer-facing usage visibility, forecasting, budget controls, and the ability to test and revise pricing models; it presents Orb’s billing platform as a tool intended to provide these capabilities.

Enterprise billing software has expanded from subscription invoicing into infrastructure for usage-based, hybrid, and consumption-driven pricing, requiring coordination among product, sales, engineering, finance, and revenue operations teams. The guide compares Orb, Metronome, Flexprice, Stripe Billing, Chargebee, Lago, and Maxio based on pricing flexibility, event metering, invoicing, payment processing, financial reporting, deployment options, and support for retroactive corrections. It presents Orb as a comprehensive usage-based billing platform distinguished by persistent raw-event storage, SQL metrics, dimensional pricing, pricing simulations using historical data, invoicing, accounts-receivable workflows, revenue recognition, and integrations such as NetSuite, while noting its acquisition by Adyen in 2026 and continued processor flexibility. Metronome is positioned for high-volume usage billing within the Stripe ecosystem, Stripe Billing for payments-integrated subscriptions and metered usage, Chargebee and Maxio for established subscription and finance operations, and Flexprice and Lago for organizations seeking open-source transparency or self-hosting. The guide emphasizes that raw-event retention, pricing versioning, invoice-finalization rules, and adjustment policies affect rerating capabilities, while implementation timelines depend heavily on project scope. It also frames in-house billing as an alternative that offers early control but can become a long-term engineering and operational burden as pricing and contract complexity increase.

Usage-based billing is rapidly becoming a dominant revenue model across various industries, including telecom, utilities, finance, healthcare, and particularly SaaS, as it aligns charges with actual customer consumption, offering flexibility and expansion potential. A report projects the cross-industry usage-based billing market to grow from $9.4 billion in 2025 to $28.6 billion by 2034, with SaaS adoption surpassing 59% by 2025. The hybrid billing model, combining fixed subscriptions with usage-based components, shows the highest growth potential, with companies reporting a median growth rate of 21%. Cloud-based billing solutions are favored for their faster implementation and lower overhead, capturing 67.8% of the market revenue in 2025. Large enterprises contribute significantly to market revenue, emphasizing the need for robust billing infrastructure that can handle metering, invoicing, and reconciliation, as well as offer transparency and accuracy in billing processes. Despite the challenges of transitioning to a usage-based model, companies like Vercel and Stytch have successfully reduced billing-related engineering time and operational inefficiencies through specialized billing platforms like Orb, which supports metering accuracy and financial compliance.

Lago is an open-source billing infrastructure option that offers flexibility for businesses emphasizing vendor independence, enabling them to manage where billing data resides through various deployment models like self-hosted and cloud options. However, as companies grow, the responsibility of managing a self-hosted billing stack can become burdensome, prompting many to seek alternatives that provide managed infrastructure and enterprise-grade pricing execution. This guide evaluates seven alternatives, with emphasis on usage-based billing maturity and financial operations readiness. Orb emerges as a notable contender, offering SQL-based billable metrics, pricing simulations, and a robust managed infrastructure capable of handling high event throughput. Its platform supports complex pricing models and boasts integrations with finance systems like NetSuite, accommodating diverse billing needs and demonstrating significant customer success in reducing billing setup times and enhancing revenue growth. Orb's built-in pricing simulations and enterprise-scale metering position it as a comprehensive solution for organizations seeking to transition from self-managed to managed billing systems, particularly for AI companies and API providers handling large volumes of transactions.

Stripe Billing is a useful tool for companies reaching their initial millions in annual recurring revenue (ARR), but its limitations become evident as pricing models grow more complex. Companies often experience bottlenecks in engineering, finance, and sales due to Stripe Billing's constraints in handling advanced pricing structures. Instead of replacing Stripe Payments, many modern SaaS companies are opting to upgrade their billing systems with specialized usage-based billing engines like Orb, which offer greater flexibility in pricing models and revenue operations. This approach allows companies to retain their existing payment-processing setup while gaining the ability to manage complex pricing models, usage metering, and operational workflows. Orb's migration guidance emphasizes the retention of customer records, tax configurations, and payment methods, ensuring a seamless transition without requiring customers to re-enter payment details. Despite Stripe Billing's limitations, it remains a convenient option for companies with straightforward pricing needs, but for those experiencing operational friction, transitioning to a dedicated billing platform can streamline processes, reduce engineering dependencies, and support dynamic pricing strategies.