AI and automation can genuinely take work off your people. But you cannot hand over what you have never written down. This is where that starts.
Free while the tool is in early use. No card, no trial clock.
A process, drawn so you can see what a machine could take and what it should not. Shape says who powers the step. Colour says whether it is live. The badge says AI is helping, not replacing.
The first step
The tools are here and they are good. What is usually missing is a clear account of how the work currently runs — who does what, in what order, with which system, and how long it takes them. Without that, automation gets bolted onto whichever task shouts loudest, and the business ends up faster at things it should not be doing at all.
Write the work down, and it becomes obvious what a machine should be doing.
A blueprint is that account. It takes an afternoon, not a consulting engagement, and it is the thing every sensible automation decision comes after.
What it does
Every step carries the same four facts, encoded so a whole process can be read without a key. Not to produce a tidy diagram — to make it obvious who is spending their time on what.
Rounded for a person, hexagon for automation, cut corners for AI. The shape answers who would stop the step if you took them away.
White runs today. Red is real but paused — the step you turned off in March and never deleted, still visible, still counted separately.
A double outline marks a handoff you do not control — a customer filling a form, a supplier confirming stock. The steps most likely to leave someone waiting.
A meeting with an AI notetaker is still a human step. Enablement sits on top of the shape instead of pretending the work went away.
What you get back
Every step carries its owner, its tools and — on human steps only — the minutes it takes. So the map totals itself. This is a real reading of an eight-step quote process:
That fifteen minutes is the useful figure — not because it is a saving waiting to be banked, but because it is somebody's afternoon. The question a blueprint sets up is where it should go instead.
The measure that counts
It would be easy to build this so it reported hours saved and roles removed. Those are simple to count and they are the wrong target. A business that automates its way to the same work with fewer people has not got smarter; it has got cheaper, once.
The measure worth chasing is whether time moved from work that barely mattered to work that does — for the person doing it, for the business, and for whoever is on the other end of it. That is harder to quantify, and we would rather say so than dress a percentage up as an answer.
It is also the most motivating thing a team can be handed. Most people never get to see the good their work does. Mapping it is where that starts becoming visible.
Nobody starts from nothing. Paste in the process however you keep it today and correct from there — it is parsed in your browser, so nothing is uploaded and nothing is charged.
Straight out of a Word doc or an email. Numbering and bullets are stripped for you.
CSV or TSV. Columns named owner, tools, stage, type or minutes are picked up automatically.
Nodes and connections, including the labels on branches, come across intact.
Exported JSON round-trips exactly, which is how a blueprint moves between people.
Blueprints are kept to your account, and the isolation is enforced by the database rather than the page. Export to JSON, SVG, PNG or a written spec whenever you want a copy that owes us nothing.
Pick the one you already suspect is the problem. Ten minutes will tell you whether you are right.