Method
Six weeks to go from intuition to a production pilot.
A four-step journey, each stage delivering a tangible result. No 200-page report gathering dust in a drawer.
Six weeks is a target, not a contractual promise that holds everywhere: a multi-entity group with scattered data will take longer. What doesn't change is the order of the steps and the fact that each one ends with a deliverable whose value you can judge before committing to the next.
Explore
Business interviews, review of existing data and tools. We identify the real pockets of value.
We meet the people who do the work, not just those who manage it. In parallel, we look at what already exists: available data and its real quality, tools already in place, previous attempts and why they were dropped — that last question is often the most instructive.
DeliverableA map of candidate processes and a data maturity note.
Weeks 1–2Scope
Use case selection, gain costing, architecture choices and compliance analysis.
Each use case is costed on both sides: estimated annual gain and total cost, covering both implementation and operations. The architecture is finalized at this stage, placing every building block on the sovereignty grid, and the AI Act qualification is done before a single line of code is written.
DeliverableA costed roadmap, an architecture file and a regulatory qualification.
Week 3Prototype
Building a working pilot on your own data, tested by your teams under real conditions.
The pilot runs on your real data, in your environment, with your users. A prototype validated only by the provider proves nothing: what matters is what your teams find when they use it on their own work.
DeliverableA live pilot, with usage metrics and documented limitations.
Weeks 4–5Deploy
Going live, user training and skills transfer. You stay in control.
Going live comes with user training and the full handover of the technical file. We consider the engagement successful when your teams can evolve the solution without calling us back.
DeliverableSolution in production, documentation, trained teams.
Week 6
FAQ
Frequently asked questions
What happens if the diagnostic concludes no use case is worth pursuing?
We tell you, and the engagement stops there. It has happened before and it will happen again: a context where the data isn't ready, or the volume too small, doesn't justify investment. An honest scoping costs less than an abandoned pilot.
Can we stop after a single step?
Yes. Each step ends with a deliverable you can use without the next one — that's the whole point of this structure. A standalone diagnostic is a complete engagement, and you're free to hand its execution to whoever you want.
Do you work with our teams or in their place?
With them, and increasingly through them. Skills transfer isn't a final step: from the prototyping stage onward, your developers or business leads work on the code and the configuration, otherwise the autonomy promised at the end never actually happens.
Contact
Let's talk about your next use case.
Thirty minutes is enough to work out together whether an aumia diagnostic makes sense for your organization. No commitment, no jargon.