Asset Purchase vs Stock Purchase in a Startup Acquisition

Asset purchase vs stock purchase: the core difference

The asset purchase vs stock purchase decision determines what a buyer actually owns after closing. In an asset purchase, the buyer acquires selected assets of a business, such as code, domains, trademarks, customer contracts, and accounts, while the seller's legal entity stays with the seller. In a stock purchase (or share purchase, or a purchase of membership interests in an LLC), the buyer acquires the entity itself, and with it everything the entity owns and owes.

That one difference drives most of the negotiation that follows: which liabilities transfer, how contracts and accounts move, how much paperwork closing requires, and how each side is taxed. For small startup and SaaS acquisitions, structure is usually agreed in the letter of intent, and changing it later can reopen price.

This guide is general information, not legal or tax advice. Entity type, jurisdiction, contracts, and each party's tax position all affect the right answer, and the consequences can be significant. Involve a lawyer and a tax adviser before agreeing structure.

Side-by-side comparison

What the buyer gets

Asset purchase: only the assets and liabilities listed in the agreement.
Stock purchase: the whole entity, including all assets, contracts, history, and liabilities, known and unknown.

Liabilities

Asset purchase: the buyer generally takes on only liabilities it expressly assumes, although some liabilities can follow assets by law.
Stock purchase: liabilities stay with the entity, which the buyer now owns. Protection comes from representations, warranties, indemnities, and escrow.

Contracts and accounts

Asset purchase: each contract, license, and account must be assigned or recreated, which may need third-party consent.
Stock purchase: contracts usually stay with the entity, but change-of-control clauses can still require consent.

Paperwork at closing

Asset purchase: more transfer documents (assignments, account migrations, IP assignments).
Stock purchase: fewer transfer documents, but more diligence on the entity's history.

Taxes (U.S., simplified)

Asset purchase: buyer and seller allocate the price across asset classes; the buyer gets a cost basis in the assets.
Stock purchase: the seller usually sells a capital asset; the buyer inherits the entity's existing tax basis in its assets, unless a special election applies.

Who usually prefers it

Asset purchase: often buyers of small businesses.
Stock purchase: often sellers, particularly of corporations.

These are tendencies, not rules. Plenty of deals go the other way.

Liabilities: the main reason buyers prefer asset deals

In a stock purchase, the buyer steps into the entity's shoes. Unpaid taxes, past privacy violations, contractor claims, unpaid sales tax, disputes with former co-founders, and anything else the entity did before closing remain the entity's problem, and therefore the buyer's. Representations, warranties, indemnities, and escrows shift some of that risk back to the seller, but only as far as the seller can and will pay.

In an asset purchase, the buyer can choose which liabilities to assume, often limited to obligations under transferred customer contracts after closing. That is why buyers of small, owner-operated software frequently push for asset deals: the entity's history may be poorly documented, and indemnities from an individual seller are only as good as that individual's finances.

The protection is not absolute. Depending on jurisdiction and facts, some liabilities can follow the assets (for example, under successor-liability doctrines or certain tax rules). Diligence still matters in an asset deal. Our buyer due diligence guide covers what to check.

Deferred revenue deserves attention in either structure. If customers prepaid annual plans to the seller, the buyer will deliver service it was not paid for. Deals often address this with a price adjustment.

Contracts, accounts, and transferability

For SaaS businesses, transferability is often the practical deciding factor.

In an asset purchase, every contract and account that matters must be moved:

Customer contracts: many standard click-through terms permit assignment in a sale, but negotiated enterprise contracts may require consent.
Payment processors: Stripe, for example, asks the existing owner to contact Stripe Support before transferring an account after a sale, so it can confirm which information needs updating (payout bank account, legal business name, tax ID, and owner email), and treats acquisitions by an entity in another country differently (Stripe Support). Check each provider's process during diligence; see integrations for the providers RevenueBug supports.
App stores: Apple's app transfer process moves an app between developer accounts while keeping reviews and ratings, but it has criteria and side effects, such as Apple Pay merchant IDs not transferring (Apple Developer).
Vendors and APIs: some API terms prohibit assignment without consent, and some pricing is tied to the original account.
IP: code, trademarks, and domains need written assignments, and contractor IP assignments should already run to the seller.

In a stock purchase, most of these stay put because the entity that holds them does not change. That is a real advantage when the business depends on hard-to-move contracts, licenses, or accounts. But contracts with change-of-control clauses may still require consent or allow termination, so they need review either way.

Tax differences (U.S. overview)

Tax is often the reason sellers and buyers disagree on structure. The following is a simplified U.S. overview; other countries work differently.

Asset purchase

The IRS explains that the sale of a business usually is not a sale of one asset; instead, each asset is generally treated as sold separately for gain or loss, and the residual method must be used for any transfer of a group of assets that constitutes a trade or business (IRS, “Sale of a business”). Different assets produce different tax characters. For example, the IRS notes inventory produces ordinary income or loss, while capital assets produce capital gain or loss.

Buyer and seller each generally report the allocation on Form 8594 when goodwill or going-concern value attaches, or could attach, to the assets (IRS, About Form 8594). The Form 8594 instructions group assets into seven classes, with Class VI covering section 197 intangibles other than goodwill and going-concern value, and Class VII covering goodwill and going-concern value (IRS, Instructions for Form 8594). For a software business, most of the price usually lands in intangibles and goodwill.

For buyers, a cost basis in acquired assets can produce amortization or depreciation deductions. For sellers, the allocation affects how much gain is capital versus ordinary. Because their interests can conflict, the allocation should be negotiated before signing, not left to the tax returns.

A further wrinkle for C corporations: in an asset sale, the corporation recognizes gain, and shareholders may be taxed again when proceeds are distributed. That double-tax risk is a common reason C-corporation sellers prefer stock deals.

Stock purchase

The IRS notes that corporate stock sales usually produce capital gain or loss for the seller (IRS, “Sale of a business”). The buyer generally inherits the entity's existing tax basis in its assets, which can mean smaller future deductions than an asset purchase would provide.

For some corporate targets, the tax code allows elections that treat a qualifying stock purchase as a deemed asset purchase for tax purposes. Under Internal Revenue Code section 338, the target can be treated as having sold its assets and as a new corporation that purchased them (26 U.S.C. § 338, Cornell LII). These elections have specific eligibility rules and consequences and are a matter for tax advisers.

For LLCs and partnerships, the analysis differs again. The IRS notes partnership interests are generally treated as capital assets, but the portion of gain attributable to unrealized receivables or inventory is ordinary (IRS).

Which structure is common for small SaaS deals?

For small, owner-operated software businesses, buyers often favor asset purchases because:

the seller may run several products from one entity and only one is for sale;
the entity's records and liabilities may be hard to verify;
the buyer wants a cost basis for tax purposes;
many key assets (code, domains, standard customer terms) can be transferred without consent.

A stock purchase becomes more attractive when:

important contracts, licenses, or accounts cannot be assigned easily;
the seller is a C corporation and asset-sale taxes would be costly;
the entity is clean, well documented, and dedicated to the product;
the buyer is comfortable relying on representations, warranties, indemnities, and escrow.

Worked example

Consider an illustrative case. A founder runs two products from one LLC and wants to sell one, a $15,000-per-month SaaS. The buyer proposes an asset purchase of that product: code, domain, trademark, customer list, and the payment account. The LLC keeps the other product, its cash, and its pre-closing liabilities.

During diligence, the buyer learns that one enterprise customer contract prohibits assignment without consent, and the payment processor requires a support-led ownership change. The parties respond by making the customer's consent a closing condition, scheduling the payment-account migration before closing, and agreeing a price adjustment for annual plans prepaid to the seller. They agree the tax allocation across asset classes, with each side's adviser, before signing.

A stock purchase would not have worked here, because the LLC owns another product. That is common in micro-SaaS.

Mistakes to avoid

Leaving structure open in the LOI and fighting about it after diligence starts.
Assuming an asset purchase removes all liability risk.
Ignoring change-of-control clauses in a stock purchase.
Forgetting to agree the tax allocation before signing.
Not checking whether payment and app-store accounts can transfer.
Overlooking deferred revenue on prepaid annual plans.

For the wider process, see how to sell a SaaS business and how to buy a SaaS business.

Frequently asked questions

Which is better for the buyer, an asset or stock purchase?

Buyers often prefer asset purchases because they choose which liabilities to assume and may get a stepped-up tax basis. But if critical contracts or accounts cannot be transferred, a stock purchase may be more practical. It depends on the business and the buyer's tax position.

Which is better for the seller?

Sellers often prefer stock sales because they are cleaner exits and usually produce capital gain treatment. For C corporations, an asset sale can create two layers of tax. LLC and S corporation sellers face different considerations, so get tax advice.

Do customer contracts transfer automatically in an asset purchase?

No. Each contract must be assigned, and some require the customer's consent. Standard online terms of service often allow assignment in a business sale, but negotiated contracts may not. Review them during diligence.

Can a buyer change from a stock deal to an asset deal after the LOI?

Yes, if both sides agree, but it often changes the seller's tax result and may lead to renegotiating price. It is better to settle structure in the LOI.

What is Form 8594?

It is the IRS Asset Acquisition Statement. Both buyer and seller of a group of assets making up a trade or business generally file it to report how the price was allocated among asset classes, when goodwill or going-concern value attaches or could attach.

Does RevenueBug help structure the deal?

No. RevenueBug publishes payment-provider-verified revenue profiles and relays private buyer inquiries for startups marked for sale. It does not provide legal or tax advice, broker deals, or transfer businesses.