Ownership6 min read

Who holds the keys to your company? Find out before a buyer does.

Code, domains, hosting and app store accounts end up in the names of people who have left: a co-founder, a developer, a freelancer. Our free ownership check walks through eighteen questions in your browser and shows each gap with the rating a reviewer would give it, why a buyer cares and the first step to close it.

We see the same story in company after company. Two people built the business. One ran the product and the customers. The other looked after everything digital: the domain, the hosting, the cloud account, the social pages, the app store listing and the developer who knew how it all fitted together. Then the second partner sold their share, or simply stepped away, and the one who stayed found that a good part of what the company sells is not in the company's name.

Getting it back is rarely a fight. It is slower and duller than that: a former partner who answers in a week, a developer who changed numbers, a registrar that needs the original email, a store account that only transfers when both sides agree. Each piece takes days. Together they take months, and in technology businesses we meet this constantly. This note is about finding those pieces while there is still time, before they show up in a buyer's report.

How the keys end up in other hands

Nobody plans it. Accounts are opened by whoever is at the keyboard on the day. The developer registers the cloud account with a personal email because it is faster. A freelancer creates the app store listing under their own developer account. A co-founder buys the domain on a personal card and never moves it. Years later the company runs on a set of logins spread across people, some of whom no longer work there, and nobody has the full list.

The rights to the code follow the same pattern. Paying an invoice does not by itself make the company the owner of the work. Under US law, software written by an outside developer is usually not a work made for hire, and ownership passes by a written transfer signed by the person who holds it (17 U.S.C. 204). If the agency or the freelancer never signed one, the company may be using code it does not own. Whether the rights passed under a given contract is a question for counsel, and the answer depends on the contract and on the country, but a buyer's reviewer will ask it either way.

What stays behind

The quieter problem is what people leave inside the product when they go. A developer who built a site can wire in access that is hard to see from the outside. We have seen sites that sent a copy of every enquiry to a former developer, forms that forwarded leads to an address nobody at the company recognised, and admin accounts still tied to the personal email of someone who left years before. None of it breaks anything. All of it means that someone outside the company still holds a key, and in a sale that is a finding.

When one person leaves

Ownership is also about knowledge. In a small technology company one person often holds the whole picture: where the servers are, how a release goes out, which scheduled jobs keep the business running. When that person leaves, the company keeps the product and loses the map. If the partner who managed the developers is also gone, nobody even knows whom to call. We wrote about the deal side of this in key person risk, and about the moment a partner wants out in when a co-founder wants out.

The usual reaction makes it worse. The owner hires a freelancer from a marketplace to keep things going. The freelancer reads enough of the project to make the requested change, adds code generated in a hurry, and moves on. Each patch works on its own. Together they add holes that nobody owns, written by people who never saw the whole system. We look at what that does to a review in AI-written code in due diligence.

What a buyer does with it

Early in a technical due diligence, the reviewer matches what the company says it owns with the evidence: who is the owner of the code repositories, in whose name the cloud and the domains are registered, who signed the developer contracts, who still has admin rights. Every mismatch becomes a finding with a severity on a scale like ours. Most are fixable, and many are fixed before closing as a condition of the deal. Some move into the terms: a holdback, a specific indemnity or a lower price, because the buyer is paying for assets the seller cannot yet hand over. We list the common ones in ownership gaps in a software acquisition.

The difference between a gap the seller found and fixed and one the buyer found alone is large. The first reads as housekeeping. The second reads as a question about what else nobody checked.

An 18-question check

We built a free ownership check for owners who want to see their own position first. It asks eighteen questions in four groups:

  • Code. Whether the repositories belong to a company account, whether at least two company people hold owner rights, and whether someone other than the original developers can build and release the product.
  • Accounts and domains. Cloud and hosting, domains, DNS and email, the Apple and Google Play developer accounts, payment, analytics and other key services, and whether people who left have lost their access.
  • Rights to the work. IP assignments from staff and founders, rights from agencies and freelancers, open source licences, paid fonts and templates, anything shared with another business of the same owner, and contracts that survive a sale.
  • Data and knowledge. Where customer data sits, whether backups are in a company account and have been restored, and whether every critical part of the product is known to more than one person.

Each question takes one of five answers: yes, partly, no, not sure, or not applicable. Every gap gets a rating on the scale our reviews use, kept to three levels: High, Medium and Low. "Not sure" is rated like "no", because a buyer treats an unknown as a gap until the documents show otherwise. "Partly" is one step lower. The check never sets Critical: that needs the contracts and the accounts themselves, and a reviewer sets it with the evidence in front of them.

Next to each gap the page says why a buyer cares and what the first step is. The answers stay in your browser: nothing is sent to us or stored on our side. The result can be copied as a list or saved as a PDF report with the name of the company, ready for a board meeting or for the data room.

What to do first

Start with what can stop a sale. Move the domains into a registrar account the company controls; the registrars follow a common transfer policy, and a change of registrant is routine when the current holder cooperates. Bring the cloud and hosting accounts onto company emails and company cards. Move the apps into the company's own developer accounts through Apple's app transfer and Google Play's. Ask counsel for confirmatory assignments from the agencies and freelancers who wrote the core code. Then remove every person who left, and look for the quiet leftovers: forwarding rules, extra recipients on forms, admin users nobody recognises.

Most of this costs days of attention, not money. It costs far more once a buyer has found it and a deadline is running.

When a check is not enough

The check works from the owner's own answers. It does not open the accounts, read the contracts or look inside the code, so it cannot confirm that an answer is right. If a buyer will read the company soon, a red-flag memo puts severity, cost and time to fix next to each item with the evidence. If the sale is a year or more away, exit readiness closes the gaps month by month, so the list a buyer receives is short and already explained. For the dated side of the same question, the end-of-support dates of what your software runs on, use our stack check.

Sources

Questions

Does the ownership check send my answers anywhere?

No. The answers stay in your browser, on your device. Nothing is sent to us or stored on our side; the page only counts how many gaps were found, never what was answered. Start again clears them from the browser too.

Why is not sure rated like no?

Because a buyer reads it that way. A reviewer treats an account, a contract or an assignment nobody can show as a gap until the documents prove otherwise. Finding out costs little, and the answer often turns a High into nothing at all.

Does paying a developer make the company the owner of the code?

Not by itself. Under US law, software written by an outside developer is usually not a work made for hire, and ownership passes by a written transfer signed by the person who holds it. Whether a given contract did that is a question for counsel, and the law differs by country.

What should a company fix first?

Whatever can stop a sale: domains, cloud and hosting accounts, app store accounts and the rights to the core code. Then access for people who left, and the quiet leftovers such as forwarding rules or extra recipients on forms. Most of it takes days of attention rather than money.

Can the check replace a technical due diligence?

No. It works from the owner's own answers and does not open the accounts, read the contracts or look at the code. It shows where to look. A red-flag memo or a full review confirms the answers with evidence and puts a cost and time to fix next to each item.

Written by
The Structure Team
Review teamThe Structure Team

Deal people and engineers of The Structure, writing together: practical tools, checklists and how a reviewer reads a software company before a deal.

Next step

Preparing a sale or looking at a target?

We reply within one business day. NDA before any documents change hands.