Intellectual property clauses are the most dangerous part of any freelance contract — and the most misunderstood. Sign the wrong IP clause and you could lose the right to use your own code libraries, design templates, or even display the work in your portfolio. Here's what you need to know.
The three buckets of IP in a freelance engagement
Every piece of work you produce falls into one of three categories:
- Work Product (the client gets this)
This is what the client hired you to create: the design files, the codebase, the copy, the brand assets. In most contracts, you assign ownership of the Work Product to the client — and that's usually fine. The key protection: IP assignment should be conditional on full payment. No payment = no transfer. This single sentence in your contract prevents the most common startup horror story: delivering the work and never getting paid while the startup uses your output to raise money.
- Background IP (you keep this)
These are the tools, frameworks, templates, code libraries, design systems, and methodologies you developed before the engagement — and that you'll use again after it. Background IP is yours, and the contract should say so explicitly. Without this clause, a client could argue that your reusable React component library is now theirs because it was used in their project.
A strong Background IP clause says something like: "Freelancer retains all rights to pre-existing materials, tools, frameworks, and methodologies. To the extent Background IP is incorporated into Work Product, Client receives a non-exclusive, perpetual license to use it — but Freelancer retains ownership."
- Portfolio Rights (you need these)
Can you show the work you did? Put it on your website? Mention the client's name? Many freelancers assume the answer is yes. Many contracts say no — or, more commonly, say nothing, which is just as bad when a founder decides they don't want their pre-launch product design on your Dribbble.
A portfolio rights clause should say:
You can display the work in your portfolio after the product launches publicly (or after X months if it never launches)
You won't disclose the client's confidential information
For pre-launch startups, you'll defer portfolio display until their public launch (with a reasonable deadline — say, 12 months)
If a startup refuses to include portfolio rights, ask why. If the reason is legitimate competitive sensitivity, negotiate a delayed display. If the reason is "we don't want anyone to know we used freelancers," that's a red flag about how they'll treat you generally.
The open-source question
If you use open-source components in the client's work, make sure your contract doesn't inadvertently require you to open-source the client's proprietary code. A simple clause: "Freelancer may use open-source components in delivering Services, provided such use does not impose licensing obligations on Client's proprietary code." This protects both of you.
What happens when the engagement ends badly
If the startup runs out of money, cancels the project, or refuses to pay: who owns the work you did? Without a clear IP clause, the answer is legally messy. With one, it's straightforward: if they haven't paid, they don't own it. The IP stays with you until payment clears.
This is why "payment is a condition of IP transfer" is the most important sentence in your contract. Don't remove it, no matter how much the founder says "our lawyer needs clean IP assignment for the investor." Clean IP assignment is fine — after clean payment.
When to get a real lawyer
This guide covers the basics, but IP law varies by jurisdiction and by the type of work. If the engagement is large ($10K+), involves patentable work, or crosses international borders, spend the money on a real IP lawyer. A few hundred dollars of legal review upfront is cheap compared to an IP dispute later.
For most startup freelance work, though, a well-written contract with clear IP terms — like the one in the Startup Freelance Contract Pack — gets you 90% of the protection you need. The remaining 10% is having the confidence to push back when a founder asks you to sign away more than is fair.
This post originally appeared on Freelancer Kit, where you can find the Startup Freelance Contract Pack — contract templates built for freelancers who work with startups.
Top comments (0)