How to build a small high-confidence referral queue: a fit-permission-confidence triage board with five ready slots and a column for every card that cannot move

Short answer

Keep the queue short and let three things move a company forward: fit facts the company itself confirmed, permission from the person who can say yes, and confidence that what you know is firsthand rather than inferred. Score each card on all three, allow at most five in the ready column, and park everything else in verify, ask, no path or out. A public clue can open a card; it never moves one.

Visual briefFull-size diagram
An Illustrative triage board with five columns: Out holds cards C, G and H; No path holds D; Verify holds A; Ask holds F; Ready, capped at five, holds B and E with three empty dashed slots that wait for a card scoring 2 on fit, permission and confidence.
Illustrative board for eight generic companies, matching the worked example on this page. Empty ready slots are a result, not a gap to fill.

A channel partner's business development lead often inherits a spreadsheet of sixty "possibles": half remembered from client work, half copied from an event attendee list. The count is not the real problem. Every row mixes guesses with facts, nobody can tell which rows are ready to act on, and the CEOs behind the best rows wait while the team argues about the worst.

Five ready cards are worth more than fifty possibles

Three reasons keep the queue small.

  • Each introduction spends something. A CEO's time, and the goodwill of whoever asked them. Spending it on a row that later fails a basic test costs both.
  • The clock is real. Section 2 of the terms says "The first valid introduction of a new company within the 90-day attribution window receives credit when that company submits a verified application." An introduction made before the CEO is ready can use up time the company needed.
  • Limits make flow visible. The Kanban Guide puts it plainly: "Kanban system members must explicitly control the number of work items in a workflow from start to finish." It also has new work pulled in only when there is a clear signal of capacity. A ready column with a fixed number of slots is that signal.

Five is our default for one person running introductions alongside client work, not a program figure. If your constraint is hours rather than certainty, the queue rubric for limited review capacity prices the work at each stage. This page is about something narrower: how sure you are of what sits in the queue.

Where a card starts: a dated clue and a named path

Every card carries five fields, and two of them decide whether it can move at all.

FieldWhat to writeWhat does not belong
CompanyA generic description until the legal entity is knownLogos, contact lists or anything bought
The clueWhat you saw, where, and the dateAn undated "I think they're big"
The pathWho knows the CEO, how, and when they last spoke"Someone at the firm probably knows them"
Confirmed factsEach fact, who at the company confirmed it, and whenFacts copied from your engagement files
Open questionsWhat is still unknown, and who could answerQuestions nobody intends to ask

A card with an empty path field goes straight to the no path column, however strong the clue. Purchased lists never start cards at all, a rule the known-contact shortlist worksheet also builds on. And reach is not authority: network reach versus reachable decision-makers shows why a big contact list hides few real paths.

The fit-permission-confidence triage board

Score each card from 0 to 2 on three axes, then place it by rule.

Axis012
FitA published fit fact fails: full-time headcount at peak, the company's own records, rights or locationOne or more fit facts are still unknownEvery fit fact is confirmed
PermissionNobody has askedThe relationship owner agreed to ask, or the CEO said they would hear moreThe CEO agreed to the introduction, in writing
ConfidenceFit facts are secondhand, public or inferredFirsthand from a company person who does not own the factFirsthand from the person who owns each fact, or in a company document

Read the columns left to right and place each card in the first one whose rule it meets.

ColumnRuleA card leaves when
OutFit is 0, or the CEO or relationship owner said noA named trigger changes the failing fact
No pathNobody you know can reach the CEOA real relationship appears
VerifyFit is 1, or confidence is 0The fact owners confirm, raising both scores
AskAnything short of 2, 2, 2The CEO's written yes arrives, or a no
Ready, at most five2, 2, 2It is introduced, or a score drops

Confidence is a separate axis on purpose. The U.S. Intelligence Community's analytic standards, in ICD 203, ask analysts to express and explain the uncertainty behind major judgments and to keep underlying information apart from their own assumptions and judgments (our paraphrase). A referral card benefits from the same split: "140 full-time at peak" means one thing from the finance lead and another from a LinkedIn page, and the score should say which.

Method note. The fit axis follows SourceX's screening page and program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), checked 2026-10-27. The three scales, the column rules and the cap of five are our framework, informed by the Kanban Guide's limit on work in progress and ICD 203's separation of information from judgment. SourceX has published no conversion data, so the board ranks certainty, not likely outcomes.

Seen, told, assumed: annotating one card

Illustrative. A generic commercial roofing contractor, invented facts.

  • Seen (company website, 12 October): "serving the region since 2004."
  • Told by the operations manager (call, 15 October): job files with photos and inspection notes in one project system since 2013; about 140 full-time employees at the 2024 peak.
  • Assumed (ours): warranty claims probably link back to job files.
  • Missing: whether any job files belong to the general contractors the company works for; the CEO's view.

Scores: fit 1, because rights are unknown; permission 1, because the operations manager agreed to ask the CEO; confidence 1, because the headcount came from operations rather than finance. Column: verify. Next move: the relationship owner asks who owns job files shared with general contractors, and the finance lead confirms the peak figure. The assumption about warranty claims stays labeled as ours and travels nowhere.

Eight cards on one board (Illustrative)

Illustrative. Generic companies, invented facts, no outcome implied.

CardCompanyFitPermissionConfidenceColumnNext move
A140-person roofing contractor111VerifySettle who owns job files shared with general contractors
B230-person claims administrator, your firm's client222ReadySubmit the introduction
CDesign studio with 45 full-time staff at peak002OutRevisit if full-time headcount passes 50
D300-person freight forwarder from an event list100No pathFind someone who knows its CEO, or drop it
E180-person managed IT provider you partner with222ReadySubmit the introduction
FStaffing firm: 85 full-time staff of its own, about 1,400 placed workers212AskThe relationship owner asks the CEO
G120-person payroll bureau022OutClose: its files belong to client employers
H95-person engineering firm whose CEO declined last month202OutDo not ask again unless the CEO raises it

Two of the five ready slots are filled, and nothing should be promoted to fill the rest. Card F shows the staffing rule at work: only the firm's own 85 full-time employees count toward size, not the placed workforce, so it passes and is described with both numbers. Card D is the no-contact case: a promising company and no one to ask. Card G is the plain no-fit: willing, warm and confirmed, but the records are its clients'.

Permission before ready, and what an introduction carries

A card reaches ready only through the CEO's own written yes. The steps around it:

  1. The relationship owner asks the CEO, discloses that you may be paid if a deal closes, and records the date. The warm contact versus authorized contact guide has the conversation turns.
  2. Ask the CEO whether the company has ever applied to or corresponded with SourceX; under section 3 an earlier relationship makes it a duplicate.
  3. Sign the SourceX Channel Partner Agreement before the first submission.
  4. Submit with the CEO's name and the date of the yes, plus confirmed metadata only: record types, systems, years, rough counts.

No card gets cold outreach to skip ahead. The screening page lists "Introductions made without the decision maker's knowledge." among the poor fits, and the partner never handles client records or system credentials at any stage.

Board rules for cards that stall

  • Age. A card with no dated event for 45 days moves back one column. Our rule; pick your own number and keep it.
  • Triggers. Every out card carries the event that would reopen it, such as headcount passing 50 or records moving into a system the company owns.
  • Exceptions to the cap. The Kanban Guide allows exceptions to a work limit but expects them to be rare and stated in the workflow's definition. Write down any sixth ready card and why.
  • Ready means now. A card in ready for two weeks without a submission needs a reason in writing or a move back to ask.
  • Review. Twenty minutes a month, covering only cards whose scores changed.

Where a small queue misleads

  • Confidence is not acceptance. SourceX reviews relevance to current programs and rights after the introduction; a 2, 2, 2 card can still be declined.
  • Scores are not probabilities. Do not add or average them.
  • A small queue can starve. If ready stays empty for a quarter, the problem is upstream, in paths, and a bigger cap will not fix it. The company fit checker can speed early screening.
  • Familiarity bias. Firsthand facts come most easily from clients you know best, so the board will lean toward them.
  • Your own numbers are the only numbers. Track cards that reached ready, introductions submitted and verified applications, and compare quarter to quarter.

One naming note: SourceX's main site writes about dataset review queue prioritization, which orders records inside a dataset for quality review. That is a different queue, run long after any introduction.

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 a card reaches ready with all three scores at 2, register for a partner link, recheck its fit facts against who qualifies and read sections 2 and 3 of the program terms before you submit. Other sourcing methods are collected in the guides library.

  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

Why cap the ready column at five instead of ten?

Five is our default for one person working introductions alongside client work, not a SourceX rule. Each ready card means a CEO waiting on you, so set the cap by the hours you can give, and lower it if ready cards sit for more than two weeks.

Can a company with strong public signals skip the verify column?

No. Public signals can open a card, but every fit fact still needs confirming by the company person who owns it. A strong clue held only secondhand scores zero on confidence and stays in verify.

Should the three scores be added up to rank cards?

No. The scores are ordered categories, not probabilities, and a 2 on permission cannot make up for a 0 on fit. The board uses the rule order instead: out, no path, verify, ask, then ready.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. kanbanguides.org/the-kanban-guide/2020.12
  4. archive.dni.gov/files/documents/ICD/ICD-203.pdf

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