This question almost never comes first. It comes at the moment someone sees the system running and realizes something has been built 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 his own knowledge land inside a system:

is that something I could then, could I edit that myself? could I make changes to it myself?

That's not the ownership question. That's the control question: will I still be able to get in. And that's the more honest question, because ownership on paper is worthless if you can't reach it.

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

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

You do. Not as a favor, but because they're in your name.

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

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

02 / the exitWhat stays yours if you cancel?

Everything that was already yours, plus everything that got added in 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 wrecks your business, it was never yours to begin with.

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

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

What comes out day to day is not a finished product but a draft. Every email, every post, every proposal lands as a draft in your own environment. You read, adjust, and send. That's not a limitation we bolted on afterward, it's how it's designed: everything that goes out passes through a human.

What you do yourself is more than approving, then. You correct, and those corrections are the input the system uses to learn your voice better. That comes with one fixed moment each week where you talk or type through what's changed in your offer, your target audience, or your way of working. Skip that moment and 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. Want something different there, you ask and we do it. That's exactly the part you pay for.

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

For maintenance. Not for rent on something that stays ours.

That distinction isn't cosmetic. Rent means: stop paying and the door gets locked, and you're out. Maintenance means: stop paying and the upkeep stops. Your systems stay, your data stays, and what we did to it no longer happens.

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

05 / the catchSo where does the dependency actually sit?

In the build layer. That's ours, and it's 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're looking for a provider who hands you the entire engine so you never need anyone again, that's not us, and you can stop reading now.

What we offer instead is this: the dependency affects the speed, not your business. Your client relationships, your knowledge, and your admin sit outside our reach. That's the line we deliberately drew.

Four questions you can ask any provider, including us:

• Whose name are the accounts in that this gets built on? 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 written down?
• What keeps working without you, and what doesn't? Anyone who only lists benefits hasn't understood the question.

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