Who Owns the Code? IP Ownership When You Hire a Development Studio

Short answer: when you hire a studio or freelancer to build your product, you own the code only if your agreement says so. A good contract states that the intellectual property (IP) in the custom code, designs and documents made for you transfers to you, usually once you have paid in full, and that you receive the source code repository and the accounts the product runs on. Without that in writing, ownership can be unclear, which can cause serious problems with investors, acquirers and future developers.

This is a practical overview for founders, not legal advice. For your specific situation, especially before raising money, have a lawyer review your agreements.

Why code ownership matters for a startup

• Fundraising. Investors expect the company to own its core technology. Unclear IP can delay or block a round.
• Acquisition. Buyers check that the company owns what it is selling.
• Switching developers. If you cannot take the code to another team, you are locked in.
• Control. Owning the accounts (hosting, domain, database, app stores) means nobody can switch off your product.

What "owning the code" should include

Ownership is more than a sentence in a contract. In practice you want:

1. An IP assignment of the custom work created for you.
2. The source code repository in an account you control, or transferred to you.
3. Admin access to every service the product depends on: hosting, domain, database, email, payments and analytics.
4. Credentials and environment settings needed to run and deploy the product.
5. Basic documentation explaining how to set it up and deploy it.

The usual structure: transfer after full payment

Most studios assign IP once the work is paid for. This protects both sides: the builder is not giving away work that has not been paid, and you receive full rights once you have. Check that the agreement says clearly when transfer happens and that there are no extra conditions.

Until full payment, the work typically remains the builder's. That is normal, as long as the transfer is automatic and complete once you pay.

Pre-existing tools and open source

Studios rarely start from a blank page. They reuse their own libraries, templates and know-how, and nearly every product uses open-source components. A fair agreement handles this explicitly:

• Pre-existing materials stay owned by the builder, but you receive a perpetual, royalty-free license to use them as part of your product.
• Open-source components remain under their own licenses, which generally allow commercial use.

This is standard. What you want to avoid is a license that can be revoked, limited to the builder's hosting, or tied to an ongoing subscription.

Accounts: the part founders forget

Code ownership is useless if the product runs on accounts you do not control. Insist that:

• The domain is registered in your name.
• Hosting, the database and email services are under your organization or transferred to it at handover.
• Payment provider accounts are yours from the start, since they hold your revenue.
• App store accounts, if any, are in your company's name.

Third-party services are usually billed to you directly, which also makes ownership clear. We list typical providers in How to choose a tech stack for your MVP.

Clauses to look for in a development agreement

• Assignment of IP in the deliverables, with the trigger (usually full payment).
• License to pre-existing materials that is perpetual and royalty-free.
• Confidentiality for both sides' non-public information.
• Delivery of source code and accounts at handover.
• Portfolio mentions: whether the builder may say they worked with you.
• Governing law and where disputes are resolved.

Red flags

• No mention of IP at all.
• Ownership that stays with the builder "until further notice."
• A license instead of ownership for custom work.
• Accounts registered only to the builder with no transfer plan.
• Code delivered only as a compiled app with no source.
• Ongoing fees required to keep using your own product.

How AI-generated code fits in

AI coding tools do not change the basic principle: the agreement between you and your builder determines ownership of the deliverables. Make sure the contract covers all work produced, however it was written, and that the builder reviews AI-assisted code for quality and licensing concerns. More on this in AI-assisted software development for startups.

A handover checklist you can use

At the end of a build, go through this list with your builder:

• Source code repository transferred to, or created in, your organization's account.
• Domain registrar login in your company's name, with two-factor authentication.
• Admin access to hosting, the database, file storage and email services.
• Payment provider account owned by your company from the start.
• Environment variables and secrets documented and stored securely.
• A short setup and deployment guide.
• A list of every third-party service the product uses, with who pays for it.
• Written confirmation that the IP assignment applies now that payment is complete.

If any item is missing, fix it before you consider the project closed. It is much harder to recover access months later.

Keep your records

Store the signed agreement, final invoice and handover confirmation together. These are the documents investors and acquirers ask for, and having them ready makes due diligence faster.

Frequently asked questions

If I pay for the work, don't I automatically own it? Not necessarily. Ownership depends on the agreement and applicable law, which is why the assignment should be written down.

Can a builder reuse my code for other clients? Your custom code should be yours after payment. Builders can reuse their own general tools and know-how, which is why a license to pre-existing materials is standard.

What should I receive at handover? The source code repository, admin access to all accounts, configuration needed to deploy, and short setup documentation.

FounderMate's ownership terms

At FounderMate, you own the custom code, designs and documents created for you once your service is paid in full, and we hand over the source code and the accounts we set up for your product. Our pre-existing tools come with a perpetual, royalty-free license to use them in your product. The details are in our Terms of Service. Start with an MVP Spec ($490) or go straight to Launch MVP ($4,900, with code handover included).