# Readiness review for an acquisition-built group | SourceX

Canonical: https://refer.sourcex.si/guides/a-readiness-review-for-an-acquisition-history-business
Last updated: 2026-11-05

A business built through acquisitions is ready for a referral summary when every line names the entity and the period it describes. Founding year, headcount, years of records and customer terms each come from different acquired businesses, so a group-level sentence such as "operating since 1987" or "thirty years of records" usually overstates what the group can reach today. Review the draft entity by entity and era by era, restate or hold each line, and let the group CEO approve what remains.

Which entity to introduce and where each acquired business's records sit is covered by the [growth-source lineage map](/guides/when-acquisition-led-growth-changes-the-referral-entity), and who can say yes at each phase of a single deal by the [post-acquisition sponsor map](/guides/the-referral-questions-to-ask-after-an-acquisition). This page assumes that work is done and asks the next question: does the summary you are about to send claim anything the group cannot stand behind?

## Why an acquisition-built group is hard to summarize

Every acquisition hands the group a borrowed past. The oldest add-on's founding year appears in pitch decks, headcounts are added across businesses that peaked in different years, and an archive that stayed with a seller gets counted as the group's. In a referral summary each of these becomes a problem in review that a careful line would have avoided.

SourceX's screening guide is specific about this ownership pattern. For a private equity platform with add-ons, the platform CEO authorizes for the whole group; the size and history check uses group headcount at peak and each acquired business's history; rights depend on how each business was bought; and the usual failure is records stranded in an add-on's old systems. Each of those maps onto a line in the summary, which is where a readiness review looks.

## The minimum context, gathered entity by entity

Collect these facts for the platform and for each acquired business, in conversation, before drafting anything.

| Fact | Why the review needs it | Who usually answers |
|---|---|---|
| Founded, and joined the group | Separates the business's own past from its time in the group | CFO or corporate development lead |
| Deal type, as the company describes it | How a sale was structured decides who holds the records afterward | CFO, with general counsel |
| Systems at joining, and what happened to them | Shows whether pre-deal records were migrated, archived or left behind | Integration or IT lead |
| Where pre-deal records sit today | Records in a seller's hands or a switched-off system are not the group's to describe as reachable | IT lead |
| Customer terms the records were collected under | Each business made its own promises to its own customers | General counsel |
| Full-time headcount at the group's peak, with the date | The size check uses the group's own peak, contractors excluded | CFO, from payroll |
| Any earlier contact with SourceX | Earlier contact by any entity has to be known before submission | Each business's leadership |

Deal-room materials stay out. What the fund learned in diligence or board meetings is a reason to ask the CFO a question; it never becomes a line of the summary.

## The entity-history review map

The map is one row per business and one column per claim a summary usually makes. It borrows its logic from provenance work: the Data & Trust Alliance describes its Data Provenance Standards as metadata meant to make clear where data comes from, how it was created and whether it can be used legally. The review asks those three questions at the level of the acquired business, without claiming to apply the standard itself.

Illustrative. A generic facilities maintenance services group, owned by a private equity fund since 2020, with invented entities and dates.

| Entity | Founded and joined | Deal type, as the CFO describes it | Records the group can reach today | Where pre-deal records sit | Customer terms at collection | Readiness |
|---|---|---|---|---|---|---|
| Platform | Founded 2002; the original company | Not applicable | Work orders and billing from 2015 in current systems | 2002 to 2014 on a retired server, read-only | Platform's own terms | Ready, with the archive marked |
| Add-on A | Founded 1987; joined 2021 | Stock purchase, merged into the platform in 2023 | Work orders from 2012, migrated in 2023 | Before 2012: not retained, according to the CFO | A's terms until 2023 | Restate |
| Add-on B | Founded 1996; joined 2022 | Stock purchase, kept as a subsidiary | Its own system, from 2005 | Unchanged, still in B's system | B's contracts, with confidentiality clauses nobody has read for this purpose | Hold the rights line |
| Add-on C | Founded 2009; joined 2024 | Asset purchase | Customer files and work orders that moved at closing | Accounting archive kept by the seller | C's terms; the seller's archive is not the group's | Restate |

Three verdicts are enough. **Ready**: the line names its entity and era and has a source. **Restate**: the fact is true for one entity or period but was written as a group fact. **Hold**: the fact is unknown and would change the summary, so it waits for an answer or goes out marked open.

## Seven summary claims under review (Illustrative)

Illustrative. The same invented group's draft summary, line by line.

| Draft line | What the review found | Verdict | Line as restated |
|---|---|---|---|
| "Operating since 1987" | 1987 is Add-on A's founding year; A kept nothing before 2012, and the oldest records the group can reach start in 2002 | Restate | Four businesses founded 1987 to 2009; the oldest reachable records start in 2002 |
| "640 full-time employees at peak" | The sum of each business's own peak, reached in different years; the group's peak was about 510 in 2025 | Restate | About 510 full-time employees at the group's peak, 2025, contractors excluded (CFO, payroll) |
| "Thirty years of work orders" | Continuous work orders begin in 2005 at B and 2012 at A; the platform's begin in 2015, with 2002 to 2014 read-only | Restate | Work orders: B from 2005, A from 2012, platform from 2015, plus a read-only platform archive for 2002 to 2014 |
| "All records belong to the group" | C's accounting archive stayed with the seller under the asset purchase | Restate | C's pre-deal accounting archive is held by the seller and excluded |
| "Customer data collected under group terms" | Each business collected under its own terms until it joined | Hold | Collected under four sets of customer terms; general counsel to list them |
| "The group CEO approves this introduction" | The platform CEO authorizes for the whole group; B's president sponsors | Ready | Unchanged |
| "No earlier contact with SourceX" | Checked for the platform and A only | Hold | Earlier contact checked for two of four businesses; B and C pending |

After review the summary says less, and every sentence of it holds.

## Labels for estimates, constraints and unanswered questions

Use four labels, and put the entity in every one: "Reported, Add-on B's IT lead, 22 October"; "Estimate, platform IT lead, size of the 2002 to 2014 archive"; "Constraint, B's customer contracts, unread"; "Open, earlier contact at C, asked 24 October."

Two kinds of open question deserve their own lines in an acquisition-built group.

- **Promises made before the deal.** Each acquired business collected customer information under its own terms and notices, and those commitments do not simply dissolve at closing. When the FTC's consumer protection bureau wrote to Facebook and WhatsApp in 2014 about their proposed deal, it said WhatsApp's existing privacy commitments had to be honored afterward and that affirmative consent was needed before material changes to how already collected data would be used. Record which terms applied to which business and era; counsel and SourceX's rights review decide what follows. [Whether privacy promises follow data in a deal](/questions/ftc-privacy-promises-follow-data-acquisition) goes further.
- **Credit across a group.** The published terms do not address how an earlier conversation between SourceX and one business in a group, or another partner's introduction of a sibling business, affects credit for introducing the group. SourceX settles that in its duplicate review, and this page states no rule for it. What is settled is how a group counts: a parent company and its subsidiaries count as one company, so the USD 50,000 floor applies once, to the group's first qualifying transaction, and further qualifying transactions first agreed within 12 months pay 15%, with no cap however many entities license.

If records from two businesses are meant to join, ask whether anyone kept a crosswalk of old and new IDs, as [acquisition identity mapping](/guides/acquisition-identity-mapping-data-licensing) explains.

## The approved handoff and the first-call agenda

1. **The platform CEO approves the restated summary in writing**, after each add-on's leadership has checked its own lines.
2. **Every entity is checked for earlier contact.** Any earlier lead, account or email correspondence with SourceX makes a company a duplicate, and a duplicate is not credited.
3. **Whoever submits has signed** the SourceX Channel Partner Agreement and holds an approved partner account.
4. **The group applies itself.** Its verified application is the point where credit is settled, and the credit goes to whichever valid introduction of this new company came first inside the 90-day attribution window.

Fit still applies at group level: 50+ full-time employees at the group's peak, documented operating history, rights to license and an authorized 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.

A 45-minute first call between the platform CEO, the CFO, the integration lead and SourceX can walk the map row by row, mark which held lines matter most, name who answers each open question, note any read-only archive with a switch-off date and set a date for the updated map. For the operating partner's role in that call, see [private equity operating partners](/for/private-equity-operating-partners), and for portfolio reviews that surface groups like this, the [portfolio operations review screen](/guides/moment-portfolio-operations-review-vc-platform-teams).

## Where the review can be wrong

- **Memory is not a document.** Deal types, migration dates and retention gaps come from the CFO and IT lead. Counsel reads the agreements, and how [asset and stock sales](/compare/asset-sale-vs-stock-sale-data-ownership) differ depends on drafting.
- **Rights are decided later.** The map flags where rights usually break; SourceX's rights review and the group's counsel decide what is licensable.
- **Integration consumes attention.** A team mid-cutover may not have time for seven columns per business, and asking spends goodwill; no data on how management teams respond has been published.
- **Demand is unknown.** SourceX checks relevance to its current data needs in review, and programs change. A clean summary can still be declined.
- **Synthetic substitutes.** If buyers come to rely more on synthetic or public data, demand for any group's records could narrow. That market analysis belongs on sourcex.si, which also keeps a [review of published enterprise data readiness surveys](https://sourcex.si/research/enterprise-data-readiness-published-research); this page stays on the summary.

**Method note.** The map applies SourceX's screening guidance for platforms with add-ons and the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), both checked 2026-10-27, plus the provenance questions and FTC letter cited above. The group and its figures are invented. The review measures whether each line names its entity, era and source; it does not measure record quality, rights or demand, and it has not been tested on a cohort. To test it, count for each group how many draft lines were restated or held, and whether SourceX's first call questioned any line marked ready. More in the [guides library](/guides).

## 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 every line of the group's summary names its entity and era, earlier contact has been checked for every business and the platform CEO has approved it, [register for a partner link](/register), confirm the group against [who qualifies](/who-qualifies) and read the [program terms](/terms) before the group applies.

Reviewing a group's referral summary is network work. Evaluating SourceX as a company to invest in is a separate decision, and materials for it are available on request through the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://www.ftc.gov/news-events/news/press-releases/2014/04/ftc-notifies-facebook-whatsapp-privacy-obligations-light-proposed-acquisition
- https://dataandtrustalliance.org/our-initiatives/data-provenance-standards
- https://sourcex.si/investors
