# Why "just plug in the model" never works in production

_A neuroscientist trying to run code on living neurons found the limit fast. You cannot plug a model into a system whose interface layer does not exist yet. The same is true of your enterprise stack._

Just plug in the model fails because production systems lack the interface the model needs. An anonymized biocomputing advisor on the missing abstraction layer, plus how Density Labs finds it in the AI Readiness Assessment.

# Why "just plug in the model" never works in production

"Just plug in the model" is the most expensive four words in an AI pilot. It assumes the hard part is the model and the rest is a cable. In production, the reverse is true. The model is ready. What is missing is the layer that lets it actually talk to the system on the other end, and that layer almost never exists until someone builds it.

The evidence sits in the failure rate. Around 95 percent of AI pilots that stall do so on integration and trust, not on model quality. The models are capable. They just get handed to a system that has no clean way to receive them, and everyone acts surprised when the plug does not fit the socket.

## The interface that does not exist yet

A neuroscientist advising a biocomputing startup described the purest version of this problem. Her team runs code on living neurons. You would think the challenge is the model or the code, but it is neither. You write Python, she explained, and "everything is translated into" hardware behavior, an electrical spike or a dose of dopamine sent to the cells. The catch: "we still don't have perfect formula on how to interact with neurons to get some meaningful interactions."

The plug does not fit because the interface layer, the encoding and decoding between the code and the substrate, has not been invented. In her words, you actually need a new framework, "like a new programming language, totally new," to move information in and out of the system reliably. Until that exists, plugging the code in produces motion, not meaning.

She added the second half of why plugging in fails. Computers are stable: same input, same output, every day. "But brain is plastic." The same input can give a different output tomorrow. The downstream system is not deterministic, so even a perfect connection cannot assume the thing on the other end behaves the same way twice.

Swap neurons for a legacy enterprise system and the lesson holds exactly. The model is fine. The system it plugs into has no clean interface, holds data in shapes nobody documented, and behaves differently under real load than it did in the demo. "Just plug it in" assumes an interface and a determinism that production does not have.

## The missing middle

Between a capable model and a real system there is always a middle layer that has to be designed: the translation of the model's output into something the system can act on, the handling of data that arrives in the wrong shape, the fallback for when the downstream system does something unexpected. That middle is the actual product. Skipping it is not integration. It is a demo with optimism where the engineering should be.

The reason this trap catches smart teams is that the middle layer is invisible in the demo. In a demo, the inputs are clean and the downstream system is a slide, so the plug appears to fit and everyone concludes the hard work is done. Production removes both comforts at once. The inputs get messy and the downstream system gets real, and the middle layer that was never built is suddenly the only thing standing between a working feature and a stalled one. The teams that ship budget for that layer from the start. The teams that stall keep believing the demo, right up until the cable does not fit.

## How we approach it at Density Labs

In the AI Readiness Assessment ($2,500), we look for the missing middle before anyone says the word plug. We identify whether the interface the model needs actually exists, where the target system behaves unpredictably, and what translation layer has to be built for the model to do real work. Naming that gap up front is the difference between a pilot that ships and one that ends the day the cable does not fit.

Nothing worth deploying just plugs in. Build the layer that makes the connection real, or accept that the demo is as far as it goes.