Tell Amy how the work runs.
She maps the process.
Process knowledge often sits in a few heads, and classic process diagrams end up maintained by nobody. With Amy, you describe the work in conversation. She asks about responsibilities, rules and exceptions until the flow is right, and records it as a model your whole team can read and review. That’s the foundation before anything is automated.
- No drawing tool needed
- Export as BPMN 2.0
- Open AIM format
You talk.
Amy asks.
Describe the work the way you’d explain it to a new colleague. Amy asks where things would otherwise go wrong later: limits, exceptions and responsibilities. What you confirm is in the model right away.

- Above what amount does Jonas decide?
- Who decides when the budget falls short?
- What happens to a rejected quote?
- Where does the order go after approval?
The result: a model your whole team can read.
Roles, steps, decisions and rules, connected into one flow. See it as paths, a tree or a map, and click through every step.
Amy finds the gaps before your team trips over them.
After every change, Amy checks the whole model. What she finds, she asks as a question – and your team decides what applies.
Who is responsible?
Steps, decisions and deadlines without a responsible role.
What happens next?
Decisions and exceptions that leave a case without a next step.
Who hears it?
Outcomes and signals that no later step picks up.
Is the role allowed?
Steps that need data or actions the role has no permission for.
What you do with your model.
A reviewed model is worth having on its own. You can automate later.
Onboard and align.
Everyone with access reads the same model. Every accepted change is a version you can trace.
Export as BPMN 2.0.
Take the flow as a .bpmn file into the process tools you already use.
Use it as an AI prompt.
A reviewed part of the model becomes instructions for the AI your team uses: context, inputs, boundaries, expected result.
Put it to work.
Once the model is ready, it becomes an application for your team, without writing software.
How it works

Which process will you map first?
Pick one your team knows well and simply start talking.
Tell Amy how your team works→