How you're charged
Token-based billing
Per token, per API call.
Duvo
Per agreed unit of completed work.
Pricing
Start with a process catalogue, improvement or transformation workstream, SAP migration fact base, training programme, or production automation. Each outcome has a commercial model that matches the work.
Three ways to engage
The first proposal reflects what Duvo is delivering: an evidence-backed process outcome, programme readiness, or completed units of automated work.
Automation economics
For automated work, Duvo uses the right model, tool, or rule for each step so the agreed unit price stays predictable.
Automation pricing
How you're charged
Token-based billing
Per token, per API call.
Duvo
Per agreed unit of completed work.
What drives the bill
Token-based billing
Model verbosity, context size, retries.
Duvo
The unit definition in the proposal.
One run, ten steps
Token-based billing
Costs more every step.
Duvo
Included when it is part of the agreed unit.
Seats and overages
Token-based billing
Often on top, and by surprise.
Duvo
Never. The proposal is the invoice.
Questions
Discovery is scoped around the workflow, team, or department being captured, the evidence sources involved, and the outputs required. It is priced as a defined engagement, not as agent usage.
SAP work is scoped around the chosen outcome: process mapping, a defined read-only gap scan, or wider migration-program support. The proposal separates those workstreams and their access requirements.
One completed unit of work defined in the proposal: for example, one invoice processed, one price change completed, or one case resolved. Volume and any price bands are agreed before production starts.
No, never. Token usage is our cost to manage, not your bill to forecast. It never appears on your invoice.
No. Unlimited people on your team can approve, monitor, and review, and you're not charged per head.
Expected volumes and any price bands are agreed up front. Your invoice follows the completed work and the commercial terms in the proposal, without a separate token-usage line.
Because we engineer the cost out. We use the right model for each task: small and local models do the routine work, plain code handles what doesn't need AI, and we only reach for a frontier model when it earns it.
Yes. A time-boxed, no-system-access discovery can start with interviews, walkthroughs, and documents before any production pilot. Scope, commercial treatment, and security review requirements are agreed for the specific engagement.
A short call scopes your processes and expected volume. The number you agree is the number you're billed. The proposal is the invoice.