Timing matters: data value before and after a shutdown

Most assets in a shutdown hold their value for a while. A laptop is worth roughly the same next month as it is today. Company data is different: its value tends to fall in sudden steps, each triggered by an ordinary wind-down decision that nobody connected to it. Knowing where those steps are is the simplest way to keep the value from disappearing.

The value of an operational archive to an AI lab comes from three things: how much history it holds, how many systems it covers, and whether the same work can be traced from one system to another. We explain those factors in how company data is valued.

Each of those factors depends on systems staying intact and accessible. When a tool is cancelled, coverage drops. When an export strips out the links between records, connection depth drops. When retention settings purge old messages, history drops. None of this happens a little at a time. A tool is either there or it is not.

Consider a hypothetical 80-person software company over the months of its shutdown. At each stage, some decisions are made that have nothing to do with data and still affect it.

While still operating. Every system is live, admins are on staff, and history is complete. This is when an archive is usually at its fullest. Operating companies can license their data too, with the same scope controls and exclusions, so a company that sees a wind-down coming does not have to wait until it starts.

When the wind-down is announced. Leadership is focused on customers, employees and creditors. Tools are still running, but conversations about which ones to cancel have begun. Value is largely intact, and this is the easiest time to act.

After layoffs. Departing employees take with them the knowledge of which systems were used and how. Admin accounts may be deactivated with their owners. The data is still there, but reaching it gets harder, and sometimes nobody left knows that a second project tracker existed.

After subscriptions are cancelled. This is the steepest drop. Depending on the tool and plan, history may be deleted shortly after cancellation or become inaccessible without a paid plan. A company that cancels its help desk and project tracker to save a few months of fees may lose the two systems that connected customer problems to engineering work.

After dissolution. If anything survives, the question becomes who still has authority to act for the company. A director, officer, liquidator or assignee with authority over company assets can sign a licence, and we ask for that authority document up front. But by this point, the archive is often partial at best.

It helps to be concrete about what disappears at each step, because some losses are less obvious than others:

• Whole systems. A cancelled tool takes its entire history with it, reducing coverage.
• Links between systems. Exports often flatten data, breaking the references from a ticket to a pull request or from a support case to a chat thread.
• Early history. Retention policies set to save storage costs can quietly delete the oldest years first.
• Attachments and documents. Files linked from chat or tickets may live in a drive that was cleaned up separately.
• Context about the archive itself. Without the people who ran the tools, nobody can say which channels mattered or which folders should be excluded.

Each of these reduces what a lab can learn from the data, and so what the licence is worth. Typical licences range from $20K to $400K+, and where a company lands depends heavily on how complete its archive is at the time of evaluation.

A common worry is that starting the conversation early locks the company into something before it is ready. It does not. The first step is a 15-minute intro call. Before any data moves, the seller sets the scope and any exclusions, such as a client, a channel or a folder, and those are annexed to the contract. The evaluation is read-only and takes under an hour of the seller's time.

After that, anonymization happens in-house. Every person, company, address, email, phone and account becomes a consistent token across every tool. Credentials, API keys, card numbers and government IDs are removed. HR, payroll, medical and legally privileged folders are excluded by default. The seller reviews an anonymized sample before anything is delivered, and payment goes to the company entity in 2 to 4 weeks. In total, the seller typically spends about an hour.

The cheapest step is the one that protects value without any commitment at all: delaying the cancellation of key tools until someone has looked at what is in them. Our post on what to do before you cancel Slack walks through that for one of the most common systems.

If you are planning or advising on a wind-down, one rule covers most of this: no tool gets cancelled until its history has been evaluated. Write it into the plan next to the lease, payroll and customer notification steps. It costs a few weeks of subscription fees at most, and it keeps an asset available while the people who can make decisions about it are still around.

There is no firm number before the data is counted, and counting is quick. The window to count it is not always long.

If your company is approaching a wind-down, or is already in one, book a 15-minute call while your tools are still running.