It is tempting to learn from a referral channel by studying only the introductions that worked. That teaches you what one success looked like. The declines teach you where the edge is, which is what you need to aim the next ten introductions.
Why rejected introductions belong in the evidence
A list of accepted introductions is a biased sample. It shows the companies that cleared every boundary at once and hides the ones that cleared four of five. The near misses carry the information: they tell you which single condition stopped an otherwise promising company, and whether that condition was knowable before anyone made an ask.
SourceX has not published counts of declined introductions by reason, and this page does not invent any. It works from the published screening criteria, the program terms and Illustrative cases. How to code and count declines for a report is covered in the rejection reasons study, and the general reasons a referral fails are listed in why a company referral was declined. This page asks a different question: what each kind of no says about where the opportunity is.
Separate ownership, authority, timing and mandate mismatch
Four boundaries need interpretation, size at peak is a fifth that is easy to check, and one outcome is not a boundary at all.
| Boundary | What the no says about the company | What it says about the opportunity | Fixed or movable? |
|---|---|---|---|
| Size at peak | It never reached 50 full-time employees, contractors excluded | Age alone does not meet the size test; scale at peak does | Movable if the company grows |
| Ownership and rights | Its strongest material belongs to clients, was scraped, or is personal consumer data | The opportunity is records a company creates and controls in its own operations | Often fixed for that material; other records may differ |
| Authority | The person introduced could not open a licensing discussion, or the CEO did not know | The asset is an authorized relationship, not access to an executive | Movable through the CEO |
| Timing | The CEO said not now: a sale, a migration, a leadership change | Dated events open and close windows | Movable on a date |
| Mandate | SourceX found no current program that needs these records | Demand is specific to a program and changes over time | Movable when programs change |
| Duplicate (not a boundary) | SourceX already knew the company | Nothing about the records; it is an attribution outcome | Not applicable |
Keep the duplicate row separate from the rest. Under the terms, a company with any earlier application, relationship, lead, account or email correspondence with SourceX is a duplicate and not credited to a later partner. Where the earlier contact came through a related business, such as a parent, a sister company or another partner's introduction of an affiliate, SourceX looks at the dated records in duplicate review; there is no published rule to apply in advance.
What seemed promising before review
Introductions get made because something looked promising. Five such signals are worth examining:
- Age. "They have been in business for nineteen years" sounds like deep records.
- Visibility. A well-funded company, a press feature, a strong brand.
- Volume claims. "We have millions of records" from an enthusiastic executive.
- An eager executive. A vice president who loved the idea and offered to make it happen.
- AI headlines. The sense that AI developers want every kind of business data.
Each one is a real piece of information. None of them is one of the checks SourceX screens on.
Which signals were misleading or incomplete
| Signal that looked strong | Why it misled | The signal that would have predicted the outcome |
|---|---|---|
| Years in business | A long-lived small firm can still stay below the size line its whole life | Full-time headcount at peak, contractors excluded, and the year its own records start |
| Funding, press or brand | Funding appears nowhere in the screening checks | The same five checks every company faces |
| "Millions of records" | Volume says nothing about who created or controls the records | Whether the company created the records in its own work, and whether clients own them |
| Total headcount including contractors | The program counts full-time employees only; a staffing firm counts its own staff, not placed workers | Full-time headcount at peak, with placed or contract workers described separately |
| An English-language website | Outside the U.S., Canada and the EU, the language test applies to the records themselves | The language of the records actually offered |
| An eager vice president | Enthusiasm is not authority; the CEO authorizes | The CEO's own yes, given before the introduction |
| "AI wants all data" | Demand is assessed against current programs in review | Nothing a partner can check; leave it to SourceX |
The geography rule is worth quoting in full, because a website's language can suggest the wrong answer. 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.
The scraped-data boundary has a backdrop worth knowing. The Consent in Crisis audit of 14,000 web domains found that in a single year, from 2023 to 2024, 5%+ of all tokens in the C4 web corpus, and 28%+ of its most actively maintained, critical sources, became fully restricted from use. Scraped content is usually not a fit under SourceX's screening guidance; records a company created itself while doing its work are what the screening profile asks for. Broader analysis of AI data demand lives on sourcex.si.
The rejection-to-opportunity evidence map
Every row below is Illustrative: generic companies with invented facts, one per boundary. Read across to see where the adjacent opportunity sits and what would confirm it.
| Boundary hit | Illustrative case | What looked promising | Misleading signal | Adjacent opportunity | Evidence that would confirm it |
|---|---|---|---|---|---|
| Size at peak | A 42-person engineering consultancy with 19 years of project files | Age and tidy documentation | Years in business | Larger firms doing the same work, or the group that acquires this firm one day | Peak full-time headcount of 50 or more |
| Ownership and rights | A 300-person marketing agency whose best material is client campaigns | A huge creative archive | "Millions of files" | The agency's own project histories, QA reviews and SOPs | Records the agency created for its own operations, and client contracts read in SourceX's rights review |
| Authority | A 600-person logistics company introduced through a regional vice president | Strong interest inside the company | An eager executive | The same company, through whoever owns the CEO relationship | The CEO's yes before any introduction |
| Timing | A 150-person software company in the middle of being acquired | Ten years of support records | A CEO who liked the idea | The same records after the deal closes, with the acquirer's CEO deciding | A closing date and the new CEO's interest |
| Mandate | A 400-person property manager with maintenance tickets | Deep, structured history | "AI needs every kind of data" | A later program; nothing to promote today | Only SourceX can say a program fits |
| Source | A 90-person listings company whose dataset was scraped | A large, current dataset | Volume | None in that dataset | Records the company created in its own operations, if any |
Two patterns stand out. First, most boundaries are movable, and the map's job is to record what would move them. Second, the adjacent opportunity usually sits in the network you already have rather than a new one: a peer of the company, the CEO of the same company, or the same company later.
Turn rejection patterns into a better opportunity map
Your own declines are the only rejection data you can use today. Tally them by boundary for a quarter, then read the most frequent boundary as a statement about your network rather than about the companies.
| Most frequent boundary in your tally | What it suggests about your network | What to change next quarter |
|---|---|---|
| Size at peak | You know many established small firms | Ask the same contacts about their larger peers, buyers and suppliers |
| Ownership and rights | You work with client-service businesses and see their client work | Ask about the firm's own records: tickets, project histories, QA, SOPs |
| Authority | You reach executives, not CEOs | Find the person who owns each CEO relationship before asking |
| Timing | You hear about companies at turning points | Keep a dated revisit list instead of pushing |
| Mandate | You are guessing demand | Stop ranking by imagined demand; screen on the published checks and let SourceX judge relevance |
Method note. The boundaries come from SourceX's published screening profile and program terms, checked 2026-10-27. The map measures where an introduction stopped and what would have predicted it. It does not measure how often each boundary occurs across the program, because those figures are not published, and it cannot measure demand. A tally of fewer than ten outcomes tells you little; keep counting before you change course. If you are working from an old copy of the criteria, the risk of old mandate criteria shows how that skews a tally.
Explain what changed without revealing the company
Lessons from a decline travel well; the company's name should not travel at all. Four rules keep a write-up useful and safe:
- Describe the boundary, not the business. Use a sector and a headcount band, never a name, a city or a distinctive detail.
- Write the lesson as a change in your own practice. "We now confirm the CEO's yes before submitting" is a lesson. "Their VP overpromised" is gossip.
- Aggregate before sharing beyond your team. One decline is an anecdote that can identify a company; five on the same boundary are a pattern.
- Ask before using anything identifying. If a detail could point to the company, ask the company or leave it out.
A before-and-after rewrite, Illustrative:
| Draft that reveals too much | Rewrite that keeps the lesson |
|---|---|
| "A regional freight carrier's VP of operations pushed the intro without telling the CEO, and it went nowhere." | "One logistics introduction reached an executive without the CEO's knowledge. We now confirm the CEO's yes first." |
Tracking declines with the least identifying information is covered in tracking declined referrals respectfully, and telling the company itself is covered in explaining a mandate rejection. Other reading on declines and fit sits on 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.
When your boundary tally points you to a better company, register for a partner link, screen it against who qualifies and read the program terms before the CEO is asked.