/loop in practiceProcess mapping
Every process of your company, drawn before anything is built.
In the first four weeks of the /loop model, we meet each area of the company and draw how its work runs today: every step, every decision, every tool. The map shows where work waits, where it repeats and where an agent can take part, so the company decides where to invest with the facts in hand.
The problem
Few companies have a map of how their work really runs.
- 01
Procedures describe how work should run, not how it runs.
- 02
Each area knows its own part; the hand-offs between areas belong to no one.
- 03
Without a map, automation is chosen by intuition, and often on the wrong step.
What you receive
One map, four things in it.
Every process in BPMN.
Lanes for each role, every activity and every decision, in the standard notation.
The tools in use.
Which programs each step relies on, and how far each step follows fixed rules.
Today and with automation.
The same process in two versions, at the same scale, with the steps an agent would cover.
Open points.
What is still missing, and the questions for each area.
Online behind a login, or as a document. Processes can also be exported as standard BPMN files for Camunda, Signavio and other modelling tools.
How it works
Four weeks, three steps.
- 01
Interviews
One meeting with each area involved. We collect procedures, documents and real examples of the work.
- 02
Map
Each process is described as data and drawn by our renderer, never by hand, so every map follows the same rules.
Step Role With automation Invoice arrives by email Admin office Typed into the ERP Admin office Agent Matched to the order Admin office Agent Approved Purchasing Paid Admin office - 03
Validation
The people who run each process read the map and add written comments. The map is closed when every area has confirmed it.
12- 1
Sales office Orders also arrive by phone.
- 2
Warehouse Stock is checked twice a day, not at every order.
- Sales office1 comment open
- WarehouseConfirmed
- 1
- Next
Priority Framework
In two weeks, the company chooses which processes to address first.
The five phases of /loopWave 1
Supplier invoice approval
Order entry
Wave 2
Customer requests
Later
Purchase request
Your company
Your processes, the same method.
What changes
The areas, the processes and the tools: ERP, CRM, mailbox, shared folders, spreadsheets.
What stays the same
The method, the standard notation, and one rule: we read your systems and never write to them.
What we need from you
A calendar of interviews, the documents you already have, one contact person, and first figures on volumes and time.
Is it for you
It fits if
Your company has recurring work that moves between people and areas.
Part of that work follows rules: invoices, orders, requests, reports.
You want to know where AI pays back before you invest in building it.
See a sample map
A sample map, on test data.
The same map we deliver, on an invented manufacturing company. Choose an area and switch between today and with automation.
- Steps
- 5
- Done by people
- 5
- Done by people
- 3
- Done by the agent
- 2
- Tools
- Email, ERP, Bank portal
- Steps
- 5
- Done by people
- 5
- Done by people
- 3
- Done by the agent
- 2
- Tools
- Email, PDF, ERP
- Steps
- 5
- Done by people
- 5
- Done by people
- 2
- Done by the agent
- 3
- Tools
- Email, CRM
- Steps
- 5
- Done by people
- 5
- Done by people
- 4
- Done by the agent
- 1
- Tools
- Spreadsheet, Email, ERP
Test data of an invented manufacturing company.
Want to see your processes drawn this way?
Process mapping is one way we understand your business in the first phase of /loop, Business Understanding. Tell us which area of your company you have in mind.
Let’s build your AI product