Skip to content

Pricing

Price the outcome you need now.

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

Different outcomes need different commercial models.

The first proposal reflects what Duvo is delivering: an evidence-backed process outcome, programme readiness, or completed units of automated work.

Process outcomes

A fixed-scope engagement for one workflow, team, or department. Duvo captures and diagnoses the process, then delivers the catalogue, training, or improvement outcome you need.

Transformation and SAP

Programme pricing based on process scope, markets, evidence volume, and the required handoff into Signavio, an SI, or an internal transformation team.

Production automation

A predictable price for each agreed unit of completed work, such as an invoice processed or a case resolved. No token line item and no per-seat fee.

Automation economics

When Duvo runs the work, cost is engineered into the unit.

For automated work, Duvo uses the right model, tool, or rule for each step so the agreed unit price stays predictable.

Right model for the task

Small and local models handle the routine work; the frontier model is saved for the moments that actually need it. A Ferrari shouldn't idle at a toll plaza.

Sometimes the smartest AI is no AI

Where a rule, a lookup, or a line of plain code does the job, we use the line of code. Faster, exact, and never billed per token.

Cost is engineered, not passed on

Because we don't pay frontier prices for simple work, you don't either. That discipline is why a single process run costs cents.

Automation pricing

Pay for the agreed work unit, not the model conversation.

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

Pricing, answered.

How is process discovery priced?

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.

How is SAP migration support priced?

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.

What counts as one process run?

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.

Do you charge per token?

No, never. Token usage is our cost to manage, not your bill to forecast. It never appears on your invoice.

Is there a per-seat fee?

No. Unlimited people on your team can approve, monitor, and review, and you're not charged per head.

What happens at high volume?

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.

Why is the price this low?

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.

Can we try it before we commit?

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.

How do I get an actual number?

A short call scopes your processes and expected volume. The number you agree is the number you're billed. The proposal is the invoice.