The MSP referral pilot that protects client trust: a 120-day trust-and-fit measurement plan with tripwires written before the first ask, a holdout group and a readout that counts the clients who said no

Short answer

Run the pilot as a test of whether you can raise data licensing without denting client trust, not as a forecast of earnings. Choose 8 to 12 accounts with a dated system event and a reachable CEO, write the trust tripwires, fit measures and decision rule before the first ask, keep a holdout group you do not ask, and read out at day 120, when every introduction made in the first 30 days has had its full 90-day attribution window. Revenue stays out of the plan: SourceX publishes no conversion rates, and rewards arrive later.

Visual briefFull-size diagram
A three-by-three decision grid set before the first ask: columns for weak, mixed and strong fit signals and rows for no tripwire, a minor tripwire and a breach; only no tripwire with strong fit reads expand, the breach row reads stop in every column, and the remaining cells read adjust, except a minor tripwire with weak fit, which reads stop.
The progression rule from the plan on this page. Thresholds are set by each MSP before the pilot starts.

An MSP's trust is built ticket by ticket over years, and one awkward ask can cost more than any reward. The plan below is designed so that the first sign of strain stops the pilot before it spreads.

What a pilot can tell an MSP, and what it cannot

A pilot answers feasibility questions: can the asks be made without harm, do the selected clients pass the fit facts, and does the team keep its own rules. It cannot tell you what the program is worth, because the sample is small and the money comes after the window closes.

Clinical researchers met this problem long ago with their own pilots. Methodology papers on external pilot trials describe them as small standalone studies run to test whether a larger trial is feasible, and recommend progression criteria that decide whether to go ahead and in what form (a paraphrase). A methodological review adds that those criteria should be fixed before the pilot starts, since setting them afterward invites bias (a paraphrase). An MSP is not running a trial, but the discipline transfers well: decide in advance what result means expand, adjust or stop.

The pilot can showThe pilot cannot show
Whether clients react badly to being askedWhat a typical reward is; SourceX publishes no payout ranges for partners
How many selected accounts pass the fit facts in the CEO's own wordsWhether SourceX will accept any company; that is decided in its review
Whether technicians keep referral talk out of tickets and exportsHow the program performs across your whole client base
How long it takes from ask to verified applicationAnything about clients you did not select

Portal and calculator estimates are projections, not promises, under section 5 of the terms, and section 4.6 of the unsigned partner agreement sample bars telling a client that an estimate, positive interest, a signature or an upload makes a purchase or reward certain. Keep both out of the plan and out of the asks.

Choosing the accounts, and the event that makes each one timely

Select on facts you already hold as the service provider, then confirm the fit facts with the CEO, never from your consoles.

Include an account when it has a dated system event in the next two quarters (a migration, a retirement, a retention review or a platform replacement), its CEO is someone your account lead speaks with directly, it appears to have reached 50 or more full-time employees at its peak by its own account, contractors excluded, and it has years of operating records it created itself.

Leave an account out when it has an open escalation or a contract dispute, its most visible records belong to its own customers, it is in a formal process such as receivership, or it was recently acquired and nobody at your firm knows the acquirer's CEO, who now decides for it.

Keep a holdout. Set aside three or four accounts that meet every inclusion rule and are not asked. Their regular service survey scores give you a comparison for the asked group.

The person who first notices the system event, usually an IT director or operations lead at the client, often becomes the internal sponsor. The ask still goes to the CEO, who decides whether the company discusses licensing at all.

The trust-and-fit measurement plan

Twelve measures in three groups, each with its denominator and its source written into the charter on day 0. Thresholds are yours to set; write them down before anyone is asked.

GroupMeasureDefinitionDenominatorCounted from
TrustComplaintsAny complaint about the ask, to anyone at your firmAccounts askedThe account lead's log
TrustDo-not-raise requestsClients who ask you not to bring the topic up againAccounts askedThe log
TrustService score changeRegular satisfaction survey score after the ask minus before, compared with the holdoutAccounts asked and holdout accountsYour existing survey tool
TrustSponsor comfortSponsors who say the ask felt separate from your service, when asked a week laterSponsors spoken toA short follow-up call
FitFit facts confirmedAccounts whose CEO confirmed headcount at peak, years of records, rights and willingnessAccounts askedThe CEO, in writing
FitCEO yesesWritten yes to an introductionAccounts askedThe CEO's email
FitDuplicates foundCompanies with an earlier application, lead, account or email thread with SourceXCEO yesesThe earlier-contact question
FitVerified applicationsApplications verified within 90 days of the recorded introductionIntroductions submittedSourceX's status updates
DisciplineExports or samplesAny file, count, sample or login sent toward SourceXAccounts askedTarget zero
DisciplineReferral lines in ticketsReferral wording found in tickets or time entries in a spot checkTickets sampledA review of a ticket sample
DisciplineDisclosure before yesAsks where the reward was disclosed before the CEO answeredAsks madeThe log
DisciplineAgreement firstThe SourceX Channel Partner Agreement signed before the first submissionOne checkYour signed copy

The decision rule, set on day 0. Write three outcomes and the conditions for each:

  • Stop if any complaint reaches a client executive, any client links the ask to its service contract, or anything is exported for SourceX. Stop also when minor tripwires coincide with weak fit, since the asks cost trust and found nothing.
  • Adjust in every other case: no tripwire but weak or mixed fit, a minor tripwire within your thresholds alongside mixed or strong fit, or a discipline slip, such as a ticket line, that is found and fixed.
  • Expand only with no tripwires, every discipline measure at its target and fit signals you wrote down in advance as strong.

Method note. The plan was built on 2026-10-27 from SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04), its screening page, the unsigned partner agreement sample (version 2026-10-19) and the pilot-methodology sources cited above. The 120-day readout follows from Schedule A paragraph 2 of the sample, which credits an introduction when the company submits a verified application within 90 days of the recorded introduction. No MSP cohort results have been published by SourceX or anyone else, so the figures are not yet published; your first readout becomes your own baseline.

Who does what while the pilot runs

RoleWhoIn the pilotNever
Pilot ownerThe account lead or principal who signed the partner agreementMakes each ask, keeps the log, submits introductionsPromises fit or value
TechniciansYour service teamRoute any mention of the topic to the pilot ownerExport, count, sample or describe client records
SponsorAn IT director or operations lead at the clientCarries the idea to the CEO, if they chooseDecides for the company
Decision makerThe client's CEOSays yes or no, applies, signs or walks awayHands the decision to the MSP
ReviewerSourceXReviews fit and rights, deals with the company directly, decides creditTakes records from the MSP

The technicians' row is the one that fails quietly. Section 4.2 of the partner agreement sample gives a partner no authority to share a supplier's records or reach its extraction systems, and partners never see, upload or handle a company's records, inventory or data room. Keeping the topic out of the ticket system is covered in how to keep referral notes out of client support tickets.

The 120-day calendar

DaysStepGate
0Charter written: cohort, holdout, measures, thresholds, decision rule; partner agreement signedNothing is asked before the charter exists
1 to 30One ask per account, in a scheduled business review, never in a ticketReward disclosed in every ask
1 to 45Written yeses, earlier-contact checks, introductionsNo introduction without the CEO's yes
45Midpoint review of trust and discipline measuresAny stop condition ends the asks
30 to 120Applications and SourceX review run between SourceX and each companyThe MSP's part has ended
120Readout against the day 0 ruleExpand, adjust or stop

The ask and the introduction, held to the pilot's rules

The ask is one short spoken paragraph: what SourceX does, that the company would decide everything, that your firm could receive a reward from SourceX if a license closed, and that the answer changes nothing about your service. No estimate, no view on fit, no numbers from your monitoring. If the CEO says yes in writing, the introduction carries the company's name, the CEO and the CEO's own description of the business. The company describes its systems to SourceX itself. A ready-made pair of messages is in the permission-first email pair for MSPs.

One readout, with invented counts (Illustrative)

Illustrative. The counts are invented to show how the decision rule reads; they are not results from any MSP.

An MSP asks 10 accounts and holds out 4. Day 120: no complaints, one do-not-raise request, service scores flat against the holdout, sponsors comfortable in 8 of 9 follow-ups. Six CEOs confirmed the fit facts and four said yes; one of those turned out to be a duplicate, so three introductions went in, and two applications were verified within their windows. Discipline: no exports, but the ticket spot check found one referral line in a time entry, fixed the same week.

Under the day 0 rule this reads adjust: no stop condition, fit signals mixed rather than strong, and one discipline slip. The MSP retrains the service desk and runs a second cohort. Nothing about rewards appears in the readout. If one of those companies later licensed and SourceX paid it $400,000, the reward would be $70,000, payable only once every condition in the terms was met, and it belongs in a later review, not in this one.

Where the plan can mislead you

  • Small numbers. Ten accounts cannot separate a real effect from luck; treat every rate as a direction, not a finding.
  • Friendly selection. Choosing the clients who like you most flatters the trust measures. The holdout helps only if it was chosen by the same rules.
  • Slow signals. Survey scores move months after the event that moved them.
  • Programs move. SourceX applies each program's own criteria, which can change, so a fit result is valid for its date.
  • Your contracts. Service agreements or client policies can restrict outreach; read them before day 0.

For the security questions clients raise when asked, see MSP client data licensing security; for spotting suitable accounts, how MSPs can recognize suitable client businesses; for the overview, the managed service providers page 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.

When your charter is written and the decision rule is on paper, register as a partner, check the cohort against who qualifies and read the program terms before the first business review where you raise it.

  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

Why 120 days rather than a month?

A company is credited when it submits a verified application within 90 days of the recorded introduction. If the asks run for the first 30 days, a 120-day readout is the earliest point at which every introduction has had its full window.

Should revenue be one of the pilot's measures?

No. A reward becomes payable only after the Acquisition Partner accepts the dataset, SourceX is paid, the company is paid and finance approves, which can fall well after the readout. SourceX publishes no conversion rates or typical payouts, so any revenue line in the plan would be a guess.

What if a client asks to join the pilot after hearing about it?

Treat it as an inbound request outside the cohort. The CEO still decides, the same disclosure and earlier-contact check apply, and the account goes in the log with a note that it was not selected.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  4. ncbi.nlm.nih.gov/pmc/articles/PMC10105402
  5. ncbi.nlm.nih.gov/pmc/articles/PMC8240572

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