When a product is built by an outside team, ownership is easy to overlook until something goes wrong: a supplier becomes unreachable, a domain expires on someone else's card, or nobody can log in to the hosting account.
The fix is simple, but it needs to happen at the start. Here is what to check.
*This article is general information, not legal advice. For contract wording, speak to a solicitor.*
Intellectual property in the code and designs
In the UK, work created by an employee in the course of their job normally belongs to the employer. Work created by an outside contractor or agency normally belongs to the contractor, unless the contract assigns it to you in writing.
So your contract should state clearly that the intellectual property in the code, designs and documentation transfers to you, usually once the relevant invoice is paid. Check also:
- Whether the supplier reuses their own existing components, and what licence you get to use them.
- That open-source packages in the project have licences compatible with your use.
The code repository
Ask for the code to live in a repository owned by your organisation, for example on GitHub, from day one. The supplier works in it as a collaborator.
This means you always have the latest code and its full history, not just a copy handed over at the end.
Design files
Design files, such as Figma files, should sit in a team or project that you own, with the supplier invited as an editor. The same applies to logos, icons, photography and fonts: keep the source files and confirm the licences cover your use.
Accounts and infrastructure
Every account the product depends on should be registered to your business, with your business email as the owner:
- Domain name registrar and DNS.
- Hosting and cloud provider.
- App Store and Google Play developer accounts.
- Payment provider, such as Stripe.
- Email sending, analytics and error tracking.
- Any AI or other API provider.
Give your supplier access as a team member with the permissions they need. Keep billing on your own payment method, so a lapsed card on someone else's account never takes your product offline.
Credentials and secrets
Passwords and API keys should be shared through a password manager or the provider's own access controls, never by email or chat. At handover, or if a supplier relationship ends, rotate the keys and remove access you no longer need.
Documentation and handover
Ask for enough documentation that another developer could take over:
- How to run the project locally and deploy it.
- Where each environment and service is, and what it is for.
- Any scheduled jobs, integrations or manual steps.
Questions to ask before you sign
- Does the contract assign the IP in the work to my business?
- Will the code be in a repository I own from the start?
- Will all accounts be registered to my business and paid by me?
- What third-party or reused components are included, and under what licences?
- What documentation will I receive at handover?
At Pipesora, the repository, design files and accounts are set up in your name from the start, and the intellectual property in the work transfers to you when the invoice is paid.
Questions about a project you are planning? Get in touch.