This page gives no legal, insolvency or records advice. It is written for two readers who see a shutdown from the inside: the restructuring professional advising whoever is in control, and the archive custodian, such as an IT provider, hosting vendor or records-storage firm, that holds systems on that controller's instructions.
Who answers for the company on each day of the shutdown
SourceX's who-qualifies page defines the controller as "Whoever directs that entity now: its board and CEO, an acquirer, or a trustee, receiver or assignee in a formal process", and says: "In an assignment for the benefit of creditors, a receivership or a bankruptcy case, the CEO alone may not be enough, because someone else may control the assets." Its matrix row for a company that is wound down or in a formal process reads:
| Who authorizes | Size and history check | Rights check | Usual failure | First route |
|---|---|---|---|---|
| The CEO may not be enough; the estate's controller decides | Headcount at peak, not today's | The estate's control, plus personal data limits | Archives deleted during the shutdown | The controller of the estate, with counsel |
That row is the only authority rule this page uses. Who the controller is on a given day is a question of fact, and it can change mid-shutdown; who holds which powers in each kind of process is for the estate's counsel.
Neither reader of this page decides, unless they happen to be the controller. The restructuring professional can put a question to the controller they advise. The custodian takes instructions from the controller and from nobody else, including a well-meaning introducer.
The system shutdown referral decision timeline
A run-sheet lists each system, its owner and the date it goes dark. The timeline below lays the referral decision over that run-sheet without adding a single date to it.
| Phase | Who controls | What the systems are doing | The referral step | Stop signal |
|---|---|---|---|---|
| 1. Wind-down decided, no formal process | The board and the CEO | Running; the run-sheet is being drafted | The CEO hears the question once, from someone already in a relationship with them | The CEO says no, or says later than the last date on the run-sheet |
| 2. A formal process opens | A trustee, receiver or assignee; the CEO may not be enough | The new controller may reissue the run-sheet | If the controller wants to hear it, the question goes to them through their counsel, and any earlier yes from the CEO is confirmed again | The controller declines, or nobody has been appointed yet |
| 3. Disconnection notices go out | Unchanged | Providers have dates; each record family leaves reach on its own date | Nothing new; note the latest date for the record families the controller mentioned | No answer can arrive before the relevant date |
| 4. Systems disconnected | Unchanged | Access has ended; content may sit under each provider's retention schedule | Proceed only with records the controller kept for its own reasons; nobody asks for a restore | Records gone or unreachable |
| 5. Deletion done, or the estate closes | The estate's final steps, or nobody | Gone | None | Record the stop |
The decision lives in phases 1 and 2. Phase 3 is a deadline, not an opportunity, and phases 4 and 5 mostly produce stop records. That is the honest shape of a wind-down introduction: most of the value of asking comes from asking before anyone has drafted a notice.
Disconnection and deletion are two different dates
Turning a service off rarely deletes it on the same day, and each provider sets its own clock. AWS's documentation, for example, says: "The post-closure period refers to the length of time between the day you closed your account and when AWS permanently closes your AWS account. The post-closure period is 90 days." It adds that content in the account is then deleted, with exceptions it lists. Google's admin help says, in paraphrase, that the choice an administrator makes when cancelling Google Workspace decides whether users' data is kept or deleted, and it notes: "Third-party app data isn't automatically deleted when you cancel your Google Workspace subscription."
Read those schedules for what they are: facts the controller and its counsel weigh for the estate's own reasons. A partner uses them for one thing only, to know the date after which asking stops making sense. They are never an argument for keeping anything alive.
Preservation and transition constraints that outrank the introduction
Every one of these sits above a licensing question, and none of them is the introducer's to resolve:
- Holds, retention duties and court orders. What must be kept, and for whom, is decided by the controller with counsel. A licensing conversation never relaxes a duty to preserve or a duty to destroy.
- The run-sheet itself. No system is kept running, exported, copied or restored for SourceX, not even for a few weeks "just in case". If the timing does not work, the timing does not work.
- Personal data limits. The who-qualifies row names them beside the estate's control. What may lawfully be licensed from a closing company is assessed in SourceX's rights review, never guessed during the shutdown.
- The custodian's instructions. A hosting vendor or records-storage firm holds what the controller tells it to hold and releases nothing to an introducer or to SourceX.
- Whose records they are. Material created for or owned by the company's clients rarely fits, however complete the archive looks.
Three wind-downs on the timeline (Illustrative)
Illustrative. Generic companies, invented facts, no outcome implied.
Phase 1, answered in time. A regional field-services company that peaked at 230 full-time employees and now has 140 decides to close over four months, with no formal process. An adviser to its board, who has known the CEO for years, raises SourceX once in the first week. The CEO says yes, the company applies itself, and the run-sheet is never touched. Headcount is read at the peak, so today's 140 does not matter.
Phase 2, a custodian asked the wrong question. A software reseller enters an assignment for the benefit of creditors. Before anyone checks who is in control, an introducer asks the company's managed service provider to keep the backups for a few extra weeks. The provider refuses, correctly: it takes instructions from the assignee. The introducer withdraws the request and offers the question to the assignee's counsel instead. The assignee replies that it is not a priority, and the introducer records a stop with that date and reason.
Phase 5, too late. An introducer hears about a dissolved logistics broker six weeks after its main cloud accounts were closed. Nobody she can reach can say who controls the company now, and the provider's post-closure period has passed. She records a stop: no controller identified, records presumed gone. She does not go looking for old laptops or former staff with copies.
A no-copy introduction, or a written reason it cannot proceed
When the controller wants to hear about SourceX, the note to them carries no data at all:
- Who is writing, and their interest. Including that they may be paid by SourceX if they are a registered partner and a license follows.
- What SourceX does. It licenses business records directly from companies for AI training and evaluation.
- Who decides. The controller, with counsel.
- What is not being asked. Nothing needs to be kept, copied, restored or sent for this conversation.
- How to proceed. If interested, the company applies on its own behalf; the introducer submits a dated introduction only if they have signed the Channel Partner Agreement.
When the answer cannot come in time, a stop record replaces the note: the date, the phase, a reason code (controller declined, no controller identified, records gone, hold or duty, or a fit fact fails), who made the call, and no description of any record. A company with any earlier application, lead, account or email correspondence with SourceX is a duplicate under section 3 of the terms, so a stop record also prevents the same company being raised twice by two advisers to one estate.
Fit facts in a wind-down
SourceX screens for 50 or more full-time employees at the company's peak, with contractors left out; years of records the company created itself; the rights to license them, which in a wind-down includes the estate's control and personal data limits; and a decision-maker with authority, which here may be the controller rather than the CEO. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
The controller describes the company; nobody collects drives, exports or samples to prove anything. Whether the records match a current program, what a license would cover and whether any payment would follow stay unknown until SourceX reviews the company. No page can say what a closing company's records are worth, or when money would arrive.
When the restructuring professional could be paid
A professional who acts for the controller may also be eligible to register as a partner. Whether they may take a referral reward while serving the estate is a question for their engagement terms, the court where one is involved, and their own counsel, settled before any introduction. If the answer is no, the controller can still hear about SourceX from them unpaid and let the company apply on its own.
Where the timeline misleads
- Processes differ. Assignments, receiverships and bankruptcy cases move control at different points, and a company can sit in more than one at once. Counsel says which applies.
- Provider clocks vary and change. The AWS and Google examples are illustrations read on 2026-10-28, not a rule for other services.
- The controller may never answer. Silence through phase 3 is a stop, not a reason to ask the custodian.
- Neighboring cases have their own pages. One system retiring at an operating company follows the referral window before a portfolio company retires a system; a copy held by a third party starts with the current custodian; a company coming back after a quiet period is tested in a business reopens after dormancy.
- No recovery is promised. A licensing conversation can end with nothing, and a reward depends on a licensed, accepted and paid dataset.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the controller says yes before the first disconnection date, a signed partner can register and submit a no-copy introduction, check the controller's description against who qualifies and read the program terms before anything is promised to the estate.