The M&A advisor's handoff to the current operating team: a three-part briefing packet that gives the CEO a decision, gives system owners the questions SourceX will ask, and leaves the deal room behind

Short answer

Hand the decision to the CEO who runs the company today, and hand the groundwork to the operating team who would answer SourceX's questions, in one packet that carries only facts the company approved. Before closing, that CEO is the target's; after closing, it is the acquirer's. The packet names the decision waiting, lists the descriptive questions system owners will be asked, and states what the advisor keeps: data-room material, price and buyer correspondence never cross. Then the advisor steps out on a date written into the packet.

Visual briefFull-size diagram
Four swimlanes, advisor, CEO, operating team and SourceX, run across a timeline split at closing; the advisor's lane ends at a packet that drops into the CEO and operating-team lanes, the deal room stays in the advisor's lane, and the SourceX lane starts only after the CEO's yes, with metadata only.
Illustrative sequence drawn from this page's method and SourceX's published process, checked 2026-10-27; no real deal is shown.

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 momentWho decides on licensingWho runs the records day to dayYour standing
Sell-side engagement, before any LOIThe target's CEOThe target's own operations and IT leadsThe seller's advisor, engagement running
Purchase agreement signed, not yet closedThe target's CEO, subject to the signed documentsThe target's team, while the buyer plans integrationStill the seller's advisor; transaction counsel speaks first
Closed as a stock saleThe acquirer's CEOThe same team, now inside the acquirer's groupFormer advisor: a contact, not a route to the decision
Closed as an asset saleThe acquirer's CEO for records it bought; the seller's CEO for records it keptSplit between two organizationsFormer advisor, until you know which records moved
Transition services still runningThe acquirer's CEOPossibly people on both sides of the dealFormer 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.

PartEntryFilled fromRead by
A. Decision noteWhat the idea is, in two sentences: licensing selected operating records to SourceX for AI training, with nothing licensed until the company signsSourceX's published processThe CEO
A. Decision noteWhere things stand: never raised, raised with the former CEO on a date, introduction submitted on a date, or application filedYour own dated recordsThe CEO
A. Decision noteThe decision waiting: explore now, revisit after a named integration milestone, or close the fileThe CEO, in their own wordsThe CEO
A. Decision noteWho would introduce, and whether that person is a registered partner who could earn a rewardYou, disclosed in fullThe CEO
B. Operator briefThe descriptive questions SourceX's first step asks: which systems, how many years of history, what can be exportedSourceX's published first stepSystem owners, IT lead
B. Operator briefFlags for counsel rather than for you: client contract limits, personal information in the recordsThe company's own knowledgeGeneral counsel or outside counsel
B. Operator briefDates that change the picture: system retirements, migrations, the end of any transition servicesThe integration plan, as the company shares itThe CEO and system owners
B. Operator briefThe no-action line: no exports, samples or uploads for anyone until the company has signed and SourceX gives the go-aheadSourceX's published processEveryone on the team
C. Advisor's closing fileWhat was said, approved and withheld, with datesYour notesYou alone
C. Advisor's closing fileYour partner agreement status and the date you step outYouYou, 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 dealWhat 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 findingsNothing
Which bidders dropped out, and whyNothing

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.

  1. 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.
  2. 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.
  3. 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Should the advisor hand the opportunity to the operating team or to the CEO?

Both, for different reasons. The CEO decides whether the company discusses licensing at all; the operating team holds the systems and will answer SourceX's descriptive questions if the CEO says yes. The packet gives each only the part they need, and the operating team acts only after the CEO's decision.

Can the advisor stay involved after handing over?

Only in the role the CEO agrees to, written into the packet. If the advisor is the partner who submits the introduction, their part is the introduction and nothing after it; SourceX deals with the company directly, and partners never handle records, inventories or data-room material.

Does an acquisition reset the referral?

Closing moves the decision to the acquirer's CEO and puts the company inside the acquirer's group, which the program treats as one referred company: the USD 50,000 floor applies once, to the group's first qualifying transaction. Whether the acquirer's own earlier dealings with SourceX affect credit for the company is not settled in the published terms; SourceX works that out when it reviews duplicates.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/how-it-works
  4. sourcex.si/faq
  5. csrc.nist.gov/glossary/term/system_owner_or_program_manager
  6. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment