Alex is Sprintlaw's co-founder and a legal technology leader. He holds law and media degrees from the University of Sydney and has been recognized by Australasian Lawyer, Lawyers Weekly and the Sydney Young Entrepreneur Awards for his work building Sprintlaw and improving access to business legal support.
Yes, if you're paying someone outside your company to build your app, you usually need a written agreement that deals with both work made for hire and IP assignment.
The nuance is this: under US copyright law, payment alone doesn't automatically make your company the owner of the code. A work made for hire label can help in some situations, but it won't always be enough for software.
Most app projects should include a clear present assignment of copyright, source code, designs, documentation, inventions and related IP. That way, if you later raise funds, sell the business, bring on a technical co-founder or stop using your agency, you can show clean ownership.
Do I Need A Work Made For Hire Agreement For My App?
Yes, you should have a written agreement before your developer or agency starts work, but it shouldn't rely only on work made for hire wording.
An app is usually made up of several IP pieces, including:
- Source code and object code
- UI and UX designs
- Wireframes, prototypes and technical documentation
- Logos, icons, animations and other creative assets
- Databases, data structures and APIs
- Product names, taglines and branding
Different legal rules can apply to different pieces. Copyright under the US Copyright Act is usually the main issue for app code and designs. Trademark law under the Lanham Act may matter for your app name and logo. Trade secret law, including the federal Defend Trade Secrets Act, can matter for confidential technical know-how, algorithms and business processes.
A good software development agreement for an app brings those pieces together in one place. It should say who owns what, when ownership transfers, what happens if the developer uses pre-existing tools, and what rights your business has if the project ends early.
This doesn't have to be complicated, but it does need to be clear. Investors, acquirers and future partners often ask for proof that your company owns the core technology. A casual email chain usually won't be enough.
Who Owns App Code If I Paid A Developer?
The developer may own the code unless you have a written agreement that transfers ownership to your business.
That surprises a lot of founders. It feels logical that if you paid for the app, you should own the app. But copyright law doesn't work that way. The starting point under the Copyright Act is that the author of the work owns the copyright, unless an exception applies or there's a valid written transfer.
For an outside developer or agency, you may only have an implied license to use what they created. That can be enough to launch in the app store, but it may not be enough to:
- Modify the code without the original developer
- Move the codebase to a new agency
- Use the code in another product
- Stop the developer reusing similar components for another client
- Prove ownership during due diligence
Example: The Paid Build That Still Causes Problems
Say Maya's startup pays an agency $60,000 to build a booking app. The proposal or statement of work says the agency will deliver an iOS app, an admin dashboard and 6 months of support. It says nothing about copyright ownership.
Maya pays the full amount and launches. A year later, she wants a new team to rebuild the dashboard and reuse key parts of the original code. The agency says Maya can use the app as delivered, but she doesn't own the source code and can't hand it to another developer.
Even if Maya has a strong argument that she paid for broad use rights, the practical problem is real: the next developer, investor or buyer may not be comfortable unless there's a signed IP assignment.
Is Software Automatically A Work Made For Hire?
No, app software isn't automatically a work made for hire just because you paid for it or called it that in a contract.
Under the Copyright Act, a work made for hire generally falls into one of two buckets:
- Employee-created work: work prepared by an employee within the scope of their employment.
- Specially commissioned work: certain types of commissioned work, but only if there's a written agreement signed by the parties saying it's work made for hire.
The commissioned work category is limited. It covers specific categories such as contributions to collective works, certain audiovisual works, compilations, instructional texts, tests and a few others. App source code often doesn't fit neatly into those categories.
That means a software work for hire agreement can be useful, but it may not be enough on its own. If the work doesn't qualify as a work made for hire, the clause may fail to transfer copyright ownership unless the contract also includes a proper assignment.
For employees, the analysis can be different, especially if the app is built as part of their job. State law and the terms of your employment agreements can also affect employee inventions and IP ownership, so it's worth getting tailored advice if an employee is involved or a founders agreement is needed for a technical co-founder.
For contractors, the safer approach is usually to include both:
- A work made for hire clause, to the extent the law allows it
- A present assignment clause that transfers all relevant IP to your company
What Is The Difference Between Work Made For Hire And IP Assignment?
Work made for hire treats your company as the author from the start, while an IP assignment transfers ownership from the creator to your company.
That's the key difference. If a work truly qualifies as work made for hire, your business is treated as the copyright owner without needing a separate transfer. If it doesn't qualify, you need an assignment.
For app development, an assignment is usually the more reliable tool. Section 204(a) of the Copyright Act says a copyright transfer must be in writing and signed by the copyright owner or their authorized agent. A clear contract can satisfy that requirement.
Wording matters. A clause that says the developer will assign IP later can create a gap if the relationship breaks down before they sign anything else. Many app agreements use present-tense language, such as the developer assigns all right, title and interest in the project IP to your company.
Your agreement should also cover more than copyright. Depending on the project, you may need rights to:
- Inventions, patentable material and technical improvements
- Trade secrets and confidential information
- Design files, graphics, copy and documentation
- Domain names, accounts and credentials created for the project
- Third-party materials the developer has licensed or included
For your app name and logo, trademark rights are a separate issue. Registration with the USPTO can help protect your brand, but you still need to make sure any designer or agency transfers the copyright in the logo artwork and gives you access to the original files.
What Should An App Developer Agreement Include?
Your app developer agreement should spell out ownership, deliverables, payment, confidentiality, third-party materials and what happens if the project changes or ends.
Templates often miss the parts that matter most for software projects. A document works best when it's tailored to how your app is actually being built, who is contributing, and what your business needs to own at the end.
Fill-In Outline For Your Agreement
This isn't a finished legal document, but it gives you a useful structure to discuss with a lawyer before you use it.
- Parties: name your company and the developer or agency signing the agreement.
- Project Scope: describe the app, platforms, milestones, features and deliverables.
- Payment Terms: set out fees, deposits, milestone payments, expenses and when invoices are due.
- Work Made For Hire: state that eligible deliverables are intended to be works made for hire where allowed by law.
- IP Assignment: include a present assignment of all project IP, including code, designs and documentation.
- Developer Background IP: list any pre-existing libraries, frameworks or tools the developer will keep owning, and any software license terms.
- Third-Party And Open Source Code: require approval before using third-party code and identify any license obligations.
- Confidentiality: protect your product roadmap, business model, customer data and technical information.
- Delivery And Acceptance: explain how you test deliverables and what happens if they don't meet the agreed scope.
- Support And Maintenance: set out bug fixes, updates, response times and post-launch support.
- Termination: say what happens to unfinished work, source code, accounts and payments if the project ends.
- Warranties And Liability: include promises about originality, authority to assign IP and no known infringement.
Open source software deserves special attention. Some licenses are permissive and low-risk for many commercial apps. Others can require you to share source code or pass on license terms. Your developer should tell you what they're using before it becomes part of your product.
What If You Already Started Building The App Without An Agreement?
If work has already started, you should deal with ownership as soon as possible and before the relationship becomes strained.
First, gather what you already have. That includes proposals, statements of work, invoices, payment records, emails, chat messages, Git repository access logs, design files and any app store or cloud account records.
Then work through these steps:
- Check What Was Promised: look for any wording about ownership, source code, licensing, exclusivity or handover.
- Ask For A Written Assignment: have the developer sign a short IP assignment or updated development agreement covering past and future work.
- Confirm The Deliverables: make a list of code, designs, documentation, credentials and accounts that need to be handed over.
- Identify Third-Party Materials: ask for a schedule of open source libraries, stock assets, plugins and paid tools used in the app.
- Secure Access: make sure company-controlled accounts hold the repositories, app store listings, analytics, hosting and payment tools.
- Get Help If They Refuse: if the developer won't sign or hand over key materials, get tailored advice before making threats or withholding payment.
Try to keep the conversation practical. Many developers are happy to sign a proper assignment if the payment position is clear and the request is reasonable. If there's a dispute, written records will help you understand your options.
If you're preparing for funding or a sale, don't leave this until the final week of due diligence. Cleaning up app development copyright ownership early is usually much easier than trying to fix it when a deal is waiting.
Frequently Asked Questions
Does Copyright Registration Matter For An App?
Yes, it can. Copyright exists automatically when original code is fixed in a tangible form, but registration with the US Copyright Office can give you stronger enforcement options. To seek statutory damages and attorney's fees for most infringements, you generally need registration before the infringement starts or within 3 months after first publication. Statutory damages can range from $750 to $30,000 per work, and up to $150,000 for willful infringement.
Can I Own The App Name Too?
Yes, but that's usually a trademark issue rather than a copyright issue. Your app name, logo and brand can be protected under the Lanham Act, and many businesses apply to register key marks with the USPTO. You should also make sure the designer assigns the copyright in the logo artwork to your company.
Does An NDA Give Me Ownership Of The App?
No. An NDA protects confidential information, but it doesn't usually transfer copyright or other IP rights. You still need work made for hire and IP assignment wording in your app development agreement.
Can My Developer Reuse Code From My App?
It depends on your contract. Many developers want to reuse general know-how, tools and non-confidential components. Your agreement should draw a clear line between your project IP, which your company owns, and the developer's background IP, which they can keep using.
Key Takeaways
- Paying for an app doesn't automatically mean your company owns the code or related IP.
- Work made for hire language can help, but software often needs a separate written IP assignment.
- Your agreement should cover source code, designs, documentation, branding assets, third-party materials and confidential information.
- Open source and pre-existing developer tools should be identified before they become part of your app.
- If work has already started, you can often fix the gap with a written assignment and clear handover process.
- Clean IP ownership makes fundraising, sale discussions and future development much smoother.
If you'd like help with your app developer agreement, IP ownership clauses, code handover terms or copyright and trademark protection for your app, you can reach our team at (888) 449-8437 or team@sprintlaw.com. Where legal services are required, they're provided by licensed US lawyers at ElevateNext US, LLC, a trusted US law firm, through the Sprintlaw platform.








