// AI PRICING OBSERVATORY
Layer 03 of 3 · PricingThe pricing layer.
What the units cost, on what rate card, under what rules. The terminal decision of the architecture.
Pricing is the computational rulebook, not the metric. Usage-based, credit-based, and outcome-based name families of value metrics, and the metric lives in the licensing decision. The pricing model is the machinery that turns a chosen metric and a packaged bundle into a rational net price on every invoice. This page collects the moves where that machinery itself moved.
01 · The decision
The terminal decision, and the visible one.
The pricing model is the rulebook that computes a rational net price for every combination of what you sell, at every volume you sell it at, consistent across every deal: the price points, the approved adjustments, the limits that hold it all together. It is the last of the three decisions in pricing architecture — the three structural decisions (licensing model, packaging model, pricing model) that determine how a software company captures value.
Terminal, because pricing attaches to a bundle that has already been packaged from rights that have already been licensed. That is what the canonical order means in practice: by the time a number moves, two deeper decisions are either holding it up or quietly failing underneath it.
The test for any pricing announcement, a competitor’s or your own: did the rulebook change, or did the unit underneath it change? Much of what the market files as pricing news is the second thing wearing the first thing’s name, and the two age on entirely different clocks. The Pricing Architecture Assessment runs that question across your own three layers in a few minutes.
02 · “We’re changing our rate card”
How do software companies change their rate cards?
A rate card change is the narrowest move a vendor can make and the most legible: a published rate moved against its own prior value, with the metric and the editions holding still. Nothing was re-licensed and nothing was re-bundled; how revenue is captured is the only thing that moved. That is what earns it the pricing layer.
It is also the move most often confused with its neighbors. A launch rate with no prior value is a new offer, not a change. A rate that moves because the unit changed is a licensing story in pricing’s clothes. The ledger separates these deliberately, so the table below holds true changes: rates with a before and an after, each verified against the vendor’s own statement.
Take one question into the record: what does each vendor’s architecture let it change? A rate card that can move cleanly, without re-papering the grant or re-cutting the editions, is evidence of architecture underneath it. One that cannot is why so many of these announcements arrive tangled with the other two layers.
03 · The moves that only look like pricing
Two pricing announcements that live on the licensing page.
Two of the most common pricing announcements on the record are filed under licensing, and the filing is the teaching. A credit introduction is announced as a new way to pay; the decision underneath is a new unit of access. Cost-plus pass-through is announced as a formula; the core is the adoption of the supplier’s unit as your own value metric.
In both, the vendor announces the pricing surface while making a licensing decision, and the surface is the part that cannot hold on its own at renewal. If either of these is the move on your desk, read the licensing sections first, and if the rate on top is the part you are unsure of, talk to a pricing expert: the surface and the core price differently, and the difference is the work.
04 · The full record
The record is the market’s. The decision is yours.
Three layers, one architecture: the moves on these pages are what other software companies did, verified and dated, each read by a practitioner. What your company should do with the same situation depends on your own licensing, packaging, and pricing, which is where the work leaves the page. Start from the licensing layer, or go back to the full ledger.
