Moative Essay: The Mess Just Got Cheap

Power transmission companies often do not know what to charge carriers for tower access. No software tells them, and no vendor sells the answer.

The work does not live cleanly inside one system. It sits across contracts, tower assets, field constraints, carrier precedent, and the judgment of someone who has seen enough bad deals to know where the trap is. A model can read the documents. It cannot know, on its own, what this industry has learned to fear.

Every traditional industry has work like this. The official software handles the clean path: ERP, CRM, billing, claims, dispatch, compliance. The names change, but the pattern does not. The system captures the part that could be standardized, and the rest lives beside it.

It lives in spreadsheets and email threads and approval chains, in the person everyone calls before the number goes out. A regulator's note from 2019. A pricing exception after a market shift. A workaround built after an acquisition, because the new system could not express the old promise.

Every one of them formed around a real wound. They are scar tissue.

Traditional software did not ignore this work because software people lacked imagination. It ignored it because encoding the mess was expensive. Every exception became a field, every judgment a rule, every rule three more screens. Eventually the software became bloat, and the human sidecar survived because it was cheaper than pretending the work was clean.

AI changes that economics. For the first time the sidecar work can run on software: read the contract, pull the asset record, compare precedent, draft the recommendation, route the exception. The expert stays. The manual grind around them does not.

But the output still needs a human behind it. If the work touches risk, capital, price, compliance, or customer trust, someone inside the industry has to own the result. This is where the vendor story breaks: a license vendor can sell the tool and walk away. The buyer cannot.

So "I do not trust a vendor to know my world" is, more often than not, exactly right.

The labs themselves are proof of it. A frontier model on its own does not change a business, and they know it. OpenAI has stood up a separate company to send its own engineers inside customer operations, and Anthropic is building an enterprise services arm aimed at community banks, mid-sized manufacturers, and regional health systems. The model matters. So does sitting inside the work long enough to know what it is allowed to do.

Which raises the question the vendors would rather skip: who should own one of these workflows?

Probably not a software company. More likely the operator who has already lived inside the mess, the one with the expert, the customer trust, and the long memory of exceptions. So build it for yourself first. Most of these systems should stay right there, inside the business, where they cut cost, raise quality, and make the company less dependent on one heroic operator. That alone is worth doing.

A few should leave the building.

The test is strict. Does the same workflow show up across your peers? Does it sit near money the customer already cares about? Does it get sharper with every exception it handles? Can you take it to market in language the industry respects?

When the answer is yes, the workflow stops being an internal efficiency project. It becomes the product the industry did not know how to ask for, whether that is internal IP, a licensed product, a joint venture, or a new company. Not because it sounds like AI, but because it sounds like the industry.

None of this is the generic AI everyone is already buying. The writing assistants, the coding copilots, the search across the company drive: rent those, and let the labs make them cheaper every quarter. The work beside the software runs the other way. It does not get cheaper from someone else's training run, and no vendor is waiting to hand it to you.

The people who build it will probably not call it an AI product, or a new category at all. That language belongs to vendors. They speak in outcomes: which result has to be right, which exception has to escalate, which answer nobody should trust without a human name on it.

That is the difference between automation and opportunity. Automation makes the work cheaper. Opportunity is when the industry still needs someone credible to stand behind the result.

The operators who can carry these systems to market already know each other. Word of mouth among them moves faster than any sales team.

That is the premise behind what we build at Moative: the Guild for the operators who already carry the work, and the ventures and Foundry we form when one of those systems is ready to leave the building.

Someone will build the generic tools for everyone. No one is coming to build the work beside the software but you.