What you own, what you licence, and who decided
Somebody wrote to me before we'd had a single call and asked four questions. Who owns the data. Who has admin. What's exportable. What happens if we stop working with you.
It was the best email I've had all year, and I want to be honest about why: almost nobody asks. Not because people don't care, but because it doesn't occur to most business owners that these are separate questions with separate answers, or that the answers might not be the ones they'd assume.
So here's the map. Including the parts that are less flattering than the version you usually hear.
"You own everything" is not true of anybody
You'll see agencies say it, and I've been tempted to say it myself because it sounds good and it's directionally right. It isn't accurate, and an inaccurate promise is worth less than an honest description, because the first thing that happens when somebody finds the exception is that they stop believing the rest.
There are three different things sitting inside any setup, and they behave completely differently.
Things you own outright. Your content. Your photos. Your customer data. The code, if it was written for you rather than rented. Your brand. These are yours in the ordinary sense: nobody can take them back, and they keep working if everyone else disappears.
Things you licence. More than people expect. Every piece of software in the stack is rented from somebody, and the rent doesn't stop because you changed agencies. Even your domain name is a licence rather than a possession. In Australia the rules governing .au are literally called Licensing, and what you hold is a domain name licence with terms and a renewal date, not a title deed. That surprises people, and it's the clearest example of the distinction, because a domain feels more like property than anything else on the list.
Things that only exist while somebody operates them. A campaign being managed. Content being written. Somebody noticing when a form breaks. These aren't assets at all, they're activity, and they stop when the arrangement stops. That's not a catch, it's what the work is. The trap is only when activity gets described as though it were an asset. What is your monthly actually for?
Most disputes about ownership are really confusion between those three. Somebody thinks they bought a thing and they were buying activity, or they think they own something that was always a licence in someone else's name.
The question nobody asks, which decides all of it
Here's the part I'd most like people to take away.
Whether you own it is usually a decision somebody made at the start, and usually not by you.
Two businesses can buy what looks like the same website and end up in completely different positions. One has the code in their own repository, the content in a system they can log into, the domain in their name, the ad account in their name, and a database they pay for directly. The other has all of it sitting inside their agency's accounts, working perfectly, and no way to take any of it anywhere.
Nobody lied to the second business. In most cases nobody even discussed it. It just got built the way that supplier builds things, which is usually the way that's fastest for them, and fastest for them means inside their own accounts.
That's the honest version of the ownership problem. It's rarely malice. It's a default nobody surfaced.
What it depends on, and why the answer is different for different businesses
I'd be overselling if I said everyone should want maximum ownership. They shouldn't, and pretending otherwise would be its own kind of dishonesty.
Some businesses want to run it themselves. They want to be able to edit pages, add articles, export a list, change a form, and have somebody else be optional. That's a real preference and it's usually held by people who've been stuck before. Building for it costs more up front, because a system somebody else can operate is a different build from one only its author understands, and it's worth every dollar to the people who want it.
Some businesses genuinely don't want to think about it. They want the thing handled, they're not going to log in, and asking them to hold admin credentials for six tools is giving them homework, not freedom. For them the sensible arrangement is that somebody competent runs it and the exit is documented rather than exercised.
Both are legitimate. What isn't legitimate is not being asked, because then the decision gets made by whatever was easiest for the person doing the building.
At the larger end this stops being a preference and becomes a requirement. If a business has a marketing team, a procurement process and people who'll still be there in five years, the work gets built for ownership from the beginning, the licences that have to be in their name are in their name, and the fact that they'll eventually run it without us is designed in rather than negotiated later. Some tools still have to be paid for, by them, because that's what the tool costs and nobody can give that away. But the shape is: built to be handed over, priced accordingly, and the handover isn't an event anybody has to brace for.
Ownership without capability is a filing cabinet
The uncomfortable half, and I'd rather say it than have you find out.
Owning the code doesn't help if nobody can deploy it. Owning the data doesn't help if it's a format nobody can read. Holding admin on six tools doesn't help if you've never opened any of them and the person who set them up has gone.
I've seen a CRM sitting under a previous agency's login, still billing every month, with nobody at the business able to get in. Technically some of that was the client's. Practically it was a locked room.
So the thing worth asking for isn't just ownership. It's ownership plus the ability to use it: the credentials in your name, yes, but also somebody having shown you what's where, and a written note of what's what so it survives the person who was shown leaving. That last part is the bit that almost never happens.
What we do, and the parts we can't give away
The content lives in a system you can log into and edit. The customer data lives in a database you pay for, in your name. The code lives in a repository you own. The advertising runs in your accounts, on your card, so the history belongs to you and doesn't reset the day you change suppliers, which matters more than most people realise because an account that's been learning for two years does not behave like a fresh one. Teaching Google what a good customer looks like
Our access is a role, and a role can be revoked. You don't need our permission and you don't need to ask nicely.
What we can't do is make third party software free. Some tools have a licence cost and somebody has to keep paying it, and if you leave, that becomes yours to pay directly rather than something that quietly stops. We say which ones and what they cost before anything starts, because a surprise there costs more trust than the amount ever does.
And we don't pretend the activity comes with you. If we've been writing your articles, the articles are yours and the writing stops. That's the honest line between an asset and a service, and blurring it is how people end up feeling misled by an arrangement that was actually fine.
Four questions, for whoever you're paying
Ask them in one email. Nobody straight will mind.
Whose name is the domain in, and whose account is it inside? These are two different questions. A domain in your name inside somebody else's registrar account still needs them to cooperate.
If I left tomorrow, what would I walk away with, and in what format? "An export" is not an answer. Ask what the file is and whether anything can read it.
Whose advertising accounts are these? If they're the agency's, the conversion history is theirs, and you start from zero somewhere else.
Which of these tools would I have to start paying for directly? Everyone has some. The answer being "none" means somebody hasn't thought about it.
If you're signing something with a term attached, it's also worth knowing that Australia's unfair contract terms rules cover standard form contracts with businesses under a hundred staff or ten million in turnover, whatever the contract is worth, and that terms letting the other side change the deal on their own are the sort of thing the regulator looks at. Reading the clauses isn't being difficult. Why agencies sell packages, and why you learned to ask for one goes further into what those agreements tend to contain.
Why we publish this at all
Because the exit being real is the only thing that makes the rest of it credible.
If leaving is possible, then staying is a decision you keep making rather than a position you got stuck in, and that changes the relationship in a way I think is worth more than a lock-in ever produces. It also means I have to keep being worth it, which is the correct amount of pressure.
The whole method is published for the same reason. The Foundational Marketing Blueprint So is the whole system for a trade business, stage by stage. Use it with us or without us.
