It is written for a head of channel partnerships whose network of introducers sends companies toward SourceX. Program facts come from SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and sample Channel Partner Agreement, read on 26 October 2026; the charter, loop and worked year are this page's own and Illustrative.
What a council can change, and what it can only ask for
Two sets of rules govern your partners. Your network's own program, its materials, intake, support and training, is yours to change, and a council can improve it. SourceX's terms are not: rewards, caps, payment conditions and attribution are set in the published terms or a partner's signed Schedule A, and SourceX may publish new versions of those terms. Partners cannot commit SourceX either; its sample Channel Partner Agreement says a partner is not SourceX's agent and may not commit it to prices, licenses, payouts or other obligations.
| Topic | Who decides | The council's role |
|---|---|---|
| Criteria wording in your network's materials | You | Recommend rewrites, with examples of misread cases |
| Intake form and screening questions | You | Recommend fields and order |
| Support routing and response targets | You | Recommend, within staff hours |
| Training and partner communications | You | Recommend and review drafts |
| Reward rate, cap and payment conditions | SourceX's terms or a signed Schedule A | None; written feedback only, through you |
| Attribution and duplicate decisions | SourceX, from dated records | None; never discussed case by case |
| Whether a named company fits | SourceX's review | None; the company is not discussed |
Fund governance offers a useful precedent. ILPA describes the limited partner advisory committee as a sounding board for the general partner on governance questions, conflicts of interest above all, and says the general partner should not itself be a member. The same separation works here: the program owner convenes the council, prepares its evidence and answers it in writing, but holds no seat. Advice and decision stay with different people. For how an LPAC itself works, see what an LPAC is.
The numbers each meeting starts from
A council that meets without records debates impressions. Send members a one-page pack a week ahead, built from your network's records only, since SourceX has not published partner cohort data. An active partner has signed the SourceX Channel Partner Agreement and sent at least one proposal to your screen in the quarter. A useful introduction passed every published check your team can confirm, including 50 or more full-time employees at peak, named no company already claimed, and reached a CEO who wanted the conversation.
| Pack line | Counted from | Why the council needs it |
|---|---|---|
| Active partners, by cohort | Signed agreements and proposals | Shows who the program is working for |
| Fit-screen pass rate, by cohort | Your screen records | Locates the cohort that is falling behind |
| Claim collisions | Your claim log | Signals overlapping circles |
| CEO feedback flags | Notes from introduced CEOs | Catches trust problems early |
| Support hours and open questions | Question log | Shows what a new idea would cost |
| Last quarter's adopted changes and their check metric | Change notes | Keeps the loop honest |
The council charter, clause by clause
The charter fits on one page; each clause answers a common failure, from capture by the loudest partner to drift into topics nobody in the room controls.
| Clause | What it says | Why it is there |
|---|---|---|
| Purpose | Advise the program owner on how partners find, screen and introduce companies | Keeps sessions on work partners do |
| Scope | Criteria wording, intake, support routing, training, tools and communications; never rewards, attribution or named companies | Limits advice to what can be acted on |
| Seats | Seven: two highest-volume partners, two from the cohort with the lowest pass rate, one from the newest cohort, one from another profession, one drawn by lot | Puts the weakest results in the room, not only the best |
| Terms of service | One year, renewable once, staggered so half the seats change each year | Prevents a standing clique |
| Convener | The program owner convenes, prepares evidence and answers in writing, and holds no seat | Separates advice from decision |
| Conflicts | Members disclose live introductions that an agenda item touches and sit out that item | Stops a member steering a rule toward their own claim |
| No names | No company names, identifying descriptions, client lists or fee levels, in session or in minutes | Protects confidential introduction records and avoids competitor exchanges |
| Capacity | At most three recommendations for action per quarter | Matches advice to the hours available to act on it |
| Answers | A written reply to every recommendation within 14 days: adopt, decline or defer, with the reason | Shows members their time changed something |
| Review | The charter is reviewed yearly; the council pauses after two quarters with no adopted or measured change | Ends a council that has stopped working |
The no-names clause has two grounds. SourceX's sample agreement lists introduced contact identities and introduction records among confidential information, so a session where partners trade prospect names spreads exactly what the agreement protects. And the members are often competitors for the same clients: the FTC's guidance on trade associations flags exchanges of price or other sensitive business data among competitors as a concern, particularly current data that identifies individual firms. Keeping fees and client lists out of the room avoids both problems. Similar confidentiality habits from CEO peer groups are covered in peer advisory group confidentiality.
From a raised issue to a checked change
Councils usually fail here: recommendations vanish and members stop coming. Six steps, each with an owner and a clock, prevent that.
| Step | What happens | Owner | Clock (Illustrative) |
|---|---|---|---|
| 1. Raise | Any partner submits an issue with an example, without naming a company | Any partner | Any time |
| 2. Sort | Issues are tagged by topic; named-company items go to the claim or screening channel, items about SourceX's terms to a feedback list for SourceX, and each remaining issue gets a one-page evidence note with counts from records | Program owner | Weekly, notes a week before the session |
| 3. Rank | The council picks up to three issues for action and names the number each should move | Council | Quarterly session |
| 4. Answer | Adopt, decline or defer, in writing, with reasons | Program owner | Within 14 days |
| 5. Announce | A dated, versioned change note goes to every partner, not just the council | Program owner | With the change |
| 6. Check | The named number is measured a quarter later; the item closes or reopens | Council | Next session |
Feedback about SourceX's own terms takes a separate path. The program owner sends it as one written note, with cases described without company names, and reports back what SourceX said. Nobody promises the council a change: terms move only when SourceX publishes a new version, and signed agreements are never silently replaced.
A council's first year, including the cohort that was falling behind (Illustrative)
Illustrative: an invented network of 60 partners, a seven-seat council and a program team with six hours a week for partner support. Every count below is invented.
| Quarter | Raised by | Recommendation | Written answer | Checked against |
|---|---|---|---|---|
| Q1 | The two seats from the accountants' cohort, which passed 3 of 12 proposals | Ask for full-time headcount at the peak year on the intake form, not "number of employees" | Adopted in nine days; change note 1.1 | Size misses in that cohort: 7 of 12 before, 2 of 10 the next quarter |
| Q2 | A member who recognized a company another member began to describe | Treat any description specific enough to identify a company as naming it; add a claim-log lookup before outreach | Adopted; the session moved on | Claim collisions per 20 proposals |
| Q3 | Four members | Monthly one-to-one office hours for all 60 partners | Declined: 30 hours a month against about 26 available for all support; deferred to two group sessions a month | Group-session attendance and unanswered questions |
| Q4 | Several members | Ask SourceX to publish how credit works across sister companies | Sent to SourceX as one written note; no published answer yet | Logged as open |
The cohort falling behind. Without its two seats, the Q1 issue would not have reached the council, because the high-volume partners had never misread the size rule.
The duplicate-risk case. In Q2 a member began describing "a 600-person freight group out west", and another recognized it as a company they were already working with. The convener stopped the discussion. Neither member resolved it in the room; each recorded dated evidence afterwards, and credit, if any, will be decided by SourceX from dated records, one partner per company. A company that already had any application, relationship, lead, account or email correspondence with SourceX would be a duplicate for both.
The capacity limit. Office hours for 60 partners would have consumed more than the whole support allowance, so the Q3 answer gave the arithmetic and an alternative instead of a vague "we will look into it".
Staff hours, loud members and prospects two members share
Four forces decide whether a council helps or just meets. Each adopted recommendation costs staff hours to build and announce, hence the cap of three a quarter, and many good ideas, such as office hours, are really requests for more of the same scarce support hours.
Concentration is the quiet risk. If the two highest-volume partners dominate discussion, the council reflects your best partners, whose problems are rarely the network's. The reserved seats help; so does asking the lowest-pass-rate seats to speak first on every item. Overlap is the last force: members work the same towns and industries, and the no-names rule is what keeps a session from becoming a place where claims collide.
Related companies are where the council's limits show. A parent company and its subsidiaries share one reward cap, but how an earlier introduction or an earlier SourceX relationship of one group company bears on another's credit is not published. SourceX works that out when it reviews duplicates. The council can ask for clarity, as in Q4, but it should never write a rule of its own about it into your materials.
When to adopt a recommendation, and how members correct the minutes
Adopt a recommendation when four conditions hold. These are Illustrative; set yours in the charter.
- Evidence comes from records or several partners, not one anecdote.
- Staff hours exist to build it this quarter.
- It does not restate or contradict SourceX's terms.
- A number to check it against is named at adoption.
Corrections run both ways. Circulate minutes within seven days, without company names, and let members correct them before they are final. Reopen an adopted change when its check number moves the wrong way, and say so in the next change note. A member who believes a written answer misread the evidence can ask for it to be reconsidered once, with new evidence. To compare cohorts fairly across quarters, the referral quality study method fixes cohort age before comparing rates, and preventing duplicate claims sets out the lookup adopted in Q2.
When a council is the wrong tool
- A small bench. With a handful of active partners, one conversation each tells you more than a quarterly meeting.
- The issue is SourceX's terms. A council cannot change rewards, attribution or eligibility; send written feedback and say so plainly.
- Members lobby for their own claims. The conflicts clause exists for this, and a member who keeps raising their own case should rotate off.
- The council hears only survivors. Partners who left the network will not attend. Ask leavers one exit question and bring the answers to the pack.
- A customer council is a different body. Asking clients about data partnerships is a research exercise with its own rules, covered in the customer advisory board discussion.
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 council's first adopted change is checked and holds, have new partners register for a partner link, screen companies against who qualifies and read the program terms the council cannot change. The program overview and the guides hub cover the rest of the network work.