The member feedback loop that improves referral fit: a four-step cycle that codes each optional reply about the notice, changes one rule the association owns per round and records nothing about any member's company

Short answer

Ask the members who took part one optional question about the association's notice, never about their company. Sort every reply into a fixed code, tie each code to a lever the association controls, such as the notice's first line, who receives it or how often it is sent, and change one lever per round. SourceX's criteria, its review and each CEO's decision stay outside the loop, and nothing about a member's records is collected, for SourceX or for the association.

Visual briefFull-size diagram
A clockwise loop of four steps, ask one optional question, code the reply, change one rule we own and check next round, around a center that reads never collected: records, headcounts, systems, member lists. A side panel places SourceX's criteria and each CEO's decision outside the loop and shows Illustrative results: misread replies fell from 2 to 0, and replies saying the company never hit 50 full-time employees fell from 3 to 1.
Illustrative pilot. Steps, codes and counts follow the workflow on this page; no real association or member is described.

This is for the director of a business association, chamber or member community that tells members about SourceX as a referral partner. It assumes the association already offers the topic on an opt-in basis and wants the next notice to reach the right members with fewer misunderstandings.

What referral fit means for an association, and what it cannot touch

For an association, fit is not whether a member's company qualifies. That is SourceX's call after review, and the member's CEO decides whether to apply at all. Fit is the match between what the association says and who reads it: members who are clearly not candidates can tell in a sentence, members who might be can see the tests and who decides, and nobody mistakes the note for a recommendation or a promise.

The feedback loop works only on levers the association owns.

The association can changeThe association cannot change
The notice's first line and how it states the published screenSourceX's screening criteria, which vary by program
Who receives the notice, by member choice: an opt-in list, a topic preferenceA member's eligibility, or SourceX's review outcome
How often it writes, and who signs the messageWhich partner SourceX credits when two have introduced the same company
Where the disclosure of its own possible reward sitsThe CEO's decision, at any member company
The decline route, the feedback route and the introduction protocolWhat SourceX tells a member during review

Two limits from SourceX's own documents frame the loop. The unsigned sample of the Channel Partner Agreement gives a partner no authority to share a company's inventory, records, raw data or personal information, so the loop has no field for any of them. And neither party may publicly present the other as a partner without written authorization, which is one more reason the notice must never read as an endorsement in either direction.

The feedback-to-criteria improvement workflow

Four steps per round, borrowed from a well-tested method. The Institute for Healthcare Improvement describes a Plan-Do-Study-Act cycle as a small-scale test of a change in a real setting, run many times in sequence and widened gradually before the change is adopted (our paraphrase), and its worksheet closes each cycle with one of three choices: adapt the change and test again, adopt it at larger scale, or abandon it.

  1. Ask. One optional question goes to the round's opted-in members a week after the notice: "Which of these best describes your reaction to our note about SourceX?" The first option is "I'd rather not answer", and a free-text box is optional.
  2. Code. Within five working days a named staff member gives each reply one code from the table below. Free text is deleted once coded. No reply is coded from a guess about the member's company.
  3. Change. Pick one lever to change. Complaints and misreads come first, whatever their count; otherwise take the most frequent code that maps to a change.
  4. Check. The next round asks the same question. If the targeted code fell and no complaint rose, adopt the change; if it did not move, adapt it or drop it.
CodeThe reply, in substanceWhat it says about the noticeThe one change it triggersWhat never changes in response
F1Not for us: our full-time headcount never reached 50The size test came too latePut the test in the first line, and offer an education-only versionThe association never asks members for headcount
F2Not for us: most of our records are our clients' materialThe ownership test was missingAdd the line on client-owned materialNobody judges a member's contracts
F3Unclear who would decide at our companyThe authority line was missingState that the company's CEO decides and nobody else can say yes for it, the association includedNo one contacts a CEO around the member who replied
F4Read it as the association vouching for SourceX, or as a sign we would be acceptedThe relationship was described too warmlyName the association's partner role, its possible reward and that SourceX decides after reviewNo claim that SourceX vets or favors the association's members
F5Too many messages, or the wrong senderThe cadence or signature felt like pressureOne notice and at most one reminder, signed by the program leadNo open tracking to choose who gets a reminder
F6Wanted to know what the association getsThe disclosure sat too lowMove it to the opening paragraphThe disclosure is never softened
F7Already in touch with SourceX, or an advisor raised itThe notice did not ask firstAdd the "already in touch?" question before any introductionThe association does not ask who the advisor is
F8Useful; decided it is not for usNothing; the notice did its jobNoneNo follow-up to change the member's mind
F9Useful; our CEO wants to talkNothingThe introduction protocol startsNo introduction without the CEO's written request
F10Wanted detail on privacy, security or rightsA question only SourceX can answerLink SourceX's published pagesNo promise on SourceX's behalf about security or de-identification

Ten codes are enough. A reply that fits none of them is a sign the code list needs review at the end of the round, not a reason to invent a code mid-round.

A twelve-member pilot with a decline route at every step

The pilot keeps each round small enough that one change can be traced. Each round invites members to opt in until about twelve have, and every one of them gets the same sequence:

  • The notice, with the published screen in plain words, the disclosure that the association may earn a reward, which SourceX pays separately and never takes out of a company's compensation, and a line saying that one reply of "stop" ends all messages on the topic.
  • An optional brief or a 30-minute briefing, with no attendance list kept beyond a headcount.
  • The one-question feedback form, with "I'd rather not answer" listed first.
  • An introduction only on request. If a member's CEO asks in writing, the association first asks whether the company has already been in touch with SourceX or been offered an introduction, because only one partner can be credited and SourceX decides overlapping claims in duplicate review. Then it introduces that one company under its signed Channel Partner Agreement, and the CEO takes it from there.

Two routes stay open throughout. The decline route: "stop" is honored on every channel the association runs, and the member's name goes on a do-not-contact note, not into a report. The feedback route: complaints go to a named board member who has no stake in any reward, not to the staff member who runs the program.

What the association may say about fit is fixed before round one. It publishes SourceX's screen in plain words: a peak of at least 50 full-time employees (contractors excluded), several years of records the company created itself, the right to license them and a CEO who agrees to the discussion. 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. Members check themselves, for instance with the company fit checker; whether the records suit a current program stays unknown until SourceX reviews them, and SourceX notes that a company outside one program may fit another later.

Three rounds, read through the codes (Illustrative)

Illustrative. An invented association, invented members and invented counts.

RoundOpted inRepliedCodes receivedChange made after the round
1129F1 3, F2 1, F4 2, F8 2, F9 1F4 first, because misreads outrank volume: the opening now names the association's partner role and says SourceX decides after review
21210F1 3, F5 1, F8 4, F9 1, F10 1F4 fell from 2 to 0, so the change was adopted; next, F1: the size test moved into the first line
3129F1 1, F5 2, F8 4, F9 2F1 fell from 3 to 1 and was adopted; F5 rose to 2, so the reminder was dropped for round four

Three things in the log matter more than any count. The misread code disappeared after one wording change, which is the clearest gain in the pilot. Useful-but-not-for-us answers (F8) doubled from 2 to 4, and that is success: members who could not be candidates found out quickly and said so without complaint. And F9 never rose above two per round, which is the right expectation for an opt-in topic; the loop improves the notice, not the number of introductions. Each CEO who asked was introduced individually, after the earlier-contact question.

Negative feedback first: complaints, misreads and silence

  • Complaints pause the loop. Any complaint that the association pressed a member, or acted as if it could decide for one, stops the next round until the cause is fixed and the board member who handles complaints signs off.
  • Misreads outrank volume. One member who thought the association was vouching for SourceX, or that attending meant acceptance, is a wording failure even if eleven others read it correctly.
  • Silence is not a code. Members who do not reply are never counted as satisfied or opposed, and nobody follows up to find out why.
  • Small numbers stay small. Report counts, not percentages, and never a breakdown that could identify a member.
  • Report the change log, not a funnel. The board needs to know what changed and whether it worked. For measuring member benefit itself, a separate opt-in dashboard is described in measuring a partner benefit without counting every member, and a neutral way to survey members is in the association member survey questions.

Where this loop can mislead

  • Respondents choose themselves. The members who reply are the most engaged ones, so a code that falls among them may not have fallen among everyone else who read the notice.
  • Codes flatten nuance. A member's reply is reduced to one code by design. Read the free text once before deleting it, and revise the code list between rounds if several replies fit poorly.
  • One change per round is slow. It is also the only way to know which change worked. Changing three things at once produces a better notice and no learning.
  • SourceX's criteria move. SourceX applies each program's own requirements and can change them. Date every notice and reread the published screen before each round.
  • The association has a stake. If it can earn a reward, whoever codes the replies has an interest in reading them kindly. A second reader without that interest should check a sample each round.
  • A feedback request can itself feel like pressure. Ask once, make declining the first option, and never chase. Guidance on writing a no that costs nothing is in making a referral ask easy to decline.

This loop concerns the association's own messages. It is unrelated to the human feedback records some companies hold, which SourceX describes on its page about human-in-the-loop data. More association guidance sits in the industry associations overview, the guide to explaining the program to members, the vendor endorsement policy question and the guides library.

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 round one, register the association as a partner and sign the agreement, so a CEO who asks is never kept waiting; keep who qualifies as the only screen the notice repeats, and give the board the program terms version each round was written against.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can the association pass members' feedback to SourceX?

Only as program-level counts the association chooses to share, such as how many replies read the notice as an endorsement, with no member named. Nothing about a member's company, records or headcount goes to SourceX, and a member who wants to talk to SourceX does so directly.

What if a member asks the association whether its company would be accepted?

Point the member to the published screen and the company fit checker, and say that SourceX decides after its own review and the member's CEO decides whether to apply at all. Code the question as unclear fit wording, because the notice should have answered it.

How many rounds should a pilot run before the board decides?

Three rounds of about a dozen opted-in members is enough to see whether one change moves its target code. After that, the board continues, changes course or stops, using the change log rather than a conversion rate.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  4. ihi.org/library/model-for-improvement/testing-changes
  5. ihi.org/sites/default/files/QIToolkit_PDSAWorksheet.pdf

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment