A sale process is where an M&A advisor or business broker learns the most about a company's operating history, and the end of the engagement is where that knowledge usually evaporates. The deal team disperses, the people who run the systems were rarely in the room, and the one person who mentioned "all those years of service tickets" may now report to someone new. A handoff done well keeps the idea alive without carrying anything out of the deal.
Who runs the company on the day you hand over
Write down two names with a date: who decides for the company, and who holds the records day to day. They are rarely the same person, and closing can change both.
| Handoff moment | Who decides on licensing | Who runs the records day to day | Your standing |
|---|---|---|---|
| Sell-side engagement, before any LOI | The target's CEO | The target's own operations and IT leads | The seller's advisor, engagement running |
| Purchase agreement signed, not yet closed | The target's CEO, subject to the signed documents | The target's team, while the buyer plans integration | Still the seller's advisor; transaction counsel speaks first |
| Closed as a stock sale | The acquirer's CEO | The same team, now inside the acquirer's group | Former advisor: a contact, not a route to the decision |
| Closed as an asset sale | The acquirer's CEO for records it bought; the seller's CEO for records it kept | Split between two organizations | Former advisor, until you know which records moved |
| Transition services still running | The acquirer's CEO | Possibly people on both sides of the deal | Former advisor; the TSA exit guide covers where records sit |
The program names the CEO as the person who authorizes a licensing discussion and signs for the company. An integration lead, a division president or a long-serving COO can carry the idea inside the company, but none of them replaces that decision. If the deal closed, the introduction after a business sale closes covers who should carry the question to the acquirer's CEO.
The advisor-to-operator briefing packet
Three parts, each written for one reader. Every entry carries a date and the name of whoever confirmed it.
| Part | Entry | Filled from | Read by |
|---|---|---|---|
| A. Decision note | What the idea is, in two sentences: licensing selected operating records to SourceX for AI training, with nothing licensed until the company signs | SourceX's published process | The CEO |
| A. Decision note | Where things stand: never raised, raised with the former CEO on a date, introduction submitted on a date, or application filed | Your own dated records | The CEO |
| A. Decision note | The decision waiting: explore now, revisit after a named integration milestone, or close the file | The CEO, in their own words | The CEO |
| A. Decision note | Who would introduce, and whether that person is a registered partner who could earn a reward | You, disclosed in full | The CEO |
| B. Operator brief | The descriptive questions SourceX's first step asks: which systems, how many years of history, what can be exported | SourceX's published first step | System owners, IT lead |
| B. Operator brief | Flags for counsel rather than for you: client contract limits, personal information in the records | The company's own knowledge | General counsel or outside counsel |
| B. Operator brief | Dates that change the picture: system retirements, migrations, the end of any transition services | The integration plan, as the company shares it | The CEO and system owners |
| B. Operator brief | The no-action line: no exports, samples or uploads for anyone until the company has signed and SourceX gives the go-ahead | SourceX's published process | Everyone on the team |
| C. Advisor's closing file | What was said, approved and withheld, with dates | Your notes | You alone |
| C. Advisor's closing file | Your partner agreement status and the date you step out | You | You, and SourceX if credit is ever reviewed |
Part B is the piece most handoffs lack. The people who know which archive survived the 2019 migration are system owners, and NIST's glossary describes a system owner as the official responsible for a system from procurement and development through operation, maintenance and disposal. That last word is the reason to involve them early: they know which system is about to be switched off.
Part C never leaves your desk. It exists so that, if SourceX ever reviews attribution, there is a dated record of what you did, and so that anyone asking later can see what you chose not to carry forward.
Method note. The packet applies SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04), its screening guidance, its published process and FAQ, and the Channel Partner Agreement sample, all checked 2026-10-27, plus NIST's definition of a system owner. It records decisions and descriptions. It does not assess the records' quality, demand or value, which only SourceX's review can, and no figures on how often handoffs lead to applications are published.
Deal-room knowledge the packet leaves behind
The advisor knows far more than the packet says, and the gap is deliberate. Every useful entry has a version the company can state for itself.
| What you know from the deal | What the packet says instead |
|---|---|
| A data room index listing fourteen systems | "The CEO lists the systems the company wants to describe" |
| Headcount schedules from diligence | "Peak full-time headcount and the year, as the CEO states it" |
| Customer contracts reviewed in diligence | "Counsel checks client contract limits; SourceX runs its own rights check" |
| The buyer's integration plan for the old CRM | "Ask the IT lead which systems are scheduled to retire, and when" |
| Purchase price, earnout and quality-of-earnings findings | Nothing |
| Which bidders dropped out, and why | Nothing |
The partner agreement points the same way from SourceX's side. It gives a partner no right to pass on a supplier's inventory, its records or raw data, or the personal information in them, and it bars a partner from gathering or keeping copies of a dataset through the referral program unless separately authorized in writing. The handoff is a briefing, not a transfer.
What the operating team will be asked, in order
If the CEO says yes, the operating team meets SourceX in a fixed sequence, and only the first stage involves anything like work before a signature.
- The first step. A few questions with no files: the systems, the years of history, what can be exported. SourceX's FAQ puts describing the data at about 10 minutes. Qualifying companies list at least 5 systems, and no records change hands.
- The inventory. SourceX completes the inventory with the company and runs its rights check. Personal information is flagged here, and the company's own counsel answers anything uncertain.
- After the Master and the Dataset Deal Confirmation. The company signs its Dataset Deal Confirmation with SourceX, fixing the dataset, payout and deadlines. Only then, once SourceX gives the go-ahead, are records extracted, transferred and de-identified through approved processing routes, with SourceX guiding the exports.
Telling the team this sequence in advance stops the most common handoff mistake: a helpful system owner exporting a sample "to show them" before anyone has signed.
Where the records stand for SourceX's screen
The packet should let the CEO see the fit questions without the advisor answering them. Full-time headcount at its peak needs to have reached 50 or more, contractors excluded; a staffing firm counts only its own full-time staff, not workers placed with clients, though SourceX still considers such firms when their records are strong. The records need to be the company's own, built up over years, with rights to license them; client-owned material is usually not a fit. 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. SourceX's FAQ says operating, acquired and wound-down companies can all qualify.
What stays unknown until SourceX reviews it: whether the records match a current program, what client contracts permit and what any license would cover. After an acquisition, the company and its new parent count as one referred company for the program: the USD 50,000 floor applies once, to the group's first qualifying transaction, and further qualifying transactions within the Repeat Window pay 15%. Whether the acquirer's own earlier contact with SourceX turns the company into a duplicate is not answered in the published terms; SourceX settles it when it reviews duplicates.
A handoff after a stock sale (Illustrative)
Illustrative. The firm, the acquirer and every date are invented; no outcome is implied.
A sell-side advisor closes the sale of a 280-person IT services firm to a larger group. During the process the founder-CEO mentioned twelve years of service tickets and asked, in passing, whether anyone licenses that kind of history. He now runs the firm as a division president, and the acquirer's CEO decides.
Part A goes to the acquirer's CEO through the division president, who agrees to pass it on. It says the idea was raised once, nothing was submitted, and the decision waiting is whether to look at it at all.
Part B goes to the IT lead who owns the ticketing system. It lists the three questions SourceX's first step asks and notes one date the IT lead confirms: the ticketing system moves to the group's platform in the second quarter. It carries the no-action line.
Part C stays with the advisor: the date of the founder's remark, the fact that nothing from the data room was used, and a step-out date thirty days later.
The acquirer's CEO replies that the group will revisit after the migration. The advisor records it and steps out on schedule. Whether to keep a complete copy of the old system before it is retired is the company's own retention decision, made by its CEO and IT lead, not something the advisor requests.
Timing the handoff around integration, and writing down your exit
Integration calendars are crowded, and a handoff that lands in a cutover week gets lost or resented. Three habits keep it out of the way:
- One meeting, one packet. Walk through Parts A and B in a single conversation with the CEO or the person they name, and pass Part B to the operating team only if the CEO asks you to.
- Name the milestone, not a date. "After the CRM migration" survives a slipped schedule; "in March" does not. The seller transition period guide shows how those months usually run.
- Write the exit. The packet states the day your involvement ends and what role, if any, the CEO wants you to keep. A family office without its own operating staff faces a similar handoff problem from the owner's side, as family office value creation describes.
Where the packet misleads
- It goes stale. Systems retire, people leave and the decision moves at closing. A packet older than the last ownership change should be redrafted, not forwarded.
- It reads like an instruction. An eager operating team can treat Part B as permission to start. The no-action line exists for that reason, and the CEO's decision comes first.
- Your engagement duties outlast the engagement. Confidentiality owed to the seller does not end at closing; your engagement letter and counsel decide what you may say to the acquirer.
- The new CEO may simply not care. A packet makes a decision easy; it does not make it likely.
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 CEO wants the conversation and you are the agreed introducer, register as a partner, check the packet's facts against who qualifies and read the program terms before submitting; for advisors who spot the opportunity in a teaser rather than after a deal, see referring a company from a confidential teaser, and integration specialists can start from the post-merger integration overview.