Talk to an Expert

// The Architecture Read

The 2026 Read · Edition One

The Software Pricing Architecture Read

The state of software pricing architecture, from observed behavior.

The Software Pricing Architecture Read is Software Pricing Partners’ account of how B2B software pricing moved this past year, drawn from the pattern library behind every Read we have published. It is for the CEO, CFO or pricing lead deciding whether to raise list prices, freeze them, repackage, or change the licensing metric.

Each section states one finding and the evidence behind it; the last shows every finding as one pricing architecture seen from three decisions. For the same reading on your deals, Pricing Ground Truth does it the same day your exports land. Follow the year’s moves, vendors’ dated pricing changes, in the Pricing Observatory, or start with your own numbers.

There is no fee and nothing to download.

01 · The headline read

The year’s reading is plain: software pricing architecture moved far less than the market’s noise implied, and decided far more. Fewer than one SKU in five with a multi-year price history was ever repriced; where list moved, it moved as a batch calendar event, about once a year.

Raises land clean more often now than they did through the inflation years, as repricing became a normal event rather than an ambush. That is the read for 2026: the companies that treat pricing as architecture are pulling away from the companies that treat it as an event.

Deeper in the year’s variance findings is the one that inverts the org chart: in where realized price finally lands, the rep who closed the deal barely registers. Section 04 shows the anatomy.

02 · The repricing record

Most software was never repriced at all.

Across the pattern library, fewer than one SKU in five with a multi-year price history was ever repriced: 18.6 percent. Where list prices moved, they moved as batch calendar events, about once a year at most; continuous repricing was the rare exception.

The cost of standing still does not appear on the list price; it appears underneath it. Where nobody maintains the pricebook, per-customer discounts drift deeper year over year. We have watched 92 percent discount norms emerge from sales floors that started at 70 percent. Where the pricebook is maintained, the same drift does not appear.

03 · What happens when list moves

A raise passes clean, or it dies.

On list increases the pattern is unambiguous: a raise either passes fully into net prices, or the field discounts deeper against the new list and the company books higher discount percentages instead of higher revenue. There is almost no middle ground.

The clean-pass share tracks how disciplined the vendor’s list is; across the modern pattern library it runs from about two in five to half. Whether a raise holds is decided by the architecture underneath it, long before the raise ships.

04 · The two disciplines are one muscle

Freezing list did not stabilize pricing. It moved the chaos.

Companies that stopped maintaining list prices did not stabilize pricing; they moved the chaos into the discount column. Across the pattern library, companies running a static list spread comparable customers across roughly twice the range of net prices for the same product in the same period.

Pricebooks re-rated on an annual cycle held the same spread near 1.4x. Maintaining the pricebook and managing the discount column are one muscle; unused on one side, the variance shows up on the other.

From the pattern library

The anatomy of price variance.

The industry’s default story assigns realized price to the people closing the deals. The variance decomposition disagrees.

Which product, on which pricebook

nearly nine tenths of realized price variance

Which customer is buying

about a tenth

Which rep closed the deal

barely registers

The rep barely registers.

The deal-closer explains almost none of where realized price lands. An organization coaching its reps on price is managing the sliver and inheriting the nine tenths it never touched. Pricing outcomes are architecture outcomes.

05 · The hidden free-goods economy

A packaging decision, executed through the discount column.

A hidden free-goods economy runs through the discount column. In our pattern library, up to 63 percent of a company’s total list value shipped at a 100 percent discount, almost entirely as carry-along lines inside multi-SKU deals.

At that point the reported discount rate is substantially a packaging effect rather than a price concession. The company is making packaging decisions, deal by deal, through the one column nobody governs, and reading the result as a discounting problem.

06 · The negotiation fingerprint

Discount magnitudes are socially constructed.

In the most negotiation-driven records in our pattern library, up to 87 percent of discounts land on a multiple of five, against a baseline near 12 percent when discounts are computed rather than negotiated. A heavy round-number fingerprint means price realization is a negotiation ritual, not an architecture output.

This one is a self-service diagnostic. Look at your own deal record: if discounts bunch on round numbers, the number was talked into existence rather than computed. Reps negotiate on the terrain the architecture gives them.

07 · The renewal pipes

Renewal uplift runs through two different pipes.

Companies that maintain the pricebook raise net prices through it at renewal. Static-list companies raise net with list flat, through silent discount retraction. And a third group leaves renewal pricing on the table entirely, with a large share of renewals booking dead flat.

Silent discount retraction is unpriced, rep-negotiated drift that a maintained pricebook would formalize. The question for any leadership team is which pipe its renewal revenue runs through, and whether anyone chose it.

08 · The market record

The year in observed pricing moves.

Dated vendor pricing moves from the market record SPP keeps live in the Pricing Observatory. A move is one vendor’s dated pricing change, verified against the vendor’s own statement before it reaches this page. The lines here are frame-grade; the full reads live on the Observatory.

Source: SPP Pricing Observatory · 222 tracked moves across 31 vendors · last verified Oct 19, 2026.
DateVendorWhat movedThe move
FigmaLicensing · Meter extended2nd in 6 monthsTwo features that were free during their beta join the meter at general availability and draw from the same credit pool as every other AI feature. Source 7 more Figma reads →
GoogleTerms change4th in 7 monthsGoogle retires its image model a year after release and points customers at the next one Source 27 more Google reads →
HubSpotLicensing + Packaging · Repackage3rd in 12 monthsThe unit moved from the stored contact to the sent email. Source 7 more HubSpot reads →
OpenAILicensing + Packaging · Unit swap2nd in 1 monthParticipating apps and sites can now run eligible AI requests against a subscriber's ChatGPT Plus or Pro plan. Source
OpenAILicensing · Terms change2ndOnce a subscriber exhausts the plan's included usage, apps connected through Sign in with ChatGPT can draw on that subscriber's available ChatGPT credits. Source 10 more OpenAI reads →

222 moves on the ledger; the 5 most recent shown.

Open the AI Pricing Observatory →

09 · The architecture read

Every finding above is one architecture, seen from three decisions.

The repricing record, the discount column, the free-goods economy, the renewal pipes: none of these are separate problems. They are the visible behavior of three decisions every software company makes, deliberately or by default.

Decision 01

Licensing

Who may use the software, on what grant, measured by what unit. The value metric lives here, and the renewal conversation inherits whatever the grant left unsaid.

Decision 02

Packaging

What ships together and what ships separately. The hidden free-goods economy is packaging decided informally, deal by deal, through the discount column.

Decision 03

Pricing

What the units cost, on what pricebook, maintained how often. The repricing record and the dispersion regimes are this decision’s fingerprint.

Phase 1Define

Make the three decisions deliberately, as one architecture, before the market makes them for you through the discount column.

Phase 2Deploy

Move the pricebook, the field, and the paper to the architecture. A raise holds or dies on what sits underneath it.

Phase 3Defend

Maintain the pricebook on a schedule. A static list runs roughly twice the net-price spread of a pricebook re-rated annually; that gap is the observed difference between defending the pricebook and abandoning it.

What any single company should do with the direction above depends on its own licensing, packaging, and pricing, which is where the work leaves this page.

10 · Provenance and method note

Where this comes from.

SPP’s pattern library records how pricing decisions behave once they reach a deal desk, drawn from more than $481 billion of B2B software business priced, negotiated, or repriced. It cannot be assembled after the fact: early observations cannot be back-dated, which is why no comparable library exists. Every finding here is published at the precision that library supports.

Every finding on this page is written and signed by a practitioner. Chris Mele, SPP’s CEO and #1 on OpenView’s list of B2B SaaS pricing experts, leads the Architecture Read the way SPP runs every pricing architecture engagement: licensing and packaging decided before pricing sets the number.

Start with your own numbers. Pricing Ground Truth reads your closed deals and your price list, same day from intake-complete: what you really charge, where realized price leaks, and the pricing architecture you run. A fixed fee of $15,000, credited in full to whatever comes next.

Start Pricing Ground Truth Or talk it through first

11 · Questions

Frequently asked questions

A survey reports what companies say: intentions, beliefs, self-descriptions. The Architecture Read reports what companies did, drawn from SPP’s pattern library of how pricing decisions behave once they reach a deal desk, and from the market record of dated, verified vendor pricing moves. There are no respondents anywhere in it.
One flagship edition per year draws deeper on the same decades-long record. Each edition draws out more patterns already held in the library; none is a fresh reading of current-quarter pricing. Between flagships, the market record of public vendor pricing moves updates on this page. Prior editions archive here, so the URL accumulates rather than resets.
Every figure traces to a finding from SPP’s pattern library, the record described in the provenance note, and is published at the precision that record supports. Ceiling findings say “up to” and mean it. Vendor moves in the market record are dated to the vendor’s own announcement and verified against primary or corroborated sourcing before they appear.
No, and that is deliberate. The Read describes how the market behaved and prescribes no number for any one company. The one self-service finding is the negotiation fingerprint: if your discounts bunch on round numbers, price realization is a negotiation ritual rather than an architecture output. What to do about it depends on your own licensing, packaging, and pricing.
Leadership teams of software companies: the CEO, CFO, and product and revenue leaders deciding how their own licensing, packaging, and pricing should respond to a moving market. It is not a buyer’s guide, and it is not written to help procurement teams negotiate against software vendors.

12 · What continues from here

The Read is the snapshot. The Observatory is the pulse.

The market record above is a glimpse of something larger: the AI Pricing Observatory, the living continuation of this page. Dated vendor moves, each passed through the citability gate, each with a full read on the mechanic underneath the vendor’s label, refreshed weekly.

And when the question stops being what the market did and becomes what your company should do, that is a working conversation.