AI strategy consultancy: your automation roadmap, priced

• Every process, foundWe watch how the work actually happens, including the parts nobody wrote down and the workaround somebody built in a spreadsheet.
• A number on each oneHours at a real loaded cost, plus what errors cost where errors cost money. Your figures, so you can check the arithmetic.
• The build orderWhat has to be true before each item pays. Data first, then the processes that feed on it. The part most roadmaps skip.
• Build or buy, settled per lineSome of it is a subscription you already pay for and have not switched on. We say so, then switch it on.
• A fixed price on every itemEach build quoted before it starts. No day rates, no surprises.
• A document you ownPlain English and your own figures, yours to keep and hand to anyone. We are ready to start item one the week you sign it off.

1. 01WatchInside the business, seeing how the work actually happens rather than how the manual says it does.
2. 02Cost and orderEvery process priced in your own figures and sequenced by what has to be true first.
3. 03BuildItem one built at its fixed price, in your accounts and under your name.
4. 04RunLaunched, monitored and reported, with the next item already queued behind it.

• Operational workflows mapped across every company department
• Financial returns calculated for each automation option
• Priorities ranked by return and effort
• Detailed implementation roadmap published with target completion dates
• Software stack evaluated to identify integration gap opportunities
• Data security risks reviewed before launching automations
• Phased rollout plan created to prevent operational disruption
• Executive presentation delivered outlining potential annual cost savings
• Clear targets established for every proposed automation
• Vendor software costs benchmarked against custom automation builds
• Cross-department dependencies identified before starting technical builds
• Process inefficiency costs calculated using real payroll data
• Quarterly strategy reviews conducted to realign automation targets
• Implementation roadmap updated dynamically as new systems launch

Illustrations of the tools in use, drawn for this page for an example business, Marlow & Finch. Every figure in them is an example, not a client's data, and any person in them is generated. Tap a picture to open it full size.

Do we have to build with you afterwards?

No. The roadmap is a paid deliverable at a fixed price quoted before we start, and you own it outright: hand it to your own team or another supplier if you prefer. Some lines on it will be a subscription you already pay for, and we say so rather than quoting for a build. The reason to have us build it is that the team that costed every item can start the first one the week you sign off.

How long does it take?

One to three weeks depending on the size of the firm, and most of that is spent watching how the work actually happens rather than in workshops. The gap between the documented process and the real one is where the opportunity sits, and you only find it by looking. The roadmap lands as a document you can act on the day you receive it.

How do you decide the order?

Dependency first, then value. Automating a process that feeds on data nobody trusts produces the same wrong answers faster, so the roadmap puts the fix ahead of the exciting item. Every line carries a number in your own figures, which makes the order arithmetic rather than opinion.

What if we already know what we want to automate first?

Then we start there, at a fixed price, and the roadmap comes with it. The obvious build gets quoted and started; the map of everything else tells you what to do second and third. Where there are twenty candidates and two departments each certain theirs is the priority, the roadmap is what settles it.

What do you need from us?

The brief, the brand and the access: what the business is trying to achieve, how you present yourselves, and a login to the systems the work runs through. A few hours of your people's time while we watch how the work actually happens. Everything after that is us.

• Your whole stack, inside ClaudeWires every tool your team uses into one Claude window, so the CRM, inbox, calendar, files and accounts do what you type. The flagship, and nobody we audited sells it.Open page
• Team training and upskillingTrains your team on your own systems, with automations shipped in the room, a playbook in your wiki and a weekly clinic to keep it moving.Open page
• Support and maintenanceWatches every automation on every run, patches it the day a system underneath it changes, and reports what it did each month.Open page