This playbook is part of the software rationalization and cost reduction guide, which holds the cancellation-date register. Here the job is the play itself: from trigger to introduction.
The trigger: when cost reduction becomes an archive event
Cost programs cut tools for good reasons: duplicate systems after acquisitions, seats for departed staff, legacy platforms kept running "just in case". The archive event happens when a cut ends access to years of workflow history that nobody planned to keep. Three kinds of binding event turn a planned cut into a dated one:
- A contract action the company has already taken, with an end date in writing.
- A court action. In a bankruptcy, 11 U.S.C. 365 lets a debtor or trustee reject an executory contract with court approval; in Chapter 7, a contract not assumed within 60 days after the order for relief is deemed rejected. Rejecting software contracts in Chapter 11 covers the mechanics.
- The vendor's own retention schedule after the subscription lapses. These vary by vendor and plan. Microsoft 365, for example, holds customer data in a limited-function account for 90 days after a paid subscription ends so the customer can extract it, and deletes it within 180 days. Other vendors publish shorter or longer windows, and individual contracts can override any published policy.
The cancellation-date register shows how to record each tool against these tests. This playbook starts one step earlier, with noticing that a client is in the situation at all.
Signals that a client is in it
You rarely hear "we are about to lose our archives". You hear these instead:
| Signal you hear | What it often means | Question to ask next |
|---|---|---|
| "We are consolidating onto one CRM." | The losing CRM's activity history may not migrate | "Does the history migrate, or only open records?" |
| "Finance wants the duplicate help desk gone by year end." | Ticket history may end with the contract | "Has notice been sent, and what date does it state?" |
| "The acquired unit's tools go in phase two." | Project and ticket history from the acquired business is exposed | "Who owns that history now, and who decides what is kept?" |
| "Counsel is preparing the rejection motion." | A court date may fix the end of access | "Which contracts are on the list?" |
| "IT is cutting seats as people leave." | Mailboxes and workspaces tied to departing users may close with their licenses | "Whose licenses hold shared history, and what happens to it when they go?" The reduction-in-force IT checklist covers handover. |
The records a cost reduction puts at risk
Archive-holding tools in a cost plan tend to fall into five groups. What makes them interesting for AI training and evaluation is not their size but whether they record a request, the work done, and the outcome.
| Archive | What a useful history contains | What usually breaks it |
|---|---|---|
| Help desk tickets | Request, troubleshooting steps, resolution, reopen or satisfaction outcome | Export of ticket headers without the conversation |
| Project tracker history | Issues, status changes, linked fixes, release outcome | Migrating open issues only |
| CRM activity | Opportunities, activities, stage changes, won or lost reason | Merging accounts and dropping activity on the losing system |
| Shared mailboxes | Customer requests and replies linked to case numbers | Mailbox deletion when licenses are removed |
| Team chat | Escalations and decisions in channels | No retention set, workspace closed with the contract |
Partners record which of these exist, for how many years, roughly how large, and who owns them. They never request exports or open the systems.
The conversation that turns it into an introduction
Run it with the CFO or chief restructuring officer, inside a review you already lead. A longer timed version is in the cost reduction meeting agenda; the play has four moves.
- Ask the qualifying question exactly. "Which operational archives face a real cancellation date?" Write down only dates someone confirms; "unknown" is a valid answer.
- Sort the answers. Real date, not yet, or none. Only the first group justifies talking about timing.
- Check authority and fit. Who can authorize a licensing discussion: the CEO (in an owner-run company, the owner), or, in a court process, someone who needs counsel's or the court's sign-off? Does the company meet the baseline of 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact? 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.
- Disclose and offer. Say that SourceX licenses approved business data directly from companies for AI training and evaluation and manages agreement, rights review, data preparation, delivery and payout; that you may receive a referral reward if a license completes; and that SourceX pays it separately, never from the company's payout. Then ask whether the owner wants an introduction.
Illustrative. A fictional 520-person specialty insurance broker is cutting software spend after two acquisitions. Of six tools in the plan, two hold more than five years of history and have a documented end: a help desk with notice already sent and a CRM on a signed consolidation plan with a contract end date. The advisor raises those two with the CFO, discloses the referral interest, and the CFO brings in the CEO, who asks to be introduced. The other four go on a watch list with a named owner.
Mistakes that cost the advisor credibility
- Treating a savings-plan row as a deadline. Fake urgency harms the restructuring relationship and is not how SourceX works.
- Estimating value. What stays unknown until SourceX reviews it: rights, scope, de-identification and whether any buyer wants the record type.
- Skipping the agreement. Sign the Channel Partner Agreement before submitting. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application.
- Raising it with the wrong person. IT can describe archives; only the CEO (the owner-CEO in an owner-run company) can authorize a discussion, or a restructuring officer where a court process applies.
The technology advisor program page covers your role, the network opportunity finder sorts your client list, the interim CFO turnaround checklist covers adjacent turnaround tasks, and fractional CFO referral income shows how finance advisors approach the same programs.
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.
When an archive in the cost plan has a documented end date and the owner opts in, register as a partner, confirm the company on who qualifies and read the program terms before access ends.