The hardest part of automating a business process isn't the AI. It's the moment you let it act on its own. Most tools treat that as a switch: off, then on. We think it should be a dial.
Three levels, then a dial
Every process in NeodyAI starts in shadow mode: it runs every step and shows what it would do, but changes nothing. Next comes assisted: it does the work, and a person approves every action. Then supervised: it may act on its own — but only for the share of events you choose.
That share is the dial. It moves in stages: 0 → 10 → 25 → 50 → 75 → 100%. A new supervised process starts at 10%.
Who handles each event
An event is one action a process wants to take: create a payment task, send an invoice, chase a supplier.
- If it isn't safe to automate, a person handles it. High-risk actions, amounts over a cap, failed checks — always a person, whatever the dial says.
- If it is, the dial decides. Each run lands in a stable slot, so a run is either wholly automated or wholly manual, and turning the dial up only adds runs.
- A sample is always checked. Even at 100%, a share of automated events still goes to a person, so you never stop measuring.
When a person handles an event the AI would have done, their decision is a vote: approving means they agree with the AI, rejecting means they don't.
Let the evidence move the dial
Those votes are what move the dial — in both directions.
- Auto-ramp raises the share one stage once enough events at this stage were checked and people agreed often enough (by default, 20 checked events at 95% or better). It never goes above the ceiling you approved.
- Rollback is always on. If agreement drops below the floor (85% by default), the share drops a stage at once. You see why in the process history.
- A daily limit caps how many actions can run on their own in a day.
- A kill switch stops all automation instantly. Anyone who can approve the process's actions can pull it — not just admins.
Limits that follow the risk
The dial can't go anywhere. Each process takes the risk tier of its use case, and each tier has a limit: by default, low-risk work can go to 100%, medium-risk to 75% with a 5% sample, and high-risk to 50% with a 10% sample. Lowering a limit takes effect at once.
Going above a limit takes a risk officer, a written reason, and an expiry date — at most 90 days. Raising automation is always a change a second person can be required to approve.
What you can see
Each process shows the share of events automated over the last 30 days, the share the AI could have handled, how often people agree with it, and who handled every event and why. It's the evidence for every change you make — and for every question an auditor asks.