Writing
Why you should own your own data
Most consultants and software vendors end up holding their clients' data. It is a business model, not a technical necessity — and it is worth understanding the difference before you sign anything.
The default arrangement
Here is how it usually goes. You hire someone to build you a system. They build it well. Your inspections, your job costs, your customer records and your history all accumulate inside it. Two years later you have thousands of records you depend on, and every one of them lives on infrastructure that belongs to somebody else.
Nobody set out to trap you. It happens because it is the easiest way to build, and because it quietly solves the vendor's hardest commercial problem: you can no longer leave without pain. That pain is not a side effect. In a lot of business plans it is the plan.
Why it is no longer necessary
It used to be that hosting your own systems meant a server room, a person to look after it, and a backup regime nobody tested. That is genuinely gone. If you have Microsoft 365, you already own a tenant capable of holding structured business data, documents, authentication, audit logging and reporting — to a standard most small companies could not have bought a decade ago at any price.
So when a system holds your data somewhere else now, the reason is rarely technical. It is either convenience for whoever built it, or leverage over you. Usually both.
What it actually costs you
The cost is not a line on an invoice, which is why it goes unnoticed until it matters.
- You lose pricing power. Renewal conversations go differently when both sides know leaving is expensive.
- Your audit trail is not yours. If you are ever asked to produce two years of inspection records, you are asking permission to see your own compliance history.
- Integration gets decided for you. Connecting your own data to your own accounting system becomes a feature request.
- Your exit is a project. Not a decision — a migration, with a budget and a risk register.
How I work instead
Everything I build runs inside the client's own Microsoft tenant. Their data, their environment, their ownership. I do not host it and I do not hold it. I have delegated access that can be revoked in one click, and every change I make is logged where the client can read it.
Clients receive the solution files and the documentation. If someone decides to stop working with me, the system keeps running, and I hand over everything a successor needs inside thirty days. No conditions, no exit fee, no negotiation.
The tooling I build with stays mine — the same way a carpenter owns his saw and the client owns the house. What runs your business belongs to you.
The honest trade-off
This is a harder thing to sell, and I would rather say so than pretend otherwise.
A vendor-hosted product asks almost nothing of you: sign up, connect it, look at the dashboard. Owning your systems means your people adopt them, your tenant is configured properly, and you carry real responsibility for your own data. It also means I have to keep earning the relationship, because you can end it whenever you like.
I think that is the correct arrangement. It certainly produces better work.
Questions worth asking anyone who builds for you
Whether you work with me or not, these five questions will tell you most of what you need to know. Ask them before you sign, and get the answers in writing.
- Whose infrastructure holds my data? If the answer is theirs, ask why it cannot be yours.
- If we part ways, what do I keep? A data export is not the same as a working system. Ask which one you get.
- What access do you hold, and how do I revoke it? A clear answer takes one sentence. Vagueness is the answer.
- Can I see the log of what you changed? Anyone working properly can show you this immediately.
- What happens if you are unavailable? The right answer is that the system keeps running and the documentation is written for a successor — not that they are always reachable.
Why this matters more each year
AI has made building software dramatically cheaper. That is good for buyers, and it means the interface, the reports and the workflows are no longer where the leverage sits. What remains valuable is the record itself: the accumulated, structured, trustworthy history of how your business actually runs.
That record is the thing worth owning. And it is the thing you should be least willing to rent.