# Customer operations spinout referral map | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-company-splits-customer-operations-into-a-new-entity
Last updated: 2026-11-05

Ask about each entity separately, and only once the split has settled. The new customer-operations entity's own CEO decides for it, and the original company's CEO decides for whatever stayed behind. Case history often splits too: years written before the split may stay with the original company, the new entity writes its own from launch, and cases it handles for the original company or outside clients may be those clients' material rather than its own. While both entities sit in one corporate group, they share one reward cap.

## What moves when customer operations become their own company

Customer operations means the teams and systems that look after customers once the sale is made: support desks, contact centers, service dispatch, returns, and the knowledge bases behind them. A company may move them into a new legal entity to run them as a shared service, to sell the service to outside clients, or as a first step toward selling the unit. Whatever the reason, three things shift at the same moment.

- **Who employs the people.** Staff move onto the new entity's payroll, and with them go the people who understand the case history.
- **Where new records are written.** Some splits give the new entity its own systems on day one; others leave it working inside the original company's tools for months.
- **Whose work it is.** When the new entity serves the original company under a services agreement, the cases it handles may be its client's material, not its own.

Who may license each span of history is settled by the separation documents, the companies' counsel and SourceX's rights review, never by a partner's reading of them. SourceX also asks suppliers to confirm they hold the rights to license what they offer and that it has not been licensed for AI training before. The partner's job is narrower: know which questions exist, and know whom to ask.

## The spinout sponsor and rights map

One row per span of records, six columns, and every cell filled from what the CEOs or their sponsors say. No file is opened to fill it.

| Span of records | Held by | Whose material it looks like | Whose CEO decides | Who can explain it | Partner's status |
|---|---|---|---|---|---|
| Case history written before the split | Usually the original company, unless the separation documents moved it | The original company's own, subject to its customer contracts | The original company's CEO | Often a former manager who now works for the new entity | Ask that CEO |
| Cases the new entity handles for the original company | The new entity's tools, or the original company's under a services arrangement | Possibly the original company's material, handled as a service | Open until the documents are read | The new entity's operations lead | State it to SourceX as a rights question; promise nothing |
| Cases the new entity handles for outside clients | The new entity | The outside clients' material | Not the new entity's to license | Not needed | Usually not a fit |
| Playbooks, QA rubrics and training the new entity wrote itself | The new entity | The new entity's own | The new entity's CEO | Its quality or training lead | Ask that CEO |
| Knowledge base articles written before the split and copied across | Possibly both | Depends on the separation documents | Open | Whoever maintained the knowledge base | State it to SourceX as a rights question |

The second and fifth rows are where splits get hard. SourceX's who-qualifies page lists material that belongs to a company's clients among the usual reasons a company is not a fit, and after a split the original company can become the new entity's biggest client. That does not end the conversation. It means the question travels to SourceX as a stated question, not to a CEO as a promise.

The "who can explain it" column matters more than it looks. The people who understand the pre-split history usually moved with the work, so the original company's CEO may decide about records that only the new entity's staff can describe. How the two companies cooperate on that is for their CEOs to agree; a partner does not broker it.

**Method note.** The map's rows and columns are this page's design, built from SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), its who-qualifies and how-it-works pages and the sample Channel Partner Agreement, all read on 2026-10-27. It records who holds, who decides and who can explain; it does not assess rights, demand or any payout.

## Two CEOs, one cap

The new entity's own CEO decides for the new entity, even when the original company's CEO chairs its board. The original company's CEO decides for the original company and the history it kept. Neither can say yes for the other. If the new entity is being sold, its own CEO decides until the sale closes; once it closes, the acquirer's CEO decides.

While both entities belong to one corporate group, they count as one company for the reward cap. By default the reward is the greater of $50,000 plus 5% and 15% of what SourceX actually pays, with no cap across the whole group however many of its entities license. The terms say nothing more about how a split affects credit. If the original company already has a lead, an account or email history with SourceX, whether that bears on an introduction of the new entity is for SourceX to decide in duplicate review; state the history plainly and claim nothing.

Size and age deserve a separate line for each entity. Give each one's own peak full-time headcount, contractors left out, and let SourceX read the figures; the terms set 50 or more full-time employees at peak for introduced companies. A new entity's own records also start at the split, and SourceX's screening baseline is several years in operation, though some programs set higher thresholds.

## Has the split settled? Five checks before outreach

1. **Is the new entity formed, with a named CEO?** Until it is, nobody can answer for it.
2. **Has the cutover happened?** Staff on the new payroll, calls and tickets routed to the new entity. A question in the cutover month competes with the hardest weeks of the project.
3. **Who holds the systems today?** If the original company still runs the tools under a services arrangement, the records may sit with it for now. Ask who holds them; never ask to see them. Section 4.2 of the sample Channel Partner Agreement gives a partner no right to share a company's records or to reach the systems they come from.
4. **Is the split part of a sale?** If a buyer is in view, timing belongs to the people running that process. Hold until the deal closes or is dropped, then ask whoever is CEO.
5. **Are jobs or a dispute tied to the split?** Redundancies, a contested contract or a disagreement between the two entities. Wait until it has settled.

A split that passes all five is a fair moment. Both CEOs have just decided which history goes where, so the question is concrete instead of hypothetical.

## Separate questions for separate companies

Ask each CEO about their own company, in separate conversations, and never let one answer for the other. Two illustrative openings:

> To the original company's CEO: Before the split, your teams wrote eleven years of service cases. Would you like to hear how SourceX licenses a company's own operating history for AI training and evaluation? Your company would be paid the same whether or not I am involved, and SourceX could pay me a reward if you go ahead.

> To the new entity's CEO: Since launch your team has written its own playbooks and quality rubrics. Would a conversation with SourceX about licensing material your company created be useful? The same disclosure applies: I could be paid, and your payout would not change.

Record one line per entity: the entity, its CEO, the date, the answer, the next step and its owner. Each introduction covers one company whose CEO agreed, and the partner signs the Channel Partner Agreement before submitting either. The payout line rests on section 4 of the terms: the reward "is paid separately by SourceX and is never deducted from the supplier’s agreed compensation," because SourceX pays it from its own share. For more on several companies from one group, see [introducing companies from the same corporate group](/questions/can-i-introduce-several-companies-from-the-same-corporate-group).

## A service desk becomes its own company (Illustrative)

Illustrative. A generic company, invented facts and dates.

A 900-person equipment distributor moves its 160-person customer service team into a new subsidiary in April 2025. The new entity keeps serving the distributor's customers under a services agreement, signs two outside clients in its first year and runs on its own helpdesk from day one. The distributor's old helpdesk, holding cases from 2014 to March 2025, stays with the distributor in read-only mode. The former head of support now runs the new entity as its CEO.

| Span | Held by | Whose material | Who decides | Status in November |
|---|---|---|---|---|
| Distributor cases, 2014 to March 2025 | The distributor's read-only helpdesk | The distributor's own | The distributor's CEO | Asked; answer "yes, after our year-end close" |
| Cases for the distributor since April 2025 | The new entity's helpdesk | Possibly the distributor's | Open | Stated to SourceX as a rights question |
| Cases for the two outside clients | The new entity's helpdesk | The clients' | Not the new entity's | Usually not a fit |
| The new entity's own playbooks and rubrics | The new entity | Its own | The new entity's CEO | "Later; we are eighteen months old" |

Two CEOs gave two different answers, and each answer covers only its own company. Both companies sit in one group, so one cap covers whatever either of them licenses. The person who knows the 2014 to 2025 history best now runs the new entity, so if the distributor goes ahead, the two CEOs agree between themselves who explains it.

## Where a split map can mislead you

- **The documents decide, not the map.** Separation and services agreements allocate records; the map only records what the CEOs say about them. Who holds what after a sale to an outside buyer is traced in [the divestiture sponsor map](/guides/when-a-divestiture-splits-the-data-and-the-decision-makers), and the two main structures are compared in [spin-off versus carve-out](/compare/spin-off-vs-carve-out).
- **Shared tools blur the rows.** When both entities work in one system, a span that looks like one company's may hold both companies' cases.
- **Young entities have short histories.** The new entity's own records start at the split, which can leave little to discuss for years.
- **Splits reverse.** A company that later takes the work back runs the map in reverse; that move has its own guide, [bringing outsourced work back in-house](/guides/when-a-company-brings-outsourced-work-back-in-house), and the opposite of a split is covered in [combining two support teams](/guides/the-referral-conversation-after-a-company-combines-two-support-teams).
- **Customer details in the cases.** Case records name real customers. SourceX's how-it-works page places de-identification inside its own preparation step, through approved processing routes, after it gives the go-ahead; a partner has no part in it and makes no promise about it.

## 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 split has settled and a CEO wants to talk about their own company's records, [register as a partner](/register), check that entity on its own against [who qualifies](/who-qualifies), and read the [program terms](/terms) on caps and duplicates before you submit. Other business-change playbooks sit in the [guides library](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/how-it-works
