Ask the BattleTested Lawyer: Who Owns the Work When I Hire a Freelancer?

You hired someone to build your website, design your logo, write your course, or edit your videos. You paid them. So you own what they made, right? This is the question I get more than almost any other, and the honest answer catches almost every entrepreneur off guard: probably not. After 20 years litigating intellectual property ownership disputes, I've watched founders lose the very assets their business is built on, not because they didn't pay, but because they didn't understand one rule. Let me walk you through what actually decides ownership, and why paying an invoice isn't the same as owning the work.

Why doesn't paying for the work make me the owner?

Because copyright law starts from the opposite assumption. Under the Copyright Act, the person who creates a work owns it the moment it's created — automatically, by default. The developer who wrote your code owns the code. The designer who drew your logo owns the artwork. The writer who wrote your course owns the words. Paying them for their time doesn't transfer that ownership to you. It buys you the service, not the copyright. That default catches people because it feels backwards: you commissioned it, you funded it, you're using it in your business. But the law doesn't care who paid. It cares who created, and who signed away their rights in writing. If nobody signed anything, the creator still owns it.

What's the difference between an employee and a contractor here?

It's the whole ballgame. The law recognizes work "made for hire" automatically in one narrow situation: when a true employee creates the work within the scope of their employment. Their output belongs to you because the employment relationship makes it so. But most of the people you hire aren't employees. They're independent contractors, freelancers, agencies, virtual assistants — and for them, that automatic rule simply doesn't apply. Everything a contractor creates belongs to the contractor unless a signed agreement moves it to you. So the freelancer who built your site, the VA who made your templates, the editor who cut your course: unless you have the right paperwork, they own what they made, and you're only borrowing it.

So what do I actually own without an agreement?

Usually just an implied license to use the work for the purpose you paid for — and nothing more. That means you can use the logo or the code as delivered, but you may not be able to modify it, sell it, license it, or build new products on top of it without the creator's permission. And that implied license can evaporate when the relationship sours, which most business relationships eventually do. I've seen a developer send a cease-and-desist over the code running a live app, and a designer resurface to license the "custom" logo to a competitor. The founders in those situations had paid in full and still couldn't stop it. What you own without an agreement isn't ownership. It's a fragile permission slip that the other side can revoke the day they decide to.

How does a work-for-hire agreement fix this?

It replaces the default with your choice, in writing, before the work starts. A proper agreement does three things at once. First, it states explicitly that the work is being created as work made for hire under the Copyright Act. Second — and this is the part that saves people — it includes a backup IP assignment, so that if the work doesn't legally qualify as work made for hire, the contractor still assigns all rights, title, and interest in it to you. Belt and suspenders: you're covered either way. Third, it wraps in confidentiality with real teeth, because anyone building your business assets also sees inside your business. Those three provisions, signed before anyone starts, turn "I hope I own this" into "I own this, and I can prove it."

Bottom line

Ownership of the work your business depends on is decided in advance, on paper, not by who sent the payment. The single move that protects you is having every freelancer, contractor, agency, and VA sign a real work-for-hire agreement before the first line of code or the first draft — one that combines work-for-hire language, a backup IP assignment, and confidentiality. That's exactly how The Work-for-Hire Agreement is built, with training that walks you through why each provision is there. Find it in the Contract Library. Defense wins championships.

Frequently asked questions

If I paid a freelancer, don't I automatically own their work?

No. Under copyright law the creator owns the work by default. Paying for a service doesn't transfer the copyright — only a signed written agreement does that.

Does work made for hire apply to independent contractors?

Not automatically. The automatic work-made-for-hire rule generally applies to employees acting within their employment. For contractors, you need a signed work-for-hire agreement, ideally with a backup IP assignment.

What should a work-for-hire agreement include?

Explicit work-for-hire language, a backup intellectual-property assignment in case the work doesn't qualify as work made for hire, and confidentiality provisions with real consequences.

What do I actually own if I never signed anything?

Usually just an implied license to use the work as delivered. You may not be able to modify, sell, license, or build on it — and that permission can disappear when the relationship ends.

Want to legally bulletproof your business, for free? Start with the free Legal Risk Report and find your blind spots in minutes.

About the Author — Karam Nahas, The BattleTested Lawyer. A 20-year courtroom veteran who has handled over $1 billion in deals and real litigation, Karam founded Legally Bulletproof to give entrepreneurs the same legal defense systems big companies use — without big-law prices.

Ready to lock it down? Visit the Contract Library — every contract comes with the training and a 20-year lawyer inside your business, starting as low as $197, and it's constantly updated and customized.

Educational content, not legal advice.