Skip to content

From process evidence to live operation.

Duvo runs the process inside your existing systems. Your team keeps approval and exception authority through every cycle.

The Duvo loop

Capture

See how the process actually runs, including the decisions and steps that never reach a system of record.

Process Intelligence
How the cycle matures

Initial cycle

Broad human review

Assisted operation

Repeatable cases handled consistently

Exception-led operation

Human judgment focused on genuine exceptions

Verified outcomes can reduce unnecessary review and improve the next cycle.

The complete loop runs on the Execution OS. Each capability emphasizes a different part of it, and none of them owns the loop alone.

Each step names who does it and the evidence behind it.

In this invoice-reconciliation example, Process Intelligence records how a potential overpayment is identified, with both routes and their sources attached.

Explore Process Intelligence

Current process

27 steps

How was the potential overpayment identified?

Monthly sweepMarta reviews the full population on the first Tuesday of each month.

Inbound query routed to DanSupplier statement or email, ERP duplicate warning, buyer escalation, or ad hoc manager request.

Input
Trigger source for the overpayment investigation.
Condition
How was the potential overpayment identified and routed for investigation?

2 sources attached

View source step

A flagged charge reaches its owner with the evidence attached.

This freight-audit example shows a charge awaiting review. The owner can accept it or dispute it; Automation carries out the approved action.

Explore Automation

Freight Audit

Pending decision

XPO Logistics · XPO-441274-26

Potential recovery
$2,284.98
Billed
$3,550.00
Expected
$1,265.02

Uncertified reweigh and an unapplied discount.

Next action

Approve: $3,550.00 posts to SAP AP; no claim is filed.

Dispute: challenge the $2,284.98 overcharge; nothing posts to SAP until the carrier responds.

Approval thresholds

Material overcharges and policy exceptions pause for finance, logistics, or transportation owners.

Agree the controls before the process goes live.

01

Define the operating scope and measurable outcome

Your process owner and Duvo baseline the cost, cash, service, speed, or control outcome.

02

Capture how the process actually runs

Run by Duvo through walkthroughs, interviews, and documents. Your experts give hours, not weeks.

03

Agree the process, exceptions, controls, and baseline

Confirm Duvo’s scope, human judgment, controls, and the value measure: what counts, the period, and who signs off.

04

Test the agreed process before it goes live

Duvo configures the process; your approvers test it end to end with real inputs before production.

05

Go live, measure value, and expand

Track the result against the baseline, improve, then add the next valuable scope.

Freight audit example: SAP, TMS, Carrier portals, Email and shared inboxes.

Outcome

The first scope runs live in weeks, with your existing systems still in place.

Value is measured against the agreed baseline before the scope expands. After go-live, Duvo runs and tunes the agents: any change to a rule or boundary goes through your named process owner, with the reason recorded, and your team keeps every approval.