The cloud bill and the margin
Software margins are under pressure from infrastructure and inference costs, and the pressure is uneven across customers. A healthy blended margin routinely hides accounts that lose money. Recovering it is a multi-quarter program, not a cost-cutting exercise.
The eighty percent gross margin was a feature of a specific technical era, when replication was free and cloud infrastructure had finished commoditizing. That era is ending unevenly, and the unevenness is the interesting part.
The aggregate numbers still look calm. Benchmarkit’s 2026 metrics report finds median software gross margin holding above 80 percent and stable across four years, and concludes that industry-wide infrastructure costs have not yet compressed software margin at the median.
The cohort numbers do not look calm at all. ICONIQ’s January 2026 snapshot put average gross margin for products with substantial inference costs at 52 percent, up from 45 percent in 2025 and 41 percent in 2024. Aleph’s 2026 data puts usage-only pricing models at 62 percent gross margin, well below the 80 percent software median, because compute cost scales with revenue. And several public software companies began disclosing inference cost as a separate line in early 2026, typically in the range of 4 to 9 percent of revenue.
The mechanism at the unit level is easy to see. Ben Murray of The SaaS CFO walked through the arithmetic for a typical product team: add an assistant feature to an eighty dollar per month seat, and inference, routing and supporting infrastructure can add roughly fifteen dollars of direct variable cost, taking gross margin on that seat from 80 percent to closer to 65 percent.
Why the blended number hides the problem
Because cost to serve varies enormously by account, and revenue does not.
A company with a healthy company-wide margin can contain a set of enterprise accounts running at a fraction of it, driven by heavy usage, unmanaged data retention, custom infrastructure or bespoke integrations negotiated years ago at a price that no longer covers the cost. Nobody notices, because nobody calculates margin per customer. The account is large, visible and celebrated, and it is subsidized by the rest of the base.
Why this is board work
Because the fix is architectural and commercial at the same time, and it takes several quarters.
The commercial half is repricing the accounts that do not cover their cost, which is a negotiation with a customer who currently believes they have a good deal, and which cannot be done to all of them at once without a churn event.
The technical half is cost attribution before optimization. You cannot manage cost to serve you cannot see, and most companies at this size cannot attribute infrastructure cost to a customer at all.
Neither half completes inside a hundred days, and both drift the moment nobody is asking. The measurement that keeps it honest is gross margin by customer cohort, reviewed quarterly, against the plan agreed at close.
More teardowns
Nobody can state the ROI, so nobody can defend the price
A company that cannot express what its product is worth in the customer's own numbers will discount under pressure, lose renewals it should win, and never raise prices. This is one of the most tractable problems in the first hundred days after an acquisition.
Pricing built before the market changed
Most software companies at this size price per seat, on a model set years ago. Buyers increasingly want to pay for consumption or for outcomes, and investors increasingly prefer it. Moving is valuable and moving carelessly transfers real risk onto the vendor.
Last updated