How it works
From how work flows today to AI in production.
Arnaldus takes one process at a time through five stages. Business and IT see the same picture at every stage, and your team decides what goes ahead.
Five stages, one process at a time.
01
Process Scan
The process mapped: steps, roles, systems, decisions and bottlenecks.
- What you do
- Describe how the work flows today, in your own words.
- What Arnaldus does
- Asks the right follow-up questions and structures what you describe.
- What you get
- A clear map of the process that your colleagues recognise.
02
Opportunity Map
For every step, the fitting AI pattern, with value, effort and risk.
- What you do
- Check the map and add what only your team knows.
- What Arnaldus does
- Matches each step to proven AI patterns and weighs value against effort and risk.
- What you get
- A ranked view of where AI helps first, and where it should not.
03
Use Case Brief
Business case, human decision points and IT blueprint in one document.
- What you do
- Business and IT review the brief together and sign off.
- What Arnaldus does
- Writes the business case, the decision points and the technical blueprint.
- What you get
- One plan that both business and IT have signed.
04
Mission
Building and running the pilot.
- What you do
- Provide access to the people, data and systems the pilot needs.
- What Arnaldus does
- Builds the pilot with your team and prepares it for production.
- What you get
- A working pilot in your own process, not a demo.
05
Impact
Measuring after go-live: lead time, quality and cost.
- What you do
- Decide, based on the results, whether to scale, adjust or stop.
- What Arnaldus does
- Measures the KPIs agreed in the brief and reports what changed.
- What you get
- Evidence of what the use case delivers.
Business and IT see the same picture.
What the business sees
- Where time and effort go today
- Value, effort and risk per opportunity
- Which decisions stay with people
- KPIs to measure after go-live
What IT sees
- Systems and integrations involved
- Data sources, access and retention
- Security, privacy and AI Act notes
- What it takes to run and support
Guided pilots
You can start a Process Scan yourself. When a use case is ready to build, the Arnaldus team guides the pilot with you.
- Shape the Use Case Brief with business and IT
- Build and test the pilot in your process
- Prepare the path to production with your IT team
Frequently asked questions
Do we need to share data for a Process Scan?
No. You describe how the work flows; customer or personal data is not needed. If a pilot needs real data, business and IT agree in the Use Case Brief which data is used, where it is processed and who has access.
What does a pilot cost?
Starting a Process Scan costs nothing. The scope and cost of a guided pilot follow from the Use Case Brief and are agreed with you before any building starts.
Which systems does it work with?
The systems you already use. The Use Case Brief lists the integrations a pilot needs, so IT can assess them before anything is built.
Who owns the result?
The Use Case Brief and what we build for your pilot are made for your organisation. Ownership and use are agreed in writing before the pilot starts.
How long does a Process Scan take?
The first map comes out of one conversation. Most teams then refine it with the colleagues who do the work.
What happens after the pilot?
You decide, based on the measured impact, whether to take it into production, adjust it or stop. Production is planned together with your IT team.
Start with one process.
Describe one process that takes too long. Arnaldus maps it and shows where AI can help first.