# Data introduction payment journey, day by day | SourceX

Canonical: https://refer.sourcex.si/guides/from-potential-to-paid-the-journey-of-a-company-data-introduction
Last updated: 2026-11-04

An introduction becomes a paid reward through a dozen dated events, and only some of the waits between them have a published limit: the 90-day attribution window, an assessment of up to 30 days after the Master, the Closing Deadline in the Confirmation, payment within 60 days of the company's valid invoice and the reward's own 60-day deadline. The rest have no published length. Expect silence in both, and expect the reward to follow what the company is actually paid, never an early range.

Most of a partner's experience of this journey is waiting without news. Knowing which waits are bounded, and by what, turns that silence into something you can read. The case below follows one introduction from a conversation to a bank transfer, then sets it beside two that ended differently. Everything in the cases is Illustrative: invented companies, invented day counts and invented amounts. Only the limits come from SourceX's published process, its terms and the unsigned sample of the Channel Partner Agreement.

## A plausible company, a permissioned ask and six expectations

Illustrative. The partner organizes a regional peer group for chief executives. One member runs a 190-person industrial equipment rental company that keeps twelve years of rental agreements, maintenance tickets and damage claims in its ERP and a field-service system. After a session on AI, the CEO asks the organizer what "licensing operating records" means. The organizer explains it, confirms the facts at metadata level (headcount at peak, years, systems, who owns the records) and asks whether the CEO wants a conversation with SourceX. The CEO says yes, and the organizer, who had already signed the SourceX Channel Partner Agreement, records a written introduction that day.

Before anything else, the organizer writes down what they expect. Keeping that note is the habit this page argues for, because the final section scores it.

| No. | Expectation on day 0 | Kind of statement |
|---|---|---|
| E1 | The CEO applies within a month | A forecast about a person |
| E2 | The company has 50 or more full-time employees at peak | A company fact the CEO confirmed |
| E3 | The introduction will be credited to the organizer | A program outcome decided later from records |
| E4 | The reward will land near the top of the indicative range | A forecast about money |
| E5 | Everything is paid within four months | A forecast about time |
| E6 | No confidential record passes through the organizer | A rule the organizer controls |

## The conditional stage-and-payment case timeline

Each row is one event in Case A. The fourth column says whether the wait before it had a published limit, a published target or nothing at all. A target is not a promise; SourceX's process page says so in those words.

| Day | Event | Who decided | Wait before it | What could have ended it here |
|---|---|---|---|---|
| 0 | CEO agrees to a conversation; written introduction recorded | The CEO | None | The CEO says no |
| 19 | The company applies itself; application verified | The company, then SourceX | Limit: credit needs the application within the 90-day window | A late application, or any earlier contact with SourceX |
| 44 | Indicative range of $260,000 to $390,000 proposed; the CEO accepts it | SourceX proposes, the company agrees or counters | No published length for qualification | No match with a current program; qualifying never guarantees an offer |
| 52 | One Master Supplier Licensing Agreement signed | The CEO and SourceX | No published length | The CEO declines the terms |
| 76 | Dataset Deal Confirmation signed: payout fixed at $280,000, Closing Deadline set | The CEO and SourceX | Limit: the Master starts an assessment of initially up to 30 days | Terms not agreed |
| 88 | Commercial commitment secured | SourceX and its Acquisition Partner | Target only: feedback usually 7 to 14 days | Positive interest that never becomes a purchase |
| 99 | Data prepared and delivered through an approved route | The company's IT team and the route | Target only: 7 to 10 days once access and inputs are ready | Access not ready |
| 121 | SourceX accepts in writing; Closing Notice issued | SourceX | Limit: review up to 30 days from the review-start event | Not closed by the Closing Deadline, so declined and deleted |
| 123 | The company sends a valid invoice | The company | None | An invoice that is not valid |
| 138 | Acquisition Partner's final written acceptance, after handoff completed on day 125 | The Acquisition Partner | No published length | Interest or receipt alone, which the terms say is not acceptance |
| 160 | The company is paid $280,000 | SourceX | Limit: within 60 calendar days of the valid invoice | None in this case |
| 171 | SourceX receives cleared funds from the Acquisition Partner | The Acquisition Partner | No published length | Payment still outstanding |
| 180 | Finance approves and the organizer is paid $64,000 | SourceX finance | Limit: reward deadline day 198, 60 days after day 138 | Missing tax or payment details |

Three things in this table are easy to miss. First, Closing on day 121 is the company's milestone, not the organizer's: the agreement sample says supplier Closing is not the referral payment deadline, and the reward clock starts at whichever comes later, completed handoff or the Acquisition Partner's final written acceptance. In this case that is day 138, so the deadline is day 198. Second, the supplier's payment and the organizer's reward are separate obligations. The company is paid under its own invoice terms; the reward also waits for SourceX's cleared funds and finance approval. Third, the deadline is a backstop, not a date. Had the Acquisition Partner paid on day 210, the reward would have been paid promptly once that condition was met, with no new 60-day period.

## Scope, rights and terms moved the number before delivery

The range on day 44 was built from the full inventory. During the rights check, the damage-claim files raised a question about what the company's customer contracts allow, so the CEO left them out and the Confirmation fixed a payout of $280,000 for the rental agreements and maintenance tickets. The company decides what scope it provides; the organizer was not part of that conversation and should not have been. SourceX's screening page lists material that belongs to clients as usually not a fit, and a narrower dataset with clear rights is the ordinary result of taking that seriously.

The reward follows the paid amount. On a company's first qualifying transaction the default reward is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap: for $280,000, USD 50,000 plus 5% comes to $64,000 and 15% to $42,000, so the organizer's reward is $64,000, paid by SourceX separately and never taken from the company's payment. Before the company was paid, the organizer's dashboard showed an estimate; it moved through Estimated, Eligible and Approved, and showed Paid only after the transfer was recorded.

## Two timelines from the same start that end without a reward

**Case B, a window that closed (Illustrative).** The same organizer introduces a 160-person commercial landscaping company with nine years of job estimates, crew schedules and site inspection reports. The CEO says yes on day 0 but wants to raise it at the annual planning meeting first, and applies on day 104. The 90-day window closed on day 90, so the introduction is not credited. The company loses nothing and can carry on with SourceX on its own. The organizer cannot ask for an extension: the terms say the window does not extend because contact protection under the agreement continues. The lesson is about when to record an introduction, not about pressing a CEO to hurry.

**Case C, data that did not close (Illustrative).** A 300-person IT services firm signs a Master and a Confirmation, delivers its data, and the review runs past the Closing Deadline without acceptance. SourceX's process page says data not closed by the deadline is treated as declined and deleted. No Actual Supplier Payout exists, so no reward exists, however many months the work took; the agreement sample says an expired or declined unclosed deal creates no reward merely because time, introductions or review were involved.

| Stage | Case A | Case B | Case C |
|---|---|---|---|
| CEO's yes and written introduction | Day 0 | Day 0 | Day 0 |
| Verified application | Day 19, inside the window | Day 104, outside it | Inside the window |
| Credited to the organizer | Yes | No | Yes |
| Confirmation signed | Yes | Not the organizer's to follow | Yes |
| Closing | Day 121 | Not followed | Never reached |
| Reward | $64,000 paid on day 180 | None | None |

## Reading the outcome against day-one expectations

Score each expectation as held, wrong or not knowable on day 0.

| No. | Expectation | Result | Why |
|---|---|---|---|
| E1 | The CEO applies within a month | Held in Case A, failed in Case B | A forecast about a person; the same one failed a month later with another CEO |
| E2 | 50 or more full-time employees at peak | Held | Confirmed with the CEO before the ask |
| E3 | Credit goes to the organizer | Held, but not knowable on day 0 | Asking the CEO about earlier contact with SourceX helped; SourceX's own records decided |
| E4 | A reward near the top of the range | Wrong | The range's top, $390,000, would have given $69,500, but it was never the base; the fixed $280,000 gave $64,000 |
| E5 | Paid within four months | Wrong | Day 180; three waits had no published length |
| E6 | Nothing confidential passes through the organizer | Held | The organizer handled metadata only |

The pattern generalizes. Company facts confirmed with the CEO and rules the partner controls held. Program outcomes held only after someone else checked their records. Every forecast about money or time was wrong or uncertain. A partner who writes the note on day 0 and scores it at the end learns which of their own habits to trust; the [earnings calculator](/tools/referral-earnings-calculator) can model amounts, but it cannot tell you when.

## Fit facts to confirm before the first ask

Introduce a company when it plausibly clears every fit fact in the chain: a peak of 50 or more full-time employees, contractors not counted; years of self-created records; the rights to license them; and a CEO who wants to talk. 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. Ask, at metadata level only, whether the company has ever applied to, held an account with or exchanged email with SourceX; any of those makes it a duplicate. What stays unknown until SourceX reviews it: whether the records match a current program, what customer contracts allow and what any Confirmation will fix.

## Where this timeline can mislead

- **The day counts are invented.** SourceX has not published typical durations between stages or conversion rates, and nothing here forecasts either.
- **The order can differ.** This case puts the Acquisition Partner's acceptance after Closing. Whatever the order, the reward deadline keys to that acceptance and completed handoff.
- **Payments can be split.** Where supplier compensation is paid in installments, the reward accrues as each one is paid.
- **Amounts can fall later.** If the company's payout is later cut or reversed, SourceX reduces the reward proportionately to the smaller payout; a buyer refund alone, without a cut to the company's payout, changes nothing.

For the program's own summary of timing, read [when referral fees are paid](/earn/when-you-get-paid) and [what happens after a company applies](/proof/what-happens-after-company-applies). The difference between being credited and being payable is set out in [attribution and payment eligibility](/guides/the-difference-between-attribution-eligibility-and-payment-eligibility), and [why a written introduction matters](/proof/written-introduction-vs-referral-link-attribution) covers the day-0 record. More journeys sit in the [guides](/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.

If a company in your network passes the fit facts and its CEO wants the conversation, take a partner link from the [registration page](/register), compare the company with [who qualifies](/who-qualifies), work through the [program terms](/terms), and note your day-0 expectations before you record the introduction.

## Sources

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