The report breaks your work down into tasks, assesses each task, and calculates what that means in fte. That outcome is a dossier, not an assignment. What you do with it depends on what's available to you: time, knowledge of your own systems, and appetite for taking it on yourself. There are three routes. The order is not arbitrary: the first route is the cheapest, and most companies can get further with it than they think.
You receive a roadmap: the tasks from the report translated into steps, with templates included and an estimate of the time per step. Not open-ended advice, but a sequence: what comes first, what comes next, and what each step requires in terms of data quality and connections to the systems you already use.
This route fits when someone within the company knows the digital side of the work — the systems, the exports, the process owners — and is given the time to work through the steps themselves. The work isn't heavy in the sense of being specialist, but it does require persistence: filling in templates, gathering data, and genuinely finishing the steps rather than stalling after the first one.
This route doesn't fit when no one can free up time, or when the first steps already stall on data that isn't stored anywhere properly. The roadmap is still correct in that case, but it will sit unused. If you want to see first exactly how that roadmap comes together, that's explained on how it works.
Here the tool remains the dossier — the report and the roadmap remain the basis — but a partner takes over the steps that don't get picked up internally. You choose per component: some steps you handle yourself, others you hand to someone who has done it more often.
This route fits when someone can set the direction and monitor progress, but doesn't have enough hours to take every step themselves. It also fits when one of the steps falls outside your own expertise — a connection that's specialist in nature, or a dataset that needs cleaning up before a step is worth taking.
What you need to be able to do yourself: assess progress and decide what you do and don't hand over. The partner works from the report, not from their own assessment; the dossier remains the guide, even as part of the work shifts.
This route doesn't fit when there's no one internally to direct the partner. In that case, "partially guided" becomes, in practice, a full handover anyway — only without anyone having decided that in advance.
A partner takes on the implementation in full, with the report as the dossier. Not from a blank slate — the partner starts from the tasks and the assessment already in place, not from a new round of questions. And only with your permission: the report is and remains yours, and sharing it is a choice, not an automatic next step.
This route fits when there's no room to drive it yourself, or when the outcome shows that the implementation is bigger than what can be organised internally — multiple systems, multiple departments, or steps that need to happen one after another without delay.
What you need to be able to do yourself: read and assess the report before handing it over. A partner working with the dossier works faster and more precisely than a partner who has to start from zero, but that advantage only exists if you have established yourself that the outcome is correct.
This route doesn't fit when the report hasn't been reviewed yet, or when the choice for outsourcing mainly stems from haste. The dossier exists to support that choice, not to bypass it.
None of the three routes changes what the report says. The tasks, the assessment and the fte calculation are fixed once the scan is complete; the route only determines who takes the next step. A partner brought in under route 2 or 3 stands outside the scan itself — that step comes after the report, never inside it.
Whichever route fits, the basis is the same: a breakdown of your work into tasks, not a comparison with what other companies do. Exactly how that breakdown is built and what happens under the hood is explained on what it is. And for those who want to read first how other companies have used the three routes, and where that did or didn't fit, there's the knowledge base.
The choice between the routes is not final. A company that starts with route 1 and gets stuck on one specific connection can still outsource that step without abandoning the rest of the roadmap. The routes aren't levels you have to work through, but three ways of moving forward with the same outcome.
Vraag maar. Ik ken de kennisbank van deze site; wat ik niet weet, zeg ik erbij.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.