Most people say, "I do. I paid for it." It feels obvious. You wrote the check, you got the file, the logo is on your storefront and your business cards. Of course it's yours.

Often, it isn't.

Paying for creative or technical work and owning the intellectual property in that work are two different things, and the gap between them has cost business owners real money — sometimes during a financing round, sometimes in the middle of selling the company, and sometimes when a former contractor turns up using "your" design for a competitor. The good news is that this is one of the most preventable problems in business law. You just have to know the rule before the work starts, not after.

The rule that catches founders off guard

Under U.S. copyright law, the person who creates a work generally owns it the moment it's created. Not the person who paid for it — the person who made it. Ownership transfers to you only if the law treats the creator as working for you in a specific way, or if the creator signs something handing the rights over.

That single principle drives everything below. Whether you actually own what you paid for depends entirely on who made it and what you put in writing.

Independent contractors: the biggest trap

This is where most owners get burned, because the intuition ("I paid, so I own") is exactly backwards.

When an independent contractor — a freelance designer, a developer, a copywriter, an outside engineer — creates something for you, the contractor owns the copyright by default. You don't, even after you've paid in full. You typically have an implied license to use what you commissioned, but a license is not ownership. You may not be able to register the copyright, stop the contractor from reusing the work, or transfer clean rights to a buyer or investor down the road.

Many owners assume the phrase “work made for hire” solves this. It usually does not. Under U.S. copyright law, “work made for hire” is a narrow legal category. If the creator is an employee acting within the scope of employment, the employer may own the work from the start. But independent contractors are different. For a contractor’s work to qualify, the work must fall within one of a short list of statutory categories and the parties must expressly agree in a signed writing that it is a work made for hire. Those categories include things like contributions to collective works, parts of audiovisual works, translations, compilations, instructional texts, tests, answer materials for tests, and atlases.

Notice what is not clearly on that list: most custom software, logos, standalone websites, brand identity work, and many marketing deliverables. For those, simply labeling the project a “work made for hire” may not transfer ownership. The safer approach is to include a present assignment of all rights, plus a backup assignment if the work is later determined not to qualify as a work made for hire.

What actually transfers ownership from a contractor is a written assignment — a signed agreement in which the contractor assigns the rights to you. The strongest versions use present-tense language ("hereby assigns") so the transfer happens on signing, rather than a vague promise to assign "later" that can leave a gap.

The practical stakes are bigger than they sound. Without a proper assignment, a contractor can license the same code or artwork to someone else, including a competitor. They can also realize, right when you need clean ownership most, that they hold leverage — and ask to be paid again for the rights they never transferred.

Employees: closer, but still not automatic

Employees are friendlier territory, but "I have employees, so we own everything they make" is also too simple.

For copyrightable work — the marketing copy, the design, the code — work an employee creates within the scope of their job is generally a work made for hire, and the company owns it automatically. So far, so intuitive.

Inventions and patents are a different story. Patent rights start with the inventor, not the employer. Even for a full-time W-2 employee, the company does not automatically own a patentable invention. It owns those rights only if the employee has signed an agreement assigning them — again, ideally with present-tense "hereby assigns" language. Absent that, an employer who directed and paid for the work may be left with only a limited right to use the invention, not ownership of it. This is exactly why startups and growing companies have employees sign a Proprietary Information and Inventions Assignment agreement (sometimes called a PIIA or CIIAA) on day one.

State law adds another layer, and Colorado and New York handle it differently:

• Colorado has no dedicated invention-assignment statute. The question is governed by common law. Generally, if an employee was hired to invent or solve the specific problem at issue, the resulting invention belongs to the employer — sometimes through an implied duty to assign — while an employee who wasn't hired to invent and worked outside the scope of their duties keeps what they create. Because these lines are fact-specific, a clear written assignment is far safer than relying on a court's read of the situation.

  
  

• New York addressed this directly. Labor Law § 203-f, in effect since September 2023, makes an invention-assignment clause unenforceable as to anything an employee develops entirely on their own time, without the company's equipment, supplies, facilities, or trade secrets — unless the invention relates to the employer's actual or anticipated business or results from work the employee did for the company. New York employers should make sure their assignment language tracks that carve-out, or risk having the provision invalidated.

Agencies: the "license vs. ownership" surprise

Hiring an agency — for branding, web development, marketing — feels like the safe option. It often hides the same trap, just dressed up in a longer contract.

Two things routinely catch owners off guard. First, many agency agreements grant you a license to use the deliverables rather than transferring ownership, and some retain the right to reuse the work or assign ownership only "upon final payment" — meaning any billing dispute can leave the rights hanging. Background IP carve-outs (the agency's "pre-existing tools and frameworks") can also quietly stay with the agency, which matters if those tools are baked into your product.

Second, agencies subcontract. If the freelancer the agency hired never properly assigned their rights to the agency, the agency can't pass clean ownership to you — you can't receive what they never owned. A good agreement requires the agency to secure assignments from everyone who touches the work and flow those rights through to you.

The fix is simple: read the IP clause, confirm it says assignment (not just license), make sure the trigger isn't a payment milestone you might dispute, bound any background-IP carve-out, and require subcontractor assignments.

Why this matters more than it seems

If you never sell, never raise money, and never have a dispute, a shaky IP chain might never surface. But those are the exact moments business owners care about most — and they're where this quietly becomes expensive.

In any acquisition or financing, the buyer or investor will run diligence on your IP chain of title. They want proof that the company actually owns its logo, its product, its code, its content. Gaps don't just look sloppy; they get priced in. I've seen ownership holes lead to reduced purchase prices, money held back in escrow, last-minute scrambles to track down a contractor from years ago for a signature, and indemnity demands that follow the seller past closing. A missing one-page assignment from three years ago can hold up a seven-figure deal.

Cleaning this up before you need it is dramatically cheaper than cleaning it up under deal pressure, when the other side knows you have no leverage.

How to get it right

A few practical habits prevent nearly all of these problems:

• Get the assignment in writing before the work begins. The cheapest time to secure rights is when everyone is still motivated to work together.

• Use present-tense assignment language. "Hereby assigns" effects a transfer now; "agrees to assign" can leave a gap that has to be chased down later.

• Put employees on a PIIA. Don't rely on the work-made-for-hire doctrine alone, especially for anything patentable.

• Give contractors a real assignment clause — with a work-made-for-hire backup, a "further assurances" provision, and a defined list of deliverables — not just an invoice.

• Vet agency contracts for ownership vs. license, payment-contingent triggers, background-IP carve-outs, and subcontractor flow-through.

• Mind the state limits. In New York, make sure invention-assignment language respects the § 203-f carve-out; in Colorado, don't lean on assumptions when a clear written assignment removes the guesswork.

• Fix gaps now. If you suspect you don't have clean ownership of something important, a confirmatory assignment today is a fraction of what it costs during a transaction.

The bottom line

Paying for work and owning it are not the same thing. The default rules often favor the creator, not the business that hired them — and the difference tends to surface at the worst possible moment. A few well-drafted paragraphs, signed at the right time, are all it usually takes to make sure the work you paid for is actually yours.

At Auxo Law, I help business owners in Colorado and New York put the right agreements in place before there's a problem, and clean up ownership gaps before a deal puts them under a microscope. If you're not sure your company actually owns what it's built, that's a good question to answer now rather than later.