The overlooked reasons good data introductions fail: a complete-funnel map that records where each one stopped and the earliest point its cause could have been known

Short answer

Most good introductions that fail stop for a reason that could have been known earlier than the stage where it surfaced: the person who said yes was not the CEO, the records belonged to clients, a colleague had already emailed SourceX, the application came after the 90-day window, or the founder heard about the partner's reward from someone else. Log every introduction, not only the memorable ones, with two stages each: where it stopped and where its cause first became knowable. The gap between them is what you can fix.

Visual briefFull-size diagram
A grid of five cause families against six funnel stages. For each family, an open circle marks the earliest stage the cause was knowable and a filled circle marks the stage where the introduction stopped, joined by an arrow; only the mandate row starts and stops inside SourceX's review.
Illustrative pattern drawn from the method on this page; it is not SourceX data.

A few causes cannot be fixed from your side. Whether a company's records match one of SourceX's current programs is known only in review, and so is much of the rights picture. Telling those apart from the preventable ones is the whole point of the method below.

Why a warm relationship can still lead nowhere

Warmth predicts that the CEO will take your call. It says nothing about four things that decide the rest: whether the person saying yes can authorize a licensing discussion, whether the company owns the records worth licensing, whether the timing leaves room for a decision, and whether the records match what a current program needs. It can even hide a fifth problem, because people are slower to discuss money with friends. A founder who learns late, and from someone else, that the introducer earns a reward may reasonably wonder what else was left unsaid.

Six stages, and what ends an introduction at each

StageWhat has to happenWho decidesWhat ends it here
1. The askThe CEO agrees to a conversation with SourceXThe CEOA no, or a yes from someone who cannot authorize
2. Application and creditThe company applies itself; a verified application within the 90-day window; a duplicate checkThe company, then SourceXA late application, or any earlier application, relationship, lead, account or email with SourceX
3. QualificationFit, inventory, rights check and processing route, with no records sharedSourceXNo match with a current program, client-owned material; qualifying never guarantees an offer
4. TermsAn indicative range agreed or countered, a Master, then a Confirmation fixing dataset and payoutThe CEO and SourceXTerms not agreed, or a scope that shrinks to nothing
5. Delivery and ClosingPreparation through an approved route and an acceptance review of up to 30 daysSourceX and its Acquisition PartnerNot closed by the Closing Deadline, so declined and deleted
6. Payment conditionsThe company paid, Acquisition Partner acceptance and cleared funds, finance approval, the partner's tax detailsSourceX finance, and the partnerUsually a delay, not an ending: a late condition is paid promptly once met

The agreement sample adds a rule partners often miss: supplier assessment, acceptance review and Closing deadlines are separate clocks and do not extend attribution. A long deal does not keep a late application alive, and an expired or declined deal creates no reward merely because time, introductions or review were involved.

Five cause families, kept apart

Sort every stopped introduction into one primary family. A sixth row, the program's own record of earlier contact, sits apart because SourceX's records decide it.

FamilyWhat it looks likeWhere it usually surfacesWhere it was first knowableThe question that catches it
AuthorityA CFO or COO said yes and the CEO later declinedStage 2 or 3Before the ask"Is the CEO the person saying yes?"
OwnershipThe best records belong to clients or sit in customers' systemsStage 3One metadata question at the ask"Did the company create these records, and does any belong to clients?"
IncentiveThe founder learns of the partner's reward late, or assumed payment was certainStage 3 or 4At the ask"Did my first message say what I earn and when?"
TimingA sale, audit or migration takes over, or the application arrives after day 90Stage 2 or 4Usually at the ask"When could the company apply, and is anything about to change who decides?"
MandateThe records do not match a current programStage 3Only in SourceX's reviewNone a partner can ask; not preventable
Program recordA colleague at the company had emailed SourceX beforeStage 2Partly, at the ask"Has anyone at the company applied to, held an account with or emailed SourceX?"

A complete-funnel failure map for one partner's year (Illustrative)

Illustrative. One partner's twelve introductions in a year, every one of them listed, including the two that paid and the one still open. Generic companies and invented outcomes; this is not SourceX data and not a benchmark.

No.CompanyEnded atCause familyFirst knowableGap in stages
1210-person HVAC parts distributorPaidNoneNot applicableNot applicable
2340-person IT managed services firmPaidNoneNot applicableNot applicable
3120-person architecture practiceStage 3Ownership: drawings belong to clientsAt the ask2
4180-person food distributorStage 1Authority: the CFO's yes, the CEO's noBefore the ask1
5260-person engineering consultancyStage 2Program record: a manager had emailed SourceXPartly, at the ask1
6150-person commercial printerStage 2Timing: applied on day 97At the ask1
7400-person logistics software firmStage 3Mandate: no current program matchOnly in reviewNone
8130-person specialty contractorStage 3Incentive: the CEO heard of the reward late and withdrewAt the ask2
9300-person regional retailerStage 4Timing: acquired mid-process; the acquirer's CEO pausedPartly, before the ask4
10220-person facilities services companyStage 5Not closed by the Closing DeadlineOnly at acceptanceNone
11170-person equipment rental firmOpen, in acceptance reviewNot countedNot countedNot counted
12140-person market research agencyStage 3Ownership: survey data belongs to clientsAt the ask2

How to read it. Nine introductions stopped. Seven of the nine had a cause a partner could have found, fully or partly, before or at the ask; two did not, and those two are the program working as intended. The largest gap, row 9, is the costliest: a rumored sale was known before the ask and surfaced four stages later, after the CEO and SourceX had both spent time. Rows 3 and 12 share one missing question. If one question explains two failures in a year, it belongs in every first conversation.

Counting rules. List every introduction made in the period. An open case stays open, never counted as failed. Each stopped case gets one primary family at the stage it ended. Gap is the stopped stage minus the stage of first knowability, with "before the ask" as stage 0.

What the partner could reasonably have known earlier

Hindsight makes every cause look obvious. Four levels keep the analysis fair:

  • Level 0, already known. It was in your own notes before you asked: your contact is the COO, or a sale was rumored.
  • Level 1, one metadata question. It would have come out of a single descriptive question at the ask: who created the records, whether anyone ever emailed SourceX, when the company could apply.
  • Level 2, only in review. Program fit and the detail of customer contracts.
  • Level 3, only at acceptance. Whether delivered data is accepted before the Closing Deadline.

A cause counts against your process only at levels 0 and 1, and only if the question could be asked without touching records. Levels 2 and 3 are not yours to prevent. The declined-referral guide and why a well-documented company can still be declined describe what review looks at.

Four causes that are easy to overlook

  1. An email counts. In the terms, a prior lead, an account or an email exchange linking the company to SourceX already amounts to a relationship, however it began. A staff inquiry two years ago is enough to make a company a duplicate; the question on companies already known to SourceX covers what follows.
  2. The window does not stretch. The 90-day window does not extend because contact protection under the agreement continues, and no later deal clock reopens it.
  3. Group histories are judged case by case. When the company belongs to a group, nothing published says whether a parent's earlier dealings with SourceX, or another partner's introduction of a sister company, changes who is credited. SourceX makes that call in duplicate review, so promise nothing either way.
  4. A sponsor's yes is not the company's. The CEO authorizes a licensing discussion. A COO's enthusiasm is valuable preparation, but if the CEO has not heard about the introduction, SourceX's screen usually counts it as a poor fit. Introducing through a sponsor or directly to the CEO weighs the two routes.

Changes that improve the next introduction

FamilyChange before the next ask
AuthorityGet the CEO's own yes before recording anything
OwnershipAsk who created the records and whether any belong to clients
IncentiveSay in the first message what you would earn and that it is paid only after the company is paid and the conditions are met
TimingAsk when the company could apply and whether a sale, audit or migration is coming; record the introduction when it is ready
Program recordAsk whether anyone at the company has applied to, held an account with or emailed SourceX
MandateChange nothing; criteria follow each program, and a company that does not fit one may fit another later

Check the effect after a quarter. If the share of stopped introductions with a level 0 or level 1 cause does not fall, the questions are not being asked.

The fit facts every introduction rests on

The published fit facts come first: a headcount that peaked at 50 or more full-time employees, contractors left out of the count; an operating history documented in records the company created itself; licensing rights over those records; and a CEO who wants the conversation. 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. Businesses that only want to sell a one-off file with no documentation or context are usually not a fit. Three things no partner can settle in advance, because only SourceX's review answers them: whether the records match a current program, what the customer contracts allow and what any license would cover. Partners ask about all of this at metadata level and never handle records.

Where this map can mislead

  • Small numbers. A dozen introductions a year cannot support percentages. Read the map for repeated causes, not rates.
  • Hindsight still leaks in. The four levels limit it but cannot remove it; have a colleague assign the level before you see the outcome where you can.
  • You see only your own cases. Partners never receive other partners' records, so no partner can build a program-wide picture from the inside.
  • Nothing here is a benchmark. SourceX has not published conversion rates or a breakdown of why introductions stop.

Diagnosing a whole network rather than single introductions is covered in when a network has contacts but no suitable companies, and a study design for reaching authorized owners in which introductions reach an authorized data owner. More guides sit in the guides hub.

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.

Map your last year of introductions first, then register for a partner link, check your next company against who qualifies and read the program terms so the questions that would have caught your past failures are asked before the next ask.

  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

Should I count an introduction that is still in review as a failure?

No. Keep it open until it ends, and leave it out of the stopped count. Counting open cases as failures makes a slow quarter look like a bad one and pushes partners to chase companies that are simply waiting on a review.

Will SourceX tell me why an introduction stopped?

You can ask, and the terms give a dispute route for attribution, eligibility and reward decisions. Expect an explanation of your own referral only; partners never receive other partners' records or confidential buyer information.

If the cause was a mandate mismatch, should I stop introducing that kind of company?

Not on one case. Criteria follow each program, and a company that does not fit one program may fit another later. Note the record type and revisit when you hear the company's records match a current need.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/how-it-works
  4. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…

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