Adoption & Conduite du changement

AI Adoption in SMEs: Why Activated Licenses Measure Nothing

ChatGPT or Copilot licenses bought but barely used: why SMEs confuse deployment with adoption, and how to measure real AI usage instead of seat counts.

Only 11% of French SMEs currently have advanced AI usage (MIT Sloan Management Review). That number has less to do with a lack of tools than with what happens between buying the licenses and the third month of use.

In my work with SMEs and mid-sized companies, I see the same pattern often. Leadership buys twenty ChatGPT Team or Copilot licenses, runs a one-hour training session, then closes the topic and calls the project done. Three months later, five people still use the tool daily, and the other fifteen have quietly gone back to their old habits without anyone flagging it in a meeting.

That drop-off almost never shows up on a dashboard, because the metric being tracked is still the number of activated licenses, not actual usage frequency. An activated license measures deployment, not adoption, and the two get confused constantly in board updates. Between 35 and 45% of work time in SMEs involves tasks that could be automated (McKinsey, 2024), a potential that most companies never capture, because nobody tracks how many tasks are actually delegated to the tool, how much time is genuinely freed up, or who dropped off after the first week. Without that tracking, the license spend becomes a dormant cost nobody questions until renewal time.

This is exactly what the adoption stage addresses, usually in weeks 4 through 6, distinct from the initial rollout and designed as sustained support rather than a one-off training session. It is also the third of my four service pillars, change management, which is never limited to a launch event but tracks usage over several weeks before considering a tool truly adopted. Field results from 47 SMEs supported near Bordeaux in 2024 show an 89% success rate with a structured adoption method of this kind, against 27% when adoption is left to spontaneous team initiative.

An SME that wants to know whether its AI actually works should measure usage frequency and time recovered, not the number of active accounts. That gap between deployment and adoption is what separates lasting transformation from a forgotten subscription. If you'd like to discuss it, get in touch.

Frequently asked questions

Why isn't the number of activated licenses enough to measure AI adoption?

An activated license measures deployment, not usage. It shows an account exists, not that it's used weekly. This is a field observation from engagements run through nachnouchi.com, not a sourced external study.

What percentage of French SMEs currently have advanced AI usage?

Only 11% of French SMEs have advanced AI usage today (MIT Sloan Management Review).

How much work time in SMEs could be automated by AI?

Between 35 and 45% of work time in SMEs involves tasks that could be automated (McKinsey, 2024), a potential rarely tracked once licenses are purchased.

What is the adoption stage of an AI rollout?

It is the fourth stage of the method, positioned in weeks 4 through 6, dedicated to sustained team upskilling and distinct from the initial rollout of the tools.

What is the success rate of structured AI adoption compared to spontaneous adoption?

Field results from 47 SMEs supported near Bordeaux in 2024 show an 89% success rate with a structured adoption method, against 27% when adoption is left to spontaneous team initiative.

How long does it take to know if AI adoption has succeeded?

Usage needs to be measured over several weeks, not the day after launch. This is a field observation from engagements run through nachnouchi.com, not a sourced external study.

How can a company tell if a team has genuinely adopted an AI tool?

By tracking three concrete indicators: actual usage frequency, the number of tasks genuinely delegated to the tool, and time recovered as measured rather than self-reported.

What role does change management play in an SME AI project?

It is the third of my four service pillars. It is never limited to a launch event, but tracks real usage over time before considering a tool truly adopted.

Back to articles