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.
| Field | What to write | What does not belong |
|---|---|---|
| Company | A generic description until the legal entity is known | Logos, contact lists or anything bought |
| The clue | What you saw, where, and the date | An undated "I think they're big" |
| The path | Who knows the CEO, how, and when they last spoke | "Someone at the firm probably knows them" |
| Confirmed facts | Each fact, who at the company confirmed it, and when | Facts copied from your engagement files |
| Open questions | What is still unknown, and who could answer | Questions 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.
| Axis | 0 | 1 | 2 |
|---|---|---|---|
| Fit | A published fit fact fails: full-time headcount at peak, the company's own records, rights or location | One or more fit facts are still unknown | Every fit fact is confirmed |
| Permission | Nobody has asked | The relationship owner agreed to ask, or the CEO said they would hear more | The CEO agreed to the introduction, in writing |
| Confidence | Fit facts are secondhand, public or inferred | Firsthand from a company person who does not own the fact | Firsthand 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.
| Column | Rule | A card leaves when |
|---|---|---|
| Out | Fit is 0, or the CEO or relationship owner said no | A named trigger changes the failing fact |
| No path | Nobody you know can reach the CEO | A real relationship appears |
| Verify | Fit is 1, or confidence is 0 | The fact owners confirm, raising both scores |
| Ask | Anything short of 2, 2, 2 | The CEO's written yes arrives, or a no |
| Ready, at most five | 2, 2, 2 | It 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.
| Card | Company | Fit | Permission | Confidence | Column | Next move |
|---|---|---|---|---|---|---|
| A | 140-person roofing contractor | 1 | 1 | 1 | Verify | Settle who owns job files shared with general contractors |
| B | 230-person claims administrator, your firm's client | 2 | 2 | 2 | Ready | Submit the introduction |
| C | Design studio with 45 full-time staff at peak | 0 | 0 | 2 | Out | Revisit if full-time headcount passes 50 |
| D | 300-person freight forwarder from an event list | 1 | 0 | 0 | No path | Find someone who knows its CEO, or drop it |
| E | 180-person managed IT provider you partner with | 2 | 2 | 2 | Ready | Submit the introduction |
| F | Staffing firm: 85 full-time staff of its own, about 1,400 placed workers | 2 | 1 | 2 | Ask | The relationship owner asks the CEO |
| G | 120-person payroll bureau | 0 | 2 | 2 | Out | Close: its files belong to client employers |
| H | 95-person engineering firm whose CEO declined last month | 2 | 0 | 2 | Out | Do 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:
- 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.
- Ask the CEO whether the company has ever applied to or corresponded with SourceX; under section 3 an earlier relationship makes it a duplicate.
- Sign the SourceX Channel Partner Agreement before the first submission.
- 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.