Pricing principle
Price the governed boundary — the consequence controlled, evidence required, integration burden, and assurance level — not merely model usage or token volume.
Consumption pricing measures how much a model was used. It says nothing about what the model was allowed to do. A governance layer is worth what the consequence it holds back is worth, so that is what it is priced against.
A fixed-fee engagement that maps one workflow, authority model, policy/evidence requirements, threat boundary, and pilot recommendation.
Fixed scope and milestones for one controlled action, one policy domain, a named human owner, integration criteria, and an evidence-backed acceptance decision.
An annual platform license shaped by governed workflows and environments, deployment model, integration complexity, assurance obligations, service level, and support.
An evaluation license followed, where appropriate, by engineering and integration fees, field-of-use or volume economics, verification/support, and separately negotiated exclusivity or shared-roadmap terms.
Every figure above depends on which consequence is being held back and what evidence the buyer's regulator expects. That is established in the Boundary Assessment, which is why it comes first.
The assessment is the entry point for every other engagement model, and its output is yours whether or not a pilot follows.
Request enterprise access