The gaps that slow a team down are the ones nobody wrote down.
I embed with your team and learn how the work actually moves: the processes people follow, the equipment they run it on, and the software wrapped around both. Then I close the gaps worth closing. AI where it earns its place, ordinary tooling where that is the honest answer.
Processes · Equipment · Software
- ViaEurope


- BuildItPlayIt
Past professional experience on these companies' products, before this practice. Not clients of the consultancy.
Most AI projects start with a tool and go looking for a problem.
That order is backwards, and it is the reason so many of them stall after the pilot. The tool gets bought, a demo gets built, and then it meets a process that nobody fully understood, including the people inside it.
What actually drains a team is rarely in the documentation. It is the spreadsheet someone rebuilds by hand every Monday. It is the four systems one request passes through. It is the message thread that exists only to chase an approval. You do not find that in a workshop. You find it by sitting inside the team while the work happens.
So that is what I do. I join the team for a defined period, trace how the work really runs, and we decide together which gaps are worth closing. Then I build the fix and hand it over.
Before this practice, more than twenty years inside high tech companies, working on products in gaming, logistics, marketplaces, social networks, CMS and admin tools, and back office systems. Enough different industries to recognise the same few problems wearing different clothes.
Usually that means owners and department leads at small and mid-sized companies, and transformation, product and operations leaders in larger organisations: close enough to the work to feel where it drags, with enough authority to change it.
Product and platform strategy
Requirements, priorities and roadmaps that a business and a technical team both understand.
Technology operations
Support, service management and incidents, where manual work piles up quietly.
Automation and AI
Workflow automation, AI-assisted operations and low-code tools your team can maintain.
Business transformation
Process redesign, operating models, KPIs and the change management that makes it stick.
Inside, not across the table
I work in your tools, your channels and your meetings, as a member of the team rather than a visitor with a deck. People tell you different things once you are in the room every day.
Process first, tool second
The map comes before the technology. Some of the best answers are a rule change or deleting a step, and I will tell you when that is the case instead of selling you a model.
Built to be handed over
Every automation ships with documentation, a named owner on your side, and a plan for what happens when it breaks. The goal is that your team runs it without me.
Eight signs something is worth a closer look
- The same data gets typed into more than one system.
- Someone's job exists mainly to move information between two tools.
- A recurring report is assembled by hand on a schedule.
- Inbound gets read, classified and routed by a person every time.
- Approvals are chased through messages rather than requested in a system.
- Work pauses overnight because one specific person has to look at it.
- The answer to "how does this work" changes depending on who you ask.
- A machine or a tool sits idle because the work around it is badly sequenced.