Built for the people who keep the know-how
Verdin is for business analysts, knowledge managers and small teams who need to know who does what, and to keep that record true as the work changes. Here is what each of them gets from it, and who should look elsewhere.
Know who does what, without chasing anyone.
You run the workshop, and the people in the room do the work. The aim is to leave with a process that they agree on and an owner for each step. If the map needs a legend before anyone can comment on it, the detail you came for never comes out.
In Verdin each box is one activity and each line is the outcome that starts the next one, so a stakeholder checks the map on a screenshare without training. Each step carries its RASCI roles, and the handover report shows each place where work passes from one role to the next. You leave the meeting with a map that is already agreed, not one that you still have to send round.
Grow the team without losing how the work gets done.
Your problem is not the drawing. The know-how lives in a few heads, and the team grows faster than its written procedures. Each new starter shadows someone, and each new initiative starts again with the same interviews.
Verdin keeps your processes in one library that you can search and tag. A new starter reads the map to learn the basics. Health signals show the maps that nobody has reviewed for a while or that have no owner. Each map is structured JSON that you own. The longer argument is on Verdin for knowledge management.
The process work you could not get an analyst for.
Process-intelligence platforms are priced and scoped for programmes, not for a team that only needs its processes written down. And a small team seldom has an analyst to write them.
Verdin gives you a start. Give it a procedure document, a policy or a meeting transcript, and it draws a first draft for you to correct. That feature is in beta. Correcting a draft is faster than a blank canvas, and your maps export as JSON, so you are not locked in.
Who it isn’t for
Verdin is deliberately narrow, and it is better for both of us if you learn that here and not three weeks in. Look elsewhere if:
- You need executable BPMN. If the diagram has to drive a workflow engine, or your regulator asks for BPMN 2.0 specifically, use a BPMN tool. Verdin maps are for human readers.
- You want process mining or RPA. Verdin maps how work is meant to run. It does not discover processes from event logs, and it does not automate them.
- You want a low-code app builder. A map here stays a map: a shared record and the reports that come from it, not a deployed application.
What is left is what most teams need: a map that people read and keep true. To see why it works, start with the short guide.