You have the roadmap. Now what?

You have the document. Maybe it came from Made Smarter, maybe from Digital Catapult's toolkit, maybe from a consultant who scoped your operation and wrote it all up in a slide deck. It names the problems correctly. It lists what AI could do about them. And it has been sitting on your desktop, or printed and clipped to something, for however long it has been since you got it.

Nothing has changed in your business since that document arrived, and that is not a failure on your part. It is close to the default outcome for a roadmap once it is handed over.

Why a roadmap sits there

A roadmap tells you what is possible. It does not tell you what to do on Monday morning, with the staff and the software you actually have, in the order that gets you the most back for the least disruption. The document gives all twelve recommendations the same weight on the page, when some of them matter far more than others.

Some of them would give you back forty minutes a week for a couple of hours' setup. Others would give you back six hours a week and take a month to get right, because they touch three different systems and a supplier who is slow to reply. The document rarely tells you which is which, and it is not supposed to. Scoping the problem and ranking the fix are different jobs, usually done by different people, and most free diagnostics are built to do the first one well and stop there.

So the roadmap gets read once, discussed once in a meeting that runs long, and then the working week takes over again. The recommendations were not wrong. Nobody told you which one to start with, and picking wrong once is often enough to put the whole list back in the drawer.

What good ordering actually looks like

The useful version of a roadmap ranks every recommendation by two things: how many hours a week it would give back, and how much effort it takes to set up. Put those two next to each other and the order picks itself. The item that returns six hours a week for an afternoon's work goes first. The item that returns forty minutes for a month of integration goes last, or gets dropped from the list entirely, which is sometimes the more useful answer.

That is the part a diagnosis leaves out on purpose. We wrote about why in the previous post on the UK's free AI programmes: the Alan Turing Institute's own governance framework says plainly, on page 9, that it excludes cost, ROI and productivity gains from its scope. That is a different job, done properly, by people who said clearly what they were and were not doing. Someone still has to do the ranking, on your numbers, for your business, and hand you a list you can actually work down without guessing.

What we do with a roadmap you already have

You do not need a second diagnosis. If you already have one, whoever wrote it, we take the roadmap as the brief. We tell you first what each item on it is worth in hours, then we build what is on it.

That is the whole method: take the list you already have, put a number on each line, and start with whichever one pays back fastest. We are not re-scoping your business or second-guessing the person who wrote the original roadmap. We are pricing what is already on the page, then building it in the order that gives you the most hours back first.

Where to start

The HoursBack assessment does this whether you are starting from nothing or starting from somebody else's document. A 60-minute conversation, a report within two working days, and every recommendation ranked by the hours a week it would give back, at £799. We set out what an assessment costs and what drives the range separately, if you want the pricing detail first. Money back if the report does not show at least five hours a week worth reclaiming.

If you already have a roadmap, bring it to the call. It becomes the starting point, not paperwork we set to one side while we start again.

Book the assessment and find out what your list is actually worth.