Who owns the IP in custom-developed software?

The default depends on jurisdiction but usually the developer — not the customer — owns the copyright unless the contract expressly assigns it. In the US, "work made for hire" doctrine assigns ownership of certain works to the commissioning party, but not all software qualifies; elsewhere, an express assignment in writing is required. If you pay for custom work, you need a written IP assignment clause, not just an invoice.

What is IP indemnity and why does it matter?

IP indemnity is the supplier's promise to defend the customer — and pay damages and costs — if a third party claims the supplier's deliverables infringe their IP rights. It matters because patent-infringement and copyright claims can cost millions to defend even when meritless. Standard IP indemnities carve out customer modifications, unauthorised combinations with other products, and use outside the scope of the licence.

Why are open-source warranties important?

Open-source components come with licence obligations that can be incompatible with the customer's business model — copyleft licences like GPL can require source-code disclosure for derivative works. A supplier that silently includes such components without disclosure transfers a compliance burden the customer never agreed to. A well-drafted IP clause requires the supplier to list all open-source components and the licences they are subject to.

Intellectual Property (IP)

IP Rights · IP Clause · Intangible Property

Intellectual Property (IP) is the set of legally recognised rights over creations of the mind — copyrights, trademarks, patents, trade secrets, and related rights. In contracts, an IP clause allocates ownership of pre-existing and newly created IP, grants or withholds licences to use it, and sets who bears the risk if the IP turns out to infringe a third party's rights.

What an IP clause actually does

An IP clause answers four questions in sequence. First, background IP: who owned what before the contract began — each party keeps their pre-existing rights. Second, foreground IP: who owns material created during performance — by default the creator, but work-for-hire, consulting, and SaaS agreements often assign ownership to the customer or vendor. Third, licences: which party can use which IP, on what terms (exclusive or non-exclusive), for what purpose, in which territories, for how long. Fourth, IP warranties and indemnity: the supplier typically warrants that its deliverables do not infringe third-party IP and agrees to defend the customer against infringement claims, subject to standard exclusions (customer modifications, combinations, use outside the licence).

Why it matters

IP is often the single most valuable asset in a commercial deal, and the clause that allocates it is where deals either protect or destroy value. A customer that pays for custom software but does not get an ownership assignment cannot later port, sell, or reuse it. A vendor that warrants non-infringement without carve-outs for customer modifications can be on the hook for unlimited liability when the customer misuses the product. Get the IP clause wrong and you can lose the work product, the customer relationship, or both.

Common pitfalls

1.No distinction between background and foreground IP — pre-existing code or know-how gets unintentionally swept into an assignment clause.
2.Ownership silent or ambiguous — defaults (creator keeps the copyright) surprise customers who assumed they owned the custom work they paid for.
3.Licence grant too narrow — the customer cannot use the IP for reasonable purposes like internal training, backups, or affiliate use.
4.IP indemnity capped at a tiny multiple of fees — the downside of a patent-infringement claim dwarfs a 12-month-fee cap, leaving the customer exposed.
5.Open-source components undisclosed — the supplier ships code containing GPL or AGPL-licensed libraries without notice, triggering obligations the customer never agreed to.

Frequently asked questions

Who owns the IP in custom-developed software?: The default depends on jurisdiction but usually the developer — not the customer — owns the copyright unless the contract expressly assigns it. In the US, "work made for hire" doctrine assigns ownership of certain works to the commissioning party, but not all software qualifies; elsewhere, an express assignment in writing is required. If you pay for custom work, you need a written IP assignment clause, not just an invoice.
What is IP indemnity and why does it matter?: IP indemnity is the supplier's promise to defend the customer — and pay damages and costs — if a third party claims the supplier's deliverables infringe their IP rights. It matters because patent-infringement and copyright claims can cost millions to defend even when meritless. Standard IP indemnities carve out customer modifications, unauthorised combinations with other products, and use outside the scope of the licence.
Why are open-source warranties important?: Open-source components come with licence obligations that can be incompatible with the customer's business model — copyleft licences like GPL can require source-code disclosure for derivative works. A supplier that silently includes such components without disclosure transfers a compliance burden the customer never agreed to. A well-drafted IP clause requires the supplier to list all open-source components and the licences they are subject to.

Review IP clauses with Attorly

Upload any commercial contract and get a per-clause breakdown of IP ownership, licence scope, warranties, and indemnity carve-outs — in under 60 seconds.

Analyse the contract