Software companies
Selling a failed startup's assets: code, data, domains and IP
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
A failed startup can usually sell its codebase, domains, trademarks and patents outright, but operational records such as Slack, Jira, support and email archives are better licensed than sold, because privacy limits and customer obligations travel with them. Sort every asset into sell, license, retain or delete before talking to any buyer.
Key takeaways
- Code, domains, trademarks and patents usually transfer by sale; operational records usually move by license.
- Chain of title, meaning signed IP assignments from founders, employees and contractors, decides what a buyer will accept.
- Venture lenders and investors may hold security interests or consent rights over intellectual property.
- A code sale and a records license can coexist if their exclusivity terms do not collide.
- Customer production data is usually returned or deleted, not sold.
What assets does a failed startup actually have?#
A failed startup's assets usually fall into five groups: intellectual property, brand assets, contracts, operational records, and physical or financial items. Each group transfers differently and attracts a different kind of buyer.
Operational records are the group founders most often overlook, and they need the most careful handling. They are also the group most exposed to subscription cancellations, so preserve them before anything else is sold.
- Intellectual property: source code, patents and applications, trade secrets, and proprietary models or datasets the company built itself.
- Brand assets: domains, trademarks, social handles and the product name.
- Contracts: customer agreements, reseller deals and vendor contracts, some of which can be assigned.
- Operational records: Jira and GitHub history, Slack work channels, support tickets, documentation, postmortems and email.
- Physical and financial items: equipment, deposits, refunds and receivables.
Sell or license: an asset-by-asset table#
The sale-versus-license choice follows from what travels with each asset. Code and domains carry few third-party obligations once title is clean, while records carry the privacy and confidentiality obligations of everyone who appears in them.
Read the rights column as the work to finish before an asset is listed. An asset with an unresolved check is not ready, however attractive it looks.
Trade secrets need extra care. A secret disclosed without confidentiality terms can lose its protection, so buyer diligence should run under an NDA, and data rooms should hold summaries and architecture notes rather than full code until terms are agreed.
| Asset | Usual route | Rights check before any deal |
|---|---|---|
| Source code | Sell outright, or license if the company keeps it | IP assignments from every founder, employee and contractor; open-source licenses in the repo |
| Domains and social handles | Sell | The registrant is the company, not a founder personally |
| Trademarks | Sell with the associated goodwill | Registered owner and any coexistence agreements |
| Patents and applications | Sell or license | Recorded inventor assignments and lender security interests |
| Customer contracts | Assign where permitted | Anti-assignment clauses and customer consent |
| Jira, GitHub and design history | License | Company records with secrets and customer material removed |
| Slack work channels and email | License a narrow scope, or exclude | Employee notices, privacy laws that may apply, customer NDAs |
| Support tickets | License with redaction | Customer content and personal details inside tickets |
| Customer production data | Return or delete | Customer agreements and DPAs |
Why are records usually licensed rather than sold?#
Operational records are usually licensed rather than sold because a license lets the company define permitted use, keep ownership, and attach conditions that protect the people in the records. A sale hands all of those decisions to the buyer.
A license also matches how AI developers use records. They need defined rights to train or evaluate on a scoped set with documented provenance, not ownership of the archive. Non-exclusive licenses can be granted to more than one licensee where the terms allow it, while an outright sale happens once.
For a closing company, a license needs a plan for who holds the company's rights and obligations after dissolution, such as deletion requests or audit questions from the licensee. Settle that with counsel and the wind-down officer before signing.
How to sequence an asset sale#
Sequencing an asset sale starts with title and ends with signatures, because buyers discount or walk away from assets whose ownership cannot be shown.
The exclusivity step is where deals collide. A buyer of the codebase may expect the git history, review threads and issue tracker as part of the purchase. If the company also plans to license engineering history, the purchase agreement must say what the code buyer receives and what the company keeps.
- Preserve systems and exports before cancelling subscriptions.
- Build an asset register covering every row in the table above.
- Collect IP assignment agreements and fix gaps with confirmatory assignments where people are reachable.
- Check security agreements with venture lenders and any investor consent rights.
- Get board approval for the sale process and name the signer.
- Decide exclusivity: who receives what, and what each buyer is promised.
- Run sales and licenses in parallel only if their terms do not collide.
Who typically buys each kind of asset?#
Buyers of failed startup assets tend to sort by asset type. Competitors and adjacent companies look at customer contracts, code and brand; domain investors look at short or memorable names; patent buyers look at claims that read on active markets. AI developers license operational records rather than buying them.
Wind-down firms and brokers often run the process for code, domains and patents. Records follow a different path because each license needs a rights review, privacy preparation and a documented permitted use, which a general asset auction is not set up to handle.
The paths can still be coordinated. The person running the asset sale should know which record families are under review for licensing, so that no bidder is promised the same history.
Illustrative: a construction bidding startup splits its assets#
Illustrative: a fictional construction bidding software startup closes after its last round falls through. Its board appoints a wind-down officer, who builds an asset register and finds that an early contractor never signed an IP assignment; the contractor signs a confirmatory assignment.
The domain and trademark go to a regional competitor. A larger construction software company buys the codebase and the customer contracts that permit assignment. The purchase agreement states that the buyer receives the repositories but not an exclusive right to the issue and review history.
The company then licenses its Jira issues, pull request discussions and estimating-engine postmortems on a non-exclusive basis, with secrets removed and customer bid data excluded. Customer production data is deleted, and certificates go to each customer.
How SourceX handles the records portion#
SourceX handles only the licensing of operational records; code, domain, trademark and patent sales run through counsel, brokers or the wind-down officer. Keeping the two tracks separate makes it easier to avoid promising the same rights twice.
For the records track, the SourceX five-step transaction runs from Supply through Rights, Preparation, Approval and Delivery, and each license is documented in a SourceX Evidence Packet covering where the records came from, the rights relied on, the permitted use, the privacy record and who authorized release. Large archives stay in the company's storage or ship on encrypted drives.
Frequently asked questions
Can a founder sell the domain if it was registered personally?
Only the registrant can transfer a domain, so a founder-registered domain is the founder's to transfer unless an agreement says otherwise. If the company paid for it and used it as the product address, counsel should check whether it ought to be assigned to the company first so the sale is clean.
Do buyers value code more when it comes with its history?
History can make code easier to maintain and understand, so some buyers value it. Others want only the current code. Agree explicitly whether history, review threads and issues are included, because those records may have separate value as a licensed dataset.
Can we license records after the company is dissolved?
It depends on how dissolution is handled and who holds the company's remaining rights. Some companies complete licenses before dissolution; others authorize a wind-down officer or assignee to act afterward. Plan this with counsel before the final filings.
What happens to customer data in an asset sale?
Customer agreements and privacy notices control it. Some agreements allow transfer to a successor that takes over the service; many require return or deletion. If the company is in a US bankruptcy, Section 363(b)(1) of the Bankruptcy Code may block selling personally identifiable information that a disclosed privacy policy promised not to transfer, unless the sale fits the policy or a court approves it after a consumer privacy ombudsman is appointed. Customer data is rarely appropriate for a separate AI license.
Should we sell everything to one buyer to keep it simple?
A single buyer is simpler but rarely values every asset well, and it may not be able to take records that carry privacy obligations. Splitting brand, code and records across suited buyers usually reflects each asset better, as long as exclusivity terms are mapped before signing.
Do we need a formal valuation before selling the assets?
Not always, but boards often want evidence that the process reached reasonable buyers, especially when creditors are owed money. A documented process, showing who was approached and what each offered, often matters as much as any single figure. Ask counsel what the company's situation requires.
Sources
- Under 11 U.S.C. 363(b)(1), if a debtor disclosed a policy prohibiting transfer of personally identifiable information, the trustee may not sell it unless consistent with the policy or approved by the court after appointment of a consumer privacy ombudsman. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.