Who owns your systems when the builder leaves?

It almost always starts innocently. A freelancer sets up an automation in their own account because it is quicker. An agency manages your ad account, your domain and the link to your CRM. The AI assistant runs on a key tied to their credit card. Everything works, so nobody looks.

Until the relationship ends. Then it turns out you cannot reach your own leads, nobody knows which integration does what, and the assistant talking to your customers will switch off next month. We see this more often than you would expect, usually at companies that believed everything was properly arranged.

First: whose name are the accounts in? Domain, email, ad accounts, CRM, automation tools and AI services belong to your company, with the builder as a user you can remove. Not the other way round.

Second: is it written down what is running? Not a technical manual, just one page per system covering what it does, where its data comes from and what breaks when it stops. Third: could someone else take it over without calling the original builder? If the answer to any of these is no, you are not paying for a system. You are paying for a person.

There is nothing wrong with hiring someone to build and maintain things. What is wrong is losing the option to walk away. A good partner makes themselves replaceable: everything in your name, everything explained, keys you control and can revoke. It sounds like it works against their own interest, and it is exactly why you keep someone like that.

We work this way ourselves, partly because we have seen the opposite go wrong too many times. Ask the question with every new tool or partnership, before anything gets built. Clawing it back afterwards always costs more than setting it up right from the start.