Skip to main content

Do we own the software we pay someone to build?

Custom Software Published November 21, 2026
Short Answer

Only if the agreement says so in writing, and only in the sense the agreement defines. Ownership of code is also not the same as the ability to run it. What actually makes software yours is holding the repository, the cloud and domain accounts, the API credentials, and documentation good enough for another developer to deploy it. Ask which parts are assigned to you and which are licensed.

Ownership on paper

Absent a clause, the default in many jurisdictions favors the party that wrote the code, not the party that paid for it. A written assignment of the work product to your company is the fix, and it should be in the agreement before work starts rather than negotiated at the end when leverage has shifted. Contract terms vary by jurisdiction and situation, so have your attorney review the actual language.

Expect a reasonable carve-out. Most experienced builders reuse internal libraries and frameworks across clients, and they will not assign those. That is normal and generally good for you, since reused components are better tested. What matters is that the agreement names which parts are assigned and which are licensed, and that the license is perpetual enough that a business relationship ending does not switch off your software.

Ownership in practice

  • The repository. Hosted under an account your company owns, with at least one admin who works for you.
  • The accounts. Domain, DNS, cloud hosting, email, error monitoring — registered to the company, not to a developer's personal login.
  • The credentials. API keys and connected app registrations created inside your own vendor accounts wherever the platform allows it.
  • The environment. Configuration written down or scripted, so the app can be stood up somewhere else without archaeology.
  • The data. Direct database access or a documented export path, in a format that is readable without the application.

The licensing question worth asking early

Plenty of good work is built on a vendor's existing platform, which is usually faster and cheaper than starting from nothing. That is a licensing arrangement, not a transfer, and it is fine as long as everyone is explicit. The failure case is discovering after two years that the thing you thought you owned only runs inside a system you rent.

Ask directly: if we parted ways tomorrow, what continues to run, what stops, and what would a new developer need? A partner who answers that clearly is telling you the truth about the architecture. This is the split we make explicit between the Bluefrog Intelligence Platform and custom-built work.

A test you can run this week

Ask for a copy of the repository and a list of every account and credential the system depends on. If that request takes weeks, or if it surfaces logins tied to an individual rather than the company, you have found the real ownership problem — and it is one you can fix without a lawyer.

The same audit is worth running on integrations, since connected-app registrations often live wherever it was convenient to create them. Keeping them in accounts you control is a standing rule of integration work.

Topics: ownership · intellectual property · licensing · control

Have a version of this question about your own business?

The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.

Related Answers

People who read this also asked

Browse the Answer Hub →

AI is easy to access. Making it useful is hard.

Bluefrog makes AI useful by integrating it with the way your business actually works — your software, your calls, your customers, your marketing and your revenue.

Technology development since 1997 · AI integration platforms since 2001