Startup Shutdown Checklist: Selling Code, IP, and Other Assets Before Dissolution
Preserve your assets, verify what you own, and give every codebase, contract, domain, and dataset an approved next step before you dissolve the company.
Key takeaways
- Preserve your assets before employees leave, accounts close, or you file for dissolution.
- Verify what you own and can transfer, then give every asset an approved next step.
- Your production code may still interest technical buyers even when nobody wants the operating company, but a sale must justify the time and cost.
Preserve assets before access and context disappear
Preserve the materials a buyer would need before employees leave or you cancel company accounts.
- Assign one person to own the process and record where each asset lives, who controls it, and who can access it.
- Export repositories, engineering history, contracts, and other records from systems you plan to cancel.
- Keep administrative control of critical source-control, cloud, domain, and documentation accounts until the required records are in storage your company controls.
- Keep credentials, secrets, and restricted customer information out of general diligence materials.
Before removing access, make a controlled copy of anything you are allowed or required to retain.
Set limits for the sale process
Before you contact buyers, set a deadline and budget for the sale process. Identify the employees or contractors needed for diligence, map any board, investor, lender, creditor, or third-party approvals, and decide what minimum outcome would justify the work. When the deadline arrives, either continue with a real transaction or move the unsold assets to a backup plan.
Inventory every asset your company owns or controls
List everything your company owns, licenses, administers, or relies on, including assets that may not appear on the balance sheet. Control of an account or repository does not prove ownership, so track ownership and transfer questions separately.
| Asset | Preserve now | Possible next step | Core rights question |
|---|---|---|---|
| Codebases | Repositories, full commit history, releases, CI configuration, and setup instructions | Company transaction or separate code sale | Did your founders, employees, and contractors assign the relevant rights to your company? |
| Patents, trademarks, and proprietary methods | Registration records, invention files, and supporting documentation | Strategic sale, specialist sale, license, or approved abandonment | Does your company own the rights, and are there liens or transfer restrictions? |
| Domains and websites | Registrar access, DNS records, site exports, and analytics | Company transaction or domain sale | Is your company the registrant, and does it own the site's content? |
| Customer and vendor contracts | Signed agreements, amendments, renewal records, and contact history | Assignment, termination, or retention as a company record | Does the agreement permit assignment, and do you need consent? |
| Proprietary data | Schemas, provenance records, data dictionaries, and permitted exports | Specialist sale, license, required retention, or secure destruction | Do your privacy terms, consent, and contracts permit the planned use and transfer? |
| Documentation and operating records | Runbooks, architecture records, research, processes, and support materials | Bundle with code or other assets, retain, or destroy | Does your company own the material, and does it contain restricted information? |
| Cloud infrastructure | Infrastructure maps, configuration, deployment instructions, and billing records | Support an asset transfer, retain as records, or terminate | Can you transfer the account under the provider's terms, and what data or credentials must you remove? |
| Brand assets | Logos, design files, content, and style systems | Company transaction, brand sale, or approved retirement | What trademark, copyright, and license rights apply? |
| Hardware | Inventory, serial numbers, condition, and receipts | Employee sale, equipment buyer, donation, or liquidation | Do you own it outright, is it subject to a lien, and does it store company data? |
This inventory is a working document, not a legal conclusion. Use it to find missing records, assign owners, and prepare specific questions for your advisors.
Decide what happens to each asset
Your assets may follow different paths. Your team may join an acquirer while your code sells separately, your contracts terminate, and required corporate records remain in storage.
| Next step | When it fits | What you need to settle |
|---|---|---|
| Include it in a company sale | A buyer wants the product, customers, contracts, IP, or operating entity together | Deal structure, assumed liabilities, approvals, and included assets |
| Include it in an acquihire | A buyer primarily wants your founders or employees | Whether code, IP, data, and contracts are included or remain with your company |
| Sell or license it separately | An asset has value without your operating company | Ownership, transfer rights, buyer fit, price, and support obligations |
| Transfer, terminate, or return it | The asset is governed by a contract, lease, license, or third-party ownership | Consent, notice, account closure, and record-retention requirements |
| Preserve it as a company record | Legal, tax, contractual, or operational reasons require retention | Retention period, security, administrator, and storage cost |
| Securely destroy or abandon it | The asset cannot be sold or retained economically | Required approvals, deletion method, and proof of completion |
Before dissolution, give every remaining asset and obligation an approved next step.
Check whether an asset is ready to sell
An asset is worth marketing only when it passes five practical checks.
1. Ownership
Can you show how your company acquired the asset and the related intellectual-property rights? Repository access, possession of a file, or payment for work may not be enough.
2. Transferability
Do your contracts, licenses, privacy commitments, security obligations, liens, or consent rights restrict the sale? The answer may differ for the code, the data inside the product, and the contracts supporting it.
3. Buyer value
Does the asset solve a real problem, contain useful technical differentiation, generate revenue, hold a valuable name, or provide scarce and lawful information? What you spent building it does not determine what a buyer will pay.
4. Diligence readiness
Can a buyer understand, inspect, and use the asset without relying on knowledge that is about to leave your company? Clear documentation and a controlled diligence package make the asset easier to evaluate.
5. Wind-down fit
Is the likely outcome worth the legal cost, employee time, security work, and delay? An asset can have potential value and still be uneconomic to market during a short wind-down.
Classify each asset as sell now, preserve and investigate, or do not market. Spend your limited time on the small number of assets with real value and a clear path to transfer.
Preserve the engineering record, not just the source code
A technical buyer needs more than a bare repository. Preserve the commit history, branches, pull requests, review discussions, issues, releases, and changelogs that show how the product evolved. Include the architecture documents, runbooks, deployment instructions, incident history, CI configuration, and dependency manifests needed to understand how it operated.
Sanitized database schemas, development seed data, product requirements, and relevant customer use cases can add context without exposing production data. Verify that the exports open and that someone technical can follow the setup instructions. Keep production credentials and restricted data outside the diligence copy.
Clear ownership and transfer questions before diligence
Have your lawyers and tax advisors review the planned deal before you offer an asset for sale or give a buyer access. Start with founder, employee, and contractor IP assignments, then check open-source obligations and third-party software, data, and content licenses.
Your review should also cover customer and vendor restrictions, personally identifiable or regulated information, security obligations, liens, creditor rights, required consents, and the tax treatment and allocation of the purchase price.
An open rights question does not automatically mean you cannot sell the asset. It means you need an answer before you share or transfer it.
Get expert review before any transfer. This guide is not legal, tax, financial, privacy, or employment advice. Your requirements depend on your entity, contracts, assets, and jurisdictions.
Match each asset with the right buyer
A strategic acquirer may want your product and customer relationships. A domain marketplace may fit a name with standalone value. Equipment buyers and liquidators handle hardware. Specialist technical buyers may evaluate production code, data, and operating context.
Where DataVendor fits
At DataVendor, we help owners bring code and technical assets to AI companies that can use them. Our marketplace supports codebases, tasksets, runnable evaluation environments, and file bundles. You can also describe other potential supply through a data proposal.
We look for production code that powered a real product or internal operation and contains meaningful business logic or domain expertise. The strongest assets include commit history and engineering context, run from a documented setup, have clear ownership and licensing, and can be reviewed without exposing secrets or restricted information.
Generic scripts, public open-source code without meaningful proprietary context, and incomplete demos are less likely to support a standalone sale.
There are three ways to explore a sale with us:
- Estimate your codebase to get a preliminary value range without committing to a listing. Codebase estimation is live today; estimates for other asset types are still rolling out.
- Submit a data proposal to describe what you could supply and test for matching interest without preparing a complete marketplace listing first.
- Publish a listing when your asset, pricing, previews, and delivery details are ready for marketplace review.
An estimate, proposal, or listing does not guarantee buyer interest, a specific valuation, or a sale. Review what you can sell and our marketplace help center before choosing a path.
Prepare secure diligence and complete the transfer
Share enough for a buyer to evaluate the asset without exposing anything you have not approved.
- Create a sanitized diligence copy with API keys, credentials, private certificates, and unrelated customer information removed.
- Record who receives access, what they can view, and when that access expires.
- Name a technical contact and document every repository, file, domain, contract, and supporting record included in the deal.
- Confirm the required approvals and signatures, use deal documents reviewed by your lawyer, and revoke remaining access after the handoff.
Credentials are not an asset to deliver. Cloud accounts may also be nontransferable even when their configurations and operating records support the sale. Confirm the permitted handoff method for each provider and contract.
Account for the proceeds before you dissolve
Money from an asset sale still belongs to your company. Record who bought what, what they paid, your transaction costs, and when delivery happened. Work with your lawyers and tax advisors to understand how the sale affects liabilities, taxes, creditors, reserves, and any eventual return of capital.
Do not assume you can distribute every dollar immediately. Your company may need to pay or reserve for employee obligations, taxes, contracts, professional fees, claims, and other liabilities first.
Once you have completed the approved transfers and backup plans, move forward with dissolution under the rules for your entity and jurisdictions. For a general United States overview, see the and the , then get advice specific to your company.
Example 30-day asset-sale timeline
Thirty days is a planning example, not a universal legal or deal deadline. Adjust it to your runway, obligations, buyer interest, and advisors' guidance.
Week 1: Preserve and inventory
Secure critical access, export engineering and business records, assign an owner to every asset, and stop irreversible deletion. Build a complete inventory with a planned next step and list of open questions for each asset.
Deliverable: Preserved assets and a named owner for each decision.
Week 2: Clear rights and prioritize
Collect assignments, contracts, licenses, lien information, and consent requirements. Apply the five readiness checks and decide which assets you will market.
Deliverable: A short list of sale candidates, an approval plan, and a backup plan for everything else.
Week 3: Approach buyers and prepare diligence
Route each sale candidate to the right buyer or venue. Prepare sanitized previews, documentation, and controlled access. Set a deadline for real interest.
Deliverable: Buyer outreach, secure diligence packages, and a firm stop date.
Week 4: Complete approved transfers or use the backup plan
Finalize deals that have cleared legal and tax review. Document delivery, payment, and access changes. For anything without a viable buyer, carry out the approved retention, termination, destruction, or abandonment plan.
Deliverable: A recorded outcome for every asset before you proceed with dissolution.
Startup asset-sale FAQ
What happens to your startup's IP after shutdown?
Stopping operations does not decide what happens to your IP. You need an approved plan based on ownership, agreements, creditor rights, and the dissolution rules that apply to your company.
Can you sell code before dissolving your company?
Potentially. You need to verify that your company owns the code, has authority to approve the deal, and can meet the relevant license, contract, privacy, creditor, and tax requirements.
Can an unprofitable startup still sell assets?
Potentially. Production code, proprietary methods, domains, contracts, brands, and other assets may have value independent of profitability. Your historical investment does not guarantee market value or a buyer.
What should you do with source code during shutdown?
Preserve the repository and its engineering record before access ends. Confirm ownership, prepare a sanitized diligence copy, and decide whether the code belongs in a company transaction, separate asset sale, required archive, or approved destruction plan.
What if nobody wants to buy your assets?
Use the backup plan for each asset. You may need to retain required records, terminate accounts and contracts, return third-party materials, securely destroy restricted information, or abandon an asset with the right approval and documentation.
Should you give a potential buyer direct repository access?
Not automatically. Start with controlled, sanitized materials. Grant broader access only after you have reviewed the ownership, confidentiality, security, and diligence terms.
If production code is one of your strongest remaining assets, start with our free codebase estimate while the repository and its engineering history are still intact.