You Paid for It. That Doesn't Mean You Own It.
If you've paid a freelancer or agency to design a logo, build a website, or write custom code, there's a reasonable chance you don't legally own it — even though you paid in full and it's sitting on your own site right now.
This isn't a scare tactic. It's just how U.S. copyright law actually works by default, and it catches a lot of business owners who assumed payment equals ownership.
The default rule: the creator owns it, not the buyer
Under U.S. copyright law, the person who creates an original work — a design, a piece of code, written copy, a photograph — owns the copyright to it automatically, the moment it's created. That's true whether or not anyone paid them for it.
Paying someone for their work doesn't transfer copyright ownership by itself. What you're usually getting, unless something more specific was agreed to, is an implied license to use the work for the purpose it was obviously created for — not ownership of the underlying intellectual property.
For a lot of business purposes, that distinction never surfaces. But it matters a great deal the moment you want to do something the original arrangement didn't clearly cover: modify the design significantly, hand the files to a different freelancer to build on, use it in a new product line, or if a dispute ever comes up with the original creator.
"Work made for hire" is narrower than people assume
Business owners often assume the "work made for hire" doctrine covers this — the idea that if you paid for it, it's automatically treated as if you made it yourself. That doctrine is real, but it's narrower than most people think, especially for independent contractors and freelancers (as opposed to actual employees).
For a contractor's work to qualify as work made for hire, generally both of these have to be true:
- There's a signed, written agreement, made before or at the time the work is created, explicitly stating it's a "work made for hire."
- The work falls into one of a specific, limited list of categories defined by the Copyright Act — things like a contribution to a collective work, a translation, a compilation, instructional text, or a few other specific categories.
Here's the trap: a lot of the things small businesses commission — a custom website build, a piece of software, a logo — don't clearly fall into that statutory list. Without a written agreement and without fitting the category, "work made for hire" often doesn't apply, no matter how obviously the work was commissioned and paid for.
What actually transfers ownership
The reliable way to actually own what you paid for is a written IP assignment clause — explicit language in the contract stating the creator assigns all rights, title, and interest in the work to you, the client, upon completion or payment. This works regardless of whether the work fits the narrow "work made for hire" categories, because it's a separate, more direct legal mechanism: an outright transfer of ownership, not a reliance on hired-work status.
If your existing contracts with freelancers or agencies don't have this kind of clause — and a lot of small business engagements are handled with just an invoice, a deposit, and a handshake — you may not actually own the logo, the codebase, or the copy you paid for, however unlikely it is anyone would ever contest it.
Where this actually bites people
- Wanting to switch vendors. You want a different developer to take over and extend the code, but the original creator technically owns it and isn't cooperative.
- Selling the business. IP ownership gets scrutinized in due diligence. Gaps here can complicate or delay a sale.
- A falling-out with the original creator. Rare, but it happens — and without an assignment clause, the leverage sits with them, not you.
- Significant modification down the line. Depending on the license you actually have (even if implied), heavily modifying or repurposing the original work may exceed what you were ever granted rights to do.
What to actually do about it
- Going forward: any contract with a freelancer, designer, or developer should include an explicit IP assignment clause, not just a description of the deliverable.
- Looking backward: if you're not sure what your existing contracts actually say — or if some of your foundational assets (logo, website, core software) were built on a handshake with no written agreement at all — it's worth having a lawyer actually look at what you have, rather than assuming it's fine because nobody's raised it yet.
This is genuinely one of those things that's cheap and easy to fix proactively, and expensive and messy to untangle after the fact.
This post is for general informational purposes only and isn't legal advice. Talk to a licensed attorney about your specific contracts and IP situation.