What I do
Processes that survive people leaving
In many companies people come and go, while the process lives in someone's head or in a file only one person understands. When they leave, the process leaves too. I build systems that stay.
What I build
Apps around your process
From idea to product. Not a template, but the flow you actually run.
Dashboards and reports
Real-time metrics, so decisions stop waiting for Monday's report.
Workflow automation
Integrations, syncing, notifications. Repetitive work leaves the job description.
Role-based systems
Each role sees what it needs. A new hire gets access, not a training course.
How I work
Map
I document the real flow, not the documented one, hidden spreadsheets included.
Design
The right tool for each step. Not everything that can be automated should be.
Build
Delivered in pieces that reach production, not one big bang at the end.
Hand over
Documentation, training, and the handover test: a new person runs the flow alone.
The handover test
It is the only criterion I care about at the end. I take someone who has never seen the system, give them a real task, and watch whether they get through it without asking anyone. If they get stuck, it is not finished. That is the difference between an automated process and an automated process someone other than its author can keep alive.
From practice
Delivered projects, described without client names. The outcomes below are the operational ones I observed directly, not marketing estimates.
Why me
I have been on the other side
Seven years in sales before IT. I know how a process sounds when the person running it explains it, not the person who drew it.
I write requirements, not just code
Product owner and business analyst, BPMN 2.0, SAFe. The problem is almost never the technology.
I deliver in pieces
The first useful part reaches production in weeks, not at the end of the project.
I stay after launch
Support and adjustments. A system handed over and abandoned becomes a spreadsheet again within six months.
Questions that come up every time
Does automation mean laying people off?
No. Usually the problem is the opposite: you cannot find or keep people, and the ones who stay do repetitive work instead of thinking work. Automation takes the repetitive part, so someone leaving stops being a crisis.
How long does it take?
A bounded flow reaches production in two or three weeks. A system with several roles and integrations takes months, but with useful pieces along the way.
What if it breaks?
Monitoring, and a fallback path for the critical steps. Nothing ships as set-and-forget.
We already have an ERP. What is left for you?
I usually do not replace the ERP. I fix the part between the ERP and reality, which is exactly where the parallel spreadsheets appear.
Got a process that breaks when someone leaves?
Tell me what hurts. If I can help, I will tell you how. If I cannot, I will tell you who can.