You don't need more AI: you need to redesign a department
The reason almost no AI project reaches the P&L isn't the model: it's that companies gave everyone access to the tools without redesigning the processes around them. With data from Deloitte (State of AI in the Enterprise 2026), MIT NANDA (The GenAI Divide) and McKinsey (State of AI 2025) as third-party evidence of the gap, and why for an SME redesigning a single department is genuinely within reach today.
- 01
- 02 Written by the Innesti Digital team
A year ago, the owner of a small manufacturer in the provinces — thirty people — did exactly what he'd been told to do: licenses for an AI assistant for everyone, from purchasing to production. Today, if you ask him, he'll admit something uncomfortable. Everyone has access. Some use it to write emails faster. But on the P&L — margins, delivery times, hours recovered — nothing measurable has changed. The question he carries around is: did I pick the wrong tool? Almost always the answer is no. He bought the access and stopped there.
What's new: the bottleneck is no longer the model
This is the good news, and it's recent. Until not long ago, AI's limit was the quality of the model: it hallucinated, it didn't understand context, it wasn't ready for serious work. That season is over. Today's models handle the real processes of an SME, and the constraint has shifted sharply: it's no longer what AI can do, it's how the work around it is organized. Giving everyone access is the easy part — the 90% that anyone does by now. The real unlock is the 10% almost nobody does: redesigning the process. And this isn't bad news, it's the best possible news — because the lever that matters is finally under your control, not inside a lab in San Francisco.
What the data says (and it isn't ours)
The gap between access and redesign is documented by three independent sources, and it's worth reading them as third-party evidence — not as our results, but as a snapshot of the problem we solve.
- Access is now everywhere, redesign almost nowhere. According to Deloitte, “State of AI in the Enterprise” (2026), in a single year the share of workers with access to authorized AI tools went from less than 40% to about 90%. But only 30% of organizations are redesigning key processes around AI. There's the hole: almost everyone has the tool, very few have changed the work.
- And it shows on the P&L. MIT NANDA, in the study “The GenAI Divide” (2025), finds that 95% of GenAI projects produce no measurable impact on the P&L. The mechanism MIT points to isn't the quality of the model — it explicitly rules that out — but a “learning gap”: tools that neither retain feedback nor adapt to context, and companies that don't integrate them into their processes, structures, and culture.
- Those who redesign, on the other hand, gain. McKinsey (QuantumBlack), “The State of AI in 2025” shows that AI “high performers” are about 2.8-3 times more likely to have deeply redesigned their workflows instead of laying AI on top of old processes (about 55% versus about 20%). Meanwhile nearly 9 in 10 companies use AI, but fewer than 4 in 10 see an impact on results.
Three different sources, one single line: access doesn't move the numbers, redesign does. The difference between those who win and those who stay stuck isn't having bought the right AI — it's having changed the way they work.
Why redesign is genuinely within reach for an SME today
Here comes the advantage a large enterprise doesn't have. “Redesigning processes” in a giant means a multi-million-euro project, committees, months. In an SME the surface to change is small: a single department, a single workflow. You don't have to rethink the company — you have to rethink how the order desk handles confirmations, or how administration records invoices. It's a perimeter that one person with a name can embrace in a few weeks, not the ocean that paralyzes multinationals. Your size, which is usually the disadvantage, here becomes the weapon: the redesign McKinsey associates with high performers is, for you, a single-department project, not a company-wide transformation.
What to do, in practice (and it isn't buying more licenses)
If your year went like the owner's at the start, the right move isn't to add tools: it's to remove and redesign. Concretely:
- Pick just one department, the one where the work is most repetitive and rule-based — that's where redesign pays off soonest and the proof is cleanest.
- Redesign the flow, not the people. Where AI comes in, where the human checks, which step disappears and which stays. This is where the return the three sources measure — or fail to measure — lives.
- Bring people into the new process, not in front of one more tool: it's the part that decides whether it takes root. How to do it concretely, one step at a time, we cover in how to get your team to adopt AI.
- Measure in hours and in euros before you start, so you know whether you're in the 30% that redesigns or among the many who stopped at access. What to really expect is in how much AI pays off in an SME.
Where we graft in
The part pilot projects skip — redesigning the process around AI — is exactly the part we do, inside the department, with the people who work there. We don't sell you the access: you already have that, like everyone. We redesign a real flow until the new way is simply the way, and the numbers confirm it. If the year of licenses didn't move your P&L, you don't need more AI — you need to redesign a department. The AI-readiness assessment is free and tells you which one to start with; then, if it makes sense, let's talk.
The data cited (Deloitte “State of AI in the Enterprise” 2026, MIT NANDA “The GenAI Divide” 2025, McKinsey “The State of AI in 2025”) are independent sources describing the market as a whole: they are not results of Innesti Digital nor outcomes from our clients. They serve to frame the gap between access and redesign. The real return of an intervention depends on the department, the use case, and the context of the individual company.
Every resource grows out of the research we do for SMEs and the products we build ourselves: cited sources, a method we state openly, no claim you cannot check.
The sources are cited in the text. We encourage you to always check them directly at the original source.
Keep reading
More deep-dives on AI adoption in an SME.
- 01 Publishing with AI in five languages: what actually breaks, and how you catch it before the reader does This site ships in Italian, English, French, Spanish and Dutch through an AI transcreation pipeline: here is the defect register that came out of it, with names and causes. Five real classes — the French verb that, on a legal subject, turns a statement of fact into something very close to an accusation; the substantive error propagated identically across all five languages because it sat upstream of the per-locale pass; datelines written in a format none of the five languages actually uses; the missing revision marker visible to the reader (that one is already fixed and in production); and the best of the lot, the only class where the copy is right and the code is wrong — two components searching the headline for the string "AI" and never finding "IA", leaving French and Spanish with a flat title while raising no error and leaving no translation key missing. Then the controls the localization industry already runs, any of which would have caught them: the MQM taxonomy with its seven dimensions across three severity levels, the structure underneath ISO 5060:2024 and ISO 11669:2024; back-translation, which is not round-trip machine translation but an independent linguist retranslating without ever having seen the original; the three-tier glossary enforced before the text reaches a reviewer, with a named owner and a review calendar; the 10% native-reviewer sample, raised on high-risk content instead of held flat; language-aware date, number and currency formatters, and pseudolocalization. It closes with a checklist ordered by risk and the rule that cost us most to skip: a pattern defect is closed on the repository, not on the file. 10 min
- 02 How to spot a design made by AI (and the questions to ask before you sign) Three agencies, three proposals, the same site: purple gradient, blurred glass, a headline a competitor could paste verbatim. It isn't copying: it's the default setting of a generative tool, and the cause is documented. Here is how to spot it at a glance, and eight questions to put to the vendor before you sign, none of which requires technical knowledge. 9 min
- 03 Why the AI giants aren't calling your SME (and who is) Anthropic, OpenAI, Google DeepMind and Mistral sell to large enterprises through the Big Four and the big integrators, not to your company: seven dated deals (Anthropic × Deloitte with Claude to 470,000 people and 15,000 certified, October 2025; Accenture × OpenAI reselling the playbooks to clients; the forward-deployed engineering practices with Microsoft and Google/DeepMind; PwC and KPMG × Anthropic; Capgemini × Mistral) show the channel is the reseller, not the SME. The pricing keeps you out too: Claude's Enterprise plan starts at 20 seats, and the forward-deployed-engineer model — roughly $5.5 billion combined spend by Anthropic and OpenAI in May 2026 — is by explicit admission reserved for "marquee accounts", not the mid-market (Forbes, PYMNTS). From the SME side the gap shows: only 14% of small businesses have fully integrated AI, held back by privacy (50%), technical expertise (49%), tool selection (48%) and training (73%) — an implementation gap, not one of awareness (Goldman Sachs). Our reading: the giants feed large enterprises via integrators and embedded engineers, nobody productizes hands-on implementation for the SME — that's the seat an "innesto" implementation occupies, forward-deployed at the scale of a small company. 10 min
From theory to your business. We graft AI in.
Want to know which department to start from in your company? The free assessment gives you a first answer in two minutes — then, if it makes sense, we talk.
- 32
- Operational AI guides, free and no sign-up
- 5
- Languages localized across the EU