Flux Flow routes the approvals a finance team already runs, keeps the trail, and tells you where a request is sitting.
A shared sheet, a mailbox rule, and a person who chases. It works at low volume, and keeps working right up until month-end close, an auditor's question, or a holiday.
Requests go to the right approver, in the right order, with a named backup when someone is out.
Every decision keeps its date, its approver, and the evidence attached to it.
Cycle time per step, and where requests are sitting right now.
Approvers keep their authority. Flux changes where the request waits, not who decides.
The existing process keeps running for the whole pilot. This is a parallel test, not a migration.
| Criterion | How it is measured | Bar |
|---|---|---|
| Cycle time | Request to decision, in Flux, across the pilot window | Half the baseline |
| Coverage | Share of in-scope requests routed through Flux | 90% |
| Trail | A completed request reconstructed without asking a person | Every request |
| Handover | Your team runs the workflow live, without us | Demonstrated |
If a criterion is not met, it is not met. The pilot ends with the numbers, whatever they say.