Definition
What does running AI without the vendor take?
It takes documentation, tests your team can re-run and more than one trained person. The failure that ends independence is usually a person leaving.
By the Foxnut team · Updated
What does running AI without the vendor take?
Running an AI system without the vendor that built it takes three things, and none of them is code: documentation of how the system works and why it was built that way, testing your team can re-run after any change, and people trained to operate it. Not one person, a bench.
We are Foxnut Studios, a senior-only practice in Bengaluru and Paris, and we build AI systems that are handed over running, so we have to answer this question for our own clients. There’s a link to talk to us at the end of this article. Let’s first work out what independence consists of.
Operational independence is the name for the state where all three exist inside your organisation. The system runs in your accounts, your team changes it and can tell whether the change was safe, and the builder’s continued involvement is a choice and not a necessity. That state is the deliverable this territory is organised around, and the position behind it sits with Foxnut Studios on leaving a system behind. This page is about what the state consists of, and what actually ends it.
How do you avoid vendor lock-in?
You avoid vendor lock-in by solving the operational question before the contractual one.
Most writing on it splits into two halves. One is architectural: model gateways, multi-model designs, portability of the stack. The other is contractual: exit clauses, data return, deletion terms. Those are questions for counsel, and this page gives no advice on them.
Between the two sits the half that buyers actually live with: what must physically exist, and physically change hands, for your team to run the system when the vendor is gone. A contract can give you the right to leave and an architecture can make leaving technically possible, and your organisation can still be unable to leave, because the knowledge of how to run the thing lives in the vendor’s heads and calendars.
An AI exit strategy that only covers the contract and the stack has planned the exit door and not the ability to walk through it.
What is the real AI vendor risk?
The real risk is a person leaving, and the honest version of AI vendor risk is unglamorous. Once an AI system is properly built and tested, the system itself tends to hold up. In our experience these systems stay forward-compatible for at least a few quarters without intervention. The typical failure is with people, not with systems: the team member in charge of the system quits, or goes on leave, and nobody else is trained to cover them.
Nothing in the software broke. Your organisation’s ability to operate it broke, because that ability was stored in one person. Any assessment of the risk of running AI without the vendor should weigh this failure above the technical ones, because it is the one that actually happens.
How many people need to be trained to run an AI system?
You need one trained owner and a bench behind them, because one trained owner alone is a single point of failure. The single point of contact owns the system internally: one named person accountable for it, because a system owned by everyone is owned by no one. Behind that owner sits a supplementary team, all trained on the system, so that a resignation or a leave of absence is an inconvenience and not an outage.
Where the system touches specialised work, the training carries special modules for those roles. The person who runs lead enrichment learns the parts of the system that do lead enrichment, not a generic overview.
An organisation that cannot yet name the owner and the bench does not have a training gap. It has a precondition unmet, and transferring a system into it hands over software without handing over the operation.
How do you plan an AI exit strategy before you need it?
You plan an AI exit strategy by rehearsing the small case, on any system already running. Planning usually imagines the dramatic case: the vendor relationship ends and the organisation must cope. The rehearsal is the more useful habit.
Each rehearsal in the table below is a question you can answer from your own records, with no framework and no vendor’s help. Each one you cannot answer marks the exact place where independence is still notional.
| The rehearsal | What an answer proves |
|---|---|
| Who covered the owner’s last leave, and what happened to the system while they were out? | The bench exists in practice, not on an org chart |
| When did someone other than the owner last make a change and verify it was safe? | The testing material transfers competence, not just confidence |
| Could a new hire reach operating competence from the documentation and training materials alone, with nobody from the build on the call? | The knowledge lives in artefacts, not in people who can resign |
A vendor risk assessment that starts here, with your own bench, tends to find the real exposure faster than one that starts with the vendor’s roadmap.
What does Foxnut Studios require before it steps back?
We require the same things this page asks of you. We build AI systems into commercial operations and hand them over, and we hold our own exit to the definition above. We do not hand a system over without proper documentation, thorough testing, and training for your team on running the system independently. Those are the three things the first section named, and we treat them as obligations and not aspirations.
We also require the people precondition before transfer: a single point of contact who will own the system internally, plus a supplementary team that can all be trained on it, with special modules for specialised roles.
The requirement runs in your favour. A vendor that transfers a system into an organisation with no owner and no bench has not made the client independent. It has made the next engagement inevitable, and that is the dependency our work is structured to avoid leaving behind.
Most vendors earn more the longer you need them. We set out to be unnecessary, and the people who sign the proposal are the ones who build the system and train your bench, because there is one tier. We designed, made and launched our own products first. The first step is a free expert audit, and you can read how we run consulting work before you ask for it.
Run the three-question rehearsal above against your own vendor right now: who covered the owner’s last leave, when did someone other than the owner last make a verified change, and could a new hire reach competence from the documentation alone. If any of the three comes up short, that is worth a conversation.
Foxnut Studios takes on work like this from Bengaluru and Paris. If you want to see how we do it before you talk to anyone, here is how an AI engagement is scoped and priced.