Pilot review · week three of four

Flux × Acme

Capex approvals, running on Acme's own process and Acme's own NetLedger, alongside the sheet.

Updated 2026-08-19

Fictional company. Demo material.

What the pilot proves

Capex approvals over $5,000, end to end, on your ERP.

Capex approval workflow

Requests over $5,000 are submitted, routed and decided in Flux Flow, with the full trail retained.

Done when: median approval time is under 48 hours and at least 90% of Q3 capex runs through Flux.

ERP integration

Approved requests write back to your own NetLedger instance. Your production system, not a sandbox.

Done when: Tomas confirms a decided request lands correctly in NetLedger with no manual re-entry.

Handover

Acme can run and explain the workflow without Flux in the room.

Done when: Priya demonstrates it live, end to end, to an internal audience.

Out of scope, agreed 3 August: vendor onboarding, expense approvals, purchase orders, migrating the sheet's history, anything touching payroll. The sheet keeps running for the whole pilot.

Where we are

Agreed in writing on 3 August. Measured on your requests.

Criterion	Target	Where it stands	State
Approval latency	Median under 48 hours	31-hour median in the week to 14 August, against the four-day baseline	Met
Coverage	90% of Q3 capex through Flux	54 requests routed in the week to 14 August, 49 closed in Flux	In progress
ERP write-back	Verified on production NetLedger	Sandbox only so far. Waiting on the production release version to confirm the field mapping	Waiting on us both
Handover	Priya runs it live, unaided	Booked for week four. Tomas, AP, and James attending	Scheduled

A criterion that is not met is not met. The pilot ends with the numbers, whatever they say.

The plan

Four weeks, one workflow, nothing switched off.

Week 1 · Aug 3 to 7

Connector built, workflow configured to your routing rules, Priya trained

Week 2 · Aug 10 to 14

Live capex requests routed through Flux. Midpoint review on the 14th

Week 3 · Aug 17 to 21

Production write-back verified. Backup approver configured and exercisedWe are here

Week 4 · Aug 24 to 28

Handover. Priya demonstrates the workflow to an internal audience

If the production check slips, the handover holds and we demonstrate on the pilot's own results rather than on sandbox ones.

Who is involved

Five named people, one unfilled seat.

Name	Side	Role in the pilot
Priya Raman	Acme	Finance ops lead. Runs the pilot day to day and presents the handover
Tomas Eriksen	Acme	Controller. Primary approver, and verifies the NetLedger write-back
James Whitfield	Acme	CFO. Attending the handover session
Head of IT	Acme	Owns the security review. To be named
Dana Olabode	Flux	Pilot owner. Weekly checkpoint
Sam Oduya	Flux	Solutions engineer. Built the connector, ships the config changes

Before the handover

What is left, and who holds each piece.

With Acme

Production NetLedger release version (Tomas). The connector was built against 8.4; the mapping differs on 8.1.
An introduction to the head of IT (Tomas). The security packet went over on 15 August; Flux drives the review from there.
A 20-minute slot with James (Priya) ahead of the handover rather than in it.

With Flux

Field mapping confirmed (Sam), within a day of the version landing.
Delegation rule shipped (Sam) so a backup approver can be exercised before the handover.
Connector architecture note (Sam) for the security review, ahead of being asked.

Next session: handover, week four

Flux · Fictional company. Demo material.