What is an acquihire, and does IP still matter?

An acquihire is an acquisition made primarily to hire a team rather than to buy a product, revenue, or customer base. IP still matters enormously. The team's code, models, designs, and know-how usually transfer with them, and the buyer needs clean title to whatever the target built. If assignment paperwork is missing or a founder retained rights, the buyer can end up hiring people who don't actually own the work they created.

Does the buyer own the code the team built before the acquihire?

Only if the target company properly owns it first, then assigns it. That requires signed invention-assignment agreements from every employee, founder, and contractor, plus a clean chain of title into the target. Gaps are common: a co-founder who never signed, a freelancer who built the original prototype, or open-source code with copyleft terms. The buyer should verify each link before closing, not assume the team's work automatically transfers.

Can prior-invention carve-outs let an employee keep IP the buyer wants?

Yes. Most invention-assignment agreements let an employee exclude 'prior inventions' they created before joining. If a founder listed the core technology on their Schedule A carve-out, they may personally own it, not the company. In an acquihire the buyer should review every carve-out schedule, confirm nothing critical was excluded, and get a separate assignment from any individual who holds rights the deal depends on.

Should an acquihire be structured as an asset deal or a stock deal?

It depends. Asset deals let the buyer cherry-pick the IP and leave behind liabilities, but require assigning each asset and can trigger consent or anti-assignment issues in licenses. Stock (or merger) deals transfer everything automatically, including hidden liabilities, but avoid re-assigning IP one item at a time. Many acquihires are structured as asset purchases or reverse triangular mergers; tax, liability, and IP-transfer mechanics drive the choice.

IP in Acquihires: What to Watch

How IP is handled in acquihires: assigning the team's work, prior-invention carve-outs, non-competes, and making sure the buyer gets clean title.

Quick answer: In an acquihire, a company buys a startup mainly to hire its team, but IP still matters because the team's code, models, and know-how transfer with them. To get clean title, the buyer must confirm the target actually owns what its people built — every employee, founder, and contractor signed an invention-assignment agreement, no critical technology sits inside a prior-invention carve-out, and any open-source or third-party code is accounted for. The deal then assigns the target's IP to the buyer and layers in retention, confidentiality, and (where enforceable) non-compete terms so the acquired talent — and their trade secrets — stay put.

An acquihire looks like a hiring event dressed up as an acquisition, and that framing causes buyers to underweight the IP. But the whole reason a team is worth buying is what they know how to build — and what they have already built. If the target doesn’t actually own that work, or a founder quietly kept the crown jewels, the buyer can pay acquisition prices for people who arrive empty-handed. This guide walks through the IP issues that decide whether an acquihire delivers clean, usable technology or an expensive headache.

What is an acquihire, and why does IP still matter?

An acquihire (acqui-hire) is an acquisition whose primary purpose is to hire a team rather than to buy a going business. The product may be shut down; the revenue may be trivial. What the buyer wants is the engineers, researchers, or designers — and, almost always, the technology they created along the way.

That is exactly why IP can’t be an afterthought. In a typical acquihire the buyer expects to keep:

The codebase, models, and design assets the team built.
The know-how and trade secrets in the team’s heads and repositories.
Any patents, applications, or filed IP the target holds.

The risk is that these assets don’t cleanly belong to the target — and therefore can’t cleanly transfer to the buyer. Acquihires are often small, fast, and lightly negotiated, which is precisely when diligence gets skipped and title problems slip through. The same discipline you would apply to a full acquisition applies here, just scaled to the deal. For the broader framework, see our hub guide on IP diligence for fundraising and M&A.

Does the target actually own what the team built?

This is the first question, and it is answered by the chain of title — the unbroken series of signed assignments that moves IP from the individuals who created it into the target company. U.S. copyright and patent law default ownership to the creator, not the company that pays them, unless there is a written assignment (patents) or a qualifying work-made-for-hire arrangement (copyright). So a company only owns its code because its people signed it over.

For each person who touched the technology, the buyer wants to confirm a signed Proprietary Information and Invention Assignment Agreement (PIIA) or equivalent:

Founders — the most commonly missing signatures, because early teams “just start building.”
Employees — ideally signed at hire, with a present assignment (“I hereby assign”) rather than a promise to assign later.
Contractors and freelancers — who own their work by default absent a written assignment, and who frequently built the original prototype.

Gaps here are the single most common defect in a startup’s IP. We cover how to find and fix them in IP assignment gaps, and who should own what in the first place in who owns startup IP. If a critical assignment is missing, the buyer should require the individual to sign a confirmatory assignment as a closing condition — not close and hope.

Watch out for two subtle traps. First, an old contractor agreement may promise a future assignment (“agrees to assign”) without ever transferring anything — in some readings that leaves legal title with the contractor until a separate document is signed. Second, patents have their own requirement: to be the record owner, the target must have executed assignments from each named inventor and recorded them with the USPTO (recordation is handled through the USPTO’s Assignment Center). An unrecorded or missing inventor assignment can cloud title to the very filings the buyer is counting on, so pull the assignment history for each patent and application, not just the issued certificate.

What about prior-invention carve-outs?

Even a signed invention-assignment agreement often contains an escape hatch: a prior inventions (or “prior developments”) schedule where the person lists things they created before joining and therefore do not assign to the company. It is usually an exhibit — “Schedule A” or similar — attached to the PIIA.

In an acquihire this deserves close reading. Imagine a founder who built the core algorithm as a side project, then listed it on their prior-inventions schedule when they later signed the company’s standard agreement. On paper, the company never owned the very thing the buyer is paying for — the founder does, personally.

Practical steps for the buyer:

Collect every signed agreement and its carve-out schedule, not just a representative sample.
Read each schedule for anything that overlaps the target’s core technology.
Get a separate, personal assignment from any individual whose carve-out (or missing signature) leaves them holding rights the deal depends on.

A blank or “none” carve-out schedule is good news. A schedule that describes the product’s foundational tech is a red flag that has to be cleared before money changes hands.

What about open source and third-party code?

Owning the code your team wrote is only half the picture. Modern software is assembled from open-source and third-party components, and their licenses ride along with the acquihire. Copyleft licenses like the GPL and AGPL can require you to release derivative source code; permissive licenses like MIT, BSD, and Apache 2.0 are friendlier but still carry attribution and notice obligations.

Before closing, the buyer should get a software bill of materials or dependency scan and confirm:

No copyleft component is entangled with proprietary code the buyer wants to keep closed.
All third-party libraries, APIs, and SDKs are properly licensed and the licenses survive a change of control.
Any AI or ML models were trained on data and code the target had the right to use.

Our guide on open-source licensing for startups breaks down which license terms create acquisition headaches.

How do retention, trade secrets, and non-competes work when the team joins?

Here the acquihire diverges from an ordinary asset purchase: the buyer isn’t just acquiring IP, it is absorbing the people who carry the trade secrets. Two things have to happen at once — the buyer needs the team to stay, and it needs the target’s confidential information to travel cleanly into the buyer without contaminating anyone.

On the retention side, acquihires typically use:

Retention or “golden handcuff” packages — equity or cash vesting over one to four years, often the real economic core of the deal.
New employment agreements with the buyer, including fresh invention-assignment and confidentiality terms so everything built after closing clearly belongs to the buyer.
Non-solicitation and, where lawful, non-compete covenants.

That last point is jurisdiction-critical. California voids most employee non-competes under Business & Professions Code §16600, and a 2024 addition — §16600.5, alongside the employer-notice duty in §16600.1 — makes contracts void under that chapter unenforceable regardless of where or when they were signed, reaching even out-of-state non-competes asserted against California workers, though a narrow exception exists for owners selling the goodwill of a business (§16601). We unpack this in are non-competes enforceable in California?. At the federal level, the FTC’s 2024 rule banning most non-competes was struck down by a federal court in August 2024 and is not in effect, so state law continues to govern.

Trade-secret hygiene matters just as much. Departing employees can carry a former employer’s secrets into the buyer, creating liability. The buyer should confirm the team is bringing only the target’s information, that confidentiality obligations to prior employers are honored, and that the target’s own secrets were protected by reasonable measures under the Defend Trade Secrets Act (DTSA) and applicable state law. For the protective-measures playbook, see protecting a trade secret in California and the real disputes in our trade secrets case archive. A solid confidentiality agreement remains foundational — see the NDA that holds up.

How is the deal structured — asset, stock, or merger?

The transaction structure decides how the IP actually moves, and it interacts with tax and liability.

Asset purchase. The buyer picks the specific assets — code, patents, marks, domains — and expressly assigns each. This leaves behind unwanted liabilities but requires an assignment for every asset, and anti-assignment clauses in the target’s inbound licenses may require third-party consent to transfer.
Stock purchase. The buyer acquires the target’s equity, and the company (with all its IP and its liabilities) comes along automatically. No item-by-item IP assignment is needed, but hidden liabilities transfer too.
Reverse triangular merger. A buyer subsidiary merges into the target, which survives as a subsidiary. Like a stock deal, IP stays put inside the surviving entity, which often avoids triggering change-of-control consent in licenses — a frequent reason it’s chosen for acquihires.

Small acquihires are frequently done as asset purchases (clean, selective) or as mergers when preserving in-license continuity matters. Whatever the form, the definitive agreement should carry robust IP representations and warranties — that the target owns or has rights to all IP, that it doesn’t infringe third parties, that all contributors assigned their work, and that no open-source obligations compromise the code. Those reps, plus indemnities and sometimes an escrow holdback, are the buyer’s backstop if a title defect surfaces later. See IP representations and warranties for what to demand and what a seller will resist.

An acquihire IP checklist

Before signing, work through the essentials:

Chain of title confirmed for every founder, employee, and contractor via signed present-assignment agreements.
Prior-invention carve-out schedules collected and read; personal assignments obtained where core tech was excluded.
Open-source and third-party licenses inventoried; copyleft entanglements resolved.
Patents and applications identified, with inventor assignments recorded at the USPTO.
Trade-secret protection documented (access controls, confidentiality agreements) and the team confirmed to be bringing no prior employer’s secrets.
Retention and post-closing employment terms signed, with new invention-assignment and confidentiality covenants.
Non-compete/non-solicit terms tailored to each employee’s jurisdiction — never a one-size template in California.
IP reps, warranties, indemnities, and any escrow built into the definitive agreement.

The bottom line

An acquihire is a bet on people, but the value walks out the door with them — and so does the code, the models, and the trade secrets they built. Treat the IP with the same rigor you would in any acquisition, scaled to the deal: verify the target truly owns what its team created, read every prior-invention carve-out, clear open-source and third-party licenses, and lock in retention and confidentiality on the way in. Get clean title first, then hire the team — not the other way around.

This guide is general education, not legal advice, and does not create an attorney-client relationship. Acquihire structures and non-compete enforceability vary sharply by state and by deal — consult an attorney licensed in your jurisdiction before acting.