The day an AI consulting engagement ends says more about it than the day it starts.
Picture the month in which you end such a mandate, and not in anger: you have found someone internally, the budget is needed elsewhere, or you want to switch providers. The last month is paid, the provider's access is switched off, the final email is friendly. Then the first week without them begins, and that week shows what you bought: does what was built keep running, and can someone at your company change it?
For that question it makes no difference which model was in use. It depends on whether what was built sits with you as readable files or as settings inside someone else's interface. Anyone who buys AI consulting buys a layer made of context, instructions, access and measurements. So the question when buying is who owns that layer in the end.
The objection comes immediately: we have no intention of switching providers. That is usually true, and it changes nothing about the check. What belongs to you at the end is the same thing that is created during the mandate, so the question about the last month is the most convenient way to test the value of the work in progress. If nothing can be handed over at the end, there was little along the way that belonged to anyone.
What AI consulting leaves behind
Four things, and none of them is a model.
The context first: who the company is, what it sells, what a quote looks like at your place, which abbreviations everyone in the building understands, which rules apply. Nobody enjoys this work, and it explains why the same tool gives useful answers in one company and not in another.
Then the work instructions for the recurring processes, step by step, including the exceptions that appear in no manual. How the monthly report comes together, in which order, what gets checked along the way, and at which point a person looks at it before anything goes out.
The access is what hardly anyone writes down: which system is connected, with which permission, on whose account, read or write, one key per process or one for everything.
Finally the measurements: what a process cost before somebody rebuilt it, and what it costs afterwards. Without the first number, the second one is an assertion.
These four things are the asset a mandate builds up. Together they form a layer between your operations and the model; why that is a question of architecture is covered in How AI changes your company's architecture.
How to tell that the layer is not with you
Three signs, and you can spot all three without technical knowledge.
You cannot read it. There is no document holding your company context, only fields in an interface that somebody filled in. In day-to-day work, both do the job. Only one of them can be taken along, printed, shown to a new colleague or copied into a different tool.
The access does not run on your company. The key to your CRM sits in the provider's workspace, the automation runs under an account in their name, and the bill for model usage comes through them. That is convenient as long as everything runs well. On handover day, this is exactly where it gets stuck.
Nobody at your company has ever changed anything. If half a year of mandate has passed without a single change from the inside, the handover has never been tested, and then the provider does not know either whether it works.
In our experience these signs rarely show up during the mandate. As long as someone is there who can do it, everything looks fine. It becomes visible in the week when that person is on holiday and the monthly report still has to go out.
The test you can send today
Ask for the four things by email, without any particular occasion: the company context, the instructions for the two or three most important processes, a list of access with the permissions behind it, and the numbers before and after.
If it arrives within a day and you understand it without a guided explanation, things are in order. If it takes a week, these things do not yet exist as files and are being produced for you. There is rarely bad faith behind that, it follows from how the work was built: what has never been handed out was never built to be handed out.
The second part of the test is shorter. Change one line yourself. A formulation in a work instruction, a rule about what never goes out automatically, a sentence in the company context. If that only works through the provider, what you have is a dependency with a monthly invoice.
The third part is the most honest one, and it costs a week of patience. Let one process run for a week without the provider touching anything, with no quiet corrections in the background. Whatever surfaces during that week is the work that today sits invisibly with the provider. It does not disappear when the mandate ends, it moves desks. Better to know in advance how much of it there is.
All three parts also work when you only have a quote on the table. Ask what the state of things will look like at your company after three months, as a file. The answer comes either concrete or general, and that alone is the information.
The model is the interchangeable part
In our experience tools and models change faster than an SME sees a plan through. Anyone who builds a mandate around one particular product will have an unplanned topic on their hands within a year.
Plain text is therefore the least spectacular and best answer. A company profile, a work instruction and a baseline sheet in Markdown or simple text can be copied into the next tool, because it is text. The file stays the same, and you swap out the model underneath. We keep these things in readable files because it is the only form that survives a switch.
The same holds for you as the buyer. The more of the layer sits in readable files, the less your operations hang on one provider, one vendor and one price list.
What you cannot demand
There is a line here, and it is fair to name it. Your layer belongs to you. The provider's craft belongs to them: their templates, their tools, their way of breaking a process apart, the experience from other mandates. Anyone who demands that the skill belong to them in the end needs an employee, not an engagement.
Nor will operations keep running afterwards without maintenance. A process that reaches into three systems changes, because those systems change. Somebody has to look at it later, and if that is no longer the provider, then someone at your company.
The difference is simple. The skill may stay with the provider, the state of your operations may not. If context, instructions, access and numbers sit with you, you can buy the skill again, build it internally or do nothing for a while. If the state sits with the provider, you do not have that choice.
How a provider answers this question
Ask who owns the context, and pay attention to the shape of the answer. A useful answer names things: the company profile as a text file in your storage, the work instructions next to it, the access in a list with a date. If what comes back are attitudes instead, partnership, transparency, meeting as equals, the question has not been answered. Both sound friendly, only one of them can be opened.
The second question brings clarity quickly in any AI consulting conversation: what would you have to send me if we stopped tomorrow? Anyone who answers that in two sentences has done it before. If the question gets negotiated instead, it is new.
The third one is the most uncomfortable for both sides: who at our company has ever changed something in it? If no name comes up, what is missing is not goodwill but a person. The handover needs someone at your company who knows the current state and has a few hours a month for it. Without that person, the layer stays formally your property and practically unusable.
What you put into the agreement
Four lines are enough, and they belong in the written agreement, before the relationship with your contact person turns good.
- Everything created belongs to the company, in readable files and in no proprietary format of the provider.
- Access runs on company accounts, and you can withdraw every permission individually.
- The current state sits with you monthly, not only at the end.
- Notice period and handover are settled before anyone needs them.
For a provider who works this way, these lines cost nothing. For you they change the situation: a mandate you can leave every month without losing anything does not have to become a yearly decision. That is how we hold it with the AI Builder, the AI lead inside your operations: cancellable monthly, with the context, the processes, the approval rules and the measurements sitting with the company.
You can check these four lines yourself, you do not need us for that. If you want an outside view on an agreement that is already running, bring it along to the free first conversation. We will tell you which of the four lines is missing at your company.
Before you sign
Three things weigh more when buying than the choice of model and the price per month.
- The four parts of the layer are named: context, instructions, access, measurements. What is not named does not get handed over.
- They sit as readable files with the company, and somebody in house has changed something in them at least once.
- The handover is described and rehearsed once on a small scale, before anyone needs it.
Models and interfaces change anyway; these three points hold through every switch.
Frequently asked questions
Who owns what is created during AI consulting?
The company paying for it, provided that is what the agreement says. Ask for readable files in no proprietary format of the provider: the company context, the work instructions for the main processes, a list of access with the permissions behind it, and the measurements before and after the rebuild. What is not named does not get handed over.
How do I know I am dependent on an AI provider?
Three signs. There is no readable document holding your company context, only fields in an interface. The access runs on the provider's accounts instead of your company's. And nobody at your company has ever changed anything, which means the handover has never been tested.
What belongs in an AI consulting agreement?
Four lines are enough. Everything created belongs to the company, in readable files. Access runs on company accounts, and every permission can be withdrawn individually. The current state sits with you monthly, not only at the end. Notice period and handover are settled in writing before anyone needs them.
