Wind-down for a 50-500 person company vs a small startup: what differs

What actually differs when a larger company winds down?#

A larger company's wind-down differs mostly in the number of moving parts that must be stopped in the right order. The comparison below covers the areas where founder-focused shutdown guides are too thin for a company with real operations.

None of these rows is a reason to delay. They are reasons to assign owners early, because a larger company has more places where a missed step becomes a claim later.

Why do employee and payroll records weigh more at this size?#

Employee and payroll records weigh more at this size because obligations multiply with headcount and with the number of states where people worked. Final pay rules, benefit plan terminations, continuation coverage notices and, at some sizes, advance layoff notice laws such as the federal WARN Act may apply, and each one creates records someone must keep.

Retention clocks keep running after the doors close. The IRS says to keep employment tax records for at least 4 years after the tax is due or paid, whichever is later, and federal wage-hour rules require payroll records to be preserved for at least three years. Operators with plant or field crews also keep OSHA injury and illness logs, which must be saved for five years after the end of the year they cover.

Assign one person, often the controller or HR lead, as custodian of personnel and payroll records after dissolution. Give that person read-only access to the payroll provider's history before the account closes, and confirm how long the provider keeps reports available.

How does the systems problem change?#

The systems problem changes from closing a few accounts to retiring an application estate. A mid-size company may run an ERP, a CRM, a help desk, a payroll provider, a field service or warehouse system, an engineering tracker and dozens of smaller tools, each with its own admin, contract and deletion schedule.

A frequent and avoidable failure at this size is losing admin access. When the IT manager is among the first to leave, nobody can export the help desk or reset the ERP administrator password. Keep IT staff engaged through the export stage, even on a reduced schedule or a short consulting agreement.

• 1Build a system register: name, owner, admin accounts, renewal date, export method and deletion terms.
• 2Freeze automatic deletion and retention policies before staff leave.
• 3Export systems of record first: ERP, CRM, help desk, HR and payroll, and file storage.
• 4Confirm a second named admin on every system before the last IT person departs.
• 5Cancel subscriptions only after exports are verified and the retention decision is written down.

Who approves decisions in a larger wind-down?#

Approval in a larger wind-down usually runs through the board, any secured lenders and, depending on the charter and investor agreements, preferred stockholders. A small startup can often act on a written consent from a small board; a company with a bank line, equipment leases and several investor classes usually cannot.

Major asset decisions, including equipment sales, assignment of customer contracts and any license of company records, typically need a board resolution and may need lender consent under the credit agreement. Many companies appoint a wind-down officer or an outside restructuring professional so authority stays clear as executives leave.

The route matters too. A solvent dissolution, an assignment for the benefit of creditors, a receivership and a bankruptcy each put different people in charge of the assets and set different rules for who may sign.

What changes with customers and their data?#

Customer obligations change from a few standard terms to a portfolio of negotiated contracts. Master service agreements, SLAs, warranties and data processing addendums often say what happens to customer data when the relationship ends, and some require notice, return or certified deletion within a set period.

Pull the customer contract list from the CRM or contract system and sort it by obligation: data return, deletion, transition support, open warranties and confidentiality that survives termination. Customers with return or deletion rights get their data handled before any archive decision, and their confidential material stays out of any later license scope.

A small startup can often handle customers with a single notice email. A larger company usually needs an account-by-account plan, because a missed deletion request or warranty claim can surface long after the doors close.

Why is the records opportunity bigger, and riskier, at this size?#

The records opportunity is bigger at this size because a company with 50 or more full-time employees at peak and several years of history tends to hold connected operational records: tickets linked to fixes, jobs linked to invoices, quality issues linked to corrective actions. Those links are what AI developers look for, and small startups rarely have enough of them.

The risk is bigger as well. More records mean more personal information about customers and employees, more customer contracts with confidentiality terms, and more systems where history may already have been lost in a migration. A plan that separates the preserved copy, the retained copy and any licensed copy keeps those concerns manageable.

Illustrative example: a regional distributor that outgrew the startup checklist#

Illustrative: a fictional industrial distributor with branches in several states decides to wind down after its largest product line moves to a competitor. The CEO starts from a founder shutdown checklist found online, which covers dissolution filings, final payroll and closing the bank account.

The COO adds what that checklist missed: a system register for NetSuite, the WMS, the TMS, the help desk and the HR platform; a custodian for payroll and OSHA records; lender consent for forklift and racking sales; and a hold on records tied to an open freight claim. The IT manager stays on a consulting agreement until every export is verified.

With exports in hand, the board reviews the order exception and customer service history, which links orders, carrier problems and resolutions across many years. It approves a metadata-only fit check before the NetSuite subscription ends and names the COO as signer for any resulting license.

How SourceX works with larger wind-downs#

SourceX runs alongside a larger wind-down as a records transaction rather than a separate project. The SourceX five-step transaction starts with a metadata-only Supply check, so nothing is shared while the board and lenders are still choosing the route.

At the Rights and Approval steps, SourceX maps who can sign, which lender or investor consents apply and which records are held for claims. Delivery happens only after release authorization is recorded in the SourceX Evidence Packet, and SourceX does not host large archives: they remain on the company's systems or travel on encrypted drives.