# Growth story, fragmented systems: a risk map | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-company-s-growth-story-hides-fragmented-systems
Last updated: 2026-11-05

Read a growth story as a pointer to where records were split, not as evidence that the company fits. Acquisitions, platform migrations, regional expansion and fast hiring each scatter operating records across tools and legal entities. Scattered systems rarely end a referral on their own, because SourceX manages data preparation. What ends one is history deleted when an old system is switched off, rights left with an acquired entity or a client, or a CEO who does not speak for the entity that holds the records. Map each growth move against those risks before anyone asks the CEO.

## The growth signal, its source and its blind spot

A growth signal is any public or semi-public sign that a company changed size or shape: an acquisition announcement, a headcount jump visible in hiring, a new country office, a replaced CRM or ERP, a financing. Each one comes from somewhere you can date, usually the company's own press release, board materials or a filing. Each one tells you the company changed. None tells you whether the records from before the change survived it.

| Growth signal | Where it usually comes from | What it tells you | What it leaves out |
|---|---|---|---|
| Acquisition announcement | The acquirer's press release or board pack | A business joined the group on a date | Whether its old systems were kept, merged or switched off |
| Headcount jump | Hiring activity, board updates | The company is adding people | How many are full-time employees rather than contractors |
| New region or country office | Company announcement, local registration | A new entity or team exists | Which entity holds that region's records, and in which language |
| System replacement | Vendor case study, board pack, IT roadmap | A new platform is live | Whether the full history moved or only open records |
| Financing round | Company announcement or securities filing | Capital was raised | Anything about records, rights or authority |

Age is the clearest example of the blind spot. The U.S. Census Bureau's Business Dynamics Statistics give a firm the age of its oldest establishment when the firm is born, so a firm that starts life by acquiring an existing business can begin with an age above zero. A referral screen needs the same habit. A holding company formed three years ago may own an operating business that has kept records for thirty, and those records live in that business's systems, not the parent's.

## The fragmentation referral risk map

The map pairs six common growth moves with the fit fact each one puts at risk. Rate each cell on one rule: **High** when the move can make a fit fact false or unknowable unless someone acts by a date; **Watch** when it adds work that SourceX's review and preparation normally absorb; **Low** when it leaves the fact untouched.

| Growth move | What fragments | Fit fact most at risk | Risk | Metadata question for the relationship owner |
|---|---|---|---|---|
| 1. Acquisitions or a roll-up | Each acquired business keeps its own email, ERP and ticketing until integration | History and rights | High | Which acquired businesses still run their pre-deal systems, and when is each due to be switched off? |
| 2. Platform migration during scale-up | Old CRM or helpdesk history left behind, or imported without notes and attachments | History | High once a switch-off date exists | Did the full history move, or only open records, and can anyone still read the old system? |
| 3. Regional expansion | Separate instances and local entities per country | Rights and location | Watch | Which entity and country holds each region's records, and in what language? |
| 4. Fast hiring with tool sprawl | Teams buy their own tools, so daily work spreads across many small systems | Depth per system | Watch | Which three systems hold the work that repeats every day, and since when? |
| 5. Carve-out or divestiture | Records split between seller and buyer under transition arrangements | Rights and authority | High | Which side owns the carved-out records under the sale documents, and which CEO speaks for them? |
| 6. Contractor-heavy scaling | Headcount looks large while much of the work sits with contractors, sometimes in their own tools | Headcount and rights | Watch | How many full-time employees at peak, contractors excluded, and whose systems do contractors work in? |

**Methods note.** The rows come from the growth moves investors most often read about; the columns come from the published fit facts (SourceX terms and who-qualifies page, checked 2026-10-26) and the owner's rulings on authority and corporate groups. The risk rule above is this page's own. The map does not measure how often each move ends a referral, what any company's records are worth or whether they match current demand. Only SourceX's review assesses those. For the systems themselves, the live guide on [assessing a large company with fragmented business systems](/guides/how-to-assess-a-large-company-with-fragmented-business-systems) covers how to look at departments and subsidiaries one at a time.

## What the old systems still hold, and the switch-off date that ends it

The test of a growth signal is one question: where did the records from before the change go? Three answers are common. They moved in full. They moved in part, usually open records without the closed history, notes or attachments. Or they stayed in the old system, which is now on a decommissioning plan.

The third answer carries a date. Microsoft says that after a Microsoft 365 for business subscription is canceled, customer data left behind might be deleted after 90 days and will be deleted no later than 180 days after cancellation. When an acquired company's old tenant is canceled after integration, its email and files are readable only until then. That is the kind of urgency this program accepts: a documented retention event, not a quarter-end. Other systems follow their own vendor terms, so each date has to be checked separately.

Your part stays at metadata level. Ask the relationship owner whether the CEO knows the switch-off date and who owns the decommissioning plan. Do not ask for exports, screenshots or samples. Whether to keep a full copy is the company's decision, made with its own IT team and counsel. The live guides on [system decommissioning after an acquisition](/guides/system-decommissioning-after-acquisition) and [Microsoft 365 tenant-to-tenant migration](/guides/microsoft-365-tenant-to-tenant-migration-after-acquisition) show what that work involves on the company's side.

## A roll-up and a hypergrowth company on the same map (Illustrative)

Illustrative. Generic companies, invented facts, no outcome implied.

**Company A** is a 380-person property inspection group formed in 2021 by buying five regional firms founded between 1994 and 2012. Each firm kept its own scheduling and reporting system. Two have moved onto the group platform, and their old tenants are due to be canceled next quarter. The group's CEO is reachable through a co-investor who sits on its board.

**Company B** is a four-year-old support outsourcer that grew from 30 to 240 people and replaced its helpdesk twice. Most of its ticket history lives inside its clients' helpdesk accounts. Its own QA reviews, playbooks and training records sit in its internal systems. Its founder-CEO is a portfolio founder you speak to monthly.

| Question | Company A | Company B |
|---|---|---|
| Full-time employees at peak, contractors excluded | 380 today, its peak | About 190 of 240 are full-time |
| History still readable | Up to 30 years across five firms, two of them on a deletion clock | Four years, broken by two helpdesk changes |
| Which entity holds the records | Five subsidiaries, not the parent | One operating company |
| Company-created or client-owned | Inspection reports are delivered to clients; working files are internal | Ticket history largely client-owned; QA and playbooks internal |
| CEO of the record-holding entity reachable | Group CEO, through the co-investor | Founder-CEO, directly |
| Dated event | Two tenant cancellations next quarter | None |
| Map rows triggered | 1 and 2, both High | 2 and 6, Watch |

Company A goes first, through the co-investor, because its history is deep and part of it has a documented end date. Company B is a slower, narrower conversation: the client-owned ticket history is usually not a fit, so any introduction would rest on its internal records, and SourceX decides in review whether those match a current program. Neither company's fit is settled by the growth story that brought it to your attention.

## Rank the asks by retrievability, entity, CEO path and integration load

SourceX has not published conversion rates or typical payouts, so a ranking that guesses value only ranks guesses. Order fragmented companies on four things you can observe:

1. **Retrievable.** The history you would describe still exists in a readable system; no deletion date has passed.
2. **Entity named.** You know which legal entity holds the records, not just the brand in the headline.
3. **CEO path confirmed.** Introducing an acquired subsidiary or a carve-out often means a different approval path from the parent; name the CEO who speaks for the entity that holds the records, and a relationship owner who has agreed to ask.
4. **Integration load.** A CEO in the middle of a migration may say not this quarter. Record the date and ask again after go-live, unless a switch-off date falls before go-live, in which case say so plainly once and leave the decision with the CEO.

Set your own limit on open asks per relationship owner, one you can actually follow through on. Groups need one more check. For reward purposes a parent and its subsidiaries are one referred company, so a roll-up of five firms gets the USD 50,000 floor once, on the group's first qualifying transaction, and further qualifying transactions first agreed within 12 months of that first Closing pay 15% of their Actual Supplier Payout, however many of the firms license. Whether a parent's earlier contact with SourceX, or another partner's introduction of a sister company, affects credit is not set out in the terms; SourceX decides it in duplicate review. The [legal entity rationalization guide](/guides/legal-entity-rationalization-after-acquisitions) explains why entity lists change after a roll-up, and the [growth-versus-suitability guide](/guides/ai-data-companies-growth) covers fast growth without acquisitions.

The fit facts do not move with the growth story: a peak of 50+ full-time employees, counted without contractors; operating history the company can document; rights to license; a CEO who wants the conversation; and location. 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. Everything else waits for review: whether the records match current demand, what customer contracts allow and what a license would cover.

## Where the risk map can mislead

- **Fragmentation may matter less than it looks.** SourceX manages rights review and data preparation, so a company with many systems can be routine. The map flags where history or authority can be lost, not where the work is hardest.
- **Rights.** Growth through client work multiplies client-owned material, and SourceX's screening guidance treats material that belongs to clients as usually not a fit.
- **Demand.** SourceX checks relevance to its current data needs in review; some programs set higher thresholds, and a company declined today may fit a later program.
- **Synthetic data.** Epoch AI's report on AI in 2030 argues synthetic data could let scaling continue even as growth in human-provided data slows. If that holds broadly, demand for real records could narrow.
- **One retention example.** The 90-to-180-day window is Microsoft's for Microsoft 365 business subscriptions. Other vendors set different terms, and contracts can change them.
- **No frequency data.** Nobody has published how often each growth move ends a data introduction. Log each row's outcome and re-rate the map after ten asks.

Before anyone submits, the person registering must have signed the SourceX Channel Partner Agreement, the document once titled the Channel Partner Non-Circumvention and Non-Disclosure Agreement. Teams running this across a growth portfolio can pair the map with the [growth equity portfolio guide](/for/growth-equity-portfolio-operations); more screening methods sit 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 a row on your map shows retrievable history, a named entity and a CEO path, [register for a partner link](/register), check that row against [who qualifies](/who-qualifies) and read the [program terms](/terms) before the relationship owner raises it with the CEO.

Spotting fragmentation in a growth company is referral work; sizing up SourceX as an investment belongs to another conversation, and the [SourceX investor overview](https://sourcex.si/investors) takes requests for investor materials.

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://refer.sourcex.si/how-it-works
- https://learn.microsoft.com/en-us/microsoft-365/commerce/subscriptions/what-if-my-subscription-expires?view=o365-worldwide
- https://www.census.gov/programs-surveys/bds/documentation/methodology.html
- https://epoch.ai/files/AI_2030.pdf
- https://sourcex.si/investors
