The deployment once, the platform on an annual subscription, then the executed act beyond the included volume. The amount depends on your volume and the systems to connect. The structure never does.
The agent built for your process, the connections to your systems, the observation, writing the rules with you, the go-live. Fixed scope, fixed amount, fixed date.
Scoping is invoiced, then deducted from this line if the project goes ahead. The second process costs less: the platform and part of the plumbing are already there.
Identities, rights, caps, trail, revocation. It is what you keep, and what makes the agent steerable without us.
Includes a volume of acts, sized on the volume measured at scoping.
A fraction of what that act costs you today. An invoice taking eleven minutes costs about seven euros in labour: line 3 takes a small share, you keep the rest.
Capped for the year and stated before signature, so your budget stays a budget.
Billing per act creates an obvious temptation: push the agent to act more. Here is how it is removed.
The meter is the receipt chain. You check your invoice with the same trail that passes your audit, and without us.
Your invoice follows your volume, at a small fraction of today's slope. Doubling your files doubles neither your team nor your bill.
A services firm bills time, so its cost follows your volume at the price of your hours. Ours follows it at a fraction of that price. That is the difference when your activity doubles.
That reasoning justifies the amount. It does not say what we bill on: billing stays the project, the subscription, and where it applies the action.
Describe your process in three minutes. We come back with an order of magnitude and what makes it move.
SauronID