My Buddy Lost $8,000 Because of One Sentence in a Contract

I want to tell you about a friend of mine. We'll call him Marcus, because he asked me not to use his real name when I told him I wanted to write about this. Smart guy. Good developer. The kind of person who builds things on weekends because he genuinely loves the work.

Marcus had been freelancing for about three years when he picked up a six-month contract with a startup. The project was a custom inventory management system -- pretty standard stuff for him. The pay was decent. The team seemed great. He signed the contract, got to work, and everything went fine.

Here's where it went sideways.

The Side Project

While Marcus was working on the startup's inventory system, he was also building a personal project on his own time. It was a lightweight open-source tool for managing API rate limits -- totally unrelated to inventory management, built on evenings and weekends using his own equipment.

He'd been tinkering with it for about four months. It was getting traction on GitHub. A company reached out and offered to license it for $8,000 per year. For a side project built in his spare time, that was real money. Marcus was thrilled.

Then the startup's lawyer sent him a letter.

The Sentence

Buried in section 9.2 of his contract, between a paragraph about confidentiality and another about non-solicitation, was this:

"All inventions, works of authorship, developments, and discoveries conceived, created, or reduced to practice by Contractor during the term of this Agreement, whether or not related to the Services, shall be the sole and exclusive property of the Company."

Read that again. Whether or not related to the Services.

That's the sentence that cost Marcus $8,000. Actually, it cost him more than that -- it cost him the entire project. The startup claimed ownership of his API rate-limiting tool because he built it "during the term" of the agreement. It didn't matter that it had nothing to do with their inventory system. It didn't matter that he built it on his own laptop, on his own time, using his own ideas.

The contract said anything he created while he was under contract belonged to them. And he'd signed it.

How It Played Out

Marcus pushed back. He argued that the tool was completely unrelated to the work he was doing for the startup. He showed timestamps proving he only worked on it outside of business hours. He demonstrated that the tool used none of their code, none of their systems, and none of their proprietary information.

None of that mattered. The contract didn't say "related inventions." It said "all inventions." The language was intentionally broad, and it was unambiguous.

Marcus talked to a lawyer. The lawyer's advice was straightforward: you can fight this, but it'll cost you more than the $8,000 in legal fees, and based on the contract language, you'll probably lose.

So Marcus walked away from his own project. He couldn't license it. He couldn't continue developing it publicly. The startup, to their credit, never actually did anything with the tool -- they just didn't want the liability of a contractor claiming independent ownership of something built "during the term." But Marcus lost the licensing deal, the open-source project went dormant, and four months of weekend work evaporated.

Why This Happens More Than You Think

Marcus isn't unusual. A 2023 survey by the Freelancers Union found that 34% of freelancers who signed contracts with IP assignment clauses did not fully understand the scope of what they were assigning. And the broadest clauses -- the ones that claim ownership of "all work" during the engagement, not just project-related work -- appear in roughly 1 in 5 freelance contracts.

These clauses are especially common in tech, where the line between "work for the client" and "personal side project" can be blurry. But they show up in creative fields too. Designers who create personal art during an engagement. Writers who maintain a blog. Photographers who shoot personal work on weekends. If the contract says "all work" and doesn't carve out personal projects, you're taking a risk.

The frustrating part is that most clients don't even want your side projects. They put broad IP language in their contracts because their lawyer recommended it as a protective measure. The startup that claimed Marcus's tool probably didn't care about API rate limiting. But once the clause was in the contract, their legal obligation was to enforce it or risk setting a precedent.

The Three Words That Would Have Saved Him

Marcus's contract was missing a personal work carve-out. That's a clause -- usually just a sentence or two -- that says something like:

"Notwithstanding the foregoing, the IP assignment in this section does not apply to inventions or works created by Contractor entirely on Contractor's own time, using Contractor's own equipment, that are unrelated to the Company's business or the Services provided under this Agreement."

Three key phrases: own time, own equipment, unrelated to the services.

California actually has this protection built into state law (California Labor Code Section 2870). Even if the contract doesn't include a carve-out, California employees can't be forced to assign unrelated personal inventions. But most states don't have that protection, and independent contractors in most jurisdictions are subject to whatever the contract says.

If you're a freelancer working in any state other than California, you need that carve-out in writing. Don't assume it's implied. Don't assume the client will be reasonable about it later. Get it in the contract.

What Marcus Does Differently Now

I asked Marcus what he changed after this experience. His answer was pretty simple:

He reads every IP clause, word by word. Not just the scope of work. Not just the payment section. The IP clause. Every time.

He asks for a personal work carve-out in every contract. He has a standard paragraph he proposes, and he's never had a client refuse it. Most clients are happy to add it because they don't want your side projects anyway -- they just need the language to say so.

He keeps a dated log of his personal projects. Timestamps, commit histories, screenshots. If there's ever a question about when something was created or what resources were used, he has documentation.

He runs every contract through ClauseShield before signing. His words, not mine: "It takes thirty seconds and it would have caught that clause immediately. I felt stupid for not having something like this before."

Don't Be My Buddy

Marcus is fine. He learned an expensive lesson and adjusted. But he didn't have to learn it the hard way, and neither do you.

The next time someone sends you a contract -- whether it's a six-month engagement or a quick project -- don't just check the pay rate and the timeline. Find the IP clause. Read it carefully. Look for the words "all," "whether or not related," and "during the term." Those are the red flags.

And if you're not sure what you're looking at? That's what ClauseShield is for. Upload the contract, and in about 30 seconds you'll see every IP-related clause flagged and explained in plain English. It'll tell you if the scope is too broad, if you're missing a personal work carve-out, and if there's language that could put your side projects at risk.

One sentence cost Marcus $8,000 and a project he loved. Don't let the same thing happen to you.

Scan your contract with ClauseShield -- free for your first 3 reviews every month.

My Buddy Lost $8,000 Because of One Sentence in a Contract