How I work · Thun · throughout Switzerland
Process first.
Then digitise.
Digitising before simplifying is like laying a larger pipe — without checking whether the water is actually flowing.
Together, we’ll break the strategy down into sub-projects. You decide when to implement each one.
For each sub-project, you’ll know three things
What it depends on
What prerequisites are still missing, which systems are linked to it, and what decisions need to be made beforehand.
What it costs
Not just in terms of money. But also in terms of your staff’s time, risk and the effort required to run the system afterwards.
What it delivers
What pain points are resolved, how much work is eliminated, and what dependencies do you overcome as a result?
The approach is tailored to your business and your resources — not to my portfolio. I don’t have one. And in the end, your staff haven’t been overwhelmed. They’ve grown alongside the process.
Understand. Design. Implement.
In that order. Most projects fail because they start in the middle.
→ Guide: how to tell the process is missing — not the tool
Understand
What’s really happening, not what’s in the manual. Who does what, why, and since when has nobody known anymore?
Design
Cut out what nobody needs. Only then does the question arise as to which tool is actually suitable.
Implement
Roll it out, document it, hand it over. The knowledge stays with you, not with me.
From real-world experience
17 steps. Now just 4 to go.
steps
A Swiss SME with 20 sites wanted to digitise its accounts. It was already ‘digital’: PDFs were being sent back and forth. There were 17 manual steps between receiving an invoice and posting it to the accounts.
I didn’t digitise a single one. First, I understood the process. Then I simplified it. Then I automated it.
What remained were four steps. Nobody had ever needed the other thirteen. They had simply never caught anyone's eye.
My promise
I’ll pull the plug if it can’t work.
Once, I halted an ERP implementation. Not because the tool was bad — but because no tool can replace a process that doesn’t exist.
You’ll find that out early on, not later.
An honest ‘no’ costs me a contract but saves you many times that amount.
Three ways of working together
No set packages, no price list. We’ll discuss exactly what you need.
Strategic sparring
I sit at the table where decisions are made — and act as a bridge between IT and the business. Prioritisation, roadmap, governance.
More →Implementation & Empowerment
Introducing processes and tools — whilst leaving the know-how behind. Documentation, coaching and methodology for your team.
More →Interim IT Manager
Leadership, supplier management, transformation management — with one clear goal: to ensure your own structures are in place.
More →The first step
First, understand.
Then decide.
A conversation in which I listen and ask questions. If I see that you don’t need me, I’ll tell you so.
Frequently asked questions
How long does an assessment take?
That depends on how much is documented. In smaller businesses, there’s often nothing documented — so it takes longer to get to grips with things than in a large corporation with a process manual.
Do we have to change everything at once?
No. That’s precisely why we break the strategy down into sub-projects. You decide the order and pace — and can stop at any time.
Do you recommend any specific software?
If I recommend a product to you, it’s because it’s the right fit. No sales targets, no exclusive distribution, no in-house portfolio. If a referral is commissioned, you’ll know that in advance.
What if we’re already in the middle of a project?
Then we’ll first assess whether it’s viable. Sometimes all that’s missing is a decision. Sometimes the process is missing — in which case I’ll let you know as early as possible.