AI adoption in SMEs: 5 key steps

AI adoption in SMEs: 5 key steps

AI adoption in an SME happens in five steps: an inventory of existing usage, the choice of one to three measurable use cases, a minimal set of rules, a pilot phase with training, and then a decision to scale based on the numbers. Allow three to six months to move from individual use to team use.

Most published methods start with "identify use cases". That skips a step. In a company of 20 or 80 people, AI is already there: employees use chat assistants on personal accounts, and management does not know what for or with which data. Adopting AI starts with taking back control of that existing usage before creating new ones. This article covers each step with its deliverable, its duration and, above all, its exit criterion: what must be true before moving on to the next one. It complements our guide to AI in business for SMEs, which covers the overall strategy.

Where French SMEs stand in 2026

Only a minority of SMEs report using AI, and the gap with large companies remains wide. According to the ICT survey published by Insee, the French national statistics office, in 2026 (Insee Première no. 2120), 18% of companies with 10 or more employees reported using at least one AI technology in 2025, up from 10% a year earlier. The rate drops to 15% for companies with 10 to 49 employees, rises to 31% for 50 to 249 employees, and reaches 58% above 250.

The reasons given by companies that do not use AI are worth reading for anyone planning an adoption effort:

• 71% see no use for AI in their business;
• 54% cite a lack of expertise (53% among companies with 10 to 49 employees);
• 38% mention concerns about data protection;
• 33% find the costs too high.

Two lessons follow. The main barrier is neither technical nor financial: it is the lack of a concrete use case. The second is a skills issue, which means training. An adoption method that starts by picking a tool misses both.

Another useful figure from the same survey: 80% of companies using AI rely on off-the-shelf commercial software. For an SME, adopting AI almost never means building something. It means using existing tools properly.

Step 1: take stock of actual usage

The first step is to find out who already uses AI, for what, and with which data, before deciding anything. Without this inventory, you may launch a pilot while three colleagues have already found more relevant uses, or overlook a risk involving customer data pasted into a free tool.

In practice, over one to two weeks:

• an anonymous ten-question survey sent to the whole team (tools used, frequency, tasks, type of data entered);
• three or four 20-minute interviews with the most active users;
• a list of the repetitive tasks that take the most time, team by team.

Anonymity matters. If employees fear being penalised for using a free assistant, they will say nothing and you will only get part of the picture. Make it clear from the start that the goal is to build a framework, not to find culprits.

To place your company, our AI maturity assessment grid lets you position yourself on five levels in about an hour. If you prefer an outside view, an AI audit for SMEs produces the same diagnosis along with a list of costed use cases.

Exit criterion: you have a written list of existing uses and at least five candidate tasks, each with an estimate of time spent per week.

Step 2: choose one to three measurable use cases

A good starting use case is a frequent, time-consuming, low-risk task whose output is easy to check. Everything else can wait. Trying to cover everything from day one is the most common reason adoption efforts run out of steam.

Four criteria are enough to sort candidate tasks:

Examples that often pass this filter: drafting first versions of replies to common customer requests, summarising meeting notes, preparing product sheets, sorting applications for a job posting (with care, since recruitment is a sensitive area under the AI Act). Conversely, avoid as a first use case anything that directly commits the company without review: legal advice, final pricing, decisions about individuals.

For each use case you keep, measure the baseline before touching the tool: average time per task, monthly volume, error or rework rate if you have it. Without this "before" figure, no calculation of AI ROI for an SME will be credible at step 5. The glossary explains what we mean by AI ROI.

Exit criterion: one to three use cases selected, each with a named owner, a measured baseline and a realistic target (for example, halving the time needed to draft a standard reply).

Step 3: set a simple framework before scaling

Before extending use, you need three things: an approved tool with a business account, written rules on data, and a named point of contact. This is the step most often skipped, and the one that prevents the most problems later.

The tool is chosen based on the use cases, not the other way round. Check the contractual terms of the business version: whether your data is used to train models, where it is hosted, how accounts are managed. A free plan used on a personal basis generally does not offer the same guarantees.

The rules fit on two pages. They answer a few specific questions:

• which data may be entered (public data, non-sensitive internal documents) and which is forbidden (customer personal data, health data, information covered by a confidentiality agreement);
• which tools are allowed;
• who reviews what before it is sent outside the company;
• who to contact with a question or an incident.

Our AI policy template for businesses gives you a base to adapt. The point of contact does not need a technical profile: you need someone who knows the business, answers questions and reports problems.

This framework also has a regulatory side. Since 2 February 2025, Article 4 of Regulation (EU) 2024/1689, known as the AI Act, requires companies deploying AI systems to take measures to ensure a sufficient level of AI literacy among their staff. Our article on AI Act Article 4 and AI literacy explains what this means in practice for an SME.

Exit criterion: a business tool deployed for the pilot team, a rules document shared and read, a named point of contact.

Step 4: run a pilot and train the team involved

The pilot lasts four to eight weeks, with a single team, a training session at the start and a fifteen-minute weekly check-in. Its purpose is to confirm that the gain estimated in step 2 actually exists under real working conditions.

Training is not optional. Lack of expertise is the second reason given by companies that do not use AI, and a tool handed out without support almost always ends the same way: two or three people adopt it, the rest drop it after ten days. Useful training at this stage is short and applied to the chosen use cases: how to write a clear request, how to check the output, which typical errors to watch for (including AI hallucinations).

During the pilot, track few indicators, but track them regularly:

• time spent per task, compared with the baseline;
• actual usage rate (how many team members use the tool each week);
• rework rate: how many outputs needed substantial correction;
• incidents or questions reported to the point of contact.

The weekly check-in is mainly for collecting good practices and sharing them. A prompt that works well for one person should become a template for the whole team. This is where AI change management really happens: teams adopt what they have seen work for a colleague, rarely what was presented to them in a meeting.

Exit criterion: at least half of the pilot team uses the tool every week, and the measured time saving is positive on at least one use case.

Step 5: measure, decide, then scale or stop

At the end of the pilot, management makes an explicit decision for each use case: scale, adjust or stop. Stopping is not a failure. A use case that shows no measurable gain after eight weeks is unlikely to show one after six months.

To decide, compare the pilot figures with the baseline, then weigh the gain against the full cost: licences, training time, time spent by the point of contact. Our article on how much AI costs an SME in 2026 lists the items to include. A dashboard with three or four key performance indicators is more than enough at this stage.

If the decision is to scale, go back to step 2 for the next teams, with one advantage: you now have a framework, a point of contact, prompt templates and internal figures to make the case. The second wave usually moves faster than the first.

What to avoid at this point: rolling out to the whole company at once because the pilot went well. Each department has its own tasks, constraints and reluctance. Three well-prepared successive extensions work better than a company-wide rollout nobody follows.

Exit criterion: a written decision for each use case, a gain calculation weighed against cost, and a timeline for the next wave.

The mistakes that derail adoption

Most adoption efforts that fail do not stumble on technology but on organisation. These are the situations we see most often in SMEs:

• Starting with the tool. Buying licences for the whole team, then looking for something to use them for. The usual result: low usage after two months and spending that is hard to justify.
• Measuring nothing beforehand. Without a baseline, you cannot prove any gain, and the project loses its backing at the first budget squeeze.
• Banning without offering an alternative. A blanket ban does not make usage disappear, it makes it invisible.
• Leaving everything to one enthusiast. If that person leaves or changes role, everything stops. The point of contact must document what they do.
• Neglecting training. A tool without training stays in the hands of a few converts.

Frequently asked questions

How long does it take to adopt AI in an SME?

Allow three to six months for a first full cycle: one to two weeks for the inventory, two to three weeks to choose use cases and set the framework, four to eight weeks of pilot, then the decision. Extending to other departments then takes several more months depending on company size.

Do you need a big budget to get started?

No. Most SMEs start with subscription-based commercial tools and a short training course. The largest cost is often the internal time spent on the pilot and on training, not software.

Which department should go first?

Start with the department where a repetitive, frequent and easily checked task takes the most time. That is often customer service, sales administration or marketing. Avoid starting with sensitive topics such as recruitment or decisions about individuals.

Should you appoint an AI point of contact?

Yes, even in a small organisation. It does not have to be a full-time role: a few hours a week are often enough at first. Their job is to answer questions, keep the rules up to date and report problems.

Is AI training for employees mandatory?

Article 4 of Regulation (EU) 2024/1689 requires companies deploying AI systems to take measures to ensure a sufficient level of AI literacy among their staff. The text does not set a specific format, but training suited to actual usage is the simplest way to demonstrate it.

What if the pilot shows no results?

Work out why before drawing conclusions: wrong use case, unsuitable tool, insufficient training or an imprecise baseline. If the problem is the use case, stop it and test the next one on your list. A stopped pilot teaches you something, as long as you document the reasons.

How GrowthPerf supports AI adoption

GrowthPerf is a Qualiopi-certified training provider that supports SMEs and non-profits at the stages where they most often get stuck: choosing use cases, setting a usage framework and training teams. Our AI for business training covers AI literacy and framing, while the operational AI training works directly on your teams' tasks during the pilot phase. These courses can be partly funded by your OPCO (the French sector training fund), as explained in our article on funding AI training through your OPCO.

For the bigger picture, see our complete guide to AI in business for SMEs. And if you want to build your adoption plan on solid ground, start with a 30-minute call with us to review your current usage and your first use cases.