ReadNotes From the Field18 Jul 20262:473 min readAI on the factory floor

Why 95% of Company AI Projects Quietly Fail (It's Almost Never the AI)

The AI Labs Just Admitted the Model Was Never the Problem

A tangle of patch cables behind a rack, one cable lit warm gold plugged into the only occupied port
The picture for this piece. Made for it: no people, no brands.

In plain words

95% of company AI projects quietly fail. It is almost never the AI.

OpenAI, Anthropic and Amazon just spent billions on engineers whose whole job is to bolt AI onto real company data.

That is the quiet admission: the model was never the hard part. The data was.

RAND finds more than 80% of AI projects fail, twice the rate of normal IT. MIT finds 95% of pilots return nothing measurable.

On a factory floor, integration alone eats 58% of the budget.

For every 33 pilots, about 4 survive.

Picture it. Buying a racing engine for a car with no roads to drive on.

Why it matters to you. Stop asking AI about your messy data. Make it build the pipe: one canonical name per tag, one unit system, one clean table.

Terms in this piece

RAND RAND Corporation
A US policy research institute.
IT Information Technology
The office computers and networks.
MIT Massachusetts Institute of Technology
The US university whose research on AI adoption is often cited.

The number

58%

OF A FACTORY AI BUDGET GOES TO INTEGRATION · 2026

What to do Monday

Stop asking AI about your messy data — make it BUILD the pipe. Point Claude Code at one ugly historian/MES export and prompt: "map every tag alias to one canonical name, convert every unit to SI, force ISO timestamps, and flag the bad rows." Then hit /fork (new this month) so it runs as a background agent while you keep working — and save it as a reusable skill. Tested on a 10-row mess → 8 clean rows + 2 correctly flagged in one pass.

The honest caveat

The 80% and 95% failure rates use different definitions of failure and of success, so they do not add up to one number. Some pilots are meant to be closed: they are experiments. The data problem still holds.

Your turn

Be honest — what actually killed your last AI pilot: the data, the integration, or the org politics?

Argue with me on LinkedIn

Sources

The run's own source list was not recorded. These are the sources the piece names in its own words, listed here so every claim has an owner.

  1. AnalystRAND — more than 80% of AI projects fail, twice the rate of ordinary IT projects (as named in the piece)
  2. AnalystMIT — 95% of company AI pilots return nothing measurable (as named in the piece, 2026)
  3. PressOpenAI, Anthropic and Amazon — hiring forward-deployed engineers to connect AI to company data, as reported in July 2026
Read the full script (381 words)
OpenAI, Anthropic, and Amazon just spent BILLIONS… admitting their own AI models were never the problem. Stay with me — because the number at the end is the reason YOUR company's AI pilot quietly died. Here's the part the headlines skip. In the last few weeks all three stood up armies of "forward-deployed engineers" — people who fly into YOUR business and bolt the AI onto YOUR data and YOUR workflow. Not better models. Plumbing. Because that's where AI actually dies. RAND says over EIGHTY percent of AI projects fail — twice the rate of normal IT. MIT put a harder number on it: ninety-five percent of AI pilots return nothing you can measure. And on a factory floor it's worse. Integration eats FIFTY-EIGHT percent of the budget — and for every thirty-three pilots you start, four survive. Here's the tell you can feel. Your pilot ran on clean, tidy history. Production hands the model your LIVE data — three different names for the same sensor, five timestamp formats, a historian nobody built an API for. So here's that number. Ninety-three percent of manufacturers already run an MES. Only TWENTY-THREE percent have actually integrated it. That gap — the unglamorous data plumbing — isn't the boring part of AI. It IS the product. And it's the exact work industrial engineers have quietly owned for thirty years. If you'd rather understand the real bottleneck than chase the next model — you're in the right place. Now — your FabSpeak Tip of the Week. Stop ASKING AI about your messy data. Make it BUILD the pipe. Claude Code just shipped background sessions this month — the new slash-fork. Point it at one ugly historian export and say: "map every tag alias to one canonical name, convert every unit to SI, force ISO timestamps, and flag the bad rows." Then hit slash-fork so it runs in the background while you keep working. I ran that on a messy ten-row export — three names for one temperature tag, Fahrenheit mixed with Celsius — and it came back eight clean rows and two correctly flagged, in one pass. That fifty-eight-percent integration grind, turned into a reusable skill your whole team can run. This is FabSpeak — I turn the week's AI noise into one move you can actually use. Follow along, and I'll catch you at the next one.