Automation that knowswhen to ask for help.
A working run console for an invoice-intake workflow. Most runs post straight through; the interesting ones don’t — a missing PO goes to a reviewer, a shaky scan is retried, a duplicate is rejected. Handled states, shown live.
posted, no human touch
in this batch
8 routed for review
transient faults, self-healed
duplicates, cleanly
per auto-posted run
Volume through each step, and where runs branch off to a human or exit.
Select a run to inspect its steps.
Pine & Co Accounting · $1,820 · handled in 4.5s
- receive0.3s
- extract3.3s
- validate0.4s
- match po0.5sTo human
No PO within 2% tolerance — routed to the AP reviewer
01 — The happy path is easy
Exceptions are the product
Anyone can automate the invoice that’s perfect. The value is in the 20% that aren’t: no PO, over the approval limit, a bad scan. Each has a defined, visible path — retry, route, or reject.
02 — Humans where they matter
Escalation is a feature
A run sent to a reviewer isn’t a failure — it’s the system knowing its limits. Straight-through rate and manual-touch rate are tracked side by side, so you can see exactly what it costs.
03 — Sample, and it says so
Derived, not drawn
The run log is a labelled sample, generated against a fixed workflow — but every figure, funnel, and trace is computed from those runs. Point it at your inbox and it reports your real flow.