Owning the code is not the protection you think it is
Brandon Cambron ·
Everyone asks who owns the source code. Almost nobody asks the question that actually decides whether they are trapped: what does leaving look like, step by step, in writing.
The question nobody asks on the demo call
Software procurement conversations are about features. Can it do recurring appointments, does it text reminders, does it integrate with the accounting package. Those are reasonable questions and they are all downstream of one that rarely comes up: at the end of this, what do we have?
With a subscription the answer is access. You have the right to use something for as long as you keep paying. That is not automatically bad — it is how almost all good software is sold. It is only bad when nobody said it out loud, or when leaving turns out to have no defined path at all.
Question one: can you take your data out today
Source code is the answer people think they want. Be honest about what it is worth: a repository you cannot read, in a language you do not write, that a new developer needs weeks to understand before they can change a button. Very few businesses have ever used one. Almost every business needs its data back.
So ask the question that has consequences this afternoon: can I export everything, right now, without asking permission? On our builds the answer is yes — the full database, in a standard format, no request process and no export fee. A vendor who needs a support ticket and five working days has told you what you are to them.
Question two: who holds the domain and the accounts
A surprising number of businesses discover during a dispute that their domain is registered to an agency, their hosting is on an agency card, and their customer data is inside a platform account they cannot administer.
Each one of those is a lever. Held by someone else, they turn a commercial disagreement into an operational emergency. The fix is unglamorous: registrar in your name, infrastructure on your billing, admin access held by someone who works for you.
Question three: what happens if you stop paying
This is the only question that produces a genuinely useful answer, because it forces the vendor to describe the failure mode.
With most subscriptions the honest answer is that the software stops and you export whatever the export button gives you. Ours is written down instead: your data and your domain leave with you in full, whenever you ask, and after the initial term you can buy out to a perpetual licence and keep running the system indefinitely, with the infrastructure accounts and the operating documentation in your hands. The source stays ours — a perpetual licence is a right to keep running the software, not a transfer of the codebase — and that is written down rather than discovered. The point is not that we would never lose you. It is that the exit is a clause, not a negotiation.
Where subscriptions are still correct
If a tool does one job well and switching later would be easy, renting it is the right call. Nobody should commission a custom email client. The calculation changes when a tool holds the customer record, when three tools hold three versions of it, or when the bill grows every time you hire someone. That last one is worth saying plainly: we charge per location and never per person, so adding to your team never raises the price.
The point is not that ownership always wins — we license our system, and we think that is the right shape for software that has to be maintained. The point is that leaving should be a paragraph someone can read to you, and most businesses have never asked to see it.