How AI vendors are
actually pricing.

The SPP read

The resolution is a split rather than a retreat, and the split is where the revenue sits. Premium seats keep the model included but capped at half their weekly limit, with everything above it metered at the flagship's own rate, while Pro and Team Standard move onto credits outright. Read as a sequence, a heavy premium user now faces roughly twice the workhorse rate, a ceiling at half a limit they could never forecast in the first place, and a meter above it. Half of an unforecastable number is still unforecastable. What the three extensions revealed is that inclusion was never the thing being retired: a vendor that wanted out of it had three clean exits and took none, because inclusion is what holds the seats that pay the most.

The SPP read

A five-day extension announced at the deadline says the migration was not ready, commercially or operationally. Each short reprieve protects goodwill that week and spends credibility the next, because buyers start pricing in the chance that the meter never arrives. A transition window works when it is set once, up front, with an end date the vendor treats as fixed.

The SPP read

The return converts a goodwill problem into a metering transition: the included window gave way to tiered terms, with credits for the lower plans priced near API rates. Credits are a surrogate unit, a vendor-controlled currency between the subscriber and the metered resource, and they let Anthropic reprice later without touching the visible list price. Under the relaunch label, this is the pricing model change of the arc.

The SPP read

The API rate is the meter the credits translate to: ten dollars in, fifty out, the top of Anthropic's list and roughly twice the workhorse model's rate. Pricing the same tokens two ways, bundled and metered, makes the gap between those two prices the real product decision of this arc.

The SPP read

Included access arrived with an expiry date attached: the new flagship shipped at no extra cost to paid subscribers for a fixed window, with usage credits taking over on a named date. Free-for-now with the meter's start date published up front is a different promise than free, and it sets the reference point buyers carry into the first metered month.

The SPP read

A price hold at a moment of capability compression is still a pricing decision even though no number on the list changes: Sonnet 4.6 arrives twelve days after the flagship at Sonnet's unchanged rate, closing on Opus 4.6's capability without closing on its price. Every time the mid-tier model catches the flagship this fast, the flagship's premium has to re-earn its place on the list, the same pressure Opus 5 later resolved by holding its own price against Fable 5.

The SPP read

The ladder-fill finished at the org level with two seat types rather than one: standard seats keep the existing plan, premium seats add usage headroom and Claude Code access for a single incremental price per user. Individual subscribers got the bundle outright across Max and Pro; teams get it as a paid upgrade path admins assign seat by seat. The premium seat becomes the anchor for every Team and Enterprise pricing conversation that follows, the point where more usage and agent access are sold as one line rather than two.

The SPP read

A weekly limit with paid overage at published API rates bounds the vendor's exposure. It does not bound the buyer's. Anthropic ran that shape a year before the sequence that made it famous, and the asymmetry runs one direction: the ceiling is denominated in tokens, a unit no buyer can forecast from the work they actually intend to do, so the limit lands at a moment they cannot anticipate and the spend above it accrues at a rate they cannot plan. Pricing the overage at list rather than a marked-up surrogate does treat the heavy user squarely. What it cannot fix is a meter counting something the buyer has no way to see coming, which is a metric problem rather than a budgeting one. The same mechanism returns in mid 2026 behind a model at roughly twice the workhorse rate, with inclusion capped at half the weekly limit and everything above it metered.

The SPP read

A metered research preview became a subscription line item: three weeks after Max launched, Claude Code moved off pay-per-token Console billing and into Max's shared rate limits at no separate charge. The chat app and the coding agent had priced access two different ways since Code's February preview; this collapsed them into one bill and one limit pool. It is the opening beat of a ladder-fill: Pro follows within five weeks, then a Team and Enterprise premium seat within four months.

The SPP read

The frontier tier cut its entry model by four fifths and left the flagship alone: Luna's input and output rates dropped roughly eighty percent while the top model moved far less. A cut that steep on the cheapest tier is not a discount, it is a floor being reset, and every downstream product priced off that floor inherits the new economics whether or not it repriced anything itself.

The SPP read

The same repricing pass trimmed the mid tier by a fifth, which is the part that shows what the move was for: an eighty percent cut at the entry and a twenty percent cut in the middle widens the distance between tiers rather than sliding the whole ladder down. The gap between tiers is doing the selling now.

The SPP read

The commercial echo of the consumer move eleven months earlier: capabilities in, price up. Read together with the meter that arrived the same month the increase took effect, the design uses both instruments at once: the per-seat price absorbs the AI everyone gets, and the meter prices the usage that varies.

The SPP read

The consumer surface ran the credits play the same week the commercial surface metered agents: a monthly allotment burned across apps. The credit is a surrogate unit: it lets the vendor tune the exchange rate between the subscription price and the underlying model cost without reprinting either.

The SPP read

The other half of the credits move: the first price increase in the product history, paired with AI now included. Bundling the model into the subscription converts an unpriceable cost into a priced one, and the increase funds the absorption.

The SPP read

Eighteen months before the seat-plus-meter earnings call, the pattern was already set: conversation free, agency metered. Microsoft drew the line not at access to the model but at work the model performs on its own. Every later meter in this arc lands on the same side of that line.

The SPP read

The free half of the same announcement: chat for every commercial customer at no charge. Free access is not generosity; it seeds the habit that the metered agents monetize. The giveaway and the meter are one design.

The SPP read

A seat became a meter: Bugbot moved from a flat per-seat subscription to usage-based billing for teams. The direction runs against the market's comfort story, since product lines inside one vendor can walk the arc both ways, and a bounded seat fee became an unbounded meter on exactly the workload that agents multiply, code review.

The SPP read

Three weeks after the unit changed, the vendor paid for the transition itself: a public apology naming the failure precisely, unlimited had quietly meant only one mode, and full refunds for every unexpected charge in the window. Reaction events are part of the arc, and this one prices the cost of moving a meter faster than customers can re-learn it: the refund is the vendor buying back the variance it had shifted onto buyers without telling them.

The SPP read

The unit dropped beneath the request: five hundred countable fast requests became a pool of included frontier usage metered on compute, and the plan price stayed put while the thing it bought changed shape. The same announcement grew the ladder a $200 rung, Ultra at twenty times the included usage, priced as much for not having to watch the meter as for the capacity. A request was a unit the buyer could count; included-usage dollars are a unit the buyer must trust the conversion on. The rollout drew a public apology and refunds within three weeks, the price of changing the unit faster than customers could re-learn the meter.

The SPP read

Salesforce is describing outcomes in the general sense, but bills for action related items that aren’t necessarily tied to client outcomes. Many vendors are jumping on the marketing bandwagon and charging for “outcomes.” But a resolved call and an updated customer record are two very different types of outcomes. One is a step in a workflow, the other is a business outcome.

The SPP read

Three purchase models for one product, available simultaneously with no forced migration: a consumption pool, per-profile SKUs, and the shared Flex Credit pool. Choice-of-meter is what ships when no single metric has won the argument internally.

The SPP read

The flat-fee unlimited agreement is the escape hatch from their own consumption model: when per-conversation and per-action pricing stalls enterprise commitment, a ceiling-priced multi-year restores it. The shared-risk framing concedes the metering objection rather than answering it.

The SPP read

For the installed base the renewal-transition date is the real effective date. AI moved from a paid add-on into the higher editions, the standalone add-on was retired from sale, and the edition price rose twenty percent: a feature-level meter absorbed back into the edition, and the edition repriced for it.

The SPP read

A list action carrying an AI story: six percent on the premium editions with AI named as the justification, plus an unmetered $125 per-user agent add-on landing alongside the consumption meter being sold elsewhere in the catalog. Unmetered per-user agents next to per-action credits is a pricing surface admitting the metric question is not settled.

The SPP read

Eight months after putting a price on the conversation, Salesforce put a price back on the seat. The Digital Labor add-ons and the Agentforce 1 edition introduce no new unit: they are per-user wrappers sold around the same meter, priced for buyers who could not underwrite a variable bill. The meter did not go away when the wrapper arrived. It moved behind a number the buyer could put in a budget.

The SPP read

Seven months after pricing the conversation, the meter moved down a level: actions at a dime, denominated in credits sold in hundred-thousand blocks, with licenses convertible into credits on demand. A finer unit gives the vendor pricing precision and gives the buyer a forecasting problem; the conversion bridge concedes that nobody yet knew which instrument would win.

The SPP read

The arc opens with a price on conversation itself: agentic AI at $2 per conversation at general availability, volume discounts standard. A conversation is a surrogate for work the buyer cannot forecast, and every later Salesforce move on this ledger renegotiates what the meter counts: a conversation, an action, a credit, a resolution. The unit kept changing; what a customer is paying for never settled.

The SPP read

Budgets and usage caps attach to the cost center giving more finely grained controls on variability. Rather than change the pricing architecture, GitHub is gearing more tools for customers to manage their own spend. Expect this trend to continue until a breakout vendor’s alternative model is to absorb the risk, ditch the tools (and the requirement for customers to have staff managing these tools) and make it easier for customers to handle variability.

The SPP read

BYOK routes inference through the customer's own provider account three weeks after credits went live, moving the token bill off GitHub's meter entirely. What stays billable is the harness: the agent loop, the client, the repository context, the governance. That splits what a Copilot subscription had been selling as one product, and it hands the largest buyers a lever they will eventually pull at renewal. A vendor that lets you bring your own tokens has told you which half of the product it believes is defensible.

The SPP read

The effective date is where the architecture sharpened: multipliers rose the same day billing went live, and code review began drawing on two meters at once, Actions minutes and AI Credits. Notice what is absent: a legacy conversion. The pattern that holds across our engagements runs new-logo pricing first, with the installed base following on a modeled schedule. GitHub instead repriced the installed base in place on a date, cushioned by promotional and flex credits that expire on a calendar. A flash-cut of the base is the most damaging path a repricing can take, and doubly so in a competitive market where the smallest customers carry the lowest switching costs. The cushions soften the first invoice, not the decision to leave.

The SPP read

The announcement did the heavy lifting a quarter early: plan prices held still while the unit underneath them changed from requests to AI Credits, and promotional credit cushions bought the installed base a quiet first quarter. Swapping the meter while the visible price stands still is the least-resistance path through a repricing, and the cushion is its anesthetic. The bill arrives when the promo expires, not when the announcement ships.

The SPP read

The annual cohort was not migrated. It was left on the old meter with its multipliers raised, then dropped to the free plan at expiry unless it re-bought. That turns a renewal into a fresh purchase decision at the moment the customer has the least leverage and the vendor has the most: mid-arc, on a repriced surface, with the prior contract already gone. A vendor that will not carry its legacy cohort across a repricing has decided the cohort is worth less than the reset.

The SPP read

GitHub stopped selling the individual plans, tightened their limits, and pulled the most expensive model out of Pro, then said why in pricing terms: a handful of requests could now cost more than the plan itself. Rationing access is what a vendor does when the licensing model cannot price the usage that has arrived, and it is the clearest admission available that a flat monthly fee had become an unhedged position against its own customers. The repricing followed one week later. When a vendor closes the front door, read it as a dated confession that the meter is wrong, not as a capacity notice.

The SPP read

The plan split the product surface in two: unlimited use of the base model, and a counted allowance of premium requests for everything else. That is a new metric introduced under cover of a new top tier, where a higher price presents the unit as generosity rather than a meter. Every later step in GitHub's arc runs through that unit. The first time a vendor counts something, the number is almost never the point; the habit of counting is.

The SPP read

Beside the token meter, a second meter appeared denominated in something new: successful tool invocations, billed per thousand calls that worked. Charging only on success moves a unit of risk from buyer to vendor, and it is the first step on this arc that prices what the model accomplished rather than what it consumed. Small in revenue terms, large in signal: a vendor experimenting with success-denominated metering has conceded that tokens measure effort, not value.

The SPP read

A budget lane opened an order of magnitude below the flagship, and the vendor's own framing priced intelligence rather than tokens: near-flagship benchmark performance at a small fraction of the rate. Two prices for the same tokens depending on context length made the meter itself tiered. And when the same benchmark performance sells at token rates an order of magnitude apart, the token has stopped being a consistent unit of the thing the buyer is buying. The vendor's framing prices intelligence while its meter still prices tokens, and the distance between those two is where this arc's later moves happen.

The SPP read

A late API entrant priced its flagship at the going flagship rate, three dollars in and fifteen out, matching the incumbent workhorse to the dollar. Entering at parity rather than under it says the vendor is selling capability membership, not a discount, and it marks the moment this arc joins the metered market it will spend the next year renegotiating.

The SPP read

Hours after the flagship model shipped, the subscription tier carrying it went from $22 to $40 a month. Pricing the carrier rather than the model kept the model's own price page clean while nearly doubling what access costs, and the same launch window brought a standalone Grok subscription, reported at the time rather than posted, which marks the start of Grok's commercial life outside the platform. When a model's access price lives in another product's tier, every model launch is a repricing option on that tier, and this vendor exercised it within hours.

The SPP read

The arc opens with a flip that looks like generosity and functions as instrumentation: a paid-only assistant went free for every user on the platform, with a bounded allowance metering how much free anyone gets and the paid tiers keeping the higher limits. A free tier with an explicit bound is pricing already at work. The bound converts free users into a measured population, and the allowance boundary becomes the upsell line that every later move on this arc renegotiates.

The SPP read

An 80% cut on the reasoning model, announced the same day a pro variant arrived at ten times the new rate, is one decision wearing two prices. The cut moves the base model toward commodity territory and the simultaneous premium launch preserves somewhere for the spend to go. Vendors under capability deflation keep doing this: the price of last year's frontier falls fast, and a new rung appears above it so the falling floor never takes the ceiling down with it. Watch the gap between rungs rather than either price alone; the gap is the actual product strategy.

The SPP read

Top-up credits complete the credit system: the allotment seeds the habit, the top-up monetizes its overflow. Once a subscription's ceiling can be bought through in small denominations, the plan price is a floor, and the meter above it is the growth instrument.

The SPP read

The ceiling experiment corrected: the top rung cut, a mid rung inserted underneath, and the same event rotated consumer limits from prompts toward compute. A price cut wrapped around a metering change is the ledger's most repeated pairing; the visible number falls while the unit underneath grows more precise.

The SPP read

More inclusion at a held price is a cut that never touches the price page, the same instrument the model layer runs with capability. Inclusion increases are how a vendor defends a rung without repricing the ladder around it.

The SPP read

The reversal beat: capability given away into every plan in 2025 came back as a paid access ladder in 2026, with a deadline on the promotional generosity. Bundling and re-monetization are one cycle, not two strategies; what the seat price absorbs can be re-fenced later at a price.

The SPP read

The down-market rung reached the home market with a credit allotment inside: the cheapest paid seat is also the most tightly metered one. At the bottom of the ladder the subscription is mostly a container for credits.

The SPP read

A new generation priced above its predecessor breaks the industry's own script that intelligence only falls in price. Each Gemini generation entered above the last at the API layer for a year, and the price of the frontier rose while the budget lanes advertised the fall.

The SPP read

The agent platform landed as a per-seat SKU, prices left off the vendor's own announcement. An agent platform priced by the seat is the transitional instrument this ledger keeps finding: the buyer understands seats, and the work is increasingly done by things that do not sit in them.

The SPP read

The ladder grew downward, and the vendor said so itself: a rung 'designed to help more people do more with Google AI for less,' priced country by country, introduced first where price sensitivity is highest. The rung is inclusion-dense for its price, storage and family sharing wrapped around the models, which puts the ladder's lowest effective price per unit of capability here. Down-market rungs are where consumption habits take root; the margin story comes later, or never.

The SPP read

Pricing images in output tokens pulls a new modality under the existing meter instead of minting a new unit for it. The token becomes the house currency: whatever the model produces, the bill speaks tokens. Extending one meter beats explaining two.

The SPP read

Doubling the monthly credit allotment without touching the price is a cut the price page never shows, and it is only possible because the credit is a surrogate unit the vendor controls. The exchange rate between the subscription and the underlying work moved; the number on the plan did not.

The SPP read

Every model family grows a budget lane, and the budget lane is doing pricing work: it catches the workloads the mid tier would lose to rivals on cost, and it anchors the family's floor while the flagship holds the ceiling. The ladder, not any one rung, is the pricing architecture.

The SPP read

Half price for workloads that can wait is a price on urgency: the vendor prices the buyer's flexibility instead of its own cost. Batch discounts sort traffic by latency tolerance, and the meter learns which work is time-critical, which is exactly the information outcome pricing will need.

The SPP read

The consumer ceiling rung arrived at work as a self-serve Workspace add-on, seat price unstated in the vendor's own post. When the top of the consumer ladder becomes a business SKU, the ladder itself has become the packaging architecture.

The SPP read

A $250 consumer rung is a statement about where the ceiling sits: Google priced its top plan an order above the default tier and fenced the agentic capability inside it, with concurrent agent tasks as the real gate. The premium rung is where agentic capacity gets rationed first; storage and models are the wrapping. The same post renamed the base plan from AI Premium to AI Pro, because Premium is a dead-end name once something must sit above it; the rename cleared the way for the ceiling tier it shipped with.

The SPP read

Collapsing the long-context price split is not a cut; it is a redistribution. The merged rate landed between the old pair: long-context work billed cheaper, while the short-context work that makes up most traffic paid more than its old floor. The simplification label carried a price increase for the majority of calls, and the same two-directional move returns later in this arc.

The SPP read

The arc opens with a familiar instrument: a flat consumer subscription, AI folded into a storage bundle at a seat-shaped price. Every later move on this ledger is Google discovering what that one number could not hold.

The SPP read

The charge moved onto the resolution: from this announcement Zendesk billed only where an AI agent closed a customer issue end to end, and not where a human had to finish it. Zendesk framed the move as displacing traditional pricing in a market it said should be measured by outcomes, and claimed the position first in its category. It is the opening beat of the arc, the moment a service vendor stopped selling the capacity to answer and started selling the answer.

The SPP read

A metric migration inside the same product. Resolution was legible to a buyer, outcome is broader and vaguer, so watch who holds the definition. The party that defines the outcome is the party that controls the invoice.

The SPP read

The first credible outcome meter in software: a price that fires only when the work succeeds, with a documented zero-charge path when it does not. The free-when-it-fails half is what made it defensible, and it is the half most imitators leave out.

The SPP read

For the first time the included-credit allotment itself became the packaging differentiator: same hub list price, double the included credits at the platform tier. When the meter is the product, allotments start doing the work editions used to do.

The SPP read

The counter-move in the same keynote: the assistant and enrichment moved into the seat while agent work moved onto the meter. The boundary being drawn, assistance included and agent work metered, is the architecture decision here; the rates are secondary.

The SPP read

Twenty-four days after pricing the effort, the vendor priced its own rollout: an acknowledgment that the transition 'did not meet our standards,' auto-refunds for a day of mis-computed checkpoint charges, and blanket credits for everyone on the new model. The remediation ran entirely through the price lever, credits and refunds, while the meter itself stood, so the allocation that caused the anger, customers carrying the cost of failed attempts, survived its own apology intact.

The SPP read

Replit priced the effort itself: a flat rate per checkpoint became a variable one that scales with how hard the agent worked, simple tasks below the old flat price and complex ones above it. Every other meter on this ledger counts inputs consumed or results delivered; this one prices the difficulty in between, the unit closest yet to the agent's own judgment of how much work the work required. Reception made the allocation visible: users found themselves billed for runs that failed or looped on the agent's own errors, and within a month the vendor conceded the transition fell short of its standards.

The SPP read

The meter dropped beneath the message: v0 stopped counting prompts and started metering the tokens inside them, converted to credits. Each plan fee became an included credit allowance, so the subscription now sets the floor and the meter charges past it. A message was a unit a buyer could count; a credit is a unit the vendor prices, and the conversion rate between them belongs to the vendor.