Showing 1–19 of 19 dossiers

Stripe says hybrid pricing has crossed from AI experiment to real adoption

The useful signal is not that every SaaS company should add usage billing. Stripe/Metronome says hybrid pricing went from barely used to roughly one in six qualifying Stripe users, while many AI products are hiding token metering behind credits or output units so customer invoices describe value rather than model cost.

SaaSPricing & BillingActive dossier

Paddle brings recurring Pix payments to SaaS subscriptions in Brazil

Brazilian customers can authorize Pix Automático mandates for Paddle subscriptions without a separate early-access application. The path broadens local-payment access for SaaS, while delayed renewals, fixed mandate amounts and re-authorisation requirements still create implementation caveats.

GitHub Copilot is moving enterprise seats to upfront billing and longer chat retention

From September and October, Copilot Business and Enterprise seat access becomes more tightly coupled to upfront payment. A separate September 28 policy migration enables a unified Copilot experience by default, retains github.com chat data for the life of the account and changes code review’s default effort from Lite to Balanced.

Private SaaS median ACV falls to $24K as bootstrapped firms stay on smaller contracts

The latest private-SaaS deal-size benchmark shows median ACV moving down, with bootstrapped companies at $18,643 versus $39,880 for equity-backed peers. For small SaaS operators, the useful question is whether larger contracts improve retention and economics enough to justify the longer sales motion.

Google is adding hard spend caps and commitment pricing for AI agent workloads

Google’s new agent FinOps model combines hard monthly spend caps that pause agent API calls, Flexible Savings Plans with one- or three-year commitments, pay-as-you-go Gemini Enterprise usage and planned deferred execution at up to half normal inference cost. The controls are useful, but commitment economics and task eligibility need to be modeled carefully.

Pricing turns product value into a business, while billing turns that promise into a system customers must trust. Usage-based plans, seat changes, payment rules and platform fees can reshape both margins and customer behaviour even when the underlying software barely changes.

BTN follows meaningful pricing moves and billing infrastructure developments from an operator perspective. Coverage asks what a change does to unit economics, implementation complexity, international sales and the customer relationship. It also separates a pricing experiment from a durable market shift. The aim is practical context for people setting plans, maintaining billing code or evaluating a vendor whose fee structure may become part of their own cost base.

Tax handling, failed-payment recovery, invoices and cancellation flows are part of the same system even when a pricing announcement ignores them. Coverage keeps those operational edges visible. A plan is only workable when the business can explain it clearly and the billing implementation matches what customers were promised.