5 Contract Red Flags That Can Bankrupt a Freelancer

Most freelancers lose money not because they charge too little, but because they signed the wrong contract. A single bad clause buried on page four can wipe out months of income, hand over your intellectual property, or lock you out of your own industry.

The worst part: these clauses are standard in contracts that clients send over every day. They look normal. They sound reasonable. And by the time you realize what you agreed to, you're already on the hook.

Here are five contract clauses that have cost real freelancers real money, how to spot them, and what to demand instead.

1. The IP Ownership Grab

The clause usually reads something like: "All works, inventions, and intellectual property created by Contractor during the term of this Agreement shall be the sole property of the Client."

Read that again. During the term. Not "under this agreement." Not "related to this project." During the term.

If you sign a six-month retainer with this language, anything you build, write, design, or code during those six months belongs to the client. That side project you're building on weekends? Theirs. The template system you developed on your own time? Theirs. The SaaS app you've been working on for a year that you happened to update one Saturday? A lawyer could argue that's theirs too.

This is the difference between work-for-hire (they own what they paid you to create) and blanket IP assignment (they own everything you create while under contract). Work-for-hire is normal. Blanket assignment is a trap.

What this costs: Consider a UX designer who signs a retainer with a startup that includes blanket IP assignment language. During the engagement she builds a Figma component library on her own time, planning to sell it as a product. The startup's legal team claims ownership. She loses the product she was building and has to spend on a lawyer to fight it. This pattern happens often enough that it's worth reading every retainer twice.

What to demand instead: Narrow the IP clause to deliverables specifically described in the scope of work. Add a carve-out: "Contractor retains all rights to pre-existing work, tools, and any work created outside the scope of this Agreement." If they push back, that tells you everything you need to know.

2. The Non-Compete That Kills Your Career

Non-competes in freelance contracts are more common than most people realize, and they can be devastating. Unlike a full-time job where you're getting a salary, benefits, and stock options in exchange for exclusivity, a freelance non-compete asks you to give up your ability to earn a living as an independent contractor in exchange for... one project.

Here's a real scenario: A web designer signs a contract with a marketing agency that includes a non-compete clause preventing them from doing design work for "any competing business" within 100 miles for 24 months after the contract ends. The project pays $8,000. The non-compete effectively bans them from working with any other agency, any direct client who could have gone to an agency, and arguably any business that has a website. For two years. In their city.

What this costs: That $8,000 project just cost you 24 months of income. If you typically bill $6,000/month, that's $144,000 in potential lost revenue. Even if the clause is unenforceable in your state (many are), fighting it still costs real money in legal fees and months of stress.

What to demand instead: Strike the non-compete entirely. If the client insists, negotiate it down to a non-solicitation clause instead, which only prevents you from poaching their specific clients, not from working in your field. If they absolutely won't budge, demand the scope be narrowed to a specific niche (not your entire industry), the geography reduced, and the duration cut to 3-6 months max. And charge a premium for the restriction.

3. The Unlimited Revision Trap

The clause says: "Client shall be entitled to revisions until fully satisfied with the deliverables."

That's a blank check written against your time. There's no definition of "satisfied." There's no limit on rounds. There's no mechanism to prevent the client's CEO's spouse from jumping in at round seven with "a totally different direction."

Here's the math that makes this dangerous: You quoted $3,000 for a brand identity project, estimating 40 hours of work. The client approved the initial concepts, then requested changes. And more changes. By revision eight, you've spent an additional 20 hours. At your $75/hour rate, that's $1,500 of uncompensated labor. Your effective rate just dropped from $75/hour to $50/hour. By revision twelve, you're working for $37/hour and resenting every email notification.

What this costs: On a $5,000 project, unlimited revisions routinely add 30-60% in uncompensated time. That's $1,500-$3,000 in free labor. Across four projects a year with this problem, you're losing $6,000-$12,000 annually.

What to demand instead: Cap revisions explicitly. Two to three rounds is standard. Define what constitutes a "round" (one consolidated set of feedback, not a rolling stream of Slack messages). After the included rounds, revisions bill at your hourly rate. Put the number in the contract. No ambiguity.

4. No Kill Fee (Or: How to Work for Free)

You're three weeks into a five-week project. You've completed the research phase, delivered wireframes, and started development. The client emails: "We've decided to go in a different direction. Thanks for your work so far."

If your contract doesn't include a kill fee (also called a cancellation clause or termination fee), you just worked three weeks for nothing. The clause that allows this usually reads: "Either party may terminate this Agreement at any time with 14 days written notice." Clean. Simple. And it means the client can walk away after you've invested significant time, materials, and opportunity cost.

What this costs: On a $10,000 project that gets killed at the 60% mark, you've done $6,000 worth of work. Without a kill fee, you recover $0 of the unbilled portion. You've also turned down other projects during this period. The true cost isn't just the unpaid work -- it's the revenue you could have generated elsewhere.

What to demand instead: A proper kill fee protects you for work completed and compensates for the disruption. Standard structures look like this: payment for all work completed to date, plus 25-50% of the remaining contract value as a cancellation fee. On that $10,000 project killed at 60%, you'd receive $6,000 for completed work plus $1,000-$2,000 as a kill fee on the remaining $4,000. You should also retain rights to all unpaid work -- if they didn't pay for it, they don't own it.

Some freelancers also structure milestone-based payments so that each phase is paid upon completion. This doesn't replace a kill fee, but it reduces your exposure. If you've been paid through milestone three and they cancel before milestone four, your loss is limited.

5. Liability Without a Cap

This clause is the sleeper. It doesn't look dangerous until something goes wrong: "Contractor shall indemnify and hold harmless Client against any and all losses, damages, and expenses arising from Contractor's services."

"Any and all." No ceiling. No limit. If your work somehow contributes to a client losing a $500,000 deal, they could come after you for the full amount. You built a $5,000 website and a security vulnerability leads to a data breach? Under unlimited liability, you're potentially on the hook for damages that dwarf your fee by orders of magnitude.

What this costs: A freelance developer built a $12,000 e-commerce integration. A bug in the payment flow caused duplicate charges to 200+ customers over a weekend. The client's total exposure was around $45,000 in refunds, chargebacks, and fees. The contract had no liability cap. The client's attorney sent a demand letter for the full $45,000. The developer settled for $18,000 -- $6,000 more than the entire contract was worth.

What to demand instead: Cap your liability at 1x to 2x the total contract value. On a $12,000 project, your maximum liability would be $12,000-$24,000. This is standard practice and any reasonable client will accept it. Also, exclude consequential and indirect damages (lost profits, lost business opportunities) from your liability entirely. You're responsible for fixing your work, not for insuring their entire business.

You should also carry professional liability insurance (errors and omissions). Policies for freelancers start around $500-$1,000/year and cover exactly these scenarios. It's cheap relative to one bad claim.

The Risk Changes by Craft

The same five red flags show up across freelance work, but the practical damage changes depending on what you do.

For designers, watch the language around concepts, drafts, and portfolio rights. A client should own the final approved deliverables they paid for, not every rejected logo concept, wireframe exploration, or visual direction you created along the way. If the contract says the client owns "all concepts, drafts, and materials prepared in connection with the project," you can lose work that should still belong to you. Add language that limits ownership to final approved deliverables and keeps portfolio display rights explicit.

For developers, protect pre-existing code, reusable libraries, and your warranty window. A broad IP clause can swallow utilities, hooks, starter kits, and internal tools you use across projects. A sloppy warranty clause can also leave you on the hook for bugs long after delivery, even after the client has changed the codebase. Name your pre-existing code and reusable tools in the agreement, carve them out of the IP transfer, and cap the post-delivery bug-fix period to a clear 30 to 90 days.

If a client refuses those two boundaries, the problem is not the wording. The problem is the client.

Before You Sign Anything

Every one of these clauses exists in contracts being sent to freelancers right now. They're not always malicious -- sometimes the client's lawyer used a template without thinking about the freelancer's side. But intent doesn't matter when you're the one losing money.

The fix is straightforward: read every contract line by line before you sign. Flag anything that gives the client unlimited rights, unlimited revisions, unlimited liability, or the ability to walk away without paying. Negotiate the specific language. If the client refuses to negotiate basic protections, that's a client who will cause problems.

Tools like Inkvex exist specifically because most freelancers aren't contract lawyers and shouldn't have to be. But whether you use a tool or read every clause yourself, the principle is the same: the thirty minutes you spend reviewing a contract can save you thousands of dollars and months of headaches. If a client asks you to sign via DocuSign, understand the difference between contract review and e-signing before you click.

Frequently Asked Questions

What clauses should every freelance contract include? Every freelance contract should include: a clear payment schedule with specific due dates, a kill fee or cancellation clause (typically 25–50% of remaining contract value), an IP ownership clause that grants rights only upon full payment, a defined revision limit, a liability cap (usually 1x–2x the total contract value), and a termination clause specifying notice period and what happens to work in progress.

What is a kill fee in a freelance contract? A kill fee, also called a cancellation fee or termination fee, is the payment owed to the freelancer if the client cancels the project after work has begun. A standard kill fee covers all completed work plus 25–50% of the remaining unbilled amount as compensation for lost opportunity. Without a kill fee, a client can terminate at any time and you receive nothing for work in progress or the revenue you turned down to take the project.

What is a reasonable liability cap for a freelancer? Standard practice is to cap your liability at 1x to 2x the total contract value. On a $15,000 project, that means your maximum exposure is $15,000–$30,000. You should also exclude consequential and indirect damages (lost profits, lost business opportunities) from your liability entirely. Never sign a contract with unlimited liability, one technical error could expose you to damages that dwarf your fee by orders of magnitude.

What does "work for hire" mean in a freelance contract? Work for hire means everything you create during the engagement is owned by the client from the moment of creation, not when they pay you. This includes first drafts, unused concepts, source files, and any creative variations you produce. The danger is that the client can stop paying mid-project and still legally own all your work. Always add a clause stating that IP transfers only upon receipt of full payment.

What should a freelance contract say about revisions? Specify a clear number of revision rounds (typically 2–3) included in the project price, and define what counts as a revision versus a new scope request. Without this, "unlimited revisions" becomes the de facto standard and clients can demand changes indefinitely with no additional payment. The clause should also define what triggers revision round 2, and what happens if the client misses a feedback deadline.

Your contract is either protecting you or exposing you. There's no middle ground.