Ask a software partner who owns the code and you should get a one-sentence answer. If it takes a paragraph, read the contract properly.
Our answer: everything we build for you is yours. The code, the repository, the data, the intellectual property. That holds whether we work together for one year or five, and it is written down rather than implied.
What people find when they check
The arrangements that catch businesses out are rarely presented as ownership clauses.
Sometimes ownership transfers only on final payment, which sounds fair until a dispute makes final payment the thing you are arguing about. Sometimes you own your custom code but it sits on a framework licensed to you, which means you own a car and lease the engine. Sometimes the repository is in the vendor's account and you have never had a login, so ownership is technically yours and practically theirs.
And often you own the code but nobody documented the deployment, so a handover to another team is a research project. That is lock-in without a clause. It happens through neglect as much as intent.
None of this is unusual and much of it is not malicious. It is what happens when nobody makes it explicit at the start.
Why we are firm about it
Partly because it is the right way to treat a client. Mostly because of what it does to us.
If leaving is expensive for you, we get paid whether or not we are doing good work. That is a comfortable position for a vendor and a corrosive one. The incentive quietly shifts from being useful to being difficult to remove, and I have watched relationships rot that way from both sides.
We would rather compete on the work. Under an Apex partnership you could take everything we have built and walk tomorrow. That means every renewal is a genuine verdict on the last twelve months, which is uncomfortable in the right way. It keeps us honest in a way no clause could.
The exception, stated plainly
There is one, and we say it up front rather than in a schedule at the back.
Our own data platform — the layer that connects your systems and keeps the numbers agreeing — stays ours. It is deployed for you at no extra cost while the partnership runs, and if you want to keep it afterwards you can license it. We built it once and deploy it many times, which is exactly why it does not cost you a development budget to have.
That is the trade and we would rather you weigh it now than discover it later. Everything built specifically for your business is yours outright. The platform underneath it is licensed. One exception, named, so there are no others hiding.
What to actually ask
If you are assessing any software partner, ours included, four questions get you most of the way:
Whose account is the repository in, and do we have admin access today? When does ownership transfer, and is it conditional on anything? What parts of what you deliver are licensed rather than owned? And if we ended this tomorrow, what would you hand over, and could another team run it from that?
That last one is the real test. A partner who can answer it clearly has thought about your position, not just their own.
The point
Good work should be the only reason to stay. Everything else is a way of making the decision harder for you than it needs to be, and a partner who needs that advantage is telling you something about the work.
