Founder Vesting and IP Assignment: The Clauses That Matter Most to Series A Investors

Of all the legal due diligence that occurs during a Series A (first institutional venture capital funding round) financing, two areas consistently produce the most friction: founder vesting arrangements and intellectual property (IP) assignment. Both issues are straightforward to address at company formation and expensive to fix during a financing — when every week of delay costs momentum, goodwill, and sometimes the deal itself.

This post addresses what sophisticated Series A investors look for in founder vesting and IP assignment documentation, why the specific provisions matter, and what founders of technology companies — particularly embedded systems and hardware companies — should build into their founding documents from the start.

Founder Vesting: Why Investors Care and What They Want to See

Investor concern about founder vesting is straightforward: investors are buying into a company whose value depends critically on the continued contribution of its founding team. If a founder can leave the day after closing — taking fully vested equity worth millions (as recorded on the company's capitalization table, or "cap table") — with no obligation to continue building the company, the investor has funded a lottery ticket for the founder, not a going concern.

Standard founder vesting in venture-backed companies uses a four-year vesting schedule with a one-year cliff. Under this structure, no equity vests until the founder has been with the company for one year (the cliff), after which 25% vests immediately and the remaining 75% vests monthly over the following three years. This aligns founder incentives with company success over the medium term — the period during which most of the value creation in a venture-backed company occurs.

What investors find at the founding documents of technology start-ups is often quite different: founders who incorporated and issued themselves fully vested stock with no vesting schedule; founders who implemented vesting but used unusual schedules (back-weighted vesting, milestone-based vesting with subjective milestones, or vesting schedules with no cliff); or founders who implemented vesting but then accelerated it immediately upon a triggering event that has already occurred or is certain to occur.

For embedded systems and hardware companies, there is an additional wrinkle: founders who are also the named inventors on core patents. If a founder with un-vested equity and no vesting agreement leaves the company and disputes the IP assignment, the company may simultaneously face a departing key person and a challenge to the ownership of its core patents. The intersection of vesting and IP assignment is where the legal exposure compounds.

The Acceleration Provisions That Investors Scrutinize

Acceleration provisions — clauses that cause unvested equity to vest upon specified triggering events — are legitimate and common in founder agreements. They are also the provisions most likely to be negotiated hard by Series A investors. The two main types are single-trigger acceleration and double-trigger acceleration.

Single-trigger acceleration causes vesting to accelerate upon a single event — typically an acquisition or change of control. An investor acquiring the company wants the founding team to remain motivated and retained post-acquisition; a founder who is fully vested the moment the acquisition closes has no equity incentive to stay. Acquirers routinely discount their acquisition price to account for the retention packages they will need to offer founders with single-trigger acceleration. Sophisticated Series A investors will flag single-trigger full acceleration provisions as a potential drag on exit valuation.

Double-trigger acceleration requires two events to occur before acceleration — typically an acquisition followed by termination of the founder without cause within a specified period (often 12 to 18 months). This structure protects founders from being acquired and immediately fired while preserving the acquirer's ability to retain motivated founders through equity. Double-trigger acceleration is investor-friendly and is the market standard for venture-backed companies.

IP Assignment: The Chain of Title Audit

Every Series A investor's legal counsel will conduct an IP chain of title audit — tracing the ownership of the company's core intellectual property from creation through assignment to the company. What they are looking for is a documented, unbroken chain from every inventor and creator to the company. What they frequently find are gaps.

The most common gap: a founder or early engineer who contributed to the core technology before a formal IP assignment agreement was executed. In a technology company where the product is firmware, algorithms, or hardware design, this gap is existential. The company may not own its own product.

For embedded systems and hardware companies specifically, the IP chain of title audit covers multiple asset types: software and firmware (copyright and trade secret ownership); hardware designs and schematics (copyright, potentially trade secret); patents and patent applications (named inventor to company assignment); and know-how and technical documentation (trade secret ownership). Each asset type requires a documented assignment from the creator to the company.

The audit also looks at pre-existing IP — technology that a founder developed before the company was formed, potentially while employed by another company. If a founder developed core technology during prior employment, that technology may belong to the prior employer, not the founder. The prior employer's IP assignment agreement may have captured it. Investors will want to see that this risk has been identified and addressed — either through a legal opinion that the prior employer's agreement does not capture the relevant technology, or through an assignment from the prior employer, or through a redesign that avoids the potentially tainted technology.

The Contractor Problem

Technology companies routinely use contractors — freelance firmware engineers, PCB designers, software developers — particularly in the early stages when they cannot afford full-time employees. Under U.S. copyright law, work created by a contractor is not automatically a work for hire owned by the company. It belongs to the contractor unless there is a written agreement assigning it to the company.

In the embedded systems world, this means that a PCB layout created by a contract hardware engineer, a firmware module written by a freelance developer, or a device driver contributed by a consulting engineer may not be owned by the company — unless a written IP assignment agreement was executed at the time of the engagement. Investors will ask for copies of contractor agreements for every significant technology contribution. Missing agreements for significant contributors are a deal condition at best and a deal stopper at worst.

---

Attorney advertising. The information in this post is provided for general informational purposes and does not constitute legal advice. Prior results do not guarantee a similar outcome. © 2026 guibert.law