← Blog · Essay

The B2B AI plateau is real — and it's sitting on the wrong side of the OT/IT boundary

July 2026 8 min read Industrial AI · OT/IT

Enterprise AI has hit a plateau. Let's be honest about what that plateau actually is.

Almost everything shipping under the "enterprise AI" banner right now is workflow optimization and headcount reduction — RPA with a language model bolted on top. Useful, sometimes. But it's the easy half of the problem, and the market is already crowded with lookalikes.

The hard half — where the real economics live — is the production environment itself.

Energy consumption per unit. First-pass yield. OEE. Throughput stability. Scrap rate.

On a real manufacturing line, one point of yield is worth more than an entire back-office automation program. A 2-point yield lift on a line doing $200M/year is $4M/year — every year, forever. That math dwarfs anything you'll extract from automating an SDR team.

And yet almost no serious AI player is operating at that depth.

Where the gap actually sits

The interesting problems don't live in the CRM or the ticketing queue. They live at the OT / IT boundary — where PLC ladder logic and structured text meet the MES, SCADA, and historian stack.

That's where you find:

  • Sensor streams and event logs coming off the line in real time
  • Control loops still hand-tuned by senior engineers who are retiring
  • Setpoints chosen by tribal knowledge, not optimization
  • Alarms treated as terminal events instead of learning signals

The AI-shaped opening here isn't "generate a report." It's a stack:

  1. Anomaly detection and drift analysis on the raw sensor / PLC data
  2. Feed the result back as model-predictive control (MPC) or dynamic setpoint adjustment — not as a dashboard for a human to interpret
  3. Reverse-engineer the existing control logic (ladder / ST) so the model reasons about full system state, not a decontextualized time series
  4. Optimize for the joint minimum of energy, scrap, and cycle time under real-world drift — without a human standing next to the HMI

That's a different beast from "install a Copilot." It requires reading PLC code, respecting deterministic control constraints, understanding safety cases, and shipping something that closes the loop back onto the line — not something that alerts a human who then alerts another human.

Why nobody's doing it

Because the two ecosystems don't overlap:

The industrial incumbents — Siemens, Rockwell, AVEVA, GE Digital — sell dashboards, historians, and asset performance suites. Great at data collection. Weak at modern ML. Their AI story is mostly "we added a chat window."

The AI-native startups — every "AI for enterprise" YC batch of the last three years — sell chatbots, copilots, and RAG-over-your-docs. Great at ML. Zero appetite for OT constraints, real-time control, or a PLC that will kill someone if you write to the wrong register.

The gap between the two is exactly where the money is.

It's a permanent moat, because the domain knowledge doesn't transfer over a weekend. You can't ship a chatbot that occasionally lies to a bottling line. You can't fine-tune your way past a safety PLC. You have to actually understand the process.

The uncomfortable question

If enterprise AI is genuinely powerful, why has almost none of it shown up on the shop floor?

My honest read: because the OT world punishes hallucination in ways SaaS doesn't. The field routed around the hard problem and sold dashboards instead. That's rational in the short term — and a massive strategic mistake in the long one.

The teams that will win the next five years of industrial AI are the ones willing to sit on both sides of the OT/IT boundary at once. Read ladder logic in the morning, tune an MPC model in the afternoon, and ship something that closes the loop by end of quarter.

Where I sit

I've spent years in industrial environments — working with PLCs at the level of reverse-engineering control logic, reasoning about full system state, and pushing lines toward genuinely optimal operating points instead of locally tuned ones. Now I'm building at the intersection of that world and modern AI, because I don't think anyone should have to choose between "understands manufacturing" and "understands ML."

If you're a leadership team seriously exploring this direction — whether that's process optimization, yield improvement, energy reduction, or closing the loop from AI back onto control — I'd be glad to have a real conversation. Not a pitch deck. A technical one.


Curious what others working near the OT/IT boundary are seeing. Is anyone shipping real closed-loop MPC or RL in production yet — or is it still 90% dashboards with an LLM front-end? Would especially love to hear the failure stories. Those are more useful than the success decks.

#IndustrialAI #OT #PLC #ManufacturingAI #ModelPredictiveControl #DigitalTransformation
← Back to all essays