From AI Photo to roadmap: what happens in ten days
"How much time does this cost me" is the first question every director asks. Here is the exact, day-by-day answer.
"How much time does this cost me" is the first question every director asks, and it is a fair one. Most answers to that question are vague: "a few weeks", "it depends". This piece gives the exact answer, day by day, because the process is already on our own site and has nothing to hide.
The process in two weeks
The path from AI Photo to roadmap takes ten working days, spread over two weeks, at a fixed fee starting at 3,900 euro.
| Day | What happens | What it costs you |
|---|---|---|
| 1 to 3 | Digital intake: you share context through a short form | A quarter of an hour to fill in |
| 4 to 6 | Conversations with a handful of key people at your company | An hour per conversation, usually two to three |
| 7 to 9 | We map opportunities, run the numbers, build the roadmap | Nothing, this is our work |
| 10 | Delivery: we present the diagnosis and roadmap live at your office | An hour, with your whole management team |
Total: a quarter hour, two to three one-hour conversations, and an hour of presentation. Less than a day spread over two weeks, for a complete picture of where you stand and what your first step is.
A conversation across the table. The part that pays off most and costs least.
Why it does not need to take longer
The reason this fits in ten days is that the scan is not an implementation. We build nothing in this phase, we map what already exists and what pays off most. That is a different activity from running a pilot, and it therefore needs a different amount of time.
An advisory process that takes weeks of workshops before anything is on paper often does not need more time because the subject is more complex. It needs more time because the process itself is set up inefficiently. See also our piece on why an advisory report is not capability: a report that takes months to write is not automatically more valuable than a roadmap produced in ten days.
What happens exactly in each phase
Days 1 to 3, the digital intake. You share context about your company through a short form: size, sector, which systems you use, what stands out about your own way of working. No workshop, no session, a quarter of an hour of work you fill in whenever suits you.
Days 4 to 6, the conversations. We speak with a handful of key people, usually the director and two or three people who actually do the work. This is the part that pays off most and costs least: an hour per conversation asking about frustrations, not wishes. See also why an AI scan is not an IT project: this is exactly why those conversations start with the owner.
Days 7 to 9, the analysis. This is our work, not yours. We map opportunities based on what we heard, run them against expected impact and feasibility, and build the roadmap. You hear nothing from us until it is done.
Day 10, delivery. We present the diagnosis and roadmap live at your office, with your whole management team present. This is the moment the ranking of opportunities, built on what we heard in the conversations, becomes visible for the first time.
Presenting to a management team. Day ten, live at the office.
What we ask the people we speak to, and what we do not
The conversations on days four to six deliberately are not about AI. We do not ask "what would you like to do with AI", we ask "which part of your work costs the most time without adding value" and "where does a good colleague get stuck on something no person should be doing". Those questions produce answers nobody resists, and they produce exactly the input we build the roadmap on.
That is also why the conversations can stay short. An hour is enough to surface three to five concrete frustrations, and that is all you need to build a ranking of opportunities. Longer conversations rarely produce more usable information, mostly they produce more time spent.
What happens if your company is larger or more complex
At a company of three hundred and fifty people with multiple locations, the number of conversations can rise to four or five instead of two or three, and that still fits within the same ten days. What does not change is the structure: intake, conversations, analysis, delivery. The scale of the company changes how many people we speak to, not the process's lead time.
What happens after day ten
The roadmap is not an endpoint, it is a decision point. Some companies choose to run with it themselves. Others choose a Capability Sprint, where we build the first working application together with your people, on a project basis.
What does not happen: a sales pitch pressuring you to continue. The roadmap stands on its own and is usable whatever you do with it.
Why this pace is also a signal
A ten-day process is not just practical, it also says something about how we view the work. A process taking months before anything concrete exists loses momentum and attention inside the organisation. Ten days is short enough that the people we spoke to on days four to six still remember what they said when the roadmap gets presented on day ten.
About this page
The exact day-by-day breakdown and the price starting at 3,900 euro come from our own AI Readiness Scan page. This is the state of play on 24 August 2026.
Frequently asked questions
Sources
- Radical: de AI Readiness Scan, proces en tarief— radicalai.nl ↗
Tell us what you need.
We respond within 24 hours, from a real human.
Get in touch
