Signature thesis

The AI productivity paradox: why most small-business AI tools sit unused

Small businesses are buying AI faster than ever and getting little measurable value from it. Here is the evidence behind the paradox, why it happens even when the technology works, and the process-first method that closes the gap.

Founder and lead engineer

Published
Updated
Reading time
9 min read

What is the AI productivity paradox?

The AI productivity paradox is the gap between how much AI businesses buy and how little measurable productivity they get from it. Companies keep adopting AI tools, but many see no measurable improvement in output, cost or profit, because they bolt new technology onto old workflows and leave the work itself unchanged.

It is the 2020s rerun of a famous economic puzzle. In 1987, Nobel laureate Robert Solow remarked that “you can see the computer age everywhere but in the productivity statistics.” Businesses were pouring money into computers, and the productivity data refused to move. Economists named it the productivity paradox. The gains did come, but only after firms redesigned how work flowed around the new machines, a lag that took years.

AI is following the same pattern. The tools are capable and adoption is real, but for most businesses the results are missing, and the model is rarely the reason.

The evidence on AI adoption and returns

Three sets of published numbers tell the story: small-business AI adoption is climbing fast, much of the software businesses buy goes unused, and most AI pilots never reach the bottom line.

8.8%

of small businesses used AI by August 2025, up from 6.3% six months earlier.

U.S. Census Bureau, Business Trends and Outlook Survey

~50%

of all software licenses go unused.

Zylo, SaaS Statistics

95%

of enterprise generative AI pilots delivered no measurable return.

MIT Project NANDA, The GenAI Divide (2025)

~6%

of organizations can attribute meaningful EBIT impact to AI.

McKinsey, The State of AI

Small-business AI adoption is rising

The U.S. Census Bureau’s Business Trends and Outlook Survey found AI use among small businesses climbed to 8.8% by August 2025, up from 6.3% six months earlier.

Much of the software that gets bought goes unused

The problem predates AI. Zylo reports that roughly 50% of all software licenses go unused and 53% of SaaS applications are underused or not used at all, and CIO Dive reported average software waste of $18M in a single year. Businesses are buying AI the same way they bought the shelfware before it.

Even when AI is deployed, it rarely reaches the bottom line

In August 2025, MIT’s Project NANDA published The GenAI Divide, drawing on more than 300 enterprise deployments. The headline: 95% of enterprise generative AI pilots delivered no measurable return. MIT attributed the failures mainly to how organizations manage adoption, and less to the quality of the models. McKinsey lands in the same place: only around 6% of organizations can attribute meaningful EBIT impact to AI.

Taken together, adoption is up, usage lags and returns are rare. Between licenses that are never opened, pilots that never ship and deployments that never touch the P&L, the share of AI spend producing measurable value is small.

Why does AI fail even when the technology works?

AI fails most often because it is dropped onto a broken or unexamined process. A tool can only amplify the workflow it is given, so when you automate a messy, redundant or poorly understood process, you get the same mess, running faster.

Economists Erik Brynjolfsson, Daniel Rock and Chad Syverson formalized this as the Productivity J-Curve (NBER working paper, American Economic Association). General-purpose technologies like AI pay off only after a wave of complementary investment: redesigned processes, new workflows, retrained people and restructured roles. That investment is largely intangible and invisible on a balance sheet, so for a while the spending looks like pure cost. Productivity dips before it climbs. Many buyers quit during the dip and conclude that “AI doesn’t work for us”, when the real problem was buying a tool and changing nothing else.

The bottleneck is usually the process around the tool.

The data backs this up. McKinsey found that 55% of AI high performers fundamentally reworked their processes when deploying AI, nearly three times the rate of everyone else. MIT found that buying from focused vendors and partnering on the workflow succeeds about 67% of the time, while internal builds succeed at roughly a third of that rate. The common thread is whether anyone redesigned the work.

The framework: Process-Driven Adoption

Process-Driven Adoption is a method for adopting AI in which you map and redesign the underlying business process before selecting any tool, so technology is matched to an improved workflow. The usual buying habit runs the other way: the tool comes first and the business bends around it.

Many businesses do the reverse, which we call Tool-First Adoption: see a demo, buy the tool, hope it sticks. That is a quick route into the 95%. Here are the two approaches in one picture.

ProductivityTime after adoptionTool first: flatthe dip (intangible investment)Process driven: gains
Tool-First Adoption: buy the tool and bolt it onto the old process. Productivity stays flat because habits do not change.Process-Driven Adoption: map, redesign, match the tool, then embed and measure. A short dip while you reinvest, then the gains show up.
Step 1

Map the real process

Write down the actual path work takes, including the workarounds, the re-keying and the “I just handle that part myself.” You cannot automate what you have not honestly described.
Step 2

Redesign before you buy

Remove steps that should not exist, merge the ones that fragmented over time, fix the handoffs. Often the biggest win here costs nothing and involves no AI at all.
Step 3

Match the tool to the step

Only now does technology enter, against a specific improved step. It might be a simple automation, an agent, a custom build or nothing at all.
Step 4

Embed and measure

Train the people, route the work through the new path, and tie the result to a number on the P&L. If you cannot measure it, you are back in the 95%.

Redesign the process first, and the right AI will amplify it.

Process-Driven Adoption deliberately does the slow part first and the fast part second. It front-loads the cheap, unglamorous work of understanding and redesign, so the expensive work of tooling has something real to amplify. For the step-by-step method, including how to choose between an automation, an agent and a custom build, see Process-First AI Adoption, and for the mapping itself, how to map a process before you automate it.

What Process-Driven Adoption looks like in practice

In practice, the same tool can produce opposite results depending on whether the process was redesigned first. Take a common small-business purchase: an AI receptionist or chatbot for a service business such as a dental practice, a clinic or a trades firm.

Tool first

The same problems, faster

Buy the chatbot and point it at the existing phone-and-paper intake. It answers faster, but inside the same broken funnel: double bookings, no-show chaos, missed follow-ups. Calls are handled quicker; the practice runs no better, and the subscription becomes one more line item nobody can defend.
Process driven

The real leak fixed

Map how a patient goes from “calls in” to “shows up and pays.” The real leak is that no-show recovery and follow-up are nobody’s job. Redesign the flow so recovery is a defined step, then match a tool to it. The result shows up in the schedule and the revenue, where it can be measured.

This is an illustration and does not describe a client. The tool is the same in both cases. The only difference is whether the process was redesigned first. If booking is your bottleneck, see how we approach scheduling and reception agents.

How to escape the AI productivity paradox

To escape the AI productivity paradox, redesign the process before you shop for tools. Find where work actually breaks down, fix the workflow first, then match AI to the specific step that needs it and measure the result against a number on your P&L.

A short checklist to put it to work this quarter:

  • Pick one painful, repetitive workflow to start with.
  • Document it honestly, workarounds and all, before naming a single tool.
  • Ask what you would remove or simplify with no AI at all. Bank that win first.
  • Only then choose a tool, matched to the redesigned step and chosen on fit.
  • Attach one metric, such as hours reclaimed, response time or revenue recovered, and watch it.
  • Expect a short dip before the climb. That dip is the J-curve at work. Do not quit in the trough.

You can run that checklist yourself. If you would rather have help, there are two ways in. When you already know the workflow, book a free call or send a brief for a fixed-price quote within 2 business days; we can build it as a done-for-you agent on Qoren from $2,000 per workflow, or as a custom agent on your own stack. When you are not sure where to start, the AI consulting and audit does the mapping and the ranking with you, and the roadmap is yours to keep whoever builds it.

FAQ

Questions

Why do most small businesses fail to get value from AI?

Because they adopt tool first: they buy AI and attach it to a workflow nobody has examined. A tool amplifies whatever process it is given, so a broken process just runs faster. MIT's Project NANDA found 95% of enterprise generative AI pilots delivered no measurable return, and traced it mainly to mismanaged adoption.

What is the productivity paradox?

It is the gap between heavy investment in a new technology and the absence of measurable productivity gains from it. Economist Robert Solow named it in 1987 for computers; the gains arrived only after firms redesigned work around the technology. AI is repeating the pattern.

What is Process-Driven Adoption?

Process-Driven Adoption is a method for adopting AI by mapping and redesigning the underlying business process before choosing any tool, so technology is matched to an improved workflow. Its four steps are map, redesign, match, then embed and measure.

Is the problem the AI tools or how we use them?

Mostly how they are used. McKinsey found that 55% of AI high performers fundamentally reworked their processes when deploying AI, nearly three times the rate of other firms. Process redesign matters more than the choice of tool.

Do I need to redesign my whole business to use AI?

No. Start with one painful, repetitive workflow. Map it honestly, fix what is broken without AI first, then match a single tool to a single improved step and measure the result. Scope small and sequence it right.

Should I start with an AI audit or go straight to a build?

If you already know which workflow costs your team the most time, go straight to a free call and a fixed-price quote within 2 business days. If you know AI should help but not yet where, the AI consulting and audit (€1,200 to €1,800) maps your workflows and ranks them by return before you spend on a build.

Sources

  1. 01AI Use at U.S. Businesses, U.S. Census Bureau
  2. 02MIT report: 95% of generative AI pilots at companies are failing, Fortune (on MIT Project NANDA, The GenAI Divide, 2025)
  3. 03The State of AI, McKinsey
  4. 04The Productivity J-Curve, Brynjolfsson, Rock and Syverson, NBER
  5. 05The Productivity J-Curve, American Economic Journal: Macroeconomics
  6. 06SaaS Statistics, Zylo
  7. 07Average software waste hit $18M last year, CIO Dive
  8. 08Productivity paradox and Solow's 1987 remark, Wikipedia

Written by

David has shipped production software for more than ten years, including enterprise work for Bentley Motors and L'Oréal. He designed and wrote every layer of Qoren, and runs every Magentic project himself.

More about David

Find the workflow to redesign first

Book a free 30 minute call about the workflow that costs your team the most, or send a brief and get a written, fixed-price quote within 2 business days.

Free 30 minute call. Fixed-price quote in writing within 2 business days.