# Product expansion referral timing: a five-question test

Canonical: https://refer.sourcex.si/guides/a-business-expands-into-a-new-product-line-is-the-timing-useful
Last updated: 2026-11-05

Sometimes, and usually later than it feels. A new product line arrives with plans, forecasts and new hires, not years of operating records, so it is never the thing a company would license. The expansion helps only when it has sent the CEO back to what the existing lines already hold, such as procedures being rewritten to train the new team, and the launch rush is over. Run the five questions below first; if any of the first three fails, treat the expansion as news and wait.

This page is for the partner network strategist whose consultants, accountants or operating partners hear about a client's new product line early and wonder whether to use it as the moment to mention SourceX.

## A new line starts with a blank history

An expansion creates a plan, a budget, a hiring push and sometimes a new entity or a purchased line. It does not create history. The OECD's Oslo Manual 2018, a guide to measuring business innovation, counts a product innovation only when a new or improved good or service differs significantly from the firm's earlier ones and has been introduced on the market (our paraphrase). Two parts of that definition help a partner. The new line is, by design, unlike the work the company's existing records describe. And an announcement is not yet a product in the market, so it is not yet an event worth reacting to.

What SourceX screens for sits elsewhere. Its screening page asks for original documentation the company created itself, naming SOPs, internal knowledge bases, project histories, QA records and support workflows, and treats material owned by the company's clients as usually outside what it looks for. In an expanding company, that kind of documentation belongs to the lines it has run for years. The expansion matters only if it has turned leadership's attention back to them.

| What the expansion brings | Bears on the licensing question? | Why |
|---|---|---|
| Launch plan, forecasts and pricing for the new line | No | Statements about the future, not a record of work the company did |
| Procedures from older lines rewritten to train the new team | Yes, as a timing signal | The CEO's people are already reviewing documentation the company wrote |
| Support, QA and project history from the lines being extended | Possibly | The company's own operating history; rights and fit are settled only in SourceX's review |
| A product line bought from another company | Depends on the deal | Its history may have stayed with the seller; after closing, the acquirer's CEO decides |
| A new subsidiary set up to run the line | Changes the entity named, not the company | A parent and its subsidiaries count as one referred company; the USD 50,000 first-transaction floor applies once across the group |
| Usage data the new product will collect from customers | Usually no | Material that belongs to customers is usually not a fit |

For the record types themselves, the [guide to product planning records](/guides/how-to-assess-product-planning-records-and-supporting-decisions) covers what decision history can look like. The opposite event, a line being retired, has its own records step in the [product sunset plan](/guides/product-sunset-plan).

## The product-change relevance test

Five questions, in this order. Each is answered by a public statement or by what the CEO has told you, never by looking at anything inside the company.

| # | Question | Useful moment | Not this moment | Where the answer comes from |
|---|---|---|---|---|
| 1 | Did the expansion send the company back to its own older records? | Leadership is writing down how the existing lines work so the new team can repeat it | The new line is a clean start: new team, new tools, nothing reused | What the CEO has said, or a public statement |
| 2 | Is the launch behind them? | The line is on the market and its first review has happened or is booked | Build, launch week or a troubled first month | The public launch date, or the CEO |
| 3 | Can you name the entity and its CEO today? | Same company, or a named subsidiary under a named parent, with the CEO's name dated | A purchase that has not closed, or a joint venture where you cannot say whose company runs the line | The announcement, the company register or the CEO |
| 4 | Did you learn of the expansion in a way you may repeat? | A public announcement, or the CEO told you directly | A board pack, a client engagement or someone else's confidential forecast | Your own notes on how you heard |
| 5 | Would the question still make sense if the expansion were cancelled tomorrow? | The question rests on records the company already has | The pitch only works as a way to help pay for the launch | Your own draft message |

**Reading the result.**

- **All five pass:** ask once, soon.
- **Only question 2 fails:** write down the launch or review date the company gave, and ask after it.
- **Question 1 or 5 fails:** the expansion is not your reason. Ask only if you would have asked anyway, on facts that have nothing to do with the launch.
- **Question 3 or 4 fails:** stop until you can name the right CEO from a source you are free to use.

Question 5 is the one partners skip. If the message reads as "this could fund your new line", rewrite it or drop it. Nobody can say what a company might license, or on what terms, until SourceX has reviewed it, and licensing is not a way to finance a launch.

**Method note.** The test applies SourceX's screening page and the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), plus the Oslo Manual definition, all checked 2026-10-27. It sorts timing only. It does not estimate how often an expansion leads to an introduction or to a license, and no such figures have been published.

## Sponsor, decider and the week you pick

Three people usually appear around a new line. The general manager or product leader running it knows which procedures were reused and when the first review falls; that makes them a sponsor, someone who can carry the question upstairs. A finance or operations lead may know the dates. The company's CEO is the only one who decides whether it talks to SourceX. If the line came with an acquisition, the target's CEO decides for the target until closing, and the acquirer's CEO decides once the deal has closed.

The best week is usually after the first post-launch review, when the leadership team has stopped firefighting and is asking what it learned. Hold the question when:

- **Launch week or a rocky first month** is under way.
- **A raise to fund the expansion** is in progress, and a licensing question could be read as part of the financing story.
- **People in an older line are being cut** to pay for the new one; raising the records of that same line reads as opportunism.
- **A recall, outage or customer dispute** is attached to the launch.
- **The CEO is changing.** Ask whoever holds the role once the change is done.

## One question, then one line in your log

**Illustrative wording.** "Congratulations on getting the new line out. Unrelated to it: SourceX licenses records that companies created in their own work, such as procedures and project histories, for AI training and evaluation. Would you like an introduction to find out whether anything from your established lines might fit? I'm a referral partner, so SourceX could pay me a reward if something came of it; that comes from SourceX's side, not out of what your company would receive. A no is a fine answer."

The company's amount does not change because a partner is involved. The terms put it plainly: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation" (section 4).

Then write one line in your log: the date, the CEO's answer in a few words, and the next authorized step with its owner, if there is one. If the answer is a written yes, the person who will submit registers and signs the SourceX Channel Partner Agreement first. The company applies itself. SourceX credits a single partner per company, the one whose valid introduction came first inside the 90-day attribution window, and only once the company has filed a verified application. A company that has already applied, corresponded or held an account with SourceX is treated as a duplicate and credited to nobody.

## Three expansions put through the test (Illustrative)

Illustrative. The companies are generic and every detail is invented; none of this predicts a result.

**A. Ask after the first review.** A 230-person commercial HVAC contractor has run installation work for 14 years and repair service for 8 years, and launched a maintenance-plan line in March. In May the CEO tells her outside accountant that the spring went into turning the service procedures from both older lines into training for the new plan team. Questions 1, 3, 4 and 5 pass; question 2 passes once the June review is done. The accountant asks in July. The maintenance-plan line itself has no history to offer; whatever might interest SourceX sits in the 14 and 8 years behind it.

**B. Not this moment.** An 85-person software company announces a second product, launching in six weeks, built by a team of new hires on new tools. Questions 1 and 2 fail. Much of its product data sits in customer tenants, which the screening page treats as a weak fit. The partner sends nothing about the launch; the company's own support and QA history could be a separate conversation on another day.

**C. Wait for closing.** A 400-person food distributor agrees to buy a private-label line from a manufacturer, closing next quarter. Question 3 fails until then, and the line's history may stay with the seller. After closing, the distributor's CEO decides for the combined business, and the group counts as one referred company, so the first-transaction floor applies once.

## What the expansion story cannot settle

- **An expansion is not a fit.** The company faces the same screen as any other: at least 50 full-time employees at its high point, contractors not counted; years of records it created; the right to license them; and a CEO who wants the conversation. Location is set out on [who qualifies](/who-qualifies).
- **New markets make CEOs guarded.** A company entering a rival's territory may be wary of anything that describes how it works. Point it to [whether licensing data helps competitors](/questions/does-licensing-data-help-competitors), and make no promises of your own about who would see what.
- **The pitch drifts toward money.** Never describe licensing as a source of income for the launch, and never estimate what a company could earn.
- **Nothing has been measured.** Whether expansions lead to more introductions than other triggers is unknown. To find out, log each expansion you hear about, its answers to the five questions and the CEO's reply over two quarters; no figures are published.

Neighboring triggers are timed the same way: [a support team merger](/guides/the-referral-conversation-after-a-company-combines-two-support-teams) and [a service catalog redesign](/guides/the-data-opportunity-question-during-a-service-catalog-redesign). More trigger playbooks 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 an expansion passes all five questions and the CEO asks to hear more, [register as a partner](/register) before anything is submitted, check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) on credit and duplicates.

## Sources

- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://www.oecd.org/en/publications/oslo-manual-2018_9789264304604-en.html
