This page is written for the head of channel partnerships at an alliance, association or referral network whose members are independent advisers. The conflict you are preventing is not mainly a quarrel over a reward. It is a CEO hearing about the same opportunity from an accountant on Monday and a fractional CFO on Thursday, and deciding that neither adviser is coordinated enough to trust.
Why an advisory network collides with itself
SourceX's home page lists the people best placed to refer: M&A advisers and business brokers, private equity and operating partners, fractional CFOs and accountants, IT managed-service providers, wind-down and restructuring advisers, and operators and executives. An advisory network often contains several of those at once, and they serve the same mid-sized companies from different angles. An outside accounting firm, a fractional CFO and a broker preparing a sale can all sit around one CEO in the same year.
Many advisers also bring habits from software partner programs, where credit is often shared or assigned by rule. In a PartnerStack and Wynter survey of 100 senior leaders at B2B SaaS companies with $50M+ revenue, 42% reported multi-touch attribution, 31% first-touch, 19% last-touch and 8% no tracking at all. SourceX's program does not split credit at all. A single partner per company is credited, the one whose valid introduction of that new company landed first inside the 90-day attribution window, and the credit attaches only when the company submits a verified application. A network that expects multi-touch credit will discover the difference after two members have both called the CEO. The comparison of first valid referrer and last touch explains why personal introductions use the first rule.
Activation and referral quality, defined for a network
Count members by what their introductions did, not by how many signed up. Set these definitions before the first quarter, and do not change them mid-count.
| Measure | Definition | Denominator | What it tells you about conflict |
|---|---|---|---|
| Activated member | A member whose introduction led to a verified application | Members who signed the Channel Partner Agreement | Whether conflict prevention is protecting real activity or paperwork |
| Unique companies | Distinct legal entities introduced, counted once however many members touched them | Introductions submitted | The gap between the two counts is your collision rate |
| Duplicate rate | Introductions SourceX reviewed as duplicates | Introductions submitted | How often members asked a company SourceX already knew |
| Clean-ask rate | Companies whose CEO was asked once, by the named asker | Companies asked | Whether the register is used before outreach |
| Stale rate | Introductions with no verified application by day 90 | Introductions submitted | Whether introductions outran support |
SourceX has not published network-level benchmarks for any of these. Write your own thresholds down before you count, so a disappointing quarter cannot quietly move them.
The overlap and attribution prevention map
Five overlaps cause most conflict in an advisory network. Each has a signal you can see early, a control that works before anyone contacts the company, and a record that settles it later.
| Overlap | Early signal | Prevention before the ask | Record that settles it | Correction path |
|---|---|---|---|---|
| 1. Client overlap: two members serve one company | The same legal name or web domain appears in two members' lists | One shared register keyed on legal entity and domain; the member who holds the CEO relationship of record asks, and the other stands down | Register entry with date, both members and the named asker | If both already asked, submit nothing until the members agree who submits; SourceX still decides credit from dated records |
| 2. History overlap: the company already knows SourceX | The CEO mentions an application, call, account or email with SourceX | The named asker asks the CEO before submitting whether the company has had any contact with SourceX | The CEO's answer, dated | Under section 3 of the terms the company is a duplicate and not credited; tell the member before effort is spent |
| 3. Role overlap: the member is paid by the company and may receive a reward | An engagement letter covers ongoing advisory work | The member checks their profession's rules on referral fees and discloses the reward to the client in writing before asking | Date and wording of the disclosure | If a member's rules bar the fee, they raise it with SourceX before introducing; the published terms say nothing about a partner turning a reward down |
| 4. Group overlap: members serve sister companies in one group | Two entities share a parent in the register | Record the parent and every entity a member serves; agree one asker for the group's CEO where one person decides for all of them | Parent and entity rows, dated | One reward cap applies across the group; SourceX's duplicate review, not the network, decides how an earlier sister-company introduction bears on credit |
| 5. Capacity overlap: requests outrun coordination | Requests waiting for a check; introductions ageing toward day 90 | Queue the checks, not the introductions; no member asks until the check is done | Open checks and open introductions, each with its age | Pause new asks; for introductions past day 90, confirm with the CEO whether the company still wants the conversation |
Two rows need more than the table gives them. On row 3, the referral home page tells licensed professionals to check their own rules on referral fees, and the AICPA's planning toolkit reminds members that commissions and referral fees must be disclosed to the client; whether CPAs must disclose referral fees goes further. On row 5, the order matters because of the clock. Schedule A of the Channel Partner Agreement counts the 90 days from the recorded introduction, so a queue before the ask costs nothing on that clock, while a queue after it spends the window. The terms also say the 90-day window does not extend because contact protection continues, a point covered in attribution versus contact protection.
The register itself should carry the fields SourceX's own records use. Section 3.3 of the Channel Partner Agreement says each introduction record must identify the company, domain, partner, opportunity, introduction method and timestamps. A network register with the same six fields, plus the named asker and the parent group, can answer almost any later question. For the member-level steps in the last 48 hours before an introduction, use how to prevent duplicate claims before they reach SourceX.
One alliance through a quarter (Illustrative)
Illustrative: the alliance, its members and every figure are invented. A regional alliance of 40 independent advisory firms adopts the map at the start of a quarter: 18 accounting firms, 12 fractional CFO practices and 10 business brokers.
| Cohort | Members | Introductions | Unique companies | Verified applications | Reviewed as duplicates |
|---|---|---|---|---|---|
| Accounting firms | 18 | 11 | 11 | 4 | 1 |
| Fractional CFO practices | 12 | 9 | 9 | 3 | 0 |
| Business brokers | 10 | 14 | 13 | 0 | 1 |
| Alliance total | 40 | 34 | 33 | 7 | 2 |
The underperforming cohort. The brokers sent the most introductions and produced no verified applications. Reading their register rows shows why: nine of their thirteen companies had a peak headcount below 50 full-time employees, the published screening profile's starting point, and one company was introduced twice by two brokers in the same firm. The fix is a better screen before the ask, not more encouragement, and the brokers' activation stays at zero until it works.
The duplicate-risk case. A 160-person engineering consultancy is an audit client of one accounting firm and a fractional CFO client of another member. Both flag it in the register in the same week. The accounting firm logged it first, but the CFO sits in the consultancy's management meetings and holds the CEO relationship of record, so the CFO asks and the accounting firm stands down. Whatever the two firms agree between themselves is private and outside the program terms. Because only one person asked, the CEO heard one coherent message.
The capacity limit. One coordinator has six hours a week, and a full check (register lookup, the history question, the disclosure check) takes about 45 minutes, so the alliance can clear roughly eight checks a week. After a newsletter mention, 23 requests arrive in one week. Fifteen wait for up to two weeks, and none of those waits touches an attribution window, because no introduction has been made yet.
The duplicate nobody could explain. One accounting-firm introduction came back from SourceX's review as a duplicate. The terms say partners never receive access to other partners' records, so the alliance learned the outcome, not whose earlier record decided it. That is how the program is meant to work, and the network should tell members to expect it.
Capacity, support, concentration and overlap across member firms
- Capacity. Checks per week is the binding number. Publish it to members so a wait reads as process, not neglect.
- Support. The network answers questions about its own register and rules. Questions about attribution, eligibility or a reward go to SourceX, whose terms provide a dispute route with the referral details and evidence.
- Concentration. If three members produce most of the verified applications, say so in member reports rather than averaging it away, and plan for what happens if one leaves.
- Overlap. Track the gap between introductions and unique companies each quarter. A gap that grows means the register is being filled in after outreach, not before.
Expand with evidence gates, and keep correction paths open
Add another member cohort, or another advisory network, only when the last one passes gates you wrote down in advance. Illustrative gates: every introduction in the quarter had a named asker recorded before outreach; the clean-ask rate stayed at or above your threshold; no licensed member introduced a client without a dated disclosure; and open checks never waited longer than two weeks.
Corrections need a path that does not depend on goodwill:
- Wrong asker. The member who should not have called tells the CEO plainly that a colleague will be the single contact, then stands down.
- Wrong record. Correct the register with a dated note, never by overwriting the original entry.
- Disagreement about credit. Send it to SourceX with dated evidence. The network does not adjudicate credit, and when two partners refer the same company sets out what that review looks at.
- Group questions. Where entities share a parent, handling multiple subsidiaries in attribution shows what to document.
Client confidentiality can block the first step entirely: an adviser bound by a confidentiality clause may not be free to name a client to anyone, which is one more reason the CEO is asked first. SourceX's main site covers that question in whether client NDAs prevent licensing data.
What the network's rules cannot change
The register decides who asks; SourceX decides credit. No internal agreement makes a duplicate creditable, extends the 90-day window or gives a member access to another partner's records. The network's job is to make sure the company experiences one adviser, one message and one decision that belongs to its CEO.
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.
Once your register names one asker for a company and its history check is clean, that member can register for a partner link, screen the company against who qualifies and read the program terms before contacting the CEO. More network playbooks are in the guides library.