How I work
1 understand.
2 design.
3 automate.
Most consultants show up with a tool already chosen or a solution already defined. My approach is to ask the right questions before making a choice.
The starting point
The starting point is always the same
The question everyone asks
"Which process do you want to automate?"
The question I ask
"How does this process really work? Who does it, when, with what exceptions, and what happens when it goes wrong?"
The difference seems subtle. It isn't.
In the answer to that second question hide 90% of the waste and 90% of the real opportunities.
I spent 10 years designing services for private companies, consulting firms and financial institutions. In those settings mistakes are expensive and processes involve thousands of people. I learned that technology doesn't solve problems — it amplifies them, for better and for worse.
If the process is broken, automating it means making mistakes faster and with greater damage.
The method
The work path
Listening and discovery
1–2 weeksWe talk. With you, with the people who do the work every day, with those who deal with the results of the processes — not just with management.
I ask uncomfortable questions: "Why is it done this way? For how long? What happens when it goes wrong? What doesn't work that nobody says out loud?"
A real picture of how your company works — not the one on the presentation deck.
Analysis and diagnosis
1–2 weeksI map the flows, identify the bottlenecks, calculate the real cost of waste: time lost, recurring errors, dependency on key people.
I separate the urgent problems from the important ones. Not everything needs to be solved immediately, and not everything needs to be automated.
A clear diagnosis: where you are losing time and money, why it happens, and what is worth tackling first.
Process redesign
2–4 weeksBefore touching any tool, I redesign the process on paper. I simplify, remove the superfluous, define responsibilities, sequences, exceptions.
Where needed I facilitate workshops with your team, because a process people don't understand is a process people don't use.
A clear, documented process that anyone can understand. Ready to be automated — or already improved, even without automating anything.
Automation
2–6 weeksOnly at this point do I choose the tools. The choice depends on your context: what you already use, what skills your team has, how much you want to depend on external platforms.
I implement, test, fix. I don't deliver something that works in theory — I want to see it work in your real environment.
Automated flows that actually run. With documentation for your team — not a black box that breaks the moment something changes.
Measurement and follow-up
2–4 weeks post-launchTogether we define the metrics that matter: time saved, errors reduced, volume handled without adding headcount.
I stay available for adjustments in the first weeks. New systems always have a settling-in period — it's normal, and it's part of the work.
Concrete data on what changed. And the certainty that the system holds even when I'm not there.
The approach
Why this approach is different
It's not a criticism of anyone. It's a description of how I work.
This way of working is for you if…
You have processes that work "more or less" but you feel they could run much better
You've already tried tools or solutions that didn't hold over time
You're growing and the operating model is starting to creak
You want to introduce automation without becoming dependent on the one technician who understands it
You need someone who talks to you and to your team — not just one of the two
It's not for you if…
You want someone who implements fast without asking too many questions
You already have everything clear and just need technical execution
You want a specific tool and the context is of no interest to you
In these cases I can still point you to the right person.
Want to find out if this approach makes sense for your situation?
Tell me in a few lines where you are now and what isn't working the way you'd like. I reply within 48 hours.
Write to me →Or, if you prefer to start on your own: download the free guide