# Insourcing and data referrals: who holds what | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-company-brings-outsourced-work-back-in-house
Last updated: 2026-11-04

When a company takes work back from an outsourcing provider, it starts writing its own records of that work from the day its team goes live, while the earlier years may still sit in the provider's systems. That split is what makes the moment useful for a referral question: the CEO is already deciding what the company should hold and run itself. Ask the CEO, through whoever holds the relationship, which part of the history the company now owns and keeps. The company confirms its rights; SourceX reviews them.

Insourcing is a business decision about cost, control or quality, and the partner has no part in it. The opening comes afterward, once the company knows where its records ended up.

## The day the work comes home, the record changes hands

During the outsourced years, someone else's people did the work, often in someone else's tools. After the move, the company's own staff do it in systems the company runs. Everything a partner needs to know follows from that change, and none of it requires opening a file.

Insourcing is a planned route out of outsourcing, not an accident. The European Banking Authority's outsourcing guidelines say an arrangement should make it possible to move a function to another provider "or its re-incorporation into the institution or payment institution", and they call for a documented exit plan for each critical or important outsourced function. The search excerpt we read also described the contract setting out the provider's duties in either case, including how data is handled, and a transition period (our paraphrase). Those guidelines bind only the institutions they cover. What they show is that a well-run exit treats the handover as a project with a plan and dates, which is exactly the kind of company-owned calendar a partner should wait for.

## Why the CEO's question fits the insourcing moment

Three features make the question relevant rather than opportunistic.

- **The CEO is already deciding what to own.** New systems, new hires and new processes are on the table. A question about which history the company holds belongs in that conversation.
- **The company's own record has a start date.** Go-live marks the day the company began writing its own history of this work. That turns the screening question about documented operating history into a plain fact with a date.
- **The exit runs on the company's calendar.** Transition periods and handover dates come from the company's plan. They are the only timing worth mentioning, and only when the company mentions them first.

Before raising it, check four things. Is the handover finished, or at least its end date known? Is the company free of an open dispute with the provider? Does someone you can ask hold a relationship the CEO would answer? And can the question be asked without any record changing hands? If you are the outgoing provider, or work for it, leave the subject alone until the exit is complete and the relationship continues on its own terms.

## The insourcing rights-owner question map

Every insourced function leaves its history in up to five layers. The map asks, for each layer, who created the records, where they sit now and who at the company can answer for them. The partner's column holds the only question a partner asks; everything else is the company's to confirm.

| Layer | Typical records | Created by | Sits where now | Who at the company answers | The partner's metadata question |
|---|---|---|---|---|---|
| 1. In-house since go-live | Tickets, job notes, approvals and quality reviews written by the new team | The company's own staff | The company's systems | Head of the insourced function | Since when, and in which system? |
| 2. Provider years, company's system | Work the provider's people logged inside the company's own platform | The provider's people | The company's systems | System owner, with the CEO deciding | Did the provider work in your systems or in its own? |
| 3. Provider years, handed back | Exports, reports and files the contract required at exit | The provider, delivered to the company | The company's archive | Whoever ran the exit | What did the handover deliver, and who keeps it now? |
| 4. Provider years, still with the provider | Records kept in the provider's own platform after the exit | The provider | The provider's systems | The company, by asking its former provider | Is anything you would want still with them? |
| 5. The provider's own know-how | Scripts, playbooks and training the provider wrote | The provider | The provider | Usually nobody at the company | Who wrote the playbooks your team now uses? |

Layer 1 is the cleanest history: records the company now creates itself, in systems it controls. Its weakness is age, since a team that went live last spring has one year of it. Layers 2 and 3 are where most of the depth sits, and where rights depend on the contract the company signed; the company confirms what it may license, and SourceX's process runs its own rights check during qualification. Layer 4 is not reachable by a partner at all: if the company wants anything back, it asks its former provider itself. Layer 5 is usually not the company's to offer unless its rights clearly cover it, and how process material is weighed is covered in [assessing rights over process materials](/guides/how-outsourced-support-providers-can-assess-rights-over-process-materials).

**Method note.** The layers combine SourceX's screening profile (records the company created, rights to license, client material and personal consumer data usually excluded) and its company process page, both read on 2026-10-27, with the exit structure described in the EBA excerpt above. The map has not been tested against completed introductions, and SourceX has not published how often insourced companies qualify.

## Three names and a date before anyone asks

Write down who runs the insourced work today, who ran the exit, and the CEO, with the date you confirmed each. The first two can answer the partner's metadata questions. Only the CEO can decide that the company talks to SourceX, and sign for it.

Check the entity, too. If the insourcing came with a reorganization, the records may now sit in a different subsidiary; for the once-per-company USD 50,000 floor on a first qualifying transaction, SourceX treats the whole group, parent and subsidiaries alike, as a single company. If the company is being acquired, the target's CEO decides until closing and the acquirer's CEO after it.

Whatever the layers show, the published fit facts still apply: at least 50 full-time employees at the company's peak, with contractors and outsourced staff left out; several years of records the company produced itself; a clear right to license those records; and a chief executive who wants to hear more. 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. Records already licensed to anyone for AI training are out: SourceX asks the company to confirm that has not happened.

## An order desk comes home at a 300-person distributor (Illustrative)

Illustrative. The distributor, its provider and every date here are invented, and nothing predicts how a review would end.

An industrial distributor with 300 full-time employees outsourced its order desk and returns handling to a business process provider in 2018. In March 2025 it brought the work back to a new in-house team of fourteen people.

| Layer | What the operations director says | Map result |
|---|---|---|
| 1. In-house since go-live | Order exceptions and returns approvals written by our own team since March 2025, in our ERP | Company's own; about eighteen months |
| 2. Provider years, company's system | Their agents keyed orders into our ERP from 2018 | Company's system; rights to be confirmed by the company |
| 3. Handed back | A returns-case export, 2018 to 2025, delivered at exit | In our archive; same rights question |
| 4. Still with the provider | Their call notes stayed in their own tool | Not reachable; the company has not asked for them |
| 5. Their know-how | Their scripts were rewritten by our team | Not offered |

The distributor's outside accountant, a registered partner who signed the Channel Partner Agreement last year, heard about the move at the year-end planning meeting. She waited until the transition period closed, asked the operations director the five partner questions over two calls, and then asked whether the CEO would want a short note on how SourceX screens companies. The CEO read it and said yes to a call. The accountant made the introduction with the CEO's agreement, the company applied itself, and the rights questions on layers 2 and 3 went to SourceX's review, where they belong.

If, after that review, the distributor licensed data and SourceX paid it USD 200,000 on a first qualifying transaction, the default reward would be USD 60,000 (Illustrative), the greater of USD 50,000 plus 5% and 15% of that payout. Section 4 of the terms says "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation", so the distributor's payout would be the same with or without her.

## The next authorized step, written down

After the CEO answers, record five things: the trigger and who mentioned it, the date the handover closed, which layers the company described, the CEO's own words, and the next step with its owner. A no gets a revisit trigger, such as "once the in-house team has two full years". A link click alone does not settle credit: under section 2, a company new to SourceX is credited to the earliest valid introduction inside its 90-day attribution window, once it files a verified application. A company that already had an application, lead, account or email exchange with SourceX is a duplicate under section 3. Where the provider, an adviser and a board member all know the company, only one introduction can be credited, and SourceX resolves overlaps in its duplicate review.

## Limits of the five-layer map

- **Contract wording decides layers 2 to 4.** This page does not interpret outsourcing contracts and gives no legal advice; the company and its own advisers read them, and SourceX reviews rights in qualification.
- **Young history.** A recent go-live can leave layer 1 too short to matter on its own.
- **Personal data.** Contact-center and order records often carry customer details. SourceX's screening treats personal consumer data as usually not a fit, so the useful part may be narrower than the volume suggests.
- **Records the company does not control.** Anything still in the provider's systems is outside the company's reach until it asks for it, and possibly for good.
- **Overlap with the outsourcing page.** For companies that still outsource, the [summary for a business with outsourced operations](/guides/a-referral-summary-for-a-business-with-outsourced-operations) applies instead; for client contracts that limit reuse, see [customer contract data use restrictions](/guides/customer-contract-data-use-restrictions), and for how licensing review differs from vendor diligence, the [vendor due diligence comparison](/compare/vendor-due-diligence-vs-data-licensing-review).
- **No published outcomes.** Nobody has published how often insourcing leads to a licensing conversation. Count layers described, CEOs asked and CEOs who said yes. Providers on the other side of this move have their own page, the [offshore outsourcing partner program](/for/offshore-outsourcing-partner-referral-program), and more trigger guides 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 the handover has closed, the company has described its layers and the CEO wants to talk, [register as a partner](/register), hold the layer answers up against [who qualifies](/who-qualifies), and read the attribution sections of the [program terms](/terms) before you send the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://www.eba.europa.eu/sites/default/files/documents/10180/2551996/38c80601-f5d7-4855-8ba3-702423665479/EBA%20revised%20Guidelines%20on%20outsourcing%20arrangements.pdf
