methodik · discover → build → test → rollout → operate
How a process becomes a system.
Building AI-native while staying in control is not a contradiction but a matter of method. Five phases, a gate at every sensitive step, a complete audit log over every action. That's how manual work becomes a system you can trust — because you can watch it work.
how we work together
How we work together.
You hand over the complexity, not the control. We take on the manual work — and every step is documented in your client portal, in real time.
what happens in this phase
Work leaves your desk for a system that keeps it.
- Open on your side
- Open on your side
- Crossing over
- Crossing over
- Running with us
- Running with us
With every phase the system takes over one more item — and on the right you see what of it is documented in your portal.
Your process map takes shape — filed as the first deliverable in the portal.
phase 01
Discover
We understand the process as it really runs — not as it reads in the manual.
- scope
- 1 process, clearly scoped
- metric
- defined before build
- risk
- mapped & named
We observe the people who run the process every day, rather than interviewing them. Each step gets a quantified picture: how often, how long, how error-prone, who waits on whom. From this comes the honest figure — hours per year, converted into your internal cost.
In the end, we know not only what can be automated, but also what is better left to hand. We prefer a documented no over a solution nobody needed.
Benefit quantified, data accessible, first process clearly scoped. Without a solid business case, nothing gets built.
A process map, a cost calculation of the manual work and a prioritized ranking — written down, not on a slide.
phase 02
Build
Built AI-native — fast, but verifiable, versioned and maintainable.
- region
- europe-west6 · zurich
- auth
- keyless ci/cd · least-privilege
- gates
- human-in-the-loop, built in
We build with AI where it gives us pace, and with discipline where it counts. Every automation gets a clear input, a clear output and the metric that shows whether it works. No step runs without a log.
At every sensitive point — where an error costs money, time or trust — there is a Human-in-the-Loop gate from the start. Control is part of the architecture, not bolted on afterwards. Operated in Switzerland, europe-west6 (Zurich), revDSG-compliant.
Every sensitive step has an approval gate, every action writes to the audit log, access follows least-privilege. Only then do we test.
A working system with a defined metric, control gates and complete logging — not a prototype without a future.
phase 03
Test
Validated against real data and the uncomfortable edge cases, before anything goes live.
- validation
- against real history
- edge cases
- played through, not ignored
- example
- held-out periods
We don't test the ideal case but the exception: the document that doesn't fit the schema, the figure that stands out, the step where someone would normally pause. We hold results against the real history — for forecasts quantified with a clear accuracy metric.
Error paths aren't defined away but played through: what happens if a gate is not approved? If a source fails? The system may fail — but only loudly, traceably and without damage.
Results reproducible against real data, error paths cleanly caught, the metric holds. A red result stops the rollout.
A validated system with documented limits — you know what it can do and where it breaks.
phase 04
Rollout
Rolled out under control — a gate at every sensitive step, not a leap into the unknown at the press of a button.
- mode
- parallel → step by step
- approval
- stays with you
- handover
- audit log as truth
We go live step by step: first in parallel operation alongside the existing manual work, then with growing volume, while the approvals stay with you. That way you see the system work before you hand the process over entirely.
The people who accompany the process afterwards, we train in — with the audit log as shared truth. Handover here doesn't mean handing off a black box, but making control visible.
Parallel operation runs smoothly, approvals work, the people in the process are trained. Only then does the system take on the full volume.
A productive system in regular operation — with clear responsibilities and traceable approvals.
phase 05
Operate
Operated, monitored, retrained — the result stays measurable, even as your business changes.
- reference
- our own operation
- monitoring
- metric · uptime · drift
- retraining
- ongoing, data-driven
That a system ran once doesn't prove it still runs. We monitor the metric, keep the models current with new data and see in the audit log when something drifts — before it becomes a problem.
This phase is our own benchmark: we first automated our own operation and built the platform on which you see your systems ourselves. What we build for you, we operate by the same rules.
Metric, uptime and audit log are continuously observed; deviations trigger a response, not a report at year-end.
A system whose benefit stays visible over time — and grows with you instead of ageing.
control
The reason pace stays safe here.
AI-native pace is only an advantage if it doesn't come at the cost of control. Two mechanisms keep you in the picture at all times — built into every system, not bolted on.
Human-in-the-Loop gates
Where an error costs something, the system stops and asks for approval. The AI proposes and prepares — the human decides. Control isn't traded for pace, it's placed deliberately.
Complete audit log
Every action, every approval, every exception is logged — traceable down to the individual operation. Not a compliance formality, but the shared truth between you, the system and us.
Security as foundation
MFA/TOTP, App Check via reCAPTCHA Enterprise, keyless CI/CD authentication and least-privilege access. Swiss operation in europe-west6 (Zurich), revDSG-compliant. Protection is built in, not optional.
- Human sign-offat every sensitive step — Human-in-the-Loop
- Complete audit logevery action traceable and recorded
- Data in Switzerlandstored and operated in europe-west6 (Zurich)
- Secured accessMFA · App Check · least-privilege
intro call
Let's run a first process through these phases.
Non-binding and concrete: we take a real process, place it in Discover and say honestly whether and where the path through the remaining phases pays off.