Who Owns Your Startup's IP? (Founders, Employees, Contractors)

Most founders assume that because the work happened “at the startup,” the startup owns it. That assumption is wrong often enough to be dangerous. IP ownership in the United States follows specific rules that depend on who created the work and what kind of IP it is, and the gaps between those rules are exactly where startups get burned. This guide walks through who owns what, founder by founder, hire by hire, and shows you the paperwork that turns “we built it” into “we own it.” For the full roadmap, start with our Startup IP pillar guide.

Founders: your pre-incorporation IP is not the company’s yet

The first ownership gap appears before the company even exists. Founders typically spend nights and weekends building prototypes, writing code, sketching designs, and naming the product long before they file incorporation papers. Legally, all of that work belongs to the individual founders who made it, not to a company that did not yet exist.

That gap does not close on its own. When you incorporate, the company is a brand-new legal person, and it owns nothing until something is transferred into it. If a founder built the core codebase before incorporation and never formally assigned it to the company, the startup is operating on IP it does not actually own. Co-founder breakups make this worse: a departing founder who never signed an assignment can credibly claim they still own the early work they created.

The fix is a founder IP assignment (often called a technology or contribution assignment) signed at or shortly after incorporation. In it, each founder transfers to the company all the IP they created that relates to the business, including pre-incorporation work. This is usually paired with a stock purchase agreement so the founder receives equity in exchange. Doing this early, while everyone is still friendly and aligned, is far easier than untangling it later.

Employees: work made for hire, with a patent-sized exception

Employees are the one group where the default rules lean in the company’s favor, but only partway.

For copyrightable work, U.S. law treats a work prepared by an employee within the scope of their employment as a “work made for hire.” That means the employer is considered the author and owner from the moment the work is created. So when your full-time engineer writes code as part of their job, the company generally owns the copyright in that code automatically, no separate signature required.

Two cautions, though. First, “within the scope of employment” matters. Work an employee creates entirely on their own time, with their own resources, and outside their job duties may belong to them, not you. Second, and this is the big one, work made for hire applies to copyright, not to patents.

Patents follow a different and stricter rule. Under longstanding U.S. patent law, rights in an invention initially vest in the inventor, the human being who conceived it, not in their employer. The Supreme Court reaffirmed this in Board of Trustees of Stanford University v. Roche (2011): an employer does not automatically own an employee’s invention just because it was made on the job. To own the patent, the company needs the employee to assign their invention rights to it in writing. This is why a strong employment agreement does not rely on work-made-for-hire language alone; it includes a present-tense invention assignment so every patentable idea flows to the company. For more on how patents work, see our patents topic hub.

Contractors: they own it by default until they assign it

Here is the trap that catches the most startups. Independent contractors own what they create by default.

When you hire a freelance developer, a design agency, or an outside dev shop, they are not your employees, so the work-made-for-hire rule for employees does not apply to them. Copyright law starts from the premise that the creator is the first owner, and for a contractor that ownership stays with them unless something in writing moves it. Paying the invoice buys you the deliverable and, at most, a license to use it. It does not, by itself, transfer ownership.

The Supreme Court drew the employee-versus-contractor line in Community for Creative Non-Violence v. Reid (1989), using ordinary agency-law factors like who controls the work, who supplies the tools, how the worker is paid, and whether they get employee benefits. A freelancer on their own laptop, on their own schedule, paid per project and given a 1099, lands squarely on the contractor side. That classification is why the contractor, not your startup, owns the work absent an assignment.

There is also a narrow “work made for hire” route for commissioned work, but it only applies to nine specific statutory categories (things like contributions to a collective work, motion pictures, translations, and tests) and only with a signed agreement. Software and logos almost never fit those categories. So the reliable fix is the same one used for patents: a written IP assignment signed by the contractor, transferring all right, title, and interest in the work to your company. Build it into every contractor agreement before work begins.

The documents that actually fix it

Ownership in a startup is not established by good intentions or by who paid; it is established by signatures. A few core documents do the heavy lifting:

• Founder IP assignment (and stock purchase agreement). Transfers each founder’s pre-incorporation and ongoing IP to the company in exchange for equity. Sign at incorporation.
• PIIA / CIIAA for employees. A Proprietary Information and Inventions Agreement (sometimes called a Confidential Information and Invention Assignment Agreement) is the standard employee document. It does two jobs: it protects confidential information, and it includes a present-tense invention assignment so every patentable idea and copyrightable work an employee creates flows to the company. This is what closes the patent gap that work-made-for-hire alone leaves open.
• Contractor IP assignment. A clause or standalone agreement in every contractor and agency engagement assigning all IP in the deliverables to the company. The best versions use belt-and-suspenders language: the work is a work made for hire and, to the extent it is not, the contractor assigns the rights to you.

A practical drafting note: courts care about wording. Language that says a worker “hereby assigns” their rights (a present transfer) is far stronger than “agrees to assign” (a mere promise to do it later, which can leave a gap). When in doubt, have these documents reviewed by an attorney licensed in your jurisdiction.

Why investors and acquirers care more than you do

If the above feels like paperwork you can defer, here is the wake-up call: IP assignments are one of the first things sophisticated investors and acquirers check, and missing ones can kill a deal.

During due diligence for a financing round or an acquisition, lawyers comb through your IP chain of title: did every founder, every employee, and every contractor sign an assignment putting the company’s core technology in the company’s name? A single key engineer or early contractor who never signed creates a frightening question for a buyer or investor, namely whether someone outside the company can claim ownership of the product. That uncertainty can lower your valuation, trigger holdbacks, stall the deal while you chase down signatures, or scuttle it entirely. We cover this in depth in our guide on IP in fundraising and due diligence.

The hard part is that these problems are nearly impossible to fix cleanly after the fact. Once a relationship has soured, or a former contractor realizes you need their signature to close a round, your leverage evaporates and their price goes up. Clean assignments collected at the start cost almost nothing; missing ones discovered at the finish line can cost you the whole deal.

The bottom line

Owning your startup’s IP is not automatic, and it is not about who paid the bill. It is about who signed an assignment. Employees’ copyrightable work within their job is generally the company’s, but patents always need an invention assignment, contractors own their work until they assign it, and founders must transfer their pre-incorporation IP into the company. Put the right documents (founder IP assignments, PIIAs for employees, and IP assignments for contractors) in place early, use present-tense “hereby assigns” language, and you will have a clean chain of title when it matters most. Start with the Startup IP playbook for the full picture.

This guide is general educational information about intellectual property law, not legal advice, and it does not create an attorney-client relationship. IP ownership rules turn on the specific facts of your situation and can vary by jurisdiction. For advice about your startup, consult an attorney licensed in your jurisdiction.