# Member introductions that respect the advisor | SourceX

Canonical: https://refer.sourcex.si/guides/the-member-introduction-that-preserves-an-existing-advisor-relationship
Last updated: 2026-11-04

Ask before you introduce. When a member's CEO asks the association for an introduction to SourceX, reply first with one question: has an accountant, consultant, IT provider, lawyer or other advisor already raised SourceX with you, or put you in touch? Then let the CEO pick the route: through that advisor, through the association, or straight to SourceX. Copy the advisor only if the CEO asks. One introduction can be credited, an earlier one may already exist, and the advisor relationship belongs to the member.

This is for a business association or community director whose members asked to hear about SourceX and some of whose CEOs now want an introduction. Measuring whether the offer helps members is covered in [the opt-in cohort dashboard](/guides/how-to-measure-a-partner-benefit-without-counting-every-member); this page is about the moment one CEO says yes.

## Whose relationship is it, and what the association adds

The member's advisors usually came first. A member company may already work with an outside accountant, an IT provider, a fractional CFO or a lawyer, and any of them may already be a registered SourceX partner. The association is a convener: it can explain, invite and, when asked, introduce. It is not the member's advisor, and its introduction should never land in the middle of an engagement the CEO values.

Three published points shape what the association does next:

- **One introduction per company.** Section 2 of the terms credits a single partner per company, the first valid introduction of a company that is new to SourceX, once that company files a verified application within the 90-day window. Section 3 treats a company with an earlier application, relationship or valid introduction as a duplicate that is not credited to a later partner, and it counts any earlier lead, account or email correspondence with SourceX as a relationship. If an advisor already raised SourceX and the company wrote to it, the association's introduction adds a record and nothing else.
- **Nobody owns the member.** Section 2.4 of the sample partner agreement says it creates no exclusivity over a contact's unrelated business and does not bind a contact that is not a party, and section 2.3 lets a partner keep its existing relationships. Registering as a partner gives the association no claim on a member, and gives the member's advisor none either.
- **Advisors answer to their own rules.** Professional bodies set conduct rules for their members. AICPA's toolkit for its personal financial planning standards, in our paraphrase, summarizes its Code as asking members to disclose conflicts fully, get client consent where a conflict exists and disclose commissions or referral fees to the client. An advisor may decline a reward, or need to disclose one, so the association should never assume the advisor wants to be the introducer.

The participation boundary follows. The association never collects records, systems or headcounts from a member, for SourceX or for itself. It never introduces a company whose CEO has not asked, never contacts the member's advisor unless the CEO asks, and never asks an advisor anything about the member. SourceX's screening page backs the second rule: an introduction the decision maker did not know about is usually not a fit.

## Six answers a CEO can give, and the association's move for each

The first email asks one question. These are the answers that come back, and what each one means for the association.

| What the CEO tells you | What the association does | What it never does |
|---|---|---|
| No advisor has raised SourceX | Offers the three routes; if the CEO picks the association, sends one written introduction | Assume an advisor would object |
| An advisor raised it and the CEO wants them to carry on | Steps back and records "in hand with the company's advisor" | Ask who the advisor is or what was said |
| An advisor already introduced the company, or the company has written to SourceX | Stands down; nothing is submitted | Submit anyway "to be safe" |
| An advisor raised it and the CEO said no | Treats the no as standing unless the CEO reopens it | Reopen the question through the association |
| The CEO wants the advisor kept informed while the association introduces | Copies the advisor on the introduction, with the CEO's agreement in writing | Ask the advisor to vouch for or describe the company |
| The CEO is not sure whether anyone raised it | Pauses until the CEO has checked with their advisors | Call around the member's advisors itself |

Stand-downs are a good outcome. A member who goes ahead through an advisor it already trusts has been served, and the association has kept out of the way of a relationship that matters more to the member than any introduction.

## The advisor-aware introduction email

Two messages, never one. The first replies to the CEO's request and carries no link. The second is the written introduction, and it goes only after the CEO has picked the association's route.

**Message 1, the reply to the CEO.** Subject: Your question about SourceX

> Thank you for asking about SourceX. Before we do anything, one question: has an accountant, consultant, IT provider, lawyer or any other advisor already raised SourceX with you, or put your company in touch with it? SourceX credits only one introduction per company, so if your company is already in contact, an introduction from us would add nothing and might confuse things.
>
> Once you have checked, you can choose how to go ahead:
>
> 1. Through your advisor, if they have raised it already or you would rather they did.
> 2. Through us: we send SourceX one short written introduction naming your company and you, nothing more.
> 3. Directly: your company applies to SourceX itself, without any introducer.
>
> We are registered in SourceX's referral program and could receive a reward from SourceX if your company licenses records after an introduction from us. SourceX pays it, and it does not come out of what SourceX pays you. If you choose your advisor or apply directly, we step out. We will not contact your advisor unless you ask us to, and we will not ask about your records or systems.

**Message 2, the written introduction.** Sent through the association's partner account or by email to SourceX, with the CEO copied, and the advisor too if the CEO asked:

> Introduction from [association name], a registered SourceX partner. Company: [legal name], [web domain]. Contact: [CEO name], CEO, who asked for this introduction in writing on [date] and is copied here. At the CEO's request we have also copied the company's [advisor role] for information. The CEO has told us that, to their knowledge, no advisor has introduced the company and the company has not been in touch with SourceX before. We have shared nothing else about the company and hold no records of it.

Delete the sentence about copying an advisor when the CEO did not ask for it.

| Line | Why it is there |
|---|---|
| The advisor question comes before any route | An earlier introduction or contact makes the association's a duplicate; asking first spares everyone a second record |
| Three routes, always in the same order | The CEO decides the route; a fixed order keeps the association's own reward from steering the choice |
| No link in message 1 | The CEO has not chosen a route yet, and a click on a link does not decide credit anyway |
| The reward sentence | The member hears the association's interest before choosing, in plain words |
| "We will not contact your advisor" | The advisor relationship stays the member's, untouched unless the CEO invites the association in |
| Message 2 names the company, domain, CEO and dates only | Section 1.2 of the agreement asks for a written introduction, and section 3.3 lists the record's fields: company, domain, partner, opportunity, method and timestamps; headcounts and systems are the company's to give SourceX when it applies |
| The CEO's statement about earlier contact | It records what the CEO knew on the day; SourceX still checks its own records |

## Education for members who are not ready, with room for their advisors

Many members will want the facts before any route. Offer the association's brief or session, and say plainly that a CEO may bring an advisor along. An advisor who attends gains no standing as the association's introducer, and the association gains none in the advisor's engagement. If an advisor wants to join the program, they [register](/register) themselves; the association does not recruit advisors through its members. Members who apply directly after the session, with SourceX's few questions and no files, are a success for the education path, not a loss for the introduction path. The [chamber member benefit page](/for/chamber-of-commerce-member-benefit-partnerships) describes the session format, and the [CPA firm partner page](/for/cpa-firm-advisory-partner-referral) shows the program from the accountant's side.

## Three requests, three routes (Illustrative)

Illustrative. Invented members and advisors; no outcome is implied.

**A. The engineering firm already in hand.** The CEO of a 180-person engineering firm asks for an introduction. Her answer to message 1: the firm's outside CPA introduced the company to SourceX two months ago. The association stands down, records "in hand with the company's advisor" and sends nothing to SourceX.

**B. The distributor that wants its IT provider informed.** A 95-person distributor's IT provider has never mentioned SourceX. The CEO picks the association's route but wants the IT provider copied, since it runs the company's systems. Message 2 goes with the IT provider copied for information; nobody asks the provider to describe a single system.

**C. The staffing firm that applies itself.** A staffing firm's fractional CFO raised SourceX months ago, and the CEO decides to apply directly. The association steps out. When the CEO checks the published criteria, only the firm's own full-time employees count toward the 50, and the workers it places with clients do not; that check is the CEO's, never the association's.

## What to count after the first ten requests

Run the email for ten requests and keep a short tally: how many CEOs reported an advisor already involved; how many stand-downs followed; which route each CEO chose; any complaint from an advisor who felt bypassed; any member who felt the association overstepped; and any duplicate that surfaced after an introduction went out. Thirty days after each request, send the CEO one optional question with a plain way to ignore it: did our introduction get in the way of anyone who already advises you? One yes means the email needs work before request eleven. SourceX has not published figures on how often introduced companies already have an advisor involved, so these counts are the association's own.

## Where the advisor check can still go wrong

- **The CEO does not know.** An advisor may have written to SourceX without telling the CEO. SourceX's records decide, and the association promises nobody credit.
- **Advisors who feel crowded.** An advisor may read any association offer as competition. Keeping to the CEO's choice, and never contacting the advisor uninvited, is the only answer that holds up.
- **Advisor conflicts.** An advisor's own rules on referral payments are between the advisor and the client; the association does not interpret them.
- **Several advisors.** When three advisors know the company, the CEO picks one and tells the others. The [two partners, one company guide](/guides/when-two-partners-refer-the-same-company) shows what happens when records collide anyway.
- **Chapters that act alone.** A chapter that introduces a member the national office has already handled creates the same collision; [chapter coordination](/guides/how-to-coordinate-local-chapters-without-duplicate-outreach) gives each member one desk.
- **Changing terms.** SourceX may publish new terms versions; reread sections 2 and 3 before reusing the email.

The member survey that tests interest before any of this is in [association member survey questions](/resources/association-member-survey-questions), and more association guides are in the [guides library](/guides).

## 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.

Before the first CEO's request arrives, [register](/register) the association as a partner, keep a copy of [who qualifies](/who-qualifies) to send members who want to check themselves, and reread sections 2 and 3 of the [program terms](/terms) so the advisor question in message 1 stays accurate.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://www.aicpa-cima.com/resources/toolkit/sspfps-toolkit
