Four layers,
one accountable system
Most automation tools give you a canvas and wish you luck. AutoSolutions gives you the supervision layer that makes automation safe to leave running.
The stack, from
the wire up
Hover a layer. Each one is separately configurable and separately auditable, which is why a workflow can change model without changing its approval rules.
A hundred processes, one table
Workflows sorted by what is failing, not by what was created last. Run cost, failure rate and hours saved sit at the top of the screen because those are the three numbers anyone asks about.
- Average run cost and month-on-month delta
- Failure rate ranking, worst workflow first
- Automation coverage against eligible processes
Approvals that fit in a pocket
The approvals that hold up a run are the ones waiting on a person who is not at a desk. The mobile app carries the same queue, the same amounts and the same audit trail.
- Waiting-on-you queue with amounts in context
- Run alerts with the failing step attached
- Draft a workflow from a sentence
Six things that make
it safe to walk away
- Spend caps
- Per workflow, per run, per month. A run that would breach its cap stops and asks.
- Approval rules
- Route by amount, counterparty or confidence. Anything unmatched waits for a human.
- Full audit trail
- Every step, input, output, retry and cost, kept per run and exportable.
- Reversible actions
- Writes are staged and undoable. A bad batch is rolled back, not reconciled.
- Credentials in region
- Connector secrets stay in your region and are never placed in a prompt.
- Model routing
- Cheap models for classification, strong models for judgement. Set per step.
Wired into the systems
you already pay for
Credentials are held in your region and scoped per workflow. If a connector does not exist yet, the HTTP block and a schema will do.
Start with one
tedious process
Most teams have their first supervised workflow running before the end of the week.