Field note

Your company should own what its AI learns

One Saturday in July we hit the ceiling on our AI provider's plan. Mid-job, mid-weekend, work stopped. We moved the same work to a different provider and kept going. By Monday you could not tell anything had happened.

That afternoon should have been expensive. It was not, for one reason. Nothing our AI knew about our company lived inside that provider. The job history, the procedures, the client context, the decisions and why we made them, all of it sits in files and systems we own. The provider brought the reasoning. We brought the memory. When the provider tapped out, we swapped it like a dead battery.

Most businesses adopting AI right now are set up the opposite way, and almost nobody selling AI will tell them that. So here it is from a shop that sells AI: your company should own what its AI learns.

What your AI is learning

Every time someone at your company asks an AI tool a question, they teach it something. How you quote. Which customers are touchy. What the boss means by "the usual." What went wrong on the last job and how you fixed it. One chat at a time, the tool builds up a working knowledge of your business, and the answers get better because of it.

That accumulated knowledge has a name: institutional memory. It is forming again right now, except this time it is forming inside chat accounts. Your estimator's account. Your office manager's account. Whatever tool each of them happened to pick.

That is a toolbox bolted to someone else's truck. Every week your crew puts better tools in it. The day the truck stops showing up, the tools go with it.

The part the industry skips

The AI companies are not villains here. The models are genuinely good and getting better, and you should use them. We use several every day. The overreach is on my side of the fence: people selling AI love to talk about what the models can do, and go quiet about where the learning ends up.

Check it yourself. Take the AI tool your company leans on hardest and ask the vendor one question: how do I export what it has learned about my business? For most of them the honest answer is a shrug. Some of the biggest will not let you take that memory out at all. The better the tool gets at your business, the more it costs you to leave. That is not an accident. Sticky memory is the business model.

To be fair about scale: if you are a two-person shop using a chatbot to tighten up emails, none of this matters yet. It starts to matter the day the answers are good because of what the tool remembers about your operation. That is the day the memory became an asset. Assets belong on your books, not theirs.

What owning it actually looks like

Owning your AI's memory does not mean hosting your own models or hiring an IT department. It means the durable knowledge lives in a place your company controls, and the AI reads from it instead of hoarding it. One backed-up, versioned home for the job history, the procedures, the customer context, the decisions. Agents and chat tools pull from it to do their work and write what they learn back into it. The models stay rented. The memory stays yours.

We run our own company on this architecture, and it has paid for itself twice this year. Both times we changed which AI provider does a chunk of our work. Both times the switch cost us a configuration change and a little testing. Zero history lost, because the history was never theirs to keep.

It is also what we now build for clients, agents and dashboards included. It has a name: Company AI Support.

Three moves to make this month

First, run the audit. Ask each person where their important AI conversations live. The answer is usually five personal accounts across three vendors, and nobody can see the whole picture. Writing that list down takes an hour and tells you exactly how exposed you are.

Second, give durable knowledge a company home. Procedures, pricing logic, job notes, anything an AI answer depends on. Even a well-organized shared drive beats knowledge scattered through chat threads. A proper versioned repo beats both, but start where you are.

Third, make the export question part of buying. Before you renew or adopt any AI tool, ask how the learning comes out. Vendors change their behavior when customers ask that question before the sale instead of after.

The trap is the timing. You find out what lived only inside one account on the day that account leaves, lapses, or gets a pricing change you will not swallow. That day is always more expensive than the habit that prevents it.

The models will keep getting better, and that is great news. Rent them all. Own the learning.