February 2026 Summaries

In the development of their AI features, a company focused on creating distinct, task-specific AI assistants rather than general-purpose chatbots, to add unique value and avoid the pitfalls of broad applications. They introduced three AI-powered assistants: a billing assistant that automates repetitive workflows, a finance assistant that generates custom reports, and a planned pricing assistant for strategy advice. This strategic delay in releasing AI features was due to the high stakes involved in financial operations, which require precision and reliability to avoid errors such as accidental refunds or unauthorized discounts. The company emphasized the importance of building true agents capable of operating APIs, rather than just chatbots, to handle intricate billing tasks with necessary safeguards, such as role-based access controls and multi-layered hallucination prevention. Despite challenges like scope expansion and the complexity of prompt engineering, the company's thoughtful approach highlights the necessity of balancing innovation with caution and learning from iterative development processes.

As global data protection laws tighten, the choice between self-hosted and cloud billing platforms has become a critical compliance decision, particularly for regulated industries like financial services, healthcare, and government. The sovereign cloud market is expanding, reflecting the increased emphasis on data residency, driven by regulations such as GDPR, DORA, and the US CLOUD Act. Self-hosted billing offers verifiable data locality, security control, and audit trail integrity, making it suitable for industries with strict data residency mandates. Conversely, cloud billing platforms provide operational simplicity, faster deployment, and automatic updates, benefitting companies with less restrictive compliance needs. However, cloud solutions pose risks of vendor lock-in and compliance gaps if data is routed through unauthorized regions. Open-source billing platforms offer a middle ground by combining the data sovereignty of self-hosting with the feature velocity of commercial platforms, enabling organizations to balance regulatory compliance with operational efficiency. As regulations continue to evolve, companies must carefully evaluate their billing infrastructure choices to avoid accumulating technical and regulatory debt.

Proration in SaaS billing is a critical yet often misunderstood process involving the calculation of partial charges or credits when a subscription changes mid-billing cycle, such as through upgrades, downgrades, or cancellations. As SaaS models increasingly combine subscription and usage-based elements, proration has become more complex than simple per-day calculations, with errors potentially undermining customer trust and complicating revenue reconciliation. The proration formula typically calculates the charge difference based on the remaining days in a billing cycle, but various factors such as billing granularity, cycle length, and payment timing (advance or arrears) can influence outcomes. Edge cases, including multiple plan changes within a single period, trial-to-paid conversions, and switches between monthly and annual billing, further complicate proration. Usage-based charges also intersect with proration, requiring billing systems to accurately apply different rates pre- and post-upgrade. Effective proration requires robust billing infrastructure capable of tracking plan changes with timestamp-level precision, maintaining a detailed subscription ledger, and generating accurate credit notes. These challenges underscore the importance of using specialized billing platforms that can handle the intricacies of proration and ensure compliance with revenue recognition standards like ASC 606.

Failed payments pose a significant risk to revenue in SaaS businesses, with an estimated 9% of recurring revenue lost annually due to this issue. Involuntary churn, often caused by expired cards or temporary holds, accounts for 20-40% of total churn in subscription-based businesses. Dunning management, which involves the automated recovery of failed payments through intelligent retries, customer communication, and escalation workflows, can recover 70-80% of these payments. Effective systems operate across three phases: pre-dunning, active dunning, and post-dunning, each with specific strategies such as account updater services, smart retry logic, and personalized communication. Pre-dunning focuses on preventing failures by updating card details and notifying customers of impending expiration, while active dunning aims to resolve issues quickly through retries and multi-channel outreach. Post-dunning involves grace periods, service degradation, and win-back campaigns for accounts that remain unresolved. The success of dunning management is measured by recovery rate, time to recovery, involuntary churn rate, and revenue recovered, with high-performing systems achieving recovery rates of 70-80%. Implementing a robust dunning system is crucial for minimizing involuntary churn, protecting monthly recurring revenue, and maintaining customer relationships.

Product-led growth (PLG) has emerged as a dominant strategy in the SaaS industry, with a focus on allowing users to experience value before committing to payment, often through a free tier with progressive paid features. However, the success of PLG largely hinges on the efficiency of billing infrastructure, which needs to support real-time usage metering, flexible pricing models, and seamless self-serve payment flows to drive conversion and revenue expansion. Companies with robust self-serve billing capabilities convert more free users to paid plans, whereas those with inadequate systems face challenges such as slow pricing iterations, revenue leakage, and engineering teams burdened with billing maintenance. Effective billing systems in PLG contexts involve complex scenarios like real-time usage tracking, automated alerts, and hybrid pricing models, enabling companies to adapt rapidly to market demands and optimize customer conversion and retention. As PLG companies scale up, especially towards enterprise contracts, their billing infrastructure must accommodate custom pricing and multi-entity billing, ensuring both flexibility and precision, thereby cementing billing as a core product function rather than a mere back-office operation.

Billing tax automation for SaaS companies involves the real-time calculation and application of sales tax, VAT, and GST across numerous jurisdictions, which is increasingly necessary due to the complexity and frequency of tax rate changes. The process is crucial for compliance, as manual tax management becomes unfeasible with cross-border sales, risking either audit liabilities from undercollection or customer disputes from overcollection. Automated systems integrate with real-time tax data providers to ensure accurate tax application based on customer location and product classification, while also maintaining necessary audit trails. The 2018 South Dakota v. Wayfair decision expanded the concept of economic nexus, requiring SaaS companies to comply with tax obligations in any U.S. state where they meet specific revenue or transaction thresholds. Globally, VAT obligations are triggered by the customer's location, complicating compliance further, especially with the EU's VAT rules and the One Stop Shop mechanism. Each country's GST system, such as those in Australia, India, and Singapore, adds another layer of complexity to tax rules. A comprehensive tax automation stack includes a calculation engine, product taxability matrix, customer tax profiles, and a filing module, often integrated with tax providers like Avalara AvaTax for streamlined operations. These systems are crucial to avoid penalties, reduce operational overhead, and prevent customer trust erosion due to incorrect tax handling. E-invoicing mandates add another dimension, requiring billing systems to produce machine-readable invoices with embedded tax calculations, underscoring the need for modern billing infrastructure that can adapt to these evolving requirements.

Fintech companies face unique billing challenges that differ significantly from those of traditional SaaS businesses due to the complexities of multi-currency transactions, real-time settlement, and stringent cross-jurisdictional regulatory compliance. The $1.5 trillion cross-border B2B payments market is growing rapidly, and fintech billing systems must navigate multi-currency conversions, regulatory shifts like PSD3 and DORA, and the adoption of standards like ISO 20022. Unlike SaaS billing, which typically involves predictable cycles, fintech billing requires handling of multiple currencies—transaction, billing, and reporting—introducing exchange rate risks and reconciliation complexities. Real-time settlement further complicates the process, necessitating per-transaction fee calculations and the ability to manage multiple payment processors to ensure compliance and mitigate risks. The need for a robust billing infrastructure is underscored by regulatory requirements, such as comprehensive audit trails for transparency and operational resilience under DORA. Moreover, fintech companies often operate across multiple jurisdictions, requiring billing systems to handle diverse tax rules and e-invoicing mandates, as well as multi-entity billing configurations for regulatory and commercial flexibility. The infrastructure must support dynamic pricing models, real-time event processing, and multi-currency wallets, with a growing preference for self-hosted solutions to ensure data sovereignty and compliance.

Selecting a billing platform is a critical decision for SaaS companies, as it influences pricing agility, engineering resources, and scalability from self-serve to enterprise levels. Many companies reactively choose between building in-house or purchasing a vendor solution, often leading to inefficiency, with 55% unable to promptly adjust pricing strategies despite frequent changes. Most SaaS firms are advised to buy a commercial billing platform, as constructing one in-house is resource-intensive and shifts engineering focus from product development to system maintenance. Building is only recommended for companies with unique billing needs or regulatory demands, though even these often utilize open-source cores. The evaluation of a billing platform should consider pricing flexibility, metering, payment infrastructure, enterprise readiness, and integration architecture, with vendor lock-in being a significant concern. Open-source platforms offer transparency, flexibility, and community-driven development, appealing to companies needing control and avoiding vendor dependency. Total cost of ownership extends beyond fees to include integration, maintenance, and potential migration costs, emphasizing the importance of choosing a platform that aligns with long-term growth and pricing strategies.

Revenue leakage in SaaS billing is a covert financial loss caused by discrepancies in metering, invoicing, pricing enforcement, and payment collection, which can account for 1% to 5% of a company's annual revenue. These losses are not as apparent as customer churn, as they often go unnoticed due to their dispersed nature across various small gaps, such as unmetered API calls, proration errors, and failed payment recoveries. The causes of revenue leakage include metering gaps, pricing enforcement failures, proration errors, failed payment recoveries, credit miscalculations, and contract-to-invoice mismatches, which are exacerbated by the complexity of pricing models. Detecting these leaks requires systematic data layer comparisons and automated reconciliations to identify discrepancies. Preventative measures involve robust billing infrastructure, real-time metering, automated pricing enforcement, and continuous reconciliation between billing and payment systems. Companies using sophisticated billing systems and automated credit management can significantly reduce revenue leakage and improve their financial outcomes.

The author reflects on their five-year journey as a founder of Lago, highlighting the emotional and personal challenges faced along the way. Initially grappling with feelings of not belonging and pressure to conform to societal expectations, they left a prestigious career at McKinsey to find fulfillment in entrepreneurship. Despite lacking a singular mission, the author's drive to create a "home" where they felt truly aligned propelled them forward. They discuss the pitfalls of comparing oneself to seemingly successful peers and emphasize the importance of building genuine relationships, both with their co-founder and in their personal life. The narrative underscores the value of trusting one's instincts, cultivating meaningful connections, and recognizing that sustainable success comes from internal satisfaction rather than external validation. Through introspection and perseverance, they seek to inspire other founders to navigate their own paths with authenticity and resilience.

GPU billing in the AI economy is complex due to the variable and continuous resource consumption it measures, which requires a sophisticated infrastructure for metering, pricing, and invoicing. Essential challenges include hardware heterogeneity, job variability, and cost of goods sold (COGS) volatility, all of which necessitate dynamic pricing models that account for GPU type, memory, and usage patterns. The guide outlines practical metering primitives such as GPU-hours, tokens, and VRAM, and explores pricing models like per-hour, per-inference, and dynamic pricing to manage these complexities. It also addresses edge cases such as idle time and preemption, along with implementation strategies for enterprise billing solutions that include contract-level controls, multi-entity invoicing, and real-time dashboards. The open-source platform Lago is highlighted as a tool that automates these processes, offering progressive billing and compliance features that enhance revenue predictability and customer satisfaction.

Pricing experimentation is crucial for optimizing SaaS pricing models, yet many companies face challenges due to the limitations of current billing systems, which often turn these experiments into complex engineering projects. The document highlights the necessity of conducting systematic pricing experiments without disrupting existing customers or creating billing errors, emphasizing the use of tools like Lago that support safe and repeatable tests. It outlines the common constraints of billing systems, such as the immutability of plans and the manual, error-prone nature of rollbacks, which prevent frequent experimentation. The text describes several key experiments SaaS companies should undertake, including new customer price testing, usage threshold testing, packaging experiments, discount testing, and billing model experiments. To conduct these experiments effectively, the document suggests adopting the experiment isolation pattern, which minimizes disruptions to the billing engine, and emphasizes the importance of using customer metadata and plan overrides to manage changes safely. Additionally, it provides guidance on measuring the impact of pricing experiments, focusing on metrics like revenue per customer, conversion rates, and customer lifetime value, while also warning against common pitfalls such as testing too many variables simultaneously and ignoring unit economics.

Marketplaces and platforms face unique billing challenges compared to traditional SaaS companies, as they must manage complex processes involving multiple parties, real-time transactions, and tax obligations. Lago offers an open-source billing infrastructure tailored to address these complexities, including features like native revenue-share capabilities, percentage-based charges, and multi-entity support, which help reduce time-to-cash and operational billing errors. The platform boasts the ability to handle high-volume metering, invoicing significant monthly sums, and maintaining high uptime, serving clients such as PayPal and Mistral AI. The guide provides insights on building scalable marketplace billing systems, highlighting differences from standard SaaS billing, various revenue split models, multi-party invoicing, tax implications, payout management, and architecture patterns. It emphasizes the importance of choosing the right SaaS pricing models, which can affect seller economics and platform revenue, with a notable shift towards value- and usage-based pricing models. The text also details the technical architecture for marketplace billing, tax considerations, revenue recognition, payout management, and dispute handling, advocating for the use of billing platforms like Lago to manage complexity effectively.

In January 2026, Stripe acquired Metronome for approximately a billion dollars, highlighting the architectural limitations of Stripe Billing that was originally designed for the SaaS subscription model prevalent in 2018. Stripe's existing billing system faced challenges with real-time event ingestion and multi-dimensional metering needed for AI-native companies and others adopting AI features, as it was built on pre-aggregated data and synchronous HTTP request-response cycles. The acquisition of Metronome, which had already addressed these complexities for companies like OpenAI, was seen as more feasible than overhauling Stripe's existing architecture, which would have required extensive changes and risked breaking current integrations. Stripe's acquisition strategy reflects a broader industry pattern where companies choose to acquire rather than build new capabilities internally due to architectural constraints. As billing complexity grows with AI and companies seek diversification in payment processing, the integration of Metronome will test whether Stripe can successfully merge the two systems or if they will remain parallel offerings.

PayPal's decision to integrate Lago for its billing infrastructure highlights a shift in the financial services market towards embedded open-source solutions, which offer both speed and control without the constraints of proprietary systems. As complex billing becomes increasingly crucial due to AI-driven cost changes and evolving pricing models, companies like PayPal are opting for solutions that provide code transparency, self-hosted deployment, and strategic flexibility. Lago's open-source platform allows PayPal to customize billing systems at the code level, ensuring compliance and security while maintaining a high processing capacity with 99.9% uptime. This approach enables PayPal to avoid long development timelines and vendor lock-in, providing a competitive edge by allowing rapid innovation and adaptation to market needs.

Multi-entity billing has become essential for SaaS companies expanding globally, as it enables them to issue legally compliant invoices from the correct subsidiary based on customer jurisdiction, which is crucial for closing enterprise deals and avoiding compliance risks. As most billing platforms are designed for single-entity operations, companies face challenges such as manual workarounds that slow revenue recognition and introduce errors. The transition to multi-entity billing intersects with various logistical and legal aspects, including data residency laws, payment processor routing, tax automation, and ERP integration. The growing cross-border B2B payments market, valued at $1.5 trillion, underscores the importance of this transition. Companies benefit from implementing multi-entity billing when entering new jurisdictions, meeting local tax registration obligations, or managing mergers and acquisitions. The architecture of multi-entity billing can be centralized, distributed, or hybrid, each offering different trade-offs in terms of simplicity, compliance, and cost. The system requires meticulous management of tax compliance, entity identifiers, and intercompany pricing to avoid costly errors. Implementation involves defining an entity footprint and configuring entity-level settings, routing rules, and tax automation. Effective multi-entity billing ensures seamless reporting and ERP integration to provide comprehensive financial insights, helping companies close their books more efficiently and maintain clean financial operations. Common pitfalls include over-provisioning entities, commingling funds, and failing to communicate entity changes to customers, which can result in financial discrepancies and eroded trust.

Billing observability leverages DevOps-grade monitoring to ensure revenue systems function with the precision of production infrastructure, addressing the financial and regulatory risks of enterprise billing solutions. It involves tracking real-time outputs such as usage events, aggregated charges, invoices, payments, and revenue-recognition status to detect and resolve issues before they impact customers. Essential components include logs for audit trails, metrics for real-time financial KPIs, and traces for end-to-end billing correlations. Lago, an open-source billing platform, supports these observability practices by providing high-volume billing solutions with real-time ingestion, transaction tracing, and customer-facing portals. The approach is crucial for handling complex, high-volume invoicing with accuracy, visibility, and compliance, ultimately improving cash flow, reducing revenue leakage, and minimizing billing-related churn. Observability in this context is distinct from retrospective revenue analytics, as it focuses on real-time operational insights to prevent financial losses. Enterprises are encouraged to implement a comprehensive observability strategy using standards like OpenTelemetry to enhance pipeline reliability and customer trust, with Lago offering a scalable solution tailored to these needs.

Migrating from a legacy billing system to a modern platform is a crucial yet risky endeavor for SaaS companies, aiming to improve cash flow, reduce billing errors, and enhance pricing strategies. This comprehensive guide outlines a six-phase migration playbook, covering assessment, platform selection, architecture, parallel run, full cutover, and optimization, with detailed strategies to preserve historical billing data and ensure operational continuity. It highlights the importance of using open-source billing platforms like Lago, which provide transparency, control, and flexibility, reducing vendor lock-in and enabling faster pricing launches. The guide emphasizes the need for disciplined planning, rigorous validation, and phased execution to avoid common pitfalls such as data complexity underestimation and insufficient edge-case testing, while also illustrating successful migration through a B2B fintech case study, demonstrating significant reductions in engineering time and processing fees.