Processes that don't wait, they act
For process managers, architects and organisations taking the next step in BPM.
Agentic BPM grew from a simple observation: SME organisations get stuck in two patterns. The first: BPM projects that try to model so much detail that the model is never finished. The second: AI experiments that take place outside of process reality and afterwards can't find a home in the business. Agentic BPM solves both by modelling at a higher level of abstraction — outcomes, goals, boundaries — and delegating execution to a combination of people, workflows and agents.
We combine 40+ years of business transformation experience with deep knowledge of process architecture and AI agents. No exclusive vendor contracts, no lock-in. Code and configuration are always client-owned. And we also tell you when agentic BPM is not the right route — that is what distinguishes honest advice from a sales pitch.
-
Frame modelling, not flow modelling
Not 'how' but 'what'. Goals, constraints and escalation paths — the execution we leave to people, workflows and agents together.
-
Employees as co-designers
Agentic redesign only works when the people who execute the process are involved. We always start with the question: which work would you like to hand over?
-
Honest about what doesn't fit
Not every process is a good candidate for agentic redesign. 'You should not make this agentic' is a valid piece of advice — and we give it.
Team
Two faces — one goal: making agentic BPM tangible for the people who need to steer processes with it.
-
Wiemer Kuik
Founder & senior agentic BPM advisor
Wiemer Kuik has worked at the intersection of process management, organisational change and technology for 40+ years. As a former transformation advisor at major Dutch organisations, he knows what it costs when processes don't work — and what it delivers when they do. His focus is on the practical side of agentic BPM: not the hype story, but the architectural choices, governance setup and adoption approach that determine whether an implementation actually succeeds.
Agentic BPM is not an AI project. It is a process project in which AI takes over the execution. That sequence is everything.
LinkedIn -
Bert Kok
Coordinator & lecturer Process Architecture
Bert Kok connects process architecture with the human side of organisations. With a background in entrepreneurship, innovation management and journalism education, he emphasises comprehensibility: how do you make agentic BPM architectures discussable for people without an IT background? He coordinates the open workshops and guides participants in translating technical concepts into their own organisational context.
Our partners
Our locations
- Main location
Digital Education Lab
Padualaan 97, 7e verdieping
3584 CS UtrechtMain location · workshops
- Secondary location
Dotslash
Europalaan 93
3526 KP UtrechtWorkshops & implementation sessions
- Secondary location
HU Heidelberglaan
Heidelberglaan 15
UtrechtEnterprise programmes on location
Frequently asked questions
- Is Agentic BPM just another buzzword?
- For anyone who has lived through BPM cycles, that is a fair question. The difference from earlier waves is that the execution layer has fundamentally changed. Agents do work that only humans could do before. That changes what you model, how you model, and who executes.
- We just bought a BPM tool. Does this start over?
- Not necessarily. The flow parts of processes — where deterministic steps suffice — continue to work fine in a classic BPM tool. What changes is that alongside the flow parts, frame parts now appear where agents work. The integration between the two is a design question, not a replacement.
- What if the agent makes a process error?
- It happens. Every agentic process piece should come with an authority model (what can the agent do independently, what requires a human), monitoring that flags deviations, and a rollback path for consequential actions. A well-designed agent makes fewer errors than a tired employee; a poorly designed agent makes far more.
- Will people lose their jobs?
- Not through this approach. The practice explicitly assumes capacity extension, not replacement. The work does change: routine execution decreases, judgement and complex tasks increase. That requires investment in people, not farewells.
- Our processes aren't well documented. Can it still work?
- Yes, and it is actually one of the attractive aspects. An agentic BPM engagement often starts with process inventory, and that inventory delivers documentation as a by-product. Agentic observability records what actually happens — not what documentation says should happen.
- Can we do this ourselves?
- Yes, and that is the ideal. Workshops and consultancy are accelerators, not a permanent crutch. A typical growth curve: year 1 with external help, year 2 in collaboration, year 3 in own management with optional sparring.
- What is your independent position?
- No exclusive sales or partner contracts with BPM, model or platform vendors. Advice is given based on what fits the client. Open-source and self-hosted options receive a full place in the assessment.
- What does an Agentic BPM engagement cost?
- The technology costs of running agents have dropped significantly in recent years. In an SME context, you often talk about hundreds of euros per month in model costs for the first process pieces. The larger costs are in process design, build and governance — one-off in setup, limited in ongoing management.
Which process domain needs attention at your organisation?
A sixty-minute conversation is enough to determine which domain is the best starting point — and whether a workshop, redesign or roadmap fits best.