Writing

Why good companies reject good AI

Established companies reject AI the way bodies reject transplants. The immune system is doing its job.

The demo went beautifully. The room was full, the agent was sharp, and the executive sponsor said the word “transformative” without irony. That was eight months ago. The pilot is still a pilot. Nothing has shipped, no launch date exists, and everyone involved has a different theory about why.

The usual theories are culture, inertia, and fear. They are comforting theories, because they locate the problem in attitudes, and attitudes can be fixed with a town hall. But the companies stuck in pilot purgatory are often the least fearful and best run. That is the clue worth taking seriously. Good companies are not failing to ship AI despite their discipline. They are failing to ship it because of it.

Processes assume physics

Every mature software organization runs on processes that were earned the hard way. QA exists because untested software hurt someone. Legal review exists because an unreviewed claim cost money. Launch gates exist because something once shipped that should not have. These processes are not bureaucracy. They are scar tissue, and scar tissue is evidence of learning.

But look at what each process silently assumes. QA assumes the product behaves the same way twice, so a passed test stays passed. Legal review assumes a finite set of outputs, so counsel can read what customers will see before they see it. The launch gate assumes that what was approved is what ships, and keeps shipping, unchanged, until someone changes it. The roadmap assumes features complete rather than converge.

Deterministic software honors every one of those assumptions. An agent violates all of them at once. It can answer the same question two ways. Its output space cannot be enumerated for counsel. What it says next month depends on context that does not exist yet. It never reaches “done,” only “measured.”

The immune system is doing its job

So the org’s defenses do exactly what they were built to do. QA cannot certify it, so QA flags it. Legal cannot read every output, so legal holds it. The gate cannot pin down what is being approved, so the gate stays closed. Each function is behaving correctly by its own charter. The organization is not rejecting the agent out of ignorance. It is rejecting it the way a body rejects a transplant: a well-calibrated immune system correctly identifying tissue that does not match.

This is why the two standard escalations both fail. Pushing harder, with executive sponsorship and deadline pressure, suppresses the immune system; the agent ships, and the risk ships with it, unmeasured. Waiting politely, with another pilot and another demo, leaves the immune system in charge of a decision it can only ever make one way. Purgatory is not indecision. It is the system working.

Make the agent legible

The way through is neither suppression nor patience. It is compatibility. The agent has to be made legible to the org’s defenses, in the language those defenses already speak.

That is harness work. Evals give QA what a test suite used to: not a promise that outputs never vary, but measured behavior under pressure, with thresholds that gate the release. Deterministic policy layers give legal a surface it can actually read: not every sentence the model might produce, but the hard boundaries it cannot cross, written down and testable. Audit trails and monitoring turn the launch gate from a single verdict into a standing inspection, which is what approval has to mean for a system that keeps learning. Escalation rules give risk owners the thing they most need: a documented account of when the machine stops and a human begins.

None of this weakens the immune system. It gives the immune system something it can recognize. The antibodies stand down not because someone overruled them but because the foreign body stopped reading as foreign.

The companies that ship

The companies shipping agents in regulated industries are not the ones with looser processes or braver lawyers. They are the ones that understood the rejection was structural and built for it: governance designed in from the start, evals in place of vibes, boundaries a compliance officer can hold in her hands.

The pilot that finally ships does not win by getting a better demo. It wins by arriving at the gate already speaking the gate’s language. If your agent has been in purgatory for two quarters, the question is not who is blocking it. The question is what your immune system would need to see, and whether anyone is building that.

Working on an agent in a regulated environment? Tell us about it.