Services / 02
Process mapping and AI agents.
Two services that usually run in sequence. The mapping shows where AI saves hours; the agents take over that work where the mapping says it is worth it.
AI process
mapping.
We find out how work runs in your company today, where the hours go, and where AI should change it.
Example / onboarding a new client
How the mapping runs
- 01
Agree the scope
In the first call we choose what to map, from one team’s processes to the whole office.
- 02
Talk to the people who do the work
Interviews with the heads of each function, video sessions with the people who run each process, and sample documents with sensitive data removed. A short questionnaire can cover larger teams.
- 03
Map and score every activity
Each recurring activity is listed with the time it takes and the tools involved, and marked with what AI could prepare, check or take over, and the risks for confidentiality and accuracy.
- 04
Hand over a ranked plan
A written report ranks the changes by hours freed, effort and risk: what to change in the tools you already have, and which agents are worth building.
Fig. 02 / step map
What a mapped
process looks like.
Illustrative example: onboarding a new client. Every company’s map is different.
| Step in the process | After the mapping |
|---|---|
| Collect client details from the intake form | An agent drafts the client record, staff confirm it |
| Ask for missing documents | An agent writes the request from your checklist, staff send it |
| Check the documents received | AI flags what is missing or unreadable, staff decide |
| Pricing, credit terms and contract | Stays with your people |
AI prepares, people approveSharedPeople only
AI agents.
Agents that take over part of a process: reading documents and extracting data, drafting replies and records, sorting requests, answering the phone.
Example / one process with agents
How an agent is built
- 01
Start from the map
We build agents for the steps the mapping ranked highest, where the volume is high and the work starts from documents, emails or calls.
- 02
Decide what it may do
With the people who own the process, we write down what the agent does on its own, what it hands over, and who approves its output.
- 03
Build and connect it
Engineers build the agent and connect it to your systems through their APIs, once access and data handling are agreed with your IT. Staff test it before it goes live.
- 04
Run it with a person in charge
A named person in your company approves what matters before it leaves the company. Maintenance and changes can continue after launch.
Two examples from our work: an invoice-reading system in production at a customs broker, and a phone agent that answers the main line of a humanitarian organization.
Questions / 06
Questions companies
usually ask.
01Do you need access to our systems?
Not for the mapping: you choose which sample documents to share and remove sensitive details first. An agent has to connect to the systems it works in, so access, data handling and where it runs are agreed with your IT before anything is connected.
02Do we have to start with the mapping?
It is the usual start, because it shows which agents are worth building. If you already know the process you want to automate, we can start with a short mapping of that process only.
03Will we need to buy new software?
The mapping starts from the tools you already have, and many changes happen inside them. An agent can have its own running costs, such as hosting and AI model usage, and the plan states them before you decide.
04How much time does it take from our team?
It depends on the scope. For the mapping we need interviews with the heads of the functions involved and video sessions with the people who run each process. We agree the calendar in the first call.
05What does it cost?
Scope and price are fixed and agreed before any work starts, based on what we map or build. We talk about them in the first call.
06Who builds the agents?
Mattia designs each agent and leads the project, and engineers build and connect it. The person you speak with in the first call stays your contact until the agent is running.
Further reading
05 articles
- What AI process mapping coversHow a company’s recurring work is mapped, scored and turned into a plan for the tools it already has and the AI agents worth building.
- Choosing the first processes for AIWhat makes a process a good first candidate, and why work driven by one expert’s judgment usually is not.
- Process mapping without access to your systemsRedacted samples and conversations with your team are enough to map the work. Access for an agent is agreed with your IT later.
- What the process mapping report containsFive parts: today’s activities, the scores, the priorities, the plan for existing tools and the agents worth building.
- When an AI agent is worth buildingWhen an agent makes more sense than the tools a company already has, how it connects to your systems, and what stays with people.
Start with a 20-minute call.
Pick a time for a 20-minute call, or write to mattia@mullionstudio.com with a line on your company. We look at where AI could save hours and whether a mapping, an agent or both make sense. Scope and price are agreed before any work starts.