Cost per run
A run is a complete ritual execution. Its cost depends on the engines involved, the volume processed and the controls applied. It is shown before launch and confirmed after execution.
Pricing
Every run shows its exact cost in the Cockpit, before and after execution. No dormant licence, no unused seat.
A run is a complete ritual execution. Its cost depends on the engines involved, the volume processed and the controls applied. It is shown before launch and confirmed after execution.
Evidence Panel · Expert validation · Audit dossier · Technical receipt · Capitalisation of validated patterns. Proof is not a paid add-on.
The format does not change the billing model, only the underlying infrastructure costs.
An industrialised first ritual typically sits between [RANGE — to be completed by the sales team] per year, including framing, deployment and the first year of execution.
Pick a value driver and adjust the assumptions. The result is indicative: it prepares a framing session, it is not a commercial offer.
Annual gross value
€30,720
Annual investment
€80,000
Annual net benefit
-€49,280
ROI
-62%
Payback
31 months
Indicative estimate based on your assumptions. This is not a commercial promise. A framing session maps the scenario onto your real volumes.
Refine with an expert →| Criterion | Seat licence | Per-request billing | NEXA — cost per run |
|---|---|---|---|
| Cost predictability | High, but paid even with no usage | Low, frequent drift | High, indexed on real usage |
| Visibility before execution | None | None | Cost shown before launch |
| Cost of idle seats | Paid in full | Not applicable | Not applicable |
| Proof included | Usually an add-on | Rarely available | Included in every contract |
| Cost / quality trade-off | Not steerable | Not steerable | Steerable per run |
Cost predictability
Visibility before execution
Cost of idle seats
Proof included
Cost / quality trade-off
A failed run is not billed.
Yes, and you can trade off. The Cockpit shows cost before launch: changing engine changes the line.
The marginal cost decreases: governance components are shared. The second ritual reuses the foundation already deployed.
A framing session maps the first ritual onto your volumes, engines and expected level of proof.