Fix the process first.
Then automate it.
Most automation projects don't fail on the technology — they fail because a broken process just runs broken faster. So we rebuild the workflow first. Then we automate what's left.
Three steps go before any tool enters the picture. Only the leaner workflow gets automated — not the old detour.
We fix workflows. We don't reinvent them.
Cut steps, rebuild logic, close media breaks, connect tools — on the existing process.
What we don't do: rethink your business model on a greenfield. We start from what already runs.
Three kinds of processes — three priorities
Not every workflow deserves attention first. This split shows where automation pays off most.
Core processes
Directly value-creating — this is where the company makes its money.
Typical examples
- Sales & distribution
- Production & service delivery
- Customer service & support
- Product development
Top priority: biggest lever, highest visibility
Supporting processes
Keep the place running without generating revenue themselves.
Typical examples
- HR & recruiting
- Accounting & finance
- IT support
- Facility management
High, quickly visible efficiency gains
Steering processes
Strategically and legally important — but rarely pure routine.
Typical examples
- Strategy & planning
- Quality management
- Compliance & governance
- Change management
Automate selectively, with judgment
Six criteria that decide on automation
Is a process even suitable? These six factors give the answer — before you invest in tools.
Frequency
How often does the process run?
Daily beats monthly
Volume
How many cases per run?
More cases, more leverage
Time effort
How long does one run take by hand?
Minutes and hours add up
Error-proneness
Where do errors creep in?
Manual entries and transfers
ROI potential
Does the saving justify the effort?
Not everything possible is worth it
Standardization
Does the workflow follow clear rules?
No rules, no clean automation
Five steps to automation that lasts
The order is no accident. Step 3 is the one most people skip — and exactly why their projects fail.
Current-state analysis
Make the workflow fully visible — as it really runs today, not as the manual describes it.
- Process mapping
- Name the people and handovers
- Measure times honestly
Find the bottlenecks
Look where it jams, waits and stalls — those are the spots that actually cost money.
- Where does work pile up?
- Waiting times and loops
- Recurring sources of error
Rebuild
Improve the process BEFORE a single line is automated. This is the core of our work — and the step most often skipped.
- Cut unnecessary steps
- Parallel instead of sequential
- Unify rules and formats
Automation potential
Only now the question: what can the machine reliably take over — and what deliberately stays with people?
- Rule-based tasks
- Data transfers without judgment
- Calculations and checks
Prioritize
Start with what works fast — the rest follows with a plan, instead of wanting everything at once.
- Impact vs. effort
- Estimate ROI roughly
- Draw up a roadmap
What first? The prioritization matrix
Impact vs. effort — that's how it's decided what comes first.
Quick wins
High impact, low effort
- Start here
- Fast ROI
- Builds momentum
Strategic projects
High impact, high effort
- Plan carefully
- Longer haul
- Highest value
Can wait
Low impact, low effort
- Into the backlog
- Nice-to-have
- If time allows
Hands off
Low impact, high effort
- Not worth it
- Ties up resources
- Look for an alternative
From experience: do's and don'ts
What makes automation projects succeed — and what makes them fail in droves.
This works
- Rebuild the process first, then automate
- Start with simple, frequent workflows
- Involve the people who run the process daily
- Document the current state cleanly
- Define how you'll measure success up front
- Pilot small before you roll out
This goes wrong
- Automate a broken process 1:1
- Jump straight into the tool without analysis
- Try to tackle everything at once
- Ignore scaling and maintenance
- Present the team with a done deal
- Consider privacy and compliance too late
Maturity: is the process even ready?
Automation requires a stable workflow. These five levels show where your process stands.
Ad-hoc
Runs differently every time, no fixed rules.
Defined
The workflow is described but not enforced.
Standardized
Executed consistently the same way.
Measured
Metrics are captured and watched.
Optimized
Continuously improved.