Why we built this, the proof, and why this is not a chatbot
We did this work by hand for ten years. Then we rebuilt ourselves.
In government, I once saw the as-is landscape alone take two and a half years to produce. Two and a half years of drawing, digging through material and chasing people who no longer worked there. And by the time it was finished, the first part was already out of date.
That is not an exception; that is how the profession has worked for thirty years. So Remco and I did something different: we rebuilt our own work. An algorithm trained on everything the two of us have seen between us in twenty-five years: how to get a process out of a messy document, when to split it up, which questions to ask when something does not add up.
And the most important part we deliberately left unautomated: judgement. Every diagram is approved or rejected by a person before it exists. That is not a limitation; that is the product.
Quincy Diepeveen Co-founder of De ProcesToppers, together with Remco Kauderer
This goes in. This comes out.
Not a demo built on someone else's example, but a real document and the validated diagram the engine made from it. Recorded live, unedited.
A 27-page work instruction goes in, the validated diagram comes out.
How it works, in five steps
1. You choose your document. A work instruction, a policy document, a spreadsheet or the minutes of a meeting. The messier it is, the more clearly you see the difference.
2. The engine does all the work. It pulls the process out of the noise, splits processes that are too large and puts roles in the right lanes.
3. The algorithm checks itself. Anything missing or doubtful becomes a question for you, not a guess.
4. It lands in your own tooling. Export to your own platform, or tool-independent as BPMN 2.0, PDF and a written description. You are not locked in to anything.
5. You validate with the business. Green, amber or red for each part. Nothing becomes final until a person signs it off.
This is the output I expect. There is real promise in this.
We budget 160 hours for describing a single process. This can be done differently, and faster.
Normally this would have taken me three months; soon it will take thirty minutes. That is something I can take to my manager.
Quotes from our conversations over the past few weeks, translated from Dutch. We leave out names because we only name references with written permission.
Why this is not a converter. And not a chatbot.
No. Two minutes that explain the difference: a model that knows one discipline, understands first and only then draws, with a person who approves. The on-screen text is in Dutch for now; the images carry most of the story, and an English version is on its way.