How we build an AI roadmap for a small or mid-sized business

Short answer

An AI roadmap is a short, priced list of decisions: which work AI takes on first, what data it needs, who approves what, and what it costs. We build it in two steps. The automated growth audit reads your site, AI visibility, funnel, stack and competitors and writes a 30-day plan; with Head of Digital, the full deep audit in the setup maps one area of your business and prices the three flows with the best return. A 90-day plan then switches them on one at a time, each measured against the numbers agreed on day one.

What goes in

A roadmap is only as good as what it starts from. We ask for five things, most of which you already have.

  • Your goals for the next 12 months. Revenue, margin, hours, or a launch date. One or two, with a number.
  • Where the hours go. The repeatable computer work in each team: quotes, follow-ups, reports, scheduling, price updates.
  • Your systems and data. CRM, accounting, ERP, field service, store and inbox: what connects, what is clean enough to use as is, and what is not.
  • Your rules. Who approves what today, and what must never happen without a person.
  • Your constraints. Budget, languages, privacy law such as Québec’s Law 25, and where your data has to be hosted.

What comes out

At the end of the audit week you get a written report and a 60-minute walkthrough. It holds a map of the area, the three highest-return flows with hours, cost and the module behind each, a data checklist, the 90-day plan and the first entries in your decision log. You keep all of it whether or not you continue.

The 90-day plan

The plan moves one flow at a time, so every step has a baseline and a result you can compare.

  • Days 1 to 30. The first flow goes live as a pilot. Systems are connected read-only first. Every draft waits for approval, and nothing sends before you approve the first real ones.
  • Days 31 to 60. We measure against the baseline, tune the settings and switch on the second flow. Approvals are loosened only where the record shows it is safe.
  • Days 61 to 90. The third flow, or the data work it depends on. At day 90 we review each flow: keep, change or stop, and we write the next 90 days.

How decisions are recorded

Every decision on the roadmap is written down in the same short form, so you can see later why it was made and change it on purpose. Decisions sit in your Brain next to the rules your agents follow. Every action an agent takes is logged with who approved it. For pricing, margin and forecast decisions made on Allometry, the Decision OS, each entry is sealed to the one before it, so a change after the fact shows.

A decision record (sample format)
Question
Do quote follow-ups send on their own after day 7?
Options
Always approve; send on their own within set limits; stop at day 7
Numbers
Approval and edit rates from the first 30 days
Decided by
The owner, with the sales lead
Review on
Day 60, or sooner if a customer complains

What it costs

The prices are published and in US dollars, before taxes.

First step$499The automated growth audit, bought online. Credited in full to any plan you start within 30 days; the full deep audit is part of Head of Digital setup.
Then$6,000/moHead of Digital: all six departments with a person on call. $2,500 setup, waived with a 12-month commitment. 3-month minimum.

An audit that covers several departments at once is scoped on a call.

What we leave off a roadmap

AI for its own sake. Projects without an owner or a number. Anything that needs your data to train shared models. Plans that only work by cutting people: we plan for capacity, and your team decides what to do with the hours that come back.

How long does it take to build an AI roadmap?

One week for the first area: a kickoff call on day 1, the work on days 2 to 4 and a walkthrough on day 5. A roadmap across several departments is scoped on a call.

Do we need clean data before we start?

No. The audit checks which data is usable as is and what needs cleaning. Cleaning becomes part of the plan only where a flow depends on it.

Who builds the roadmap?

Taylor Gendron, the founder, working as the forward-deployed engineer. The same person configures the modules once you start, so nothing is lost between the plan and the work.

What if we stop after the audit?

You keep the report, the plan and the decision log. The credit toward Head of Digital only applies if you start within the window.

Does the roadmap replace the tools we already use?

Usually not. It starts from your current stack and connects to it through official APIs. Where a module can replace a tool, the roadmap shows the cost both ways.

Is our data safe during the audit?

Access is read-only and nothing in your systems changes. Your data is never used to train shared models, and client data is hosted in North America, close to you (Toronto by default, your own US instance on request).

Start your roadmap with one area