Ownership check

Does the company own what it sells?

A buyer pays for code, accounts and data the company controls, built by people who signed their work over. Answer eighteen questions about who holds what. Every gap gets a rating on the scale our reviews use, a line on why a buyer cares and a first step. Your answers stay in your browser.

Questions
18, in four groups
Time
About ten minutes
Sent to us
Nothing
Report
PDF, free
01 · Check

Who holds what.

Answer what you know. Not sure is a fair answer: a buyer reads an unknown as a gap until the documents show otherwise, so the check does too.

Answered in your browser. Nothing is sent to us or stored on our side.

01 · Code
  1. 01

    The code sits in repositories under an organisation account the company owns.

    GitHub, GitLab or Bitbucket, in an organisation registered to a company email. Not a developer's personal account or an agency's account.

  2. 02

    At least two people at the company hold owner rights on the code, and neither is an outside contractor.

  3. 03

    Someone other than the original developers can build and deploy the product from the repository, with written steps.

02 · Accounts and domains
  1. 04

    The production cloud and hosting accounts are registered to a company email, and a company card pays for them.

    AWS, Google Cloud, Azure, DigitalOcean or the hosting panel.

  2. 05

    The domains are registered to the company, in a registrar account the company controls, with auto-renew on.

  3. 06

    The company controls its DNS and the admin of its email (Google Workspace or Microsoft 365).

  4. 07

    The Apple and Google Play developer accounts and the app listings are in the company's name.

  5. 08

    Payment, analytics and other key services are in company accounts, with admin rights held by more than one company person.

    The payment provider, analytics, CRM, the service that sends the app's email, error tracking.

  6. 09

    Everyone who has left the company has lost access, and no admin password is shared between people.

03 · Rights to the work
  1. 10

    Everyone who worked on the product as an employee or founder signed an IP assignment, the earliest people too.

    Including work done before the company existed.

  2. 11

    Every agency, freelance and offshore contract transfers the rights to the work to the company.

  3. 12

    The product's open source components have been scanned for licences, and any copyleft ones (GPL, AGPL) were checked against how the product uses them.

  4. 13

    Fonts, images, themes and other paid assets in the product are licensed for business use.

  5. 14

    Code, accounts and data shared with another business of the same owner are separated, or the sharing is written down.

  6. 15

    Key software and API contracts are signed by the company, and we know which ones can pass to a buyer or end on a change of control.

04 · Data and knowledge
  1. 16

    Customer data sits only in systems the company controls, not in personal drives, mailboxes or a contractor's servers.

  2. 17

    Backups are kept in an account the company controls, and someone has restored one in the last twelve months.

  3. 18

    For every critical part of the product, at least two people know how it works, and the essentials are written down.

02 · Why ownership first

Why we read ownership first.

Of the six layers we read in every software company, ownership comes first. Old code or a slow server changes the price. A gap in ownership can stop the deal: the buyer cannot take over code, accounts or rights the seller does not control.

Most gaps are ordinary. The first developer kept the code in a personal account. The domain was registered by a former partner. An agency contract says nothing about rights. Each is easier to fix a year before a sale, with the people still around, than in the last weeks before closing.

03 · Ratings

How the answers are rated.

High
A No or Not sure on code, cloud and app store accounts, domains, IP from staff and contractors, customer data or knowledge held by one person. Likely to affect price or terms; a reviewer often rates the worst of these Critical.
Medium
The same answers on second owners, releases, DNS and email, key services, leavers, licences, shared assets, contracts and backups. Raises the cost of owning the company.
Low
Fonts, images and templates. Hygiene, worth tidying before a buyer looks.
Partly
One step lower than a No. Not sure counts as a No, because a buyer will treat it as one.
04 · FAQ

Questions about the check.

Are my answers sent anywhere?

No. The page works in your own browser. Your answers are kept only in this browser, so you can come back to them, and Start again deletes them. We count that a check was finished and how many gaps it found, never which answers were given.

Is this legal advice?

No. Whether the rights to the work passed to the company depends on the contracts and on the law of each country. The check shows where to look; counsel decides what a document means.

Why does the check never say Critical?

Critical means a finding that can stop a deal, and that needs the documents and the accounts themselves: who is the registered owner, what the contract says, whether the person who left can still sign in. A reviewer sets it with the evidence. See how we rate findings.

Can I share the result?

Yes. Save it as a PDF with the name of the company: every gap with its rating, why a buyer cares and the first step, what is in order and what was not answered. Your browser makes the PDF, so nothing is uploaded. It suits the owner, the board or a data room.

What should I do with the result?

Fix the High items first, while the people involved are easy to reach. Before a sale, a red-flag memo checks the documents and the accounts behind each answer and puts a cost and a time to fix next to every gap, and sale preparation closes them before a buyer looks. For the dates in your software, use the stack check.

Next step

Gaps to close before a sale?

Tell us about the company and the timeline. We reply within one business day.