Who owns the code when you hire a software development company?
Unless your contract says otherwise, the company that writes the code usually keeps the rights to it, and you get permission to use it. Ownership moves to you only when the contract assigns it in writing.
Reciprocity, a custom software development company based in Bloomfield Township, Michigan, splits every build into three layers and names the owner of each one before the work starts.
Why doesn't paying for software mean you own the code?
Paying for custom software does not, by itself, transfer ownership of the code. In the United States, copyright in code written by an outside firm generally stays with that firm unless a signed agreement assigns it to the client. Without that agreement, what the client usually holds is a license to use the software.
That is why the ownership clause is one of the first things to read in any development contract. Reciprocity puts ownership in plain words before any work begins, so nobody has to find it in the fine print later.
This is general information, not legal advice. Have a lawyer review any contract before you sign it.
What are the three layers of a custom build?
A custom build at Reciprocity has three layers: your data, the software built specifically for you, and a reusable core. Your data and everything built just for you belong to you. Reciprocity owns the reusable core and keeps it maintained. Each owner is named before the work starts.
Your data is yours, always. It lives where you choose, you can export it any time, and Reciprocity never sells it or uses it for anyone else.
What Reciprocity builds just for you is also yours: your workflows, your integrations, and the modules that only make sense for your organization.
Why would a developer keep the reusable core?
Reciprocity keeps the reusable core because a core that many organizations share is a core that stays maintained. The core is the foundation Reciprocity builds once and shares with other organizations that need the same thing. When many organizations run the same core, Reciprocity has every reason to keep it alive.
That is the practical reason the software is still maintained in year five. A system that only one organization runs depends on that one contract to stay current. A shared core depends on all of them.
Can you own all of the code instead?
Yes. If your organization wants to own every layer, including the core, Reciprocity prices the work as a fully custom build. It costs more because you are taking on the whole codebase and its upkeep. Reciprocity shows you the difference in dollars and lets you choose.
Neither choice is a trick. Shared ownership trades a lower share of the upkeep for a core that someone else keeps alive. Full ownership trades a higher price for complete control.
What should a development contract say about ownership?
A development contract should name the owner of every part of the software in writing: your data, the code written for you, and any reusable components the developer brings. It should also say how you can get your data out, and what rights you hold to anything you don't own.
If any part of the software isn't named in the contract, ask about it before you sign. Reciprocity answers that question at the start of every engagement, layer by layer.