This page is for partners who serve multi-branch companies: consultants, accountants, systems partners and advisors who hear about these programs early. It is about timing and authority. What the company does with its own records during the program is the company's business, and this page leaves it there.
What a standardization program changes, and what it leaves alone
A standardization program picks one reference way to run a set of processes, such as quoting, dispatch, service or billing, and moves each branch onto it. To compare branches, the program needs a shared list of processes. Some companies write their own; some start from a published taxonomy such as APQC's Process Classification Framework, which APQC describes as "a taxonomy of business processes that allows organizations to objectively track and compare their performance."
Whatever list it uses, a program that maps every branch against it produces something an outside partner rarely sees: a written answer to which branch does what, in which system, and who runs it. That answer is close to the descriptive level a licensing conversation starts from: which kinds of records exist, roughly how many years, in which system and under whose care. It never needs the records themselves. The sample Channel Partner Agreement gives a partner no authority to share a company's inventory or records, or to access its systems (section 4.2), and SourceX's screening questions are asked in conversation, never through files, samples or logins.
What the program leaves alone matters as much. It does not change who owns the company's records, who can license them or who decides. It does not make anyone's records fit. And it does not give a partner a reason to talk to branches.
A fair moment, and when it is not one
Four features make the program a reasonable time to ask:
- The CEO sponsors it. The question joins a conversation the CEO is already having about how the company works.
- A named program lead exists. If the CEO wants to explore, someone can describe the branches without starting from zero.
- A branch-by-branch inventory exists. The company can answer "what do we have, and where" from work already done.
- A dated cutover. A real date, such as a local tool's retirement, gives the company's own decision a deadline that nobody invented.
The same program can make the question unwelcome. Run this check before raising it.
| Signal | Raise it | Hold |
|---|---|---|
| The CEO or a public announcement told you about the program | Yes | If you heard it in confidence from someone else |
| Design approved, first rollout wave scheduled | Yes, before the first wave | No reason to hold |
| Several branches going live this month | No | Until those branches are stable |
| The program comes with branch closures or layoffs | No | The question would read as opportunism |
| You are paid to deliver part of the program | Only in a separate, disclosed conversation | If your engagement terms forbid it |
| A local tool has a published retirement date | Yes, naming the date as the company's own fact | No reason to hold |
Method note. The four features and the timing check are this page's reasoning, built from SourceX's who-qualifies page and terms (Version 2026-10-22.2, since replaced by version 2026-11-04), section 4.2 of the sample Channel Partner Agreement and APQC's description of its framework, all read on 2026-10-27. No figures have been published on how often standardization programs lead to licensing conversations; the worksheet below is a method, not a measured result.
The branch-owner discovery worksheet
The worksheet has two parts. Fill Part A before you ask. Fill Part B only if the CEO wants to explore and asks the program lead to describe the branches; many introductions never need it, because the company can apply and describe itself.
Part A: company facts, before the question
| Field | Example (Illustrative) | Where it comes from |
|---|---|---|
| Operating entity that holds the branches' records | The operating company, not the holding company above it | Public records or the CEO |
| CEO, and since when | Chief executive since 2019 | The company's website or the CEO |
| Group status | Owned by a private equity platform; the platform CEO decides | The relationship holder |
| The program and its lead | A one-year standard operations program led by the VP of operations | The CEO |
| Phase and next dated milestone | Design approved; first wave in the first quarter | The CEO or program lead |
| Full-time headcount at its peak | About 320, contractors excluded | The CEO |
The location test sits beside the headcount. 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.
Part B: one row per branch group, only with the CEO's go-ahead
Illustrative: a 14-branch equipment rental company with about 320 full-time employees at its peak.
| Branch group | Who runs the process there | Local system, and since when | What the standard changes | Confirmed by, and date |
|---|---|---|---|---|
| North, 5 branches | Branch service managers | Rental management app, since 2011 | Moves to the central platform in wave 1 | Program lead, 4 November |
| South, 6 branches | Branch managers | Same app since 2014, plus local spreadsheets | Moves in wave 2 | Program lead, 4 November |
| Two acquired branches | The former owner's office manager | Their own system, since 2009 | Wave 3; their entity merged into the operating company in 2024 | CEO, 4 November |
| Central workshop | Workshop supervisor | Maintenance log in the central platform, since 2018 | No change | Program lead, 4 November |
Never on the worksheet: files, exports, samples, screenshots, logins, customer names or employee names (roles only). The acquired branches show why entity history matters; legal entity rationalization after acquisitions covers that ground. For a metadata-only list of the company's systems beyond the program, see preparing a metadata-only inventory.
Owner, sponsor and the people you never ask
- The owner is the operating entity, and its CEO decides. If the company was acquired, the acquirer's CEO decides; before a sale closes, the target's CEO still does. The reward cap is shared across a corporate group, so the two acquired branches above fall under the same single cap as the rest of the company.
- The program lead can sponsor, not authorize. A VP of operations who believes in the idea can carry it internally if the CEO wants, and can answer Part B. The yes stays with the CEO.
- Branch managers hold knowledge, not authority. Never raise the topic with them first and never ask them to compile anything. A question asked branch by branch starts several conversations nobody approved. The general case of who decides across many sites is set out in referring a multi-location business.
Date every fact. Programs move people around, and a sponsor in October may report to someone new by January.
One question, and the record of what was agreed
Illustrative wording:
You are moving the branches to one way of working this year. Separately from that program: would you want a conversation about whether the company's own operating records could be licensed to SourceX for AI training and evaluation? It is entirely your call. You should know that SourceX could pay me a referral reward if the company licenses anything, and that the company's payout would be the same either way.
The last sentence rests on section 4 of the terms, which says the reward is paid separately by SourceX and is never deducted from what the company is paid. Then write down four things: the date, the CEO's answer in their own words, the next step the CEO agreed to and who owns it, and anything the CEO asked you not to do.
If the answer is yes, sign the Channel Partner Agreement before you submit, and let the company apply itself. SourceX credits the earliest valid introduction of a company it did not already know, and only after that company files a verified application inside the 90-day window; a company that already corresponds with SourceX is a duplicate. If the answer is "after wave 2", record that milestone and say nothing until it arrives. If a private equity firm owns the company, as in the Part A example, whether to go through its operating partner or straight to the CEO is compared in sponsor route or CEO route. Other moments when a business change opens the question are gathered in the guides hub.
Where the branch trigger misleads
- A standard creates no rights. Records that belong to clients are usually not a fit however tidy the process around them, and customer contracts can limit reuse.
- Size and history still apply. Fourteen branches can still fall short if full-time headcount never reached 50 at its peak, or if the branch tools hold only a year or two of history.
- Some programs are cuts in disguise. If standardization arrives with closures, hold, whatever the program is called.
- Your own engagement. A partner paid to deliver the program has a conflict to manage; keep the referral out of the engagement, as described in separating paid work from a referral arrangement.
- Fit is decided in review. Current demand and rights are assessed only by SourceX, and each program applies its own criteria.
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.
Once Part A is complete and the timing check says raise it, register as a partner, compare Part A with who qualifies and read the program terms before the CEO hears the question.