What contract terms should I insist on to protect IP when hiring a custom software vendor?

Why IP ownership isn't automatic in the U.S.

Under U.S. copyright law, the creator of a work owns it by default. Software written by an independent contractor or a vendor firm does not automatically belong to you just because you paid the invoice. The "work made for hire" doctrine covers employees, not outside contractors — unless your contract explicitly says otherwise. A verbal agreement or a vague SOW is not enough.

The six contract terms you need

1. IP Assignment Clause. A clear, written statement that all code, documentation, designs, and derivative works produced under the contract are assigned to you upon creation (or at the latest upon final payment). Use language like: "Vendor hereby irrevocably assigns to Client all right, title, and interest, including all intellectual property rights, in and to the Work."
2. Work-for-Hire Designation. Where applicable under 17 U.S.C. § 101, classify the deliverables as works made for hire. Include this alongside the assignment clause — courts treat them as belt-and-suspenders protection.
3. NDA Before Scoping Begins. Require a mutual, signed NDA before sharing business logic, data models, or product specs. It should cover trade secrets, not just confidential information, to benefit from additional protection under the Defend Trade Secrets Act (DTSA).
4. Third-Party and Open-Source Disclosure. Require the vendor to list any third-party libraries, APIs, or open-source components used, along with their licenses. GPL-licensed code, for example, can impose copyleft obligations on your entire codebase if embedded improperly. Prohibit inclusion of code with incompatible licenses without your written approval.
5. Moral Rights and License-Back Waiver. Ask the vendor to waive any moral rights and confirm they are not retaining a license to reuse your code, architecture, or proprietary logic for other clients.
6. Representations and Warranties. The vendor should warrant that the work is original, does not infringe any third-party IP, and that they have the authority to make the assignment (important if they use subcontractors — require flow-down clauses so subcontractors assign rights to the vendor, who then assigns to you).

Additional clauses worth negotiating

• Escrow for source code — protects you if the vendor goes out of business.
• Non-solicitation clause — prevents poaching of your team.
• Residuals carve-out — vendors sometimes try to retain the right to reuse "general knowledge." Ensure this carve-out does not swallow your proprietary logic.

What to watch out for in vendor contracts

Many vendors present their own standard agreements. Look for phrases like "license to use" instead of "assignment," or clauses that let the vendor reuse "methodologies and frameworks" — these can quietly carve out large portions of your product. Have a U.S.-licensed IP attorney review any agreement before signing.

CodeNicely operates on an NDA-first, full IP assignment basis — clients own 100% of the IP and source code with no license-back provisions. If you're evaluating vendors, it's a reasonable benchmark to hold others to.