Services
Three fields, one goal: less manual work.
I work on the processes that run every day and still belong to nobody. No innovation theatre — every project moves a number you already measure.
01Automation
Workflows without the handoffs
Most mid-market processes are not complicated, they are fragmented: one step in the ERP, one in Excel, one in an inbox, one in a colleague’s head. Automation here means assembling the pieces first — and only then making them run.
Typical projects
- Turn inbound email enquiries into draft quotes automatically
- Check invoices and delivery notes without manual entry
- Reports that build and send themselves
- Keep master data in step across ERP, CRM and shop
- Approval flows with a traceable history
This is you if …
- The same data is typed in by hand in more than one place.
- A process stalls when one particular person is on holiday.
- Nobody can say how many cases actually run through per month.
- Excel has become load-bearing somewhere in the workflow.
02Artificial intelligence
AI that lands in daily operations
Language models are good at exactly the work that resisted automation until now: reading unstructured text, sorting it, summarising it, drafting a reply. They are bad at making decisions unchecked. The difference between a useful and a dangerous AI project sits precisely on that line.
Typical projects
- Classify and pre-answer documents and email
- Knowledge bases people actually use
- Check quotes and technical copy for completeness
- Pre-qualify technical enquiries automatically
- Multilingual content without a translation loop
This is you if …
- Skilled staff spend hours reading and sorting text.
- Knowledge sits in documents nobody can find.
- There was an AI pilot once — it never went to production.
- The same question gets answered afresh every week.
03Enterprise communications
Communication that does not die in an inbox
Communication is the process least often treated as one — in the contact centre as much as internally. Enquiries arrive over five channels, ownership is implicit, and whether a commitment was honoured only becomes clear when somebody complains. That can be given structure without bureaucratising the tone.
Typical projects
- Contact centre platform across multiple countries and channels
- Customer data from ERP and CRM merged into the agent workspace
- Voice dialogue and routing without nested menu trees
- Custom reporting instead of the platform’s stock dashboards
- Teams, Outlook and ticketing connected properly
This is you if …
- Agents have three systems open while the customer waits.
- Enquiries go to personal inboxes rather than to a team.
- Nobody knows how many enquiries go unanswered.
- Figures from two countries cannot be compared.
04How it works
The way I work
Every stage is time-boxed. If the pilot saves nothing, we stop there — that is the point of splitting it up.
Analysis
1 weekWe look at the process as it actually runs, not as it is documented. You end up with effort, saving potential and risk per step — and a straight recommendation about what is worth doing and what is not.
Pilot
2–3 weeksOne part of the process goes live, with real data and real users. Fixed price, so you know the downside before you commit.
Rollout
4–8 weeksExtension to the full process, including training, documentation and handover to your IT team. After this you can run it yourselves.
Operation
Ongoing, optionalMonitoring, adaptation to new cases and regular review — or you take it over entirely. No lock-in, no forced maintenance contract.
Not sure which of these applies to you?
That is the normal case, and exactly what the analysis week is for. You come out of it knowing which three processes are worth doing, and in what order.