How to refer a business that recently centralized IT: a centralization sponsor map that shows who gained the view of every system, who still owns the records and why the question waits until the last site has moved

Short answer

Wait until the move is finished, then ask the CEO, not the new IT function. Centralizing IT puts every site's systems under one team, which makes the head of IT a well-informed guide, but it moves custody, not ownership: the records still belong to the business that created them, and the decision still sits with the CEO. Treat the centralization as context for a single question once the last site has cut over, and never ask IT for access, exports or summaries.

Visual briefFull-size diagram
An Illustrative line of disruption across twelve months: seven spikes from February to August, one per office moved onto the central platform, then a flat settled stretch; a green band from September to January reads ask the CEO, a marker at February reads old servers retire, and a note at the top reads decides: the CEO, not central IT.
Illustrative. The engineering firm in example A: the question waits for the last office to move and settle, and comes before the company's own retirement date.

This page is for the partner network strategist whose consultants, accountants or operating partners watched a client fold site-by-site IT into one central team and wonder whether that is the moment to mention SourceX.

Custody moves to one team; ownership does not

Before, each office, plant or division ran its own servers, file shares and local applications, often with its own administrator. After, one team runs one service desk on a standard set of platforms, and the old local systems are retired on dates the company sets. That is a real change in who runs things. It is a much smaller change in who owns things.

Changes handsStays where it was
Administration of servers, file shares and applicationsWho created the records: the sites and units that did the work
The inventory of every system, with retirement datesWhose records they are, and what customer contracts say about them
The service desk and every access requestWho decides on a licensing discussion: the CEO
Retention and backup settingsThe company's right to refuse any outside request

ISO's governance standard draws a similar line between running IT and governing it. ISO/IEC 38500:2024 addresses its principles on the effective, efficient and acceptable use of IT to an organization's governing body, which it says can include owners, directors, partners and executive managers, while recognizing that governance happens throughout the organization (our paraphrase of the standard's summary). A centralization reorganizes how IT is run; it does not move the governing decisions into the IT function. A licensing discussion sits further from IT still. Under the program it is the CEO's call.

Is a recent centralization a good moment to ask?

Often, once it is finished, for three reasons.

  1. One place to answer from. The CEO can now ask one person what systems exist, how far back they go and which are retiring.
  2. Dates are real. A retirement date the company has stated for an old site system is a documented event, the honest kind of urgency.
  3. Leadership has just looked. A centralization forces a company to list what it holds, which makes a question about its own records easier to hear.

It is the wrong moment when:

  • Cutovers are still under way. Each site's move is a disruption for the people who run it.
  • The centralization follows an acquisition still being integrated. Until closing, the target's CEO decides for the target and the integration plan is not the partner's to discuss; after closing, the acquirer's CEO decides.
  • Site IT roles were cut as part of the change. A question about records arriving beside job losses reads as opportunism.
  • A security incident or audit has the central team's full attention.
  • The question would add work to the central team, such as scoping, counting or sampling anything.

The window opens when the last site has moved and the central team says the platform is stable, and it runs up to the company's own stated retirement date for the old systems. If that date falls before things settle, an earlier question to the CEO is fair. Keeping or retiring any system stays the company's decision.

The centralization sponsor map

Centralization reshuffles who knows what. It does not reshuffle who decides. The map names each person a partner is likely to meet, what the change did to their role, and what they can and cannot do for an introduction.

PersonWhat centralization changed for themCan carry the question to the CEODecidesNever asked for
Head of central IT (CIO or IT director)Gained the inventory and administration of every systemYes, and can name systems and years if the CEO asks them toNoCredentials, admin access, exports, samples or record counts
Former site IT staff and office managersLost their local systems but remember their historyRarely; the route runs through the central team or leadershipNoA way around the central team
Division and business-unit leadersNothing: they still create and use the recordsYes, and they can explain what work the records reflectNoCopies of their unit's files
CFO or COO who owned the centralization budgetOwns the plan, the dates and the costYesNoRetirement dates to repackage as urgency of your own
Outside MSP or integrator that ran the migrationHolds access under its contractNot with anything it holds for the client; if it wants to introduce, it asks the CEO itselfNoAnything it administers for the client
The CEONothingNo need: the CEO is the one askedYesA decision on the IT team's say-so
The acquirer's CEO, after a closed acquisitionNow runs the combined groupNo need: the one askedYes, for the acquired companyAn answer for the target before closing

A sponsor is useful and is never the yes. The contact-level permission guide shows how to record the difference between a keen IT director and a CEO who agreed.

When a centralization spans several companies in one group, such as a shared-services IT team serving four subsidiaries, the shared team decides for none of them. The question goes to the CEO of the company whose records it concerns, and how a group's documents spread that authority is covered in holding company decision rights. The program has no cap on rewards; the USD 50,000 floor applies once per referred company, to its first qualifying transaction, and further qualifying transactions with that company first agreed within 12 months pay 15%. If one group company has already been in contact with SourceX, the terms do not say how that bears on credit for its sister companies; SourceX makes that call in duplicate review, case by case.

Method note. The map applies SourceX's screening page and the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), plus the summary of ISO/IEC 38500:2024, all checked 2026-10-27. It sorts roles and timing. It does not estimate how often a centralization leads to an introduction or a license, and no such figures have been published.

Putting the question to the CEO

  1. Confirm the move is complete, from the CEO, the head of IT or a public statement.
  2. Name the entity and its CEO, with the date you checked.
  3. Find the route. If you know the CEO, ask directly. If not, ask a sponsor whether the CEO would want to hear about it, and let the sponsor decide whether to carry it.
  4. Ask once, with your interest disclosed.
  5. Record it: the date, the answer in a few words and the next step with its owner. If the CEO wants IT involved, the CEO tells IT. You never go to IT for content.

Illustrative wording. "Now that every office runs on the central platform, one question that has nothing to do with the project: SourceX licenses records companies created in their own work, such as procedures and project files, for AI training and evaluation. Would you like an introduction to find out whether any of yours might fit? I'm a referral partner, so SourceX could pay me a reward; it would come from SourceX, not out of what your company receives. No is a perfectly good answer, and I won't raise it with your IT team."

That last point about the company's amount rests on the terms: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation" (section 4). On a written yes, whoever will submit registers and signs the SourceX Channel Partner Agreement before submitting. Credit then follows the attribution rule: one partner per company, the first valid introduction within the 90-day window, recognized once the company has submitted a verified application. A company with any earlier application, account or email exchange with SourceX is reviewed as a duplicate, credited to no partner.

Three centralizations, three answers (Illustrative)

Illustrative. Generic companies; every detail is invented, and nothing here forecasts a result.

A. Ask now. A 380-person engineering firm moved seven offices' file servers and project tools onto one central platform between February and August. In September its CEO tells the firm's outside accountant that the old office servers retire next February. The accountant asks the question in October, discloses the possible reward, and gets a written yes. The IT director is never asked for anything.

B. Wait. A 260-person distributor is halfway through moving its branches, and the IT director is working weekends. The partner sends nothing, notes the date the company gave for the last branch, and plans to ask the CEO after it.

C. The right CEO in a group. A holding company has moved four subsidiaries onto a shared-services IT team. A division leader at one subsidiary is keen and offers to "get IT to pull something together." The partner declines, asks whether that subsidiary's CEO would want to hear about the program, and waits for the CEO's own answer. No cap applies; the USD 50,000 floor is paid once per referred company, on its first qualifying transaction.

Neighboring situations with their own pages

A centralization is one internal team taking over. If a client instead works with several outside providers at once, the provider-owner coordination map applies. Managed service providers thinking about their own clients start from the MSP partner page and the answer on whether an IT provider can share client data. Consolidations driven by an acquisition have their own pages on tenant consolidation and ERP consolidation. More trigger playbooks are in the guides library.

What a finished centralization still does not tell you

  • Centralized is not the same as a fit. The company faces the usual screen: 50 or more full-time employees at its high point with contractors not counted, years of records it created, the right to license them and a CEO who wants the conversation.
  • Central IT may refuse outside requests. A policy that every external request goes through IT is the company's to set. It shapes how you behave, not who decides.
  • Old site systems may already be gone. Retention choices made during the move are the company's own; never advise on what should have been kept.
  • Security questions are SourceX's to answer. If a CEO or IT director asks how records would be handled, point them to SourceX rather than answering on its behalf.
  • Nothing has been measured. Whether centralizations lead to more introductions than other triggers is unknown. Log each one you hear about, the date the last site moved, when you asked and the CEO's answer, over two quarters; no figures are published.

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 last site has moved and the CEO asks to hear more, register as a partner before submitting, check the company against who qualifies and read the program terms on duplicates and groups.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

The new IT director offers to pull a list of systems for SourceX. Should a partner accept?

No. Decline politely and keep the conversation at the question of whether the CEO wants to talk. If the CEO says yes and later wants IT involved, the CEO asks IT directly and the company deals with SourceX itself; nothing passes through the partner.

Should a partner wait until the old site servers are switched off?

No. A retirement date the company has stated is a reason to ask before it, once the move has settled. Whether anything on those servers is kept is the company's own decision, and a partner gives no advice on it.

Our firm ran the centralization project. Can we still introduce the client?

Possibly, as long as the introduction stays apart from the engagement. Ask the CEO directly, use nothing you saw through your project access, register and sign before submitting, and keep referral notes out of the client's systems.

Sources

  1. refer.sourcex.si/who-qualifies
  2. refer.sourcex.si/terms
  3. iso.org/standard/81684.html

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment