AI companies are discovering that metering what customers consume is only half the billing problem. The harder part is connecting contracts, real-time entitlements, usage data and invoices without forcing finance and engineering teams to maintain separate systems. Stigg is addressing that gap by acquiring Received.ai, a billing infrastructure startup focused on usage-based invoicing and contract management, and integrating its technology into Stigg’s platform.
The economics of enterprise software are changing as AI applications move away from predictable per-seat subscriptions toward credits, consumption and usage-based pricing.
That shift is creating a new infrastructure problem. Software companies need to know not only what a customer has purchased, but what that customer—or an AI agent acting on its behalf—is permitted to consume at a particular moment, how much that usage costs under a contract, and how it should ultimately appear on an invoice.
Stigg says its acquisition of Received.ai is designed to bring those steps together.
Received.ai’s billing technology is being integrated into Stigg, allowing companies to connect contract terms with live entitlements, usage metering and invoicing. The companies describe the combined platform as an infrastructure layer for AI and modern SaaS businesses rather than a replacement for payment processors or enterprise accounting systems.
That distinction is important.
Stripe, NetSuite, Airwallex and Checkout.com can handle important parts of payments and financial operations, but the handoff between a signed enterprise contract and the actual product permissions can remain highly manual. A sales agreement may contain custom pricing, usage thresholds, credits, mid-cycle amendments or multiple products that do not map neatly onto a standard checkout flow.
For AI companies, those problems can become particularly complex.
A conventional SaaS subscription might grant 50 employee seats for $5,000 per year. An AI platform could instead charge for tokens, model calls, compute, storage, workflow executions or credits. Customers may have different rates, minimum commitments and overage rules. Those variables need to be enforced during product usage and reconciled later by finance.
Stigg’s core technology addresses the first half of that equation. Its runtime entitlement layer determines whether a customer, user, team or AI agent is allowed to perform an action at the point of use.
The Received.ai acquisition extends that model downstream into billing.
According to Stigg, the combined platform can now convert signed contracts into live entitlements and invoices without requiring customers to build custom engineering workflows. New capabilities in public beta include contract management, automated entitlement provisioning, flexible billing schedules, prorations, credit logic, formula-based pricing and consolidated invoices.
The formula-based pricing component is particularly relevant to AI businesses. Rather than hardcoding a fixed rate into application logic, companies can use formulas to calculate charges at invoice time based on their pricing model.
That matters as AI pricing becomes more sophisticated.
A customer might pay a platform fee, receive a monthly credit allocation and then pay different rates for additional model usage. Another might have negotiated rates for different products or regions. Enterprise contracts can introduce another layer of complexity with minimums, discounts and amendments.
The infrastructure challenge is therefore less about generating an invoice than maintaining a consistent source of truth from contract to entitlement to usage to invoice.
Received.ai founder and CTO Shai Betito is joining Stigg as vice president of engineering and will lead the integration alongside the founding team. Stigg says the technology is already fully integrated into its platform.
The acquisition also illustrates a broader change in the SaaS infrastructure market.
For years, product-led growth encouraged software companies to build relatively standardized subscription and checkout flows. AI is making that model less universal. Consumption can fluctuate dramatically, customers can share resources across teams, and autonomous agents can generate usage without a human directly initiating every transaction.
That creates demand for infrastructure capable of enforcing commercial policy at runtime.
The emerging category is sometimes described as usage-based billing infrastructure, but that label increasingly understates the problem. Modern AI companies need pricing infrastructure that connects product behavior with commercial agreements.
Stigg is positioning itself around that convergence.
The company says the new billing functionality is additive and can operate alongside existing invoicing and payment systems. That could reduce the adoption barrier for enterprises that already rely on established financial infrastructure. Rather than replacing Stripe or NetSuite, Stigg can sit between the commercial contract and those downstream systems.
For finance teams, the appeal is cleaner reconciliation. For engineering teams, it can mean fewer bespoke billing rules embedded in application code. For sales organizations, the promise is that negotiated terms can become enforceable product configuration rather than another spreadsheet handed from one department to another.
There are competing approaches. Billing platforms such as Stripe Billing and Chargebee already support subscription and usage-based models, while Zuora has long focused on complex monetization and recurring revenue management. Stigg’s differentiation is its emphasis on runtime entitlements and authorization, combined with contract and invoice infrastructure.
That positioning may become more valuable as AI agents become customers’ active users of software.
An AI agent may need permission to invoke a model, consume credits, access an API or execute a workflow. Those permissions can depend on customer plan, remaining quota, contract terms or real-time usage. A system that can enforce those rules and subsequently translate the activity into billing data provides a tighter connection between product control and monetization.
Stigg says its contract management and invoicing capabilities are now available in public beta following demand from customers in its private beta, with broader general availability planned throughout 2026.
The bigger question is whether AI companies will increasingly consolidate these functions into a dedicated monetization layer.
If usage-based pricing becomes the default rather than the exception, the contract-to-invoice handoff could become as important an infrastructure layer as authentication, payments or observability. Stigg’s acquisition suggests the market is beginning to treat that handoff as a technical problem—not merely a finance workflow.
Market Landscape
The rise of AI is reshaping SaaS monetization. Traditional seat-based subscriptions remain important, but AI vendors increasingly experiment with usage-based pricing, credits, consumption tiers, hybrid subscriptions and outcome-oriented pricing.
That creates an infrastructure stack involving several distinct layers:
- Contract management: What commercial terms did the customer agree to?
- Entitlements: What can the customer, employee, team or AI agent actually do?
- Metering: What did the customer consume?
- Pricing: How should that consumption be calculated?
- Invoicing: What does the customer ultimately owe?
- Payments and accounting: How does money move and enter financial systems?
Historically, those responsibilities have often been distributed across product, engineering, sales operations, billing and finance platforms.
Stigg’s acquisition targets the seams between those layers.
The competitive landscape includes Stripe, Chargebee, Zuora and other billing platforms, while enterprise systems such as NetSuite remain important financial systems of record. Stigg’s narrower strategy is to connect runtime authorization and entitlement decisions with commercial terms and billing.
That distinction could become more important as agentic AI expands. Gartner has forecast that 33% of enterprise software applications will include agentic AI capabilities by 2028, up from less than 1% in 2024.
The more software is operated by autonomous agents, the more important it becomes to determine what an agent is authorized to consume—and what that consumption costs.
Top Insights
- Stigg acquired Received.ai to connect contract management, real-time entitlements and invoicing, addressing a growing infrastructure problem for usage-based AI and SaaS businesses.
- AI pricing is becoming more complex, with credits, consumption, model calls and hybrid contracts replacing simpler per-seat subscription structures across many emerging software companies.
- The combined platform complements existing financial systems, including Stripe and NetSuite, rather than requiring customers to replace established payment or accounting infrastructure.
- Runtime entitlements are becoming commercially important, because AI agents can generate usage autonomously and require explicit limits around permissions, quotas and customer contracts.
- Stigg enters a competitive billing market, but differentiates through the connection between product authorization, usage enforcement, contracts and downstream invoice generation.
Power Tomorrow’s Intelligence — Build It with TechEdgeAI
