Crank Labs Book a 15-min call

Strategy, 10 min read, by the Crank Labs team,

AI Strategy Roadmap for SMEs: A Practical 90-Day Plan

A week-by-week AI strategy roadmap for businesses of 20 to 500 people: use-case scoring, data readiness checklist, governance, training and how to measure ROI.

The short answer

An AI strategy roadmap for an SME is a short, sequenced plan that takes a business from scattered AI ideas to one or two working systems with measured results. A practical version runs about 90 days: two weeks to diagnose, two to score and choose use cases, six to design, build and pilot, and the rest to roll out, train staff, set governance and decide what comes next.

Most small and mid-sized businesses do not need a thick AI strategy document. They need an AI strategy roadmap that fits on one page, names a first project, and gets something working inside a quarter. This guide sets out a practical 90-day AI plan for a business of 20 to 500 people: what to do each week, how to score use cases, what to check about your data and systems, how to govern and train, and how to measure the return using your own numbers.

What is an AI strategy roadmap, and what is it not?

An AI strategy roadmap answers four questions: which business problems AI will address first, in what order, who owns each one, and how you will know it worked. It is tied to revenue, cost or time saved, not to a list of tools.

It is not:

If your business needs deeper change to how sales, operations or finance run before AI can help, read our business transformation framework alongside this plan.

Who should own the AI roadmap?

A 90-day AI implementation plan needs a small, named team. In most SMEs that means:

Budget roughly a few hours a week from the process owner and champion. If you cannot free that time, postpone the roadmap. An AI adoption strategy without operational owners stalls quietly.

What does a 90-day AI plan look like week by week?

WeeksPhaseMain activitiesOutput
1 to 2DiagnoseInterviews, process walk-throughs, collect sample data, list every repetitive taskLong list of candidate use cases with rough volumes
3 to 4Score and selectScore candidates on value, effort, data readiness and risk; take baselinesOne or two chosen use cases, written success measures
5 to 6Design and prepareTarget process, approval points, integration and access plan, data clean-upSigned-off design and readiness checklist
7 to 10Build and pilotBuild on real data, test on past cases, pilot with a small group, daily reviewsWorking system used by the pilot group
11 to 12Roll out and trainExtend to the full team, role-based training, governance rules in placeSystem in everyday use with a runbook
13Review and choose nextCompare against baseline, decide to extend, adjust or stop, pick the next use caseResults review and updated roadmap

The timeline is realistic because the first project is narrow. A focused agent or workflow, such as WhatsApp lead response or invoice entry, is typically live in two to four weeks of build. The rest of the 90 days goes on choosing well, preparing properly and making the change stick.

Weeks 1 to 2: how do you find the right AI use cases?

Do not start by asking "where can we use AI?". Start by asking where time and money leak. Three activities give you most of what you need.

Walk the process

Sit with the people who handle enquiries, orders, invoices, approvals and reports. Ask them to show you, not tell you. Note every place where information is re-typed, copied between systems, chased by phone or waits in someone's inbox.

Collect real samples

Gather a few weeks of enquiries, a batch of invoices, CRM exports and the spreadsheets people actually use. These show volumes, formats and edge cases, and they tell you early whether the data is usable.

Build the long list

Write each candidate as a sentence: "Supplier invoices arriving by email are keyed into the accounting software by two people every day." Add rough weekly volume and who does it. A long list for a mid-sized business usually covers enquiry handling, quoting, follow-ups, document processing, scheduling, reporting and internal requests.

Weeks 3 to 4: how do you score and prioritise AI use cases?

Score every candidate from 1 to 5 on four factors. The descriptions below keep scoring consistent between different people.

FactorScore 1Score 3Score 5
ValueRare task, little time or revenue at stakeWeekly task, noticeable time or some revenue at stakeDaily, high-volume task or directly tied to lost revenue
Effort (reverse scored)Many systems, custom development, unclear processTwo or three systems, some integration workOne or two systems with good access, clear process
Data readinessData scattered, inconsistent or mostly in people's headsData exists but needs cleaning or a standard formatData is digital, consistent and accessible today
Risk (reverse scored)Errors would hurt customers, patients or finances and are hard to catchErrors are recoverable with a review stepErrors are low impact and easy to spot

Because effort and risk are reverse scored, a higher total is always better. Add the four scores. Then apply two rules before ranking: any use case scoring 1 on data readiness waits until the data is fixed, and any use case scoring 1 on risk needs a mandatory human approval step built into the design.

Here is an illustrative scoring for a generic 150-person kitchen and interior manufacturer:

Candidate use caseValueEffortData readinessRiskTotal
WhatsApp enquiry response and showroom booking544417
Supplier invoice entry into the accounting software445316
Weekly production status report for management333514
Demand forecasting for raw materials421310

In this example the enquiry agent goes first, invoice entry second, and forecasting waits because the data is not ready. That is a typical pattern: the exciting use case is rarely the right first one. Before the build starts, take a baseline for the chosen use cases, such as average response time to an enquiry or hours spent on invoice entry each week.

Is your data and integration ready? A checklist

Run this checklist in weeks 5 and 6. Every "no" is either a task to fix before the build or a reason to change the design.

Weeks 5 to 10: how do you design, build and pilot?

The design should be a short written description of the new process, step by step, including where the AI acts, where it hands to a person and who approves what. Keep it to a page or two so the process owner can actually check it.

During the build, insist on three habits:

  1. Build on real data. Test against past enquiries or invoices with known outcomes before any customer or ledger sees the result.
  2. Start supervised. In the pilot, the AI drafts and a person approves. Remove approvals only where the record shows the AI is reliably right and mistakes would be cheap.
  3. Review daily, then weekly. Short reviews of what the AI did, what it got wrong and what it handed over. Fix rules and prompts as you go.

Our pages on AI automation for invoices, approvals and reporting and AI agents for WhatsApp, voice and email describe what typical builds involve.

Weeks 11 to 13: how do you handle governance and team training?

Governance that fits an SME

You do not need a committee. You need a few written rules that everyone knows:

Training by role

Training is where adoption is won. A system that staff do not trust gets worked around within weeks.

How do you measure AI ROI without making up numbers?

The only numbers that matter are your own. Measure before and after, using the same method, on the same process.

MeasureHow to take the baselineHow to measure after
Staff time on the taskTime a sample of tasks and multiply by weekly volumeTime the remaining manual work, including reviews and corrections
Response time to enquiriesTimestamps of first reply from WhatsApp or email historySame timestamps from the system logs
Missed or unanswered enquiriesCount enquiries with no reply within your target timeSame count after launch
Errors and reworkCount corrections in a sample periodCount corrections in the same length of period
Cycle timeDays from invoice receipt to posting, or from enquiry to quoteSame measure after launch
ConversionShare of enquiries that became bookings or orders in a sample monthSame calculation, compared month to month

Then put it in plain money terms: hours saved per month multiplied by the loaded cost of those hours, plus any extra revenue from enquiries that would otherwise have been missed, minus the build fee spread over a sensible period and the monthly running costs. If the result is clearly positive, extend. If it is marginal, adjust. If it is negative after tuning, stop and move to the next use case. For what drives the cost side, see our guide to AI automation costs for small businesses.

What are the most common mistakes in an AI adoption strategy?

Accounting teams in particular tend to see quick, measurable results from document-heavy workflows. Our post on AI bookkeeping automation for accounting firms walks through that use case.

What should you do next?

Block two hours this week with your process owners and build the long list. Score it with the table above, and you will already have a draft AI strategy roadmap. If you want an outside view, Crank Labs runs a free diagnosis session that maps how your leads, operations and finance flow and identifies the first use case worth building. Read how we approach AI consulting from roadmap to rollout, check our guide on what AI consulting involves, or book a free 15-minute call.

Frequently asked questions

Is 90 days realistic for a first AI project in a small business?

Yes, if the first project is narrow. One workflow with clear volume, such as enquiry response or invoice entry, can be designed, built, piloted and rolled out within a quarter. The build itself typically takes two to four weeks. What makes timelines slip is choosing a use case with poor data or no operational owner.

Do we need a Chief AI Officer or a data team?

Not for most businesses of 20 to 500 people. You need an executive sponsor, a process owner for each use case, a champion from the team and a delivery partner, whether in-house or external. Specialist roles make sense later, once several AI systems are running and the volume of work justifies them.

How often should an AI roadmap be updated?

Review it at the end of every project and at least once a quarter. Each completed project teaches you about your data, your systems and how your team adopts change, and that should reshape the order of what comes next. A roadmap that stays fixed for a year has usually stopped being used.

Should we build our own AI tools or buy off-the-shelf software?

Use off-the-shelf features where they already exist in software you pay for. Build when the value depends on connecting several of your systems, on your own rules and data, or on a workflow no product covers well. Many SMEs end up with a mix: bought tools at the edges and custom integrations in the middle.

Book a callWhatsApp