This guide is for research leads and operating partners looking at companies that grew by buying others. It asks which company you would introduce, who can say yes for it and which acquired histories are still within reach. For a single deal still moving from signing to full merger, the post-acquisition sponsor map covers whom to ask at each phase; this page is for a group that has already grown through several deals.
What acquisition-led growth tells a research lead, and where it is recorded
A group that grew by acquisition usually has more history, more systems and a different decision-maker than the company it started as. Each source of the signal dates something different.
| Source | What it records | Date it gives | Limit |
|---|---|---|---|
| Form 8-K, Item 2.01 | A US public company's completed acquisition of a significant amount of assets, including a business, disclosed within four business days of closing | The closing | Public acquirers and significant deals only; most acquirers in a venture network are private |
| State business registries | Mergers, conversions and name changes of each entity | The filing | Filings can lag the deal; the legal entity name guide covers the lookups |
| Company announcements | What the company says it bought | The announcement | Attributed and simplified; rarely states the structure |
| The CEO or CFO | Structure, and which entity holds which records | The conversation | The only source that settles the map |
| Board or deal-process materials | Often the full picture | Varies | Confidential; a reason to ask the CEO, never material to pass along |
None of these says whether rights came across, whether pre-deal archives moved, or what full-time headcount the group reached at peak; the last is covered in reading headcount growth.
The growth-source entity lineage map
Draw one line per acquired business, left to right: the business as it started, each deal with its date and type, and the entity holding its records today. A line ending in "unknown" is a research task, not a failure. The deal type decides where it ends.
| Deal type | Where the records sit afterward | The referral entity | Who authorizes | What to confirm with the company |
|---|---|---|---|---|
| Stock purchase, target kept as a subsidiary | In the acquired company, which continues under a new owner | The group, with the subsidiary inside it | The group CEO; once a company is acquired, the acquirer's CEO decides for it | Whether the subsidiary still runs its own systems |
| Statutory merger into the acquirer or a sister company | In the surviving company | The survivor; the target no longer exists separately | The survivor's CEO | Which state's law governed the merger, and when the target's systems were folded in |
| Asset purchase | With the buyer for the listed assets; anything excluded stays with the seller | The buyer for what it bought; the seller remains a separate company for what it kept | The buyer's CEO; for the seller, its own CEO, or its controller if it is in a formal process | Whether records were listed as purchased assets |
| Add-on under a private equity platform | Often still in the add-on's old systems | The platform group | The platform CEO, for the whole group | Group headcount at peak and each add-on's history |
| Divestiture out of the group | With the divested business and its new owner, as the separation agreement sets out | The divested business, now outside the group | Its new owner's CEO | What the separation agreement says about records and copies |
| Rename or rebrand only | Unchanged | The same legal entity | Its CEO | The legal name on contracts |
The merger row rests on statute. Under Delaware's General Corporation Law, section 259, the rights, privileges, powers and property of each merging corporation vest in the surviving or resulting corporation when the merger takes effect, and the debts and liabilities follow. Other jurisdictions have their own rules, so record which law applied. The asset purchase row depends on drafting, as asset and stock sales explains, and carve-out data separation covers divestitures. SourceX's screening page puts it plainly: how a sale was structured decides who holds the records afterward.
Two acquisition-led growth patterns under the same questions (Illustrative)
Illustrative. Two invented groups, as a research lead would map them after a call with each CFO.
Group R, a roll-up. A commercial HVAC services platform founded in 1998, owned by a private equity fund since 2019.
- Platform operating company (1998): holds its own records.
- Add-on A (2006): stock purchase in 2020, merged into the operating company in 2024; records now in the platform's systems.
- Add-on B (2011): stock purchase in 2021, merged in 2024; its pre-deal dispatch history stayed in B's retired system, read-only until January 2027.
- Add-on C (2009): stock purchase in 2022; still a subsidiary on its own dispatch system.
- Add-on D (2014): asset purchase in 2024; customer and job files moved, while the seller entity kept D's accounting archive.
Group M, one merger. Two 150-person engineering inspection firms merged in 2023. Firm Y (2001) merged into firm X (2004), which took a new name; Y's project archive was migrated, and Y's old system stays read-only until June 2027.
| Question | Group R, roll-up | Group M, one merger |
|---|---|---|
| Entity holding the records today | The operating company for A and B; C in its own subsidiary; D's purchased files at the operating company, D's accounting archive with the seller | The renamed survivor, X |
| Referral entity | The group, introduced once | X |
| Who authorizes | The platform CEO, for every entity | X's CEO |
| Full-time headcount at peak | 520 across the group in 2025, contractors excluded | 300 after the 2023 merger |
| Oldest records | 1998 at the operating company; add-on histories from 2006 | 2001, in Y's migrated archive |
| Rights | Depend on what each deal moved; D's accounting archive is not the group's | The survivor holds what both held, under the merger law that applied; customer contracts still need review |
| First-transaction floor | Once for the whole group, which counts as one company | Once for X |
| Dated event | B's old system read-only until January 2027 | Y's old system read-only until June 2027 |
| Integration load | High: C and D are mid-cutover until mid-2027 | Finished |
Group R grew faster and holds more history, but its lineage has two loose ends and its integration team has no time to spare. Group M is the simpler introduction: one survivor, one CEO, one dated event. Neither pattern says anything about demand, which SourceX assesses in review. Both groups are held to the same fit bar: a CEO with authority to approve, rights to license, a documented operating history and full-time headcount that reached 50 or more at peak, contractors excluded. 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.
Does the acquired history survive integration?
Acquisitions add history on paper; integration decides how much survives. SourceX's screening page warns that pre-deal archives may not have moved and that records can be stranded in an add-on's old systems. Ask four things about each acquired business:
- Where do its pre-deal records live now: the group's live systems, a read-only archive, the seller, or nowhere?
- When does any archive go away? A read-only end date is real timing, unlike a quarter-end.
- Whose employees created them? The acquired business's own staff, in its own systems, made the history worth tracing.
- Do customer contracts at the acquired business limit reuse? Treat that as unknown until counsel and SourceX's rights review answer it.
Groups that have stopped buying, or started shrinking, face the same questions; SourceX's referral site says operating, acquired or wound down companies can all qualify, though not every company does. Mapping record sets after subsidiaries merge is covered in legal entity rationalization, and which entity can license in the multi-entity ownership question.
Rank group conversations by path, lineage and integration load
Once a group's lines are drawn, order the groups by what you can verify:
- One CEO path for the whole group, confirmed by the person who owns that relationship.
- Lineage complete: every acquired business traced to a current holder.
- A dated event: an archive switch-off or a read-only end date.
- Integration load: a team in the middle of a cutover has no time for a new project, so ask after the cutover unless an archive date comes first.
- Your research hours under a cap you set; no benchmark has been published.
Group size comes last.
| Rank | Group (Illustrative) | CEO path | Lineage complete | Dated event | Integration load |
|---|---|---|---|---|---|
| 1 | M, merged inspection firms | Yes, through a co-investor | Yes | Y's old system, June 2027 | Finished |
| 2 | R, HVAC services platform | Yes, through the operating partner | Two loose ends | B's old system, January 2027 | High until mid-2027 |
| 3 | Former portfolio company, now inside a strategic acquirer | No live path | Unknown | None known | Unknown |
Group R's January date comes first, so its operating partner may reasonably raise it now, limited to B's history, rather than wait for the integration to end. See also private equity operating partners and growth equity portfolio operations.
Earlier contact, one floor and one partner across a group
A group is still one company for the reward. A parent company and its subsidiaries count as one company: the USD 50,000 floor applies once across the whole group, to its first qualifying transaction, however many entities license; further qualifying transactions first agreed within 12 months of that first Closing pay 15% of their Actual Supplier Payout, with no cap.
| Entity licensing (Illustrative) | Actual Supplier Payout | Partner reward on that transaction | Cumulative partner reward |
|---|---|---|---|
| Survivor or operating company, the group's first qualifying transaction | $120,000 | $56,000: USD 50,000 plus 5%, which beats 15% | $56,000 |
| Subsidiary C, within the Repeat Window | $180,000 | $27,000, 15% with no floor | $83,000 |
| A later license by the same group, within the Repeat Window | $160,000 | $24,000, 15% with no floor | $107,000 |
In a group, credit still goes to one partner per company: the one with the first valid introduction under the 90-day attribution window, recognized when the company submits a verified application. Companies that already have an application, a relationship or an earlier valid introduction are reviewed as duplicates, and the terms count any earlier lead, account or email correspondence with SourceX as a relationship. Whether a parent's earlier contact, or another partner's introduction of a sister company, affects credit for your introduction is not settled in the published terms; SourceX decides it in duplicate review. Before anyone makes an introduction, ask the group CEO whether any entity has been in touch with SourceX, and write the answer down.
Where the lineage map can mislead
- The documents decide, not the label. A purchase agreement or separation agreement can move or keep records in ways the deal type does not suggest; counsel reads it, and SourceX's rights review decides.
- Law varies. Section 259 covers Delaware corporations; other states, countries and entity types have their own rules.
- Public records lag. Registry filings trail the deal, and announcements rarely state the structure.
- Deal knowledge is confidential. What a fund learned in diligence can prompt a question to the CEO; it never goes into a message to anyone else.
- Integration spends goodwill. Asking a team mid-cutover to take on a licensing review costs the relationship owner something; no data on management reactions has been published.
- Acquisitions say nothing about demand. Whether demand for business records is rising is analysis that belongs on sourcex.si; this map stays on which company to introduce. Inbound buyers who appear after an announcement are covered in data offers after an acquisition announcement.
Method note. The map applies the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's screening and referral pages, Delaware's merger statute and the SEC's Form 8-K guidance, all checked on 26 October 2026. Groups R and M, their deals and payouts are invented, and the map has not been tested on a real cohort. It records where records sit and who decides, not record quality, rights or demand. To test it, map every acquisitive company in your network and count lines that end at a known holder and CEOs who agree to talk within 60 days. More in the guides library.
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 on your map ends at a known holder and the group CEO wants the conversation, register for a partner link, check the group against who qualifies and read the duplicate rules in the program terms; whoever submits signs the SourceX Channel Partner Agreement first.
Tracing an acquired company's records is preparation for an introduction; deciding whether SourceX itself merits investment is a different question, and investor materials on it are available on request through the SourceX investor overview.
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.