Start with the data
Your data describes your work, your clients and your decisions. Before choosing any model, know where that data lives, who can read it and how you would take it back.
Begin with an inventory. List the places where your company keeps information: the shared drive, the CRM, the support inbox, the notes people write for themselves. Next to each one, write three facts. Who administers it. Where it is stored. What happens to it if you leave. Most teams fill the first two columns in an afternoon. The third takes longer, and it is the one that matters.
Then sort by sensitivity. Some data can go anywhere, such as public product pages and published prices. Some can go to a provider under a written agreement, such as customer lists and internal documents. Some should stay on infrastructure you control, such as contracts, health data and anything the law obliges you to protect. A rough sort is enough, as long as it exists, so that sending a file to an AI system is a decision someone made.
Then the models
A model you can’t swap is a dependency you can’t negotiate. Keep the choice open: route by task, and keep prompts and memory in formats you own.
Routing by task means a small model answers the routine questions, a larger one drafts the long documents, and a specialist handles the code. You pay for capability where you need it. You also learn what each model is good at, which is hard to learn from a vendor’s own benchmarks.
Formats matter more than people expect. Prompts kept as plain text files, retrieval indexes built from documents you hold and conversation history exported as JSON all move with you. A memory that lives only inside one vendor’s interface does not.
A simple test helps. Ask how long it would take to run your three most important workflows on a different model next month. If the answer is a few days, you own the work. If the answer is that you would have to start again, the vendor owns part of it.
“Where a system runs, and who operates it, decides which law applies to it.”
Then the hosting
Hosting in France is a choice you can make on day one, and a costly one to make later. Check where each system runs, who operates it, and under which law.
Those are three separate questions. A server can sit in a data centre in Paris and be run by a company under foreign law, and a foreign authority can then compel that company to hand over what the server stores. A server can sit in another country and be run by a French company. Location, operator and law can all differ, and each one changes what you can promise your own clients.
Sovereign, in the sense we use it, means hosted in France and run by a company under French law. The definition is narrow on purpose. It leaves out much of what people mean by the word, and it can be checked: you can read the provider’s legal notice, find the company’s registration and see where its data centres are. It is not a guarantee of security, and it does not replace good practice on your side. It tells you which rules and which courts apply first. It does not tell you who owns the company, so check its ownership as well.
Do this early. Moving later means migrating data, rewriting contracts and retraining people, while the system stays in use.
What no vendor sells
The last layer is judgement: knowing what to automate, what to keep by hand, and why. That part you learn, and keep.
A vendor can sell you a model, a platform and a support plan. Nobody sells you the view of your own business that tells you which task is worth automating. That view comes from doing the work, writing down what you saw, and revisiting the list when the tools improve.
A useful habit is a short written note for each automation: what it does, who checks it, and what would make you switch it off. Review the notes every quarter. Some automations will have earned their place. Others will be doing work nobody reads any more, and removing them is a gain.
This is why we write about purpose next to tools. A company that knows what it is for decides faster, and chooses its constraints on purpose. The three layers above give you room to choose. Judgement is what you do with it.
Pick one system this week and write down where it runs, who operates it and under which law. That page is the start of the rest.