# Client relationship referral shortlist canvas | SourceX

Canonical: https://refer.sourcex.si/guides/the-referral-shortlist-hidden-in-your-existing-client-relationships
Last updated: 2026-11-04

Your strongest referral shortlist is already in your client book, but only part of what you know about each client may be used. Sort it into three columns: public clues anyone can see, knowledge your team gained doing the work, and facts the client has confirmed for this purpose. Only the third column travels with an introduction. Engagement knowledge can tell you whom to ask, never what to share. A client joins the shortlist when someone at your firm owns the CEO relationship and a plausible fit question exists.

For a business development lead at a managed IT provider, consultancy, accounting firm or agency, this flips the usual sourcing exercise. You do not need to find companies. You need to decide which of the ones you already serve are worth one careful question, and you need to keep what your team learned in confidence out of the answer.

## Why the client book beats any prospect list here

Fit for a data licensing introduction turns on facts a stranger cannot see: 50 or more full-time employees at the company's peak, contractors excluded; records spanning years that the company produced in its own operations; the right to license those records; and a CEO who wants the conversation. An introduction the CEO never heard about is usually a poor fit by SourceX's own screening guidance, which rules out most cold outreach before it starts. What is scarce is a person the CEO will listen to. Your firm already has those people, one per client.

The flip side is that every signal you hold about a client is a question, not proof. A job post naming a field-service platform suggests work orders exist; it does not show who owns them, whether they are complete, or whether anyone wants them.

## Three kinds of knowledge, and which one may travel

**Public clues.** Anything a stranger could find: the company's website, a press release, a job post, a trade article. Write down the source and the date you saw it.

**Engagement knowledge.** What your team learned while serving the client: the size of a tenant you administer, the years of history in a system you migrated, headcount in a payroll you run, the archive you saw during an audit. This is the most accurate column on the canvas and the one you may not pass on.

**Client-confirmed facts.** What the CEO or a sponsor has told you, for this purpose, that you may share: "we had 160 full-time employees at our peak in 2024", "our load history starts in 2013". Record who said it and when.

Professional rules draw the line between the first two columns in different places, which is why the canvas keeps them apart. The AICPA Code defines confidential client information as information obtained from the client that is not available to the public, and lists what counts as public, such as published articles, documents the client has released and publicly accessible websites. For a lawyer the line sits further out: the comment to ABA Model Rule 1.6 extends confidentiality to all information relating to the representation, whatever its source, so a clue a lawyer picked up while working on a matter belongs in the middle column even if it can also be found in public. State versions of both rules vary. The deeper guides are the [AICPA confidentiality rule and referrals](/guides/aicpa-confidential-client-information-rule) and [whether a lawyer can share client information for a referral](/questions/can-a-lawyer-share-client-information-for-a-referral).

## The relationship-first shortlist canvas

One row per client, filled in by the person who owns the relationship. Illustrative: five clients of a regional IT services and advisory firm, generic and invented.

| Client (Illustrative) | Who owns the CEO relationship | Public clue, dated | Engagement knowledge (stays inside) | Client-confirmed fact | Consent | Verdict |
|---|---|---|---|---|---|---|
| A. 230-person HVAC and plumbing contractor | Account partner, quarterly meetings with the CEO | Careers page, September 2026: dispatcher role naming a field-service platform | The tenant your team administers holds work orders back to 2014 | None yet | Not asked | Ask the CEO one fit question |
| B. 160-person freight brokerage | Project lead, who knows the CFO but not the CEO | Trade press, June 2026: moving to a new transportation management system | The migration you scoped includes 12 years of load history | CFO: 160 full-time at the 2024 peak, records since 2013 | CFO will raise it with the CEO | Wait for the CEO, through the CFO |
| C. 70-person creative agency | Founding partner, close relationship | Portfolio site lists client campaigns | Most deliverables live in accounts the clients own | Founder: client work belongs to the clients | Founder asked | Park: little the agency owns itself |
| D. 400-person distributor | Nobody at your firm | Trade article, August 2026 | None; not a client | None | None | Off the canvas: no relationship |
| E. 38-person engineering boutique | Partner, close relationship | Website: founded 1998 | The payroll you run has never shown more than 41 full-time staff | Not needed | Not needed | No fit today on size; nothing said to the client |

**How to read it.** The verdict comes from two columns only: who owns the CEO relationship, and the client-confirmed facts, with engagement knowledge allowed to stop a row but never to advance one in public. Row A advances on a public clue and a strong relationship, so the next step is a question to the CEO, not a brief. Row E is stopped by engagement knowledge and nobody is told why, which is exactly how the middle column should work. Row D shows what the canvas is for: a promising company with no relationship behind it is research, not a referral.

**What the canvas does not measure.** Demand for any client's records, the quality of those records, or what licensing might pay. SourceX assesses relevance to its current data needs in review, and fit can change as programs change.

## Separate what you saw from what you inferred

Write each clue as an observation with a source, then write the inference beside it, then turn the inference into a question for the client. Never let the inference reach the brief.

| Observed, with source | What you might infer | The question it becomes |
|---|---|---|
| A dispatcher job post names a field-service platform | Years of work orders may sit there | "Which system holds your service history, and from what year?" |
| A press item announces a new transportation system | An old system full of load history may be retired | "What happens to the old history after the move?" |
| The website says the company has served the region since 1998 | A long operating history | "Do your own records go back that far, or only to the last system change?" |
| The team page lists fifteen people | A small company | "How many full-time employees did you have at your peak?" (team pages list leaders, not headcount) |

The last row is the one that catches people. Public pages undercount headcount as often as they overcount history, which is why the fit facts in the brief come from the client, not from you.

## Get the client's yes, then send only what they confirmed

The relationship owner asks the CEO, or the person the CEO trusts, one question: would they want to hear about licensing records the company created itself? If yes, the client decides what may be shared, and you write it down: who agreed, on what date, and which facts. That record becomes the third column. Say plainly that you could earn a reward if a license follows, and that SourceX pays it separately, never out of the company's payout; the guide to [asking a business owner for permission](/guides/how-to-ask-a-business-owner-for-permission-to-make-an-introduction) has wording for it.

Before anyone submits, check three things. The company passes the location rule: 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 client has never applied, held an account or corresponded with SourceX, because any earlier relationship makes it a duplicate that is not credited. And whoever submits has signed the SourceX Channel Partner Agreement; a copy signed when the document was still named Channel Partner Non-Circumvention and Non-Disclosure Agreement remains in force as signed. On timing, the client's own verified application is what triggers credit, and the credit goes to the first valid introduction made inside the 90-day attribution window.

What goes forward is short: the company, the CEO, the confirmed facts and the open questions. No exports, tenant screenshots or file listings from systems you administer, even when you could produce them in a minute. Admin access to a client's systems exists for the work you were hired to do, not as permission to describe what they hold.

## Where the canvas can mislead

- **Engagement knowledge leaks through wording.** "They have about twelve years of loads" in an email to SourceX is the middle column escaping. Phrase every brief line as the client's own statement.
- **A strong relationship can hide a weak fit.** Row C is a firm's closest client and its thinnest owned material. Material that belongs to clients is usually not a fit.
- **Relationships go stale.** A partner who last spoke to the CEO two years ago does not own that relationship today. Date the last real conversation.
- **Asking costs something.** Even a well-handled question spends goodwill. The page on whether [an introduction can hurt the client relationship](/questions/does-referring-clients-hurt-relationship) covers the controls: ask once, disclose the reward, accept a no.

For sector-by-sector lists built from outside your client book, see the [industry shortlist guide](/guides/how-to-build-an-industry-specific-shortlist-of-suitable-introductions) or the [network shortlist worksheet](/resources/a-business-network-referral-shortlist-worksheet).

## 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 canvas row has a relationship owner, a CEO who said yes and facts the client confirmed for sharing, [create your partner account](/register), set the row against [the published qualification rules](/who-qualifies) and work through the [program terms](/terms) before the introduction goes out; the [guides hub](/guides) has the rest of the sourcing series.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://pub.aicpa.org/codeofconduct/ethicsresources/et-cod.pdf
- https://www.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/rule_1_6_confidentiality_of_information/comment_on_rule_1_6/
