What 'You Own the Code' Actually Means
Vendors promise 'exportability' and 'data portability.' They almost never mean what you think they mean. Here's the real test.
"You own your data." Every SaaS MSA contains some version of this sentence. It is almost always true in the narrowest possible sense: you can request a CSV export of your records within thirty days of termination. You cannot, however, take the software — the workflows, the UI, the logic, the integrations, the custom fields, the training your team has invested in.
You own the data. You don't own the system.
The four-part ownership test
Here's what true ownership of software looks like. If you can't answer yes to all four, you don't own it.
- Can you read the source code? As in — pull the repo, inspect every line, change it if you want.
- Does the software run on infrastructure in your name? Your cloud account, your keys, your billing relationship with the host.
- Can you fire your vendor and keep operating? Including hiring any competent developer to maintain it, with no special licensing or IP hurdles.
- Do you have write access to the database? Direct, full, with the schema documented.
A normal SaaS contract fails all four. A good custom software engagement passes all four, in writing, on day one.
What this looks like in an MSA
Our standard clause reads:
"All source code, schemas, and configurations developed for Client are the sole property of Client upon payment. Upon termination, Client receives the git repository, database snapshots, and hosting credentials within 30 days."
It is one paragraph. It is enforceable. It is the difference between a vendor relationship and a service relationship.
Why ownership reduces cost
Not just because you stop paying license fees. Because ownership changes the incentive structure:
- No lock-in premium. When your vendor can't hold the software hostage, they have to be good or you leave.
- No "enterprise tier" tax. There is no upsell to SSO, audit logs, or API limits — it's your code.
- No renewal shakedown. Your monthly doesn't spike 18% on the anniversary of your go-live.
- No abandoned-by-vendor risk. If the vendor goes out of business or gets acquired, your operations don't grind.
The question to ask every vendor
"Can you walk me through the exact thirty-day offboarding process, including what I receive?"
If the answer is a CSV export, you don't own anything of consequence. If the answer is a git repository, database snapshot, and hosting credentials — you own the system.
Want the real numbers for your own stack?
Send us three months of software invoices. We'll come back with a ranked kill-list and the 12-month ROI math. Free.
Book the audit