What Happens When the Person Who Built Your Automation Leaves

When the person who built your automation leaves, whatever they knew about it usually leaves too. Nobody else has the login. Nobody knows why a step exists or what it is supposed to do when something changes. The fix is not a fancier tool. It is making sure the knowledge and the access never live inside one person's head to begin with.

What Actually Breaks When the Builder Leaves

It is rarely the automation itself. Zapier, Make, an AI agent, whatever runs it usually keeps running for a while after the builder is gone. What breaks is everything around it.

• The login. If the accounts run under the builder's personal email or their own API key, you lose access the day they stop paying attention, whether they meant to cut you off or not.

• The logic. Nobody left behind knows what triggers what, or why a step was built a certain way. It looks like a black box because it is one.

• The alerts. If something breaks quietly, a form field gets renamed, an API limit gets hit, nobody notices until a customer complains weeks later.

• The relationship. The builder often knew who to call at the platform, or how to read an error message nobody else on the team has ever seen.

Why This Happens to So Many Small Businesses

Automation feels finished the moment it works. You test it, it runs, everyone moves on. Nobody circles back to write down what it does, because documentation is not the fun part and there is no deadline forcing it. A freelancer or agency builds it, hands you a working system, and the relationship quietly ends there. You bought software. You did not get the map that goes with it.

What to Ask For Before You Hire Someone to Build an Automation

Set these up front, while you still have leverage to ask for them.

1. The accounts run under your business email, not theirs. Every login, every API key, every subscription, in your name.

2. A plain written explanation of what the automation does and why, not just the finished build. If you cannot follow it, ask for it again in simpler words.

3. At least one person on your side has admin access, even if they never touch it day to day.

4. A plan for what happens if something breaks after the project ends. Who do you call, and what do they need from you to fix it.

How Do You Know If You Are Already Exposed

• The login for the automation platform is tied to someone's personal email, not the business.

• Nobody on your team could explain what the automation actually does if you asked them right now.

• Nothing alerts you when it breaks. You would only find out from a customer or a missed order.

• There is no copy of the setup anywhere except inside one person's account.

If two or more of those are true, you are not automated. You are dependent.

What to Do If the Builder Already Left

1. Audit every tool and account tied to the automation. Write the full list down, do not rely on memory.

2. If you can still reach the builder, ask for an export or a short walkthrough while that is still possible. Most people will do this even after a project has ended.

3. Get one person on your team to understand it at a basic level, even if they never build another one. Somebody has to be able to explain it out loud.

4. Budget time to document it properly this time, and check whether it is actually still working while you are in there. It is slower than skipping it, but it only has to happen once.

Does This Apply to AI Agents Too

Yes, more so. An AI agent trained on your content depends on knowing exactly what content it was trained on, where that content lives, and how it was set up to answer. Hand off just the login and you have handed off a black box that happens to talk. The same rule applies: you own the accounts, and someone can explain, in plain words, what the agent was actually built to do.

We build custom AI agents and automations for coaches, course creators, and small businesses, and this is one of the first things we set up on every build: the accounts stay in the client's name, and they get a plain explanation of what was built, not just access to it. If you want to see what a trained AI agent looks like in practice, we have a live one you can talk to at demo.ajmarketingresults.com.

---

FAQ: Automation Handoffs and Vendor Lock In

What is automation vendor lock in?

It is when only the person or company who built your automation can access, understand, or fix it, so you are stuck working with them even if you would rather not.

Should I ask for documentation before a freelancer starts building?

Yes. Ask for it as part of the project, not as an afterthought once it is done. It is much harder to get someone to write it up after they have moved on.

Who should own the accounts my automation runs on?

You should, always, under an email address and login your business controls. Not the builder's personal account.

What if I already do not understand how my automation works?

Start with an audit. List every tool, login, and account involved, then get someone, in house or a new freelancer, to write a plain explanation of what it does and why.

Does hiring a bigger agency solve this problem automatically?

No. Size does not fix it, process does. A solo freelancer with good handoff habits is safer than a large agency that documents nothing either.