The pricing decision in an AI product is more consequential than most product teams treat it. Pricing decides which customer behaviors get rewarded, which compounding curves the buyer experiences, and whether the renewal conversation feels like a celebration of growth or a tax on it. Most AI products in 2026 are still priced per seat, which we have argued elsewhere is structurally wrong for AI tooling. The follow-on question is what to price against instead. The most defensible answer, in the deployments where pricing is genuinely aligned with value, is to price against the corpus.
Pricing against the corpus aligns the buyer's growth curve with the vendor's revenue curve. As the buyer's institutional context deepens — more documents indexed, more workflows running against the corpus, more editorial signal accumulated — the pricing scales with the value the corpus is producing. The buyer pays for what they are actually building. The vendor is rewarded for the asset they are helping to compound. The renewal conversation is about how the corpus has grown, not about how many seats have been licensed.
What "corpus pricing" actually means.
Three concrete dimensions the pricing scales against.
Indexed corpus volume. The total volume of documents the corpus contains, measured in a stable unit (typically tokens or document count). The buyer pays for the size of the asset they have built. As the corpus grows, the pricing grows. The growth is monotonic and predictable.
Workflow depth. The number of distinct workflows running against the corpus, weighted by their depth (output volume, editorial complexity, integration count). A buyer with three deep workflows pays more than a buyer with one deep workflow at the same corpus size. The dimension captures the value the buyer is extracting from the corpus, not just the corpus size.
Editorial signal density. The volume of editor-in-the-loop corrections that have been folded into the model's fine-tunes. This is the dimension that most directly captures institutional memory. A buyer whose editor team has produced thousands of accept/reject/edit decisions pays more than a buyer whose editor team has produced hundreds, because the model's specific judgment is materially more developed.
The three dimensions roll up into a single contract dimension at procurement time, but each one is auditable. The buyer can verify the pricing against measurements they can perform themselves. The pricing model is transparent in a way per-seat pricing typically is not.
Why this aligns better than seat-based or usage-based pricing.
Per-seat taxes adoption breadth, which we covered separately.
Per-token rewards the vendor for verbose outputs and inefficient prompts, which is the opposite of what the buyer wants. A pricing model that gets cheaper when the engineering team optimizes prompts has the wrong incentive structure.
Per-output is closer to right but still misaligned, because the vendor is rewarded for output volume even when the outputs are not high-quality. A pricing model that scales with output count alone rewards generation, not value.
Per-corpus is aligned with the asset the buyer is building. The buyer pays in proportion to the institutional context they have accumulated, the depth of the workflows running on it, and the editorial judgment they have encoded. Each of these three dimensions correlates with value the buyer can defend at QBR. None of them rewards the vendor for behavior the buyer would prefer to avoid.
What the migration looks like.
Pricing migrations are operationally hard because existing customers signed contracts under the old model. The pattern that works, in the migrations we have advised, is to grandfather existing customers on their current pricing and apply the new pricing to renewals. The grandfathering window is typically twelve to eighteen months, which gives existing customers time to evaluate the new model against their actual usage and gives the vendor time to refine the new model based on real customer behavior.
The migration is also an opportunity to refine the corpus measurement. Most product teams discover, when they start measuring corpus volume rigorously, that their measurement infrastructure is incomplete. The migration forces the infrastructure to be built. The infrastructure pays back beyond pricing — corpus volume is also a key product-health metric and a leading indicator of expansion opportunity.
Where the pattern does not apply.
Genuinely shallow workflows — single-task tools, ad-hoc utilities, products without a meaningful corpus accumulation — do not have a corpus to price against. For these products, per-output or per-call pricing is fine; the value is in the operation, not in the asset.
But for any AI product whose pitch includes "the system gets better with use" — which is most enterprise AI tooling — the corpus is the asset that gets better. Pricing should reflect that. We wrote about the broader thesis here; this dispatch is the operational implementation.
If your AI product is priced per seat today and the value pitch is compounding, the pricing model is structurally fighting the value model. The migration is bounded, the alignment payoff is significant, and the renewal conversations get materially better. The teams that have made this switch are not selling differently. They are pricing in line with what they were already selling.
There is one consideration to be candid about: corpus-aligned pricing changes who inside the buyer's organization runs the procurement conversation. Per-seat pricing tends to be evaluated by HR, IT, or department heads who care about seat counts. Corpus-aligned pricing tends to be evaluated by the AI program lead, the CTO, or the architect who cares about the asset being built. The buying conversation is more substantive, slower, and more concentrated. For products selling into procurement teams that are not yet thinking about AI as architecture, the pricing migration may need to be paired with a buyer-education effort. For products already selling into AI-architecture-aware buyers, the migration is mostly a pricing change. Either way, the destination is the same.