This is for MSPs and enterprise systems consultants who run IT due diligence for buyers, IT readiness work for sellers, or the integration that follows a deal. It is narrower than the general question of raising data licensing mid-engagement, because a transaction puts three parties around the same records and moves the decision from one CEO to another on closing day.
Three diligence seats, three different clients
Start with your seat. It tells you whose records you saw, under whose papers, and whose CEO can say yes.
| Seat | Your client | Whose systems you examined | Who decides on licensing today | Earliest clean moment |
|---|---|---|---|---|
| Buy-side IT due diligence | The prospective buyer | The target's, through the data room and management interviews | The target's CEO, until closing | After closing, and only through your client if your client is now the owner |
| Sell-side IT readiness | The company being sold | The company's own, to prepare for buyers | The company's CEO now; the acquirer's CEO after closing | When the CEO raises it, as a conversation kept apart from the sale |
| Post-close integration | The acquirer | The acquired company's, now part of the acquirer's group | The acquirer's CEO | Once the integration plan dates the legacy systems, starting with your client sponsor |
| Diligence for a deal that died | The would-be buyer | The target's, for a transaction that ended | The target's CEO | Only if the target's CEO raises it independently; nothing from the deal carries over |
The table follows SourceX's screening page, which hands the decision for an acquired company to the buyer's CEO rather than to the old board. Before closing, the target's own CEO is the only person who can open a licensing discussion. A buyer that has signed a purchase agreement but not closed does not yet decide for the target, and neither does its adviser.
What a diligence review surfaces, and who inside the company owns it
One reason IT due diligence looks hard at inherited systems is risk. The UK National Cyber Security Centre's toolkit for boards notes that acquisitions and mergers can complicate an organisation's handling of cyber risk, and that many incidents trace back to vulnerabilities in acquired or older legacy systems, which is why a complete asset inventory matters (paraphrase). The same inventory is what makes a diligence consultant notice a data opportunity:
- Legacy systems the integration will retire. A dispatch platform, an old ERP or a ticketing tool with ten or more years of history and a shutdown date in the integration plan.
- Archives nobody plans to migrate. Read-only systems kept for retention, with a decision pending about what happens to them.
- Several platforms holding one workflow. Quotes, orders, service tickets and invoices spread across systems the buyer will consolidate.
Each finding has an owner inside the company, usually the head of IT or the integration lead, who can sponsor a conversation internally. None of them decides it; the CEO does. And an inventory says records exist, not whose they are or whether they can be licensed. What diligence normally covers, and the data questions worth adding, are set out in what IT due diligence means and the IT due diligence checklist.
The engagement boundary review
Eight questions, answered honestly before you mention SourceX to anyone connected with the deal. Any "wait" ends the review for now; write down the date and the event that would change the answer.
| # | Question | If yes | If no or unsure |
|---|---|---|---|
| 1 | Has the engagement ended, or does the idea sit clearly outside its scope? | Continue | Wait; raise nothing while the work is live |
| 2 | Do you know which company's CEO decides today: the target's before closing, the acquirer's after? | Continue | Confirm from public facts or your client; do not guess |
| 3 | Would anything you plan to say come only from the data room, management interviews or your report? | Strike it from the note | Continue |
| 4 | Does your engagement letter or a confidentiality agreement limit contact with the target or reuse of what you learned? | Follow it, and ask your own counsel if unsure; this page is not legal advice | Continue |
| 5 | Have you told your client before approaching anyone connected with the deal? | Continue | Tell your client first |
| 6 | Has the deciding CEO said, directly to you or through your client's sponsor, that the conversation is wanted? | Continue | Stop at an offer to explain the program |
| 7 | Can the CEO's team describe the records in their own words: types, years, systems? | Use their words | Leave the description to SourceX's review |
| 8 | Have you said you may receive a reward paid by SourceX? | Introduce | Disclose before introducing |
Questions 1, 3 and 4 protect your client. Questions 2 and 6 protect the company. Questions 5, 7 and 8 protect you, because they leave a record that the introduction rested on fresh permission rather than on access you were given for something else.
Data room access, report duties and licensing authority
Three different things, often held by the same person in the same month:
- Access. Data room permissions and interviews were granted so your client could evaluate a transaction. They are not a view into records you may describe to anyone else. SourceX's partner agreement gives a partner no authority to share a company's inventory, records, raw data or personal information, or to reach its extraction systems.
- Duties. Your report and your independence belong to your client. A buy-side report that recommends the target license its data mixes your advice with a possible reward of your own.
- Authority. The CEO decides whether to discuss licensing, and SourceX's review decides whether the records can be licensed at all. Suppliers confirm they hold the rights and that the data has not been licensed for AI training before, and records that are really the company's clients' property seldom make the cut.
The data room itself is not the asset. It was assembled for one transaction and mixes in buyers' questions and advisers' work; the operating records behind it are what a license would cover, as the answer on due diligence Q&A records explains.
A buy-side review that becomes an introduction after closing (Illustrative)
Illustrative: every company and fact below is invented, and nothing here predicts an outcome.
A 70-person MSP runs buy-side IT due diligence for a 900-person logistics group buying a 340-person regional carrier. The data room shows fourteen years of dispatch and claims history in an on-premises transport management system that the buyer expects to retire. During the deal the MSP does nothing about it: question 1 says wait. The report goes to the buyer, and the deal closes in March.
In May the acquirer hires the MSP to run the integration, and the plan schedules the old system's retirement for the following year. Now the review reads differently. The engagement is new, the acquirer's CEO decides for the carrier, and the MSP's client is the acquirer. The MSP asks its client sponsor, the acquirer's CIO, whether the CEO would want to consider licensing the carrier's history before the shutdown, and says the MSP may receive a reward. The CIO raises it; the CEO says yes in writing and asks the carrier's operations head to describe the records. The MSP introduces the acquirer's CEO using that description.
What the introduction leaves out: the data room index, anything from the diligence report, and record counts taken from the inventory. For the reward, the acquirer and the carrier are one group, so the USD 50,000 floor applies once, to the group's first qualifying transaction; further qualifying transactions first agreed within 12 months of that first Closing pay 15% of Actual Supplier Payout, with no cap, however many datasets they license. If the carrier's deal paid USD 250,000, the reward would be USD 62,500 (USD 50,000 plus 5%, which beats 15%), paid by SourceX and never deducted from what the company signed for; that figure is Illustrative only.
A sell-side variation runs the other way. A 210-person engineering firm hires a systems consultant for IT readiness before a sale, and its CEO asks about licensing its project archives. The consultant explains the program, keeps it out of the readiness report, and leaves the CEO to decide whether and when to tell the deal advisers. The CEO decides now; if the firm is sold before anything happens, the acquirer's CEO will.
The note that goes to SourceX, and the file that stays with the deal
The introduction is a short written note, which also gives it a dated record. It says who you are, how you know the company, that the deciding CEO asked for the introduction, the CEO's own description of the records, and any limits the CEO set. SourceX starts with a short set of questions and no files, so nothing needs to be attached.
It never contains the data room index, extracts from your report, screenshots, record counts you measured, valuations or deal terms, or any view on what a license might be worth.
Credit follows the program's ordinary rules. SourceX credits one partner per company, the earliest valid introduction of a company new to SourceX, once that company files a verified application within 90 days. If the target or the acquirer had any earlier application, relationship, lead, account or email correspondence with SourceX, it is a duplicate and nobody is credited. When several advisers on one deal know the company, overlapping claims are sorted out by SourceX in duplicate review from dated records.
Fit still has to be there: a full-time workforce that peaked at 50 or more, contractors excluded; years of the company's own documented records; authority to license what it created; and a CEO who has asked to talk. 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.
Where the boundary review falls short
- Papers differ. Engagement letters and confidentiality agreements vary, and yours may limit contact with the target after the deal. The review tells you to read yours; it cannot read it for you.
- Deals die and timelines slip. A failed deal returns the decision to the target's CEO and leaves your obligations in place. An integration plan that slips moves your dated trigger with it.
- Two clients in a year. An adviser who did buy-side diligence and then integration for the same acquirer has a client relationship that runs through the deal; one who worked for a losing bidder has no client on the winning side, only obligations.
- Demand and rights. Whether the records suit SourceX's current data needs, and whether customer contracts restrict them, is settled in SourceX's review.
For advisers who also handle the acquisition of MSPs themselves, the MSP acquisition due diligence checklist covers the target-side questions, and when an MSP's client is acquired covers the ongoing service relationship.
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 all eight questions come back clear and the deciding CEO has asked for the introduction, get a partner account, check the company against who qualifies and read the attribution and duplicate sections of the program terms; the guides library has more partner playbooks.