The system does the work, you approve
A system can prepare the next step on its own and only call someone when there's a decision to make. How that works, who decides what runs without a click, and what it looks like in our own Console.
Systems. October 31, 2026. 6 min read.
Most systems sit still, waiting for someone. An order comes in, and someone has to remember to enter it. An invoice comes due, and someone has to remember to chase it. A quote is accepted, and someone has to open the project, send the contract and create the charge. When that person is on vacation, busy or simply forgets, the process stops.
Our vision is software that works for you. In practice, it fits in one sentence: the system does the work, you approve. And it rests on four points.
Each step triggers the next
An order comes in, an invoice comes due, a quote is accepted: the system already prepares what comes next, without anyone having to remember.
Picture a repair shop. The customer approves the repair quote on their phone. At that moment, the system already has the work order, the parts order for the supplier and the car's slot in the bay ready. Nobody had to open three screens. Someone on the team just checks and confirms.
It works in the background
Agents read, prepare, follow up on payments and organize while your team does something else. They only call you when there's a decision to make.
An AI agent is the part of the system that handles whatever arrives in a mess: it reads the supplier's email, understands the customer's message, writes a draft reply. It works without anyone watching the screen, and the result shows up ready where the team already works.
You decide what runs on its own
This is the most important part. Each action has a level:
- Only suggests. The system points out what could be done, and a person does it.
- Prepares and asks for approval. The system gets everything ready, and a person checks it and approves with a click.
- Does it and tells you. The system does it and tells you what it did.
- Does it and just logs it. The system does it and keeps the record, for anyone who wants to check later.
Money, contracts and anything that reaches your customers always start at "prepares and asks for approval". A wrong charge, a contract with the wrong amount or a message in the wrong tone cost too much to go out without someone looking.
The rest is your call, one action at a time. Picture a clinic: tomorrow's appointment reminder reaches the patient, so it starts out asking for approval. After a few weeks without mistakes, the clinic can move that reminder to "does it and tells you". Rescheduling an appointment, which changes the doctor's calendar, might keep asking for approval for quite a while.
You can measure it
The system shows how much went through without anyone touching it and how much still needs a click. We call this the touch rate: the share of the work that still needs a click.
The goal is for that number to improve month after month. At the start, almost everything asks for approval, and that's how it should be. As the team sees the system get things right, more things run on their own. Without the measurement, that conversation comes down to each person's impression. With it, you can decide by looking at the record.
How it works in our own system
This is how our own system works: the Anuntech Console, since October 2026.
- Quote accepted: the project, the contract and the down-payment charge show up ready in a queue for the team to approve.
- Contract signed: the down-payment charge is prepared.
- Invoice 3 days overdue: the payment reminder comes written by AI for the team to review and send.
- Payment: it's recognized within seconds through the bank's notice.
And nothing involving money goes out without a click.
Today it's these cases and no others. Starting with a few cases and watching them work before letting more run is the same advice we give anyone building their own system.
What we can promise
What can run on its own does. What needs a decision waits for you. And you can see the split.
There will always be decisions that are yours: giving a discount, taking on a new customer, answering a delicate complaint. A good system takes the remembering, copying and preparing off your plate, and leaves the decision with whoever answers for it.
Where to start
- Pick a process that today depends on someone remembering. Collections are usually a good candidate.
- List the events that trigger each step: "order came in", "invoice came due", "customer approved".
- Start everything at "prepares and asks for approval". Moving up a level later is easy. Undoing a mistake that already reached a customer is usually much harder.
- Agree from the start on how the touch rate will be measured, so the decision to let more things run has numbers behind it.
