Clean IP Title Determines Whether a Spinout Can Raise

A spinout is usually an attempt to give a technology, team, or business line room to develop outside the company where it began. The common case is a project that has been built, tested, and validated but does not fit the existing company’s strategy—or would distract it from that strategy, according to Becki DeGraw. The parent may see more value in letting an interested team take the asset, build a new company around it, and return some benefit to the original business than in continuing to fund something it does not intend to scale itself.

That logic applies at many scales. Jason Calacanis points to Waymo’s separation from Google and Expedia’s origins inside Microsoft as examples of large-company spinouts. A company may want an independent valuation for a fast-growing project, or a separate equity currency with which to recruit talent. In Calacanis’s account, a venture such as a self-driving-car company may need a credible standalone upside story to compete for people against other ambitious technology companies.

Universities create another recurring form of spinout. Researchers conducting R&D may determine they have found something worth commercializing, then form a new venture around intellectual property owned by the university. The negotiation is different—the counterparty is the university rather than an operating company—but the central issue remains: on what terms does the new entity obtain the IP it needs to operate?

The business rationale does not dictate a single legal or economic structure. DeGraw stresses that spinouts are highly fact-specific. The consideration paid to the parent can be equity, cash, or a combination; more complex transactions may include milestone-based earnouts or royalties, particularly in university IP arrangements. The underlying questions are whether the original company will continue using the assets, what resources are moving with the new company, and what each side needs from the relationship after the separation.

The parent’s percentage ownership is often the most visible negotiation, but the number cannot be considered in isolation. Its equity may come with a particular class of stock, information rights, pro rata rights, a board seat, or observer rights. Those terms together determine how much influence and economic value the original company retains, Becki DeGraw says.

Jason Calacanis offers a practical benchmark rather than a universal rule: test the deal against a billion-dollar outcome. His usual starting point is for the existing company to retain roughly 20% and the new team to own roughly 80%, though he acknowledges that actual allocations can range—for example, 25/75 or 30/70—depending on whether the underlying business has revenue, losses, and other relevant characteristics. If the spinout becomes a unicorn, he argues, 20% of a billion-dollar outcome is a meaningful return to the parent. If the parent instead insists on 50% or 60%, it may leave too little ownership and upside for the departing founders to build a company around.

The concern is not merely fairness to the founders. A prospective investor will want the people expected to build the company to have enough economic stake to pursue long-term growth. DeGraw says that is the same basic question investors ask of any early-stage company. A parent’s excessive ownership can therefore create a cap table that makes a financing harder, even if the original company believes it is protecting the value it created.

Calacanis describes a related cap-table problem among startups that have already granted a large, fully vested stake to outside developers who built an early product. In his example, a company that has given 25% to the people who built the first version of an app may struggle to “clear market” with investors. He says founders can sometimes renegotiate by offering cash, a small common-stock position, and a buyback right at a stated valuation, though such efforts do not always work. The comparison is not itself a spinout structure; it is a warning that an early ownership decision can become difficult to repair once it impairs the company’s ability to raise.

There is no fixed market range, DeGraw emphasizes. The essential constraint is that the structure leave enough ownership for the new company to recruit, finance, and motivate the people expected to make it valuable.

A central early question in a spinout is who will own the intellectual property after the separation. If the parent has no continuing need for the technology, the parties may agree to a full assignment: the IP becomes the new company’s property in exchange for equity or other consideration. If the technology remains intertwined with the parent’s operations, an assignment may need to be paired with a license-back allowing the original company to continue using it. DeGraw’s point is that this analysis should begin at the outset, rather than after the parties have informally decided which business they want to create.

A license is another way to move technology into a new commercial setting without a complete transfer of ownership. Jason Calacanis describes structures in which a buyer wants a team and its technology quickly while the original corporate entity remains in place. Rather than a conventional acquisition, the parties may arrange for a global license to the technology and move the team to the buyer. Calacanis frames this as a creative response to a period when, in his view, M&A was being stifled and deals were harder to complete. He also notes that the structure can create tax complications.

DeGraw says these arrangements appear less attractive now because they bring other problems and tend to be used when they are effectively the only way to get a deal done. Still, an exclusive license can be appropriate, especially if the original company will be little more than a shell and has little reason to retain practical control of the asset.

Once ownership is settled, the parties have to document the operating dependencies that will remain between the two businesses. Calacanis’s hypothetical involving YouTube and Google’s infrastructure illustrates the distinction. A separate YouTube could not simply receive Google’s infrastructure as an asset. Instead, it might receive a defined right to use that infrastructure for a period—say, two years—after which it could remain a Google Cloud customer or move elsewhere. The point is to give the spinout an operating path without treating every dependency as property that can be permanently transferred.

The same exercise applies to transition services, costs, customers, and employees. The parties need to identify services the parent will continue providing and who will pay for them. They need to allocate customers or define how commercial relationships touching both companies will be handled. They need to decide which employees are moving, rather than assuming that a team can be informally divided after the fact.

Commercial boundaries may also be part of the bargain. Calacanis proposes that a spinout might agree not to enter the parent’s business lines for five, seven, or 10 years. DeGraw’s broader point is that license-back rights, infrastructure access, services, customer allocation, employee moves, and competitive limits are not ancillary cleanup items. They follow from the core decision about which company owns what and how the two will coexist afterward.

A newly spun-out company should expect its IP chain of title to become the first major diligence exercise in a substantial financing. If an investor is prepared to invest $20 million, that investor will want to see exactly how the technology left the original entity and whether the new company clearly owns—or has valid rights to use—the technology on which it depends, Becki DeGraw says. A spinout is not inherently problematic, she says, provided it was done correctly.

That test is why the clean exit matters as much as the new company’s formation. IP developed inside the existing company was developed subject to that company’s confidentiality restrictions. Customer information and customer lists belong to the existing entity. A spinout cannot simply designate a piece of the old business as its own without determining what assets, information, people, and rights are actually being transferred.

The stakes are especially high when the departing person was a founder, director, or other fiduciary of the old company. A board member may have a conflict of interest in negotiating a transaction with a new company they are forming. More fundamentally, DeGraw warns against deciding informally to pursue the new venture before the separation is documented. Starting to act independently before the arrangement is papered can create fiduciary-duty and confidentiality problems.

The transaction is not a quick financing document. DeGraw contrasts it with a simple $100,000 SAFE financing that might be completed rapidly. A spinout requires deeper work across corporate, IP, confidentiality, employee, and commercial issues.

Jason Calacanis compares the process to a divorce: the parties need to divide not only assets but also employees, ongoing work, and responsibilities. That makes the decision to pursue a spinout itself worth examining. A departing founder may conclude that the negotiations, paperwork, and potential ill feeling are not worth the effort. In that case, Calacanis suggests leaving and later starting a wholly new company without bringing over confidential information or IP developed at the old company.

His practical illustration is the departing developer’s laptop: return it and let the old company wipe it rather than carry it into the next venture. What a founder brings to a new company should be knowledge and experience, he says—not files, devices, or materials that blur the line between the two businesses.