This question almost never comes first. It comes at the moment someone sees the system running and realises something has emerged that they could become dependent on.

In our own conversations, it rarely sounds big. It sounds small and practical. Twice in the same conversation, from someone who had just seen their knowledge land in a system:

is that something I can then edit myself afterwards? can I make changes to that myself?

That isn't the ownership question. That's the control question: will I still be able to access it. And that's a fairer question, because ownership on paper is worthless if you can't get to it.

Below is the full answer. What's yours, what's ours, what happens if you stop, and where the dependency actually lies. Even if you buy from someone else, these are the questions you should ask.

01 / the dividing lineWho owns the accounts and the data?

Yours. Not as a favour, but because they're in your name.

The system is built on accounts you own: your CRM, your mailboxes, your calendar, your telephony. We build within them, not alongside them. There's no portal of ours that your client data moves to, where we hold the key.

That's a choice with a cost. It's technically simpler to put everything in our own environment and give the client a login. It's also exactly the construction that makes cancelling expensive. We do it the other way round, which is why we're writing it here instead of in clause 14.

02 / the exitWhat stays yours if you cancel?

Everything that was yours, plus everything that's gone in during the meantime.

In practice that means: you keep a fully populated CRM and a written-down way of working, and the work that used to happen automatically no longer happens automatically. You're back to manual work, not back to zero.

If cancelling destroys your business, it was never yours.

03 / the control questionCan I access it myself, or do I have to call for every change?

You can always access it yourself, and for most things you don't need us.

What comes out daily isn't a finished product but a draft. Every email, every post, every proposal ends up as a draft in your own environment. You read it, adjust it and send it. That's not a limitation we built in later, it's how it was designed: everything that goes out passes through a human.

So what you do yourself is more than approving. You correct, and those corrections are the input the system uses to learn your voice better. That includes one fixed moment each week where you talk or type into it what's changed in your offering, your target audience or your way of working. Without that moment, the knowledge layer quietly goes stale.

What you don't do yourself is rebuild the engine. The connections and the instructions behind the roles are our work. If you want something different there, you ask and we do it. That's precisely the part you pay for.

04 / the billWhat are you paying for every month, then?

Management. Not rent on something that stays ours.

That distinction isn't cosmetic. Rent means: stop paying, and the door gets locked and you're left outside. Management means: stop paying, and the maintenance stops. Your systems stay in place, your data stays in place, and what we did to it stops happening.

That maintenance covers the work you don't see as long as things go well. Connections that break because a supplier changes something. Instructions that need adjusting because your offering changed. New tasks that get added because something turns out to work.

05 / the catchSo where does the dependency actually lie?

In the build layer. That's ours, and it is a real dependency.

We don't sell an illusion of complete independence. The connections, the instructions and the flows that do the work are our methodology. We don't hand that over. If you want a provider who transfers the entire engine to you so you never need anyone again, that's not us, and you can stop reading now.

What we offer in return is this: the dependency affects the acceleration, not your business. Your client relationships, your knowledge and your administration lie outside our reach. That's the boundary we've deliberately drawn.

Four questions you can ask any provider, including us:

• Whose name are the accounts in that things are built in? If the answer is "ours", you know enough.
• What can I export tomorrow, and in what format? An answer without a format isn't an answer.
• What happens to my data if I cancel, and is that in writing?
• What keeps working without you, and what doesn't? Anyone who only lists advantages in answer to that question hasn't understood it.

This text was produced with AI assistance and checked and approved by a human before publication.