It is written for a head of channel partnerships whose introducers, advisors in a firm or members of an alliance, send companies toward SourceX. Program facts were read on 26 October 2026 in SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and its who-qualifies page; the diagnosis, its thresholds and every worked number are this page's own and Illustrative.
A content request is often a criteria problem in disguise
When a cohort underperforms, the first request is usually for material: a deck, a longer FAQ, a webinar. But a partner who counts contractors toward a size threshold will keep doing so after a 30-page playbook that repeats the sentence that misled them.
The record shows the difference. A criteria gap leaves proposals that fail the same check for the same reason; a content gap leaves good-fit proposals that stall because the partner could not explain the program to a CEO. Only the second is fixed by writing more.
The wider market points the same way, with caution. In PartnerStack and Wynter's survey of 100 senior leaders at B2B SaaS companies with $50M+ revenue, fielded in September 2025, alignment between teams was the most cited blocker to partner-driven revenue, at 37%, and no clear partner program came second, at 20%. It is a vendor-run sample of software firms, not referral introducers, so read it as a sign that clarity problems are common, not as a measure of yours.
Activation and a useful introduction, defined before you diagnose
The diagnosis needs fixed definitions while you measure.
| Term | How this page counts it |
|---|---|
| Activated partner | Signed the SourceX Channel Partner Agreement and sent a first proposal that reached your fit screen within 90 days of signing |
| Useful introduction | Passed every published check you can confirm, named no company already claimed, and reached a CEO who wanted the conversation |
| Miss | A proposal that failed a check, turned out to be a duplicate, or stalled because nobody had asked the CEO |
The checks your screen applies are the published ones: a full-time headcount that reached 50 or more at its peak, with contractors not counted; years of records generated by the company's own work; the rights to license them; a CEO who wants the conversation; and location. 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. Relevance to current data needs is checked in SourceX's own review, not by your team. For how partners move from registered to active, see the activation ladder.
The enablement gap diagnosis
Three tests, run in order. None needs data from SourceX; all use records your team keeps or can collect in a week.
Test 1, the miss log. Take your last 20 misses and code each by its first failed check: size, history, rights, authorization, location, duplicate, or stalled with no CEO asked. If one code holds more than 40% of misses, that check is your suspect.
Test 2, the two-reader test. Write five short company sketches that sit near the boundary of the suspect check. For size, that means a company with seasonal crews, one that shrank after its peak, a staffing firm and two plain cases. Ask at least three partners to mark each sketch pass, fail or unknown on their own, then compare with the answer the published rule gives. If readers match the rule on fewer than four of five sketches, the wording is ambiguous to them, whatever it means to you.
Test 3, the CEO question log. For every useful introduction, record the CEO's first question and whether the partner could answer it. A recurring unanswered question is a content gap, and the content to write is that answer.
| Gap | What the records show | Test that confirms it | The fix | What more content does |
|---|---|---|---|---|
| Criteria | Misses cluster on one check across many partners | Two-reader agreement below 4 of 5 | Rewrite that check as a decision rule with a boundary case | Repeats the ambiguous sentence |
| Content | Proposals pass but CEOs decline the first conversation | One unanswered CEO question recurs | Write the answer to that question, one page | Helps, if it answers that question |
| Access | Few proposals, and those come through functional executives | Partners cannot name a CEO they could reach | Accept lower volume, or pair the partner with a relationship owner | Nothing; reading does not create relationships |
| Duplicate | Proposals name companies already claimed or already known to SourceX | A claim-log lookup catches them | A lookup and one screening question before outreach | Nothing |
| Capacity | Questions wait days for an answer and partners go quiet | Response times exceed your own target | Fewer recruits or more hours | Adds questions to the same queue |
Method note. The diagnosis applies the published fit checks and attribution rules (SourceX terms and who-qualifies page, checked 2026-10-26) to records your team keeps. It does not measure demand, rights in fact or payout, which only SourceX's review assesses. The 40% and four-of-five thresholds are planning choices; SourceX has not published partner cohort data, and none is used here.
Rewrite the failing check as a decision rule
A criterion is usable when a partner can apply it to an awkward company without asking you: the rule in one sentence, a boundary case that passes, a counterexample that fails, and what to do when the answer is unknown. Add the source and terms version, because the terms list five versions in October 2026 alone, from 2026-10-12 to 2026-10-22.2.
| Part | Size check, before | Size check, after |
|---|---|---|
| Rule | "Companies with 50+ employees" | Count full-time employees at the company's peak year; contractors, temps and placed workers do not count |
| Boundary case | None given | Passes: 64 full-time staff at a 2022 peak and 41 today |
| Counterexample | None given | Fails: 30 full-time staff plus 90 contractors in every year |
| Unknown | Partner guesses | Mark unknown and ask the relationship holder for the peak year and the full-time count |
| Source and version | None | Terms Version 2026-10-22.2, since replaced by version 2026-11-04 and the who-qualifies page, read 26 October 2026 |
Staffing firms need their own line: only the firm's own full-time employees count, not workers placed at clients, yet SourceX still considers staffing firms, so partners give both numbers and introduce a firm with strong records anyway. For rights, "records the company created itself" passes a support desk's own ticket history and fails the bookkeeping files an accounting firm keeps for its clients. Authorization takes one sentence: the CEO decides, and an introduction the CEO does not know about is usually not a fit.
Add one question your rules probably lack: has the company ever applied to, emailed or held an account with SourceX? If SourceX already holds any earlier application, relationship, lead, account or email correspondence with the company, it is a duplicate and is not credited to any partner. Which questions belong to the partner and which to SourceX is sorted in the responsibility table for eligibility questions, and keeping criteria sentences current once sent is covered in versioned criteria distribution.
One underperforming cohort, diagnosed (Illustrative)
Illustrative: an invented cohort of 14 bookkeeping and payroll advisors recruited at one regional event. In their first 90 days they sent 18 proposals and 3 passed your fit screen. Their lead asked for a 30-page playbook.
The miss log sorted the 15 misses in an afternoon. The size misses counted seasonal crews or contractors; the rights misses proposed the client records the advisors keep for their own customers. Of the two duplicates, one was already in another partner's log, and in the other the CEO mentioned applying to SourceX the year before.
The two-reader test on size confirmed it: four cohort members matched the published rule on 2.5 of 5 sketches on average, an established partner on all five. Only three introductions had reached a CEO, so the content bin held nothing; no miss came from a partner who understood the rules and lacked words.
| Code | Misses | Gap | Fix applied |
|---|---|---|---|
| Size | 8 | Criteria | Size rule rewritten with peak year, contractor exclusion and two sketches |
| Rights | 3 | Criteria | Client-records counterexample added to the rights rule |
| Authorization | 2 | Access | Partners asked to name the CEO and who will ask before proposing |
| Duplicate | 2 | Duplicate | Claim-log lookup plus the earlier-contact question |
| Stalled, CEO never asked | 0 | None | No action |
The capacity limit. Your team has five hours a week for partner support. The cohort's 26 clarification questions took about 20 minutes each, close to nine hours a quarter, and the requested playbook was estimated at 20 hours, four weeks of the whole allowance. Rewriting two rules took about three hours. In the next 90 days the cohort sent 12 proposals, 7 passed, and clarification questions fell to 9; whether a real cohort responds the same way is what your own miss log will show.
Review hours, concentration and claim overlap before anything new ships
A rewrite changes who proposes what, so check four things before and after it. Clearer criteria usually mean fewer proposals and a higher pass share, freeing screen time, while new content usually raises inbound questions. If one partner supplies most passing proposals, their success says little about whether the rules are clear to others. Overlap grows as members of one profession share a town and its CEOs; preventing duplicate claims before they reach SourceX sets out the lookup.
Corporate groups are the overlap case your rules cannot settle. Because the reward cap treats a parent and its subsidiaries as one company, link related entities in your log. The terms say nothing about the harder question: if a sister subsidiary was introduced first, or the parent already dealt with SourceX, does that touch this subsidiary's credit? SourceX answers that in duplicate review, so your criteria flag the link and predict nothing.
| Check | Read it from | Signal (Illustrative threshold) | Response |
|---|---|---|---|
| Review hours | Screen time per proposal, by month | Hours rise after a content release | Pause the release; ask which question it created |
| Concentration | Share of passing proposals from the top partner | Above 30% | Run the two-reader test without that partner |
| Overlap | Proposals hitting an existing claim, per 20 | More than 2 | Make the lookup mandatory before outreach |
| Version drift | Proposals screened under an older terms version | Any | Re-screen against the current version and tell the partner |
Evidence gates for new content, and how a partner corrects a code
Commission new partner content only when four Illustrative gates are met; set your own before the next cohort.
- No single check holds more than 40% of the last 20 misses.
- Partners match the published rule on at least four of five sketches for the three most-missed checks.
- The CEO question log shows one recurring question that partners cannot answer.
- Your support hours have room for the questions a new piece will generate.
Share each partner's own miss log with them, never anyone else's, and let them dispute a code with a dated reason; record why any code changes. Tag every proposal with the terms version it was screened under, and re-run the two-reader test after each new version. To compare cohorts of different ages fairly, use the referral quality study method.
Where this diagnosis misreads a network
- Small numbers. Twenty misses from five partners can reflect one partner's habit; read the log by partner too.
- Silent partners leave no trail. A partner who never proposes produces no misses, so access gaps hide outside the log. Count non-proposers separately.
- Your key can be wrong. The two-reader test compares partners with your reading of the rule; check that reading against the who-qualifies page each time.
- SourceX's review is not your screen. A proposal that passes every check you can see can still be declined for relevance or rights, and criteria differ by program.
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 rewritten rules pass the two-reader test, have partners register for a partner link, check each company against who qualifies or the company fit checker, and read the program terms for the version your rules now cite. More network playbooks sit in the guides hub.