Why you should own your automations

Because the alternative is renting your own operations. If your workflows run in an agency's account, on their subscription, with logic only they understand, you do not have an asset — you have a dependency that stops working the day the relationship does. Ownership means the accounts sit in your name, the credentials are yours, the logic is documented, and you can change any of it without asking permission.

What does owning an automation actually mean?

Four things, and most "done for you" arrangements fail at least two of them:

1. Accounts in your name. The workflow platform, the AI tools, the enrichment services — subscriptions on your company card, admin access held by you.
2. Credentials you control. API keys, integrations, and connected accounts that you can revoke, rotate, or hand to someone else.
3. Documentation. A plain-English record of what each workflow does, what it depends on, and what to check when it misbehaves.
4. The right and the means to change it. In-house, or via any competent contractor — not exclusively through the firm that built it.

This matters because, as I set out in AI Automation for B2B: what actually works, automation only pays back over time — and you only capture that payback if the thing keeps running and improving after the builder moves on.

Why do some vendors keep automations in their own accounts?

Partly convenience: managing fifty client systems from one master account is genuinely easier, and some platforms price agency plans to encourage exactly that. Partly margin: reselling tool subscriptions with a markup is quiet recurring revenue. And partly retention: a client whose entire lead flow lives inside the agency's login has a very expensive exit door.

I would not call it malicious in most cases. But the incentive is plain — dependency is stickier than results, and a rented workflow is a permanent reason not to leave. When you evaluate any automation partner, the question "whose account does this run in?" tells you more about the engagement than the case studies do.

What actually happens when you don't own them?

The mechanism plays out the same way almost every time. When the engagement ends — pricing dispute, acquisition, the agency folding, or you simply outgrowing them — the workflows either switch off or keep running on someone else's terms. When you cannot see the logic, every change, however small, joins a queue behind other clients' work; a field rename that should take ten minutes takes two weeks. When you finally decide to move, there is nothing to migrate — no export, no documentation — so you pay a second time to rebuild from observed behaviour, reverse-engineering your own business process from its outputs.

And because workflows rot regardless of who owns them, the rented version has a nastier failure mode: you cannot even see the error logs telling you something broke.

Does ownership mean you have to maintain everything yourself?

No. Separate ownership from operation — you can own a system and pay someone to run it, exactly as you own a building and hire someone to maintain it.

This is how we structure our own work. An Outbound Engine is £4,000–£6,500 as a fixed-price build, live in 30 days, or £1,500–£3,000 per month managed — and in both cases the domains, mailboxes, database, and CRM sit in the client's accounts. The test I would apply to any provider, ourselves included: if they disappeared tomorrow, would everything keep running? If the honest answer is no, you are renting.

The same standard applies to data. The enriched lists and research notes that AI lead research produces should land in your CRM as records you keep, not accumulate in a vendor's spreadsheet you will never see again.

How do you take ownership of what's already running?

A practical sequence, in order:

1. Inventory. List every automation touching your revenue process, and note whose account each one runs in.
2. Request admin access or transfer. A reasonable provider will move workflows into accounts you own; resistance here is diagnostic.
3. Move the subscriptions. Platform and tool billing onto your company card, even if the provider keeps operating them.
4. Demand documentation. One page per workflow: trigger, steps, dependencies, failure behaviour.
5. Name an internal owner. Someone accountable for knowing the system exists and checking it works.

Your outbound system is the clearest case of all. The whole machine described in the complete UK B2B outbound playbook — list, enrichment, verification, sending, reply handling — accrues value to whoever owns the domains and mailboxes, because sender reputation is built over months and cannot be transferred. Warm it up in accounts you own and the asset compounds for you; warm it up in an agency's accounts and you are building equity in someone else's infrastructure.

Ownership costs a little more friction up front — more logins, more invoices, more responsibility. It is worth every bit of it the day you need to change something, or someone.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks and what to build first.