This is for the business development lead at a channel partner, such as an MSP, agency, accounting or consulting firm, who wants to know which client accounts could support a permissioned introduction to SourceX and which only look reachable. SourceX's program is introduction-only; how that differs from reselling is set out in channel partner versus referral partner.
What your contact list actually reaches
Service work creates contacts at the level where the work happens. Over the years a firm collects billing addresses, help-desk senders and project leads, and only occasionally the person who owns the company. Sort every contact into one of four kinds before you count anything.
| Contact kind | Typical example | What it can tell you | Where it leads |
|---|---|---|---|
| Role mailbox | info@, accounts@, a web form | That the company exists and is active | Park; nobody in particular reads it |
| Functional contact | IT administrator, office manager, accounts payable lead | Which systems exist, at metadata level, if they choose to say | A metadata answer at most, never a messenger to the CEO |
| Executive, not the CEO | CFO, COO, head of operations | Whether the CEO might want to hear it | A sponsor, after the CEO's yes |
| Owner or CEO | The founder-CEO, or an owner who appointed the CEO | The decision itself | The ask, with the CEO authorizing |
Whether a message is lawful is a lower bar than whether it is useful. In the UK, the ICO says the PECR rule on email marketing does not apply to corporate subscribers, so a business may email a company's generic address without consent provided it does not hide its identity and gives a valid opt-out address. Sole traders and some partnerships are treated as individuals, and an address that names an employee still brings data protection duties: tell them what you are doing and have a lawful basis. None of that makes a role inbox the right door. SourceX's screening guidance lists introductions made without the decision maker's knowledge among the cases that are usually not a fit. If a shared mailbox already sits in your records, the shared inbox identity check resolves it to one company and one CEO.
Public clues to ownership, and where they stop
Before you look for a path, find out whose company it is, from sources you can date.
- UK companies. Companies House guidance treats an individual with more than the greater of $50,000 plus 5% and 15% of voting rights as a person with significant control, and most PSC details are on the public register apart from home addresses and full dates of birth.
- U.S. companies. FinCEN's interim final rule of March 2025 exempted companies created in the United States from reporting beneficial ownership information to it, and a later final rule made that permanent. For a domestic private company, the ownership picture usually comes from the company's own website and announcements, and from people who know it.
- Everywhere. The leadership page, dated press announcements and, for a listed company, its own filings.
A public record shows control, not intent. A PSC entry can name a holding company or an investor rather than the CEO, and in this program the CEO, not the largest shareholder, authorizes a licensing discussion. Record what the source showed and the date you looked, nothing more.
The owner contact mapping workflow
Six steps, each filling one column of the map. Steps 1 and 2 use only what your firm already holds; nothing is opened, exported or copied from client systems.
| Step | What you do | Column it fills | Source |
|---|---|---|---|
| 1. List accounts | Export company names and the kinds of contact you hold, not message contents | Account; contact kinds held | Your CRM or billing system |
| 2. Grade the route | Mark the best route held: role mailbox, functional, executive or owner and CEO | Route grade | Step 1 |
| 3. Name the decision-maker | Look up the owner and the CEO in public sources and date the check | Owner; CEO; date checked | Registers, the company site, announcements |
| 4. Find the holder | Identify the colleague who knows the CEO or owner personally: account lead, engagement partner or founder | Relationship holder | An internal question |
| 5. Ask the holder | Will they raise it with the CEO, and do they agree to the firm submitting? | Holder's answer and date | The holder |
| 6. Route | Apply the rules below | Route | Steps 2 to 5 |
| Route | When it applies | What happens next |
|---|---|---|
| Ask now | A holder knows the CEO, has agreed to ask, and the fit facts you can see look plausible | The holder asks the CEO; nothing is sent until the CEO says yes |
| Find a path | The CEO is known by name but nobody at your firm knows them | Look for a client executive who would sponsor the idea, or leave it |
| Park | Only role mailboxes or functional contacts, and no holder | Record the date and revisit when a relationship changes |
| Drop | A fit fact fails: size, records the company does not own, or location | Record the reason and do not raise it |
The workflow ranks by path, not by guessed value. SourceX has not published conversion rates or typical payouts, so a column estimating what an account might earn would only rank your guesses. For the step before this one, listing everyone you know once, the network opportunity worksheet works; for an executive who has changed employers, use find the business behind the executive.
One MSP's account list, three outcomes (Illustrative)
An MSP with 60 client accounts runs the review in an afternoon. Three rows show the range.
| Account (Illustrative) | Best contact held | Owner and CEO on record | Relationship holder | Route |
|---|---|---|---|---|
| A 120-person freight forwarder | IT administrator and help-desk tickets | Founder is CEO, per the company site | The MSP's founder, who signed the account with that CEO in 2015 | Ask now |
| A 300-person UK manufacturer | accounts@ and the IT administrator | PSC register names a holding company; CEO named on the site | Nobody | Park, no contact |
| A 45-person architecture practice | The managing partner, directly | The managing partner owns it | The account lead | Drop, no fit |
Row A goes ahead because a person with a real relationship agreed to ask, not because the IT administrator was helpful. Row B is the trap: two working addresses and a public ownership record make it feel reachable, yet no one at the MSP knows the CEO, and a message to accounts@ would reach whoever pays the invoices. Row C has the warmest path on the list and fails on size: the practice has never had 50 full-time employees.
What the map saw, what it guessed and what an owner said
Every cell carries one of three tags.
- Observed. A public record or document you can point to, with its date: a PSC entry, a leadership page, an announcement.
- Inferred. Your reading of observed facts, such as "the founder probably still decides, because no sale was announced".
- Confirmed. The owner, the CEO or the relationship holder said it.
Only observed and confirmed facts go into a submission, and only what the CEO approved. Inferences stay in the map until they are checked or deleted. Two more rules keep the map clean: one partner is credited per company, so when two colleagues know the same CEO, agree internally who asks and who submits; and any split of a reward inside your firm needs its own written agreement.
From a parked row to a permissioned introduction
Only ask-now rows move. The holder raises it with the CEO in conversation, not by forwarding a template, says the firm may receive a referral reward that SourceX pays separately and never deducts from the company's payout, and waits for the CEO's yes. Then:
- Check the published fit facts. A peak of at least 50 full-time employees, not counting contractors; a documented operating history; records the company owns or can license without breaching client confidentiality, employee privacy or third-party contracts; and location. 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.
- Send little. The legal name, the CEO's approved contact and a metadata-level description the company approved. No files, samples, logins or exports, and nothing from your service tickets.
- Sign first. Whoever submits signs the SourceX Channel Partner Agreement before submitting introductions.
Dated records decide credit. It goes to the first valid introduction of a company SourceX has not met before, made inside the 90-day attribution window, and it lands once that company submits a verified application. A company with any earlier application, relationship, lead, account or email correspondence with SourceX is a duplicate and not credited, so ask the CEO about earlier contact before anyone spends time. A parked row is not lost: when a client executive changes, a holder joins your firm or the company announces a dated event such as a system migration, run steps 3 to 6 again. MSP-specific context sits on the managed service providers page.
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 map shows an ask-now row with a willing relationship holder and a CEO who said yes, move that row out of the map: register as a partner, confirm the company against the qualification rules and review the program terms before you submit; more sourcing guides sit in the guides library.