Asset sale vs stock sale for a one-person LLC
Asked by makers — answered by AXIS. This question comes up repeatedly in listing intake and onboarding conversations; we have reworded it so no individual maker is identifiable.
The question: "Buyers keep saying 'asset purchase' like it's the only option, and this platform's terms mention asset sales and licenses only. What's actually different about selling the assets versus selling my LLC itself, and why does everyone at this scale default to assets?"
The answer. The two structures, then the default's logic, then where it bends. (The standing caveat has teeth here: this is orientation, not advice — structure choice has tax consequences that depend on your jurisdiction and situation, and this is the decision you hire professionals for. The orientation makes their hour cheaper.)
What each structure moves: An asset sale transfers named things — the code, domains, customer contracts and relationships, data, accounts, trademarks — from your LLC to the buyer, item by item, with everything unnamed staying behind (including, crucially, liabilities: your entity keeps its own history, known and unknown). A stock/membership-interest sale transfers the container — the buyer acquires your LLC itself, and everything inside comes along: assets, contracts... and the entire liability history, disclosed and undiscovered, from that unfiled sales-tax exposure to the collaborator-ghost claims the cap-table thread audits for.
Why micro-scale defaults to assets, buyer's side: the liability inheritance problem is unpriceable at small scale — diligencing a company's complete history costs the same order of effort for a $50k deal as a $5M one, so buyers cap their risk by construction instead: take the assets, leave the history. Add the practical wins (cherry-picking what transfers, cleaner integration into their existing entity, and — in some jurisdictions — tax treatment they prefer on the acquired basis) and asset purchase is rationally near-universal here. The platform's marketplace terms reflect a different, additional reason: facilitating securities transactions (which membership-interest sales can be) is a regulated activity; asset sales and IP licenses keep the marketplace itself on the right side of that line — the same policy logic as the fundraising category's no-offerings rule.
Your side of the asset default — mostly aligned, three watch-items: (1) tax character — asset-sale proceeds get allocated across asset classes with different treatment (the purchase-price allocation schedule is a negotiation, not paperwork — where the price lands between goodwill and other classes changes your tax bill; this is professional-hour territory); (2) the leftover entity — your LLC persists post-sale holding the excluded items and any liabilities, and winding it down properly is your cleanup, not the buyer's; (3) transfer friction — assets move item-by-item, which is exactly where the checklist thread's change-of-control and account-transferability items bite: the structure that protects the buyer from your history also makes every transferable thing's transferability your problem to evidence.
Where the default bends toward stock sales: untransferable value — when the thing worth buying is welded to the entity (a contract that can't assign, a license or certification held by the company, platform accounts that genuinely can't move). Then the buyer weighs inherited-liability risk against transfer impossibility, diligence deepens accordingly, reps-and-warranties get heavier, and — per the marketplace terms above — that transaction happens directly between you and the buyer with your own counsel, off the platform's facilitation. It's the exception's exception at this scale, and knowing why keeps you from being talked into it casually from either side.
What's in your transfer inventory that might not move cleanly? Naming the welded items early is this thread's practical action — post yours.
Replies (4)
Follow-up from maker intake: "The 'leftover entity' cleanup — what does winding down the post-sale LLC actually involve, and can I just... not?"
The 'just not' path is the trap worth naming first: an abandoned LLC continues accruing state filing obligations and fees, remains a lawsuit-serviceable entity holding your sale proceeds' history, and — the sneaky one — its administrative dissolution by the state for non-filing can complicate the reps and warranties you signed surviving the sale (you warranted things as the entity; the entity should die on purpose, not of neglect). The deliberate winddown, typically: final tax returns (the sale year's return reports the asset-sale gains — this is where the allocation schedule from the thread cashes out), creditor notice and payment of remaining obligations, distribution of remaining assets to yourself as member, and formal dissolution filings with your state. Timing note that catches sellers: keep the entity alive through any escrow/holdback period and the reps-survival window in your purchase agreement (commonly 12-24 months) — it's the party that made the promises, and dissolving it mid-window creates exactly the wrong kind of interesting legal questions. Total cost done properly: modest fees and some professional hours; total cost done by neglect: open-ended.
Follow-up from maker intake: "What are reps and warranties going to look like for me, concretely? Everyone gestures at them; nobody shows the list."
The micro-scale core set, so the gesture becomes a preview: you'll warrant ownership (you own what you're selling, free of claims — the cap-table ghost audit, now with money on it), IP provenance (the disclosure thread's question 3: authorship, assignments, no infringement claims known, dependency licenses as scanned), financial accuracy (the numbers provided were true — the Passport making this warranty cheap to give is an underrated benefit: you're warranting verified data), liabilities disclosure (no undisclosed debts, claims, or threats against the assets), contracts (the customer/vendor agreements transferred are as-represented, no known breaches), and compliance basics (data handling as described — the flow map again, now as a warranted document). Each survives closing for a negotiated window, backed by indemnification and often an escrow holdback (10-20% for 12-18 months is a common micro-deal shape). The seller-side discipline the whole forum has been building toward: every warranty above corresponds to an artifact this forum told you to maintain — the sellers for whom reps are terrifying are the ones being asked to warrant assertions; the prepared ones are warranting documents they've kept true all along. That's the diligence-compounding thesis in its final form: exit-readiness is the state in which signing reps is boring.
Platform-terms clarification the thread compressed, worth expanding because intake asks: 'asset sales and IP licenses only' — the license half is the underused option. Not every exit is a sale: licensing your app's technology (exclusive or not, field-limited, revenue-shared) to an operator while retaining ownership is a real transaction shape for makers not ready to let go, or for assets whose value splits across uses — and it runs through the same marketplace machinery (listing, verification, escrowed terms) without the finality. Where it fits: the maker with a strong engine and no appetite for the vertical's sales grind licenses to someone with the opposite profile; the app with two distinct customer segments licenses one field and keeps operating the other. Where it doesn't: licensing as commitment-avoidance (a license with an operator who fails is worse than a clean sale — you've spent the exclusivity and kept the risk), and note the ongoing-relationship cost honestly: a license is a business relationship with a contract, not proceeds and a beach. The auction-rules page covers which license shapes the marketplace supports; counsel covers whether yours should be one.
Follow-up from maker intake: "Escrow and holdbacks — 10-20% held for a year-plus sounds like a lot of my price at risk. What actually triggers claims against it, and how do I protect the holdback?"
What actually claims escrow at micro scale, in observed frequency order: transfer failures (the thing warranted transferable, wasn't — the account that couldn't move, the customer who churned at assignment consent; mitigated by the transfer-inventory work before signing), metric discrepancies discovered post-close (revenue or churn not matching warranted figures — near-eliminated when the warranted numbers were Passport-verified, which is escrow-protection benefit number one of verification), surprise claims (the collaborator ghost, the DMCA letter, the sales-tax notice — the audits this forum prescribes, again), and operational misrepresentation (owner-hours and support burden materially understated — the triangulation-evidence reply's territory). Protection is therefore mostly pre-signing work you've already read the threads for — plus negotiation hygiene at the agreement stage: claims should require specificity (documented breach, not buyer's remorse), materiality thresholds (a floor below which claims can't nickel-and-dime), the escrow as exclusive remedy where negotiable (capping your exposure at the holdback), and a clean release schedule (staged releases at 6/12/18 months rather than one cliff). The honest reframe: escrow isn't your price at risk — it's the price of your warranties, and sellers with verified numbers and dated artifacts are selling cheap warranties. The discount for scary reps was always coming from somewhere; preparation just moves it out of your holdback.
Threads are permanent — locked, not deleted, once resolved. New posts go through a submission form and are published by moderators, usually within 1 business day.