What must be noticed
A deadline that is approaching. A meter that has gone quiet. An invoice that arrived twice. Noticing is half the work — and the part that is most often neglected.
Product
What runs the same every week does not have to be done by hand every week.
Deadlines, documents, maintenance, official correspondence: processes that recur and still demand attention every time. In future they run by themselves — up to the point where a person has to decide.
Approval stays with a person
Runs in-house
One process first
What it is about
Three kinds of work that can run by themselves.
What can be prepared
Matching documents, sorting incoming post, drafting recurring letters. The result is a draft, not a completed action.
What has to be documented
Who approved what, and when. ⭐ Produced along the way instead of reconstructed afterwards — and in a dispute that is exactly the difference.
How it works
One process, one week, then the next.
01
Naming the most annoying process
Not the biggest — the one that annoys most often. It shows fastest whether it works.
02
Rebuilding how it works today
First the as-is route, with all exceptions. Anyone who forgets the special case automates past everyday reality.
03
Building in approval
At what point does a person look at it? That point is defined before anything runs — not afterwards.
04
Letting it run alongside
A week in parallel with the old route. Only when both give the same result is the switch made.
What is there afterwards
What happens by itself afterwards.
- Deadlines report themselves before they become tight — not the day after.
- Documents are matched when they arrive, not at month end.
- Recurring letters are ready as drafts, ready for review.
- Every approval is logged: who, when, on what basis.
- And the most important point: nothing goes out without approval.
And what it does not
This is here because everything else would be worthless without it.
Anyone who promises everything is switched off at the first objection. That is why we say beforehand where the limit lies.
It decides nothing
Every process ends with a person who approves. A system that runs straight through does not relieve you of work but of control.
It sends nothing by itself
No email, no letter, no report goes out on its own. What a system has sent, nobody can bring back.
It is no substitute for good order
Automation does not make an unclear process clearer, only wrong faster. That is why rebuilding the as-is route comes first.
Frequently asked questions
The questions that come first.
What if a special case occurs?
Then the case stops and reports itself. ⭐ This is intentional: a system that solves special cases by itself will eventually solve them wrongly, without anyone noticing.
Do we have to change our programmes?
No. The automations sit alongside what you have. Where an interface is missing, we say so instead of promising one.
How long does the first process take?
That depends on how clear the process is today. ⛔ The effort is almost always in describing it, not in building it — and that is work you have to do anyway.
What happens in a power cut?
Nothing is lost. Processes that were started are there afterwards where they were interrupted — with a note that they were interrupted.
Can we switch an automation off again?
At any time, individually. The old route stays in place in parallel for the first weeks anyway.
Bring us your biggest annoyance.
One conversation, one real task from your daily work. We use it to show what AI and automation can do for you.