How to test a workshop's effect on actual introductions: a now-or-later draw that gives every invitee the session, half of them only after the counting window closes, and scores the gap on CEO-agreed introductions that reach a verified application

Short answer

Draw everyone you would invite into two groups before sending a single invitation: a now group that attends the workshop at once and a later group that attends after a 90-day counting window. Then compare the groups on introductions whose CEO agreed in writing and that reached a verified application SourceX credited, read on day 180. Compare by invitation, never by attendance, because the people who show up are the ones most likely to introduce anyway. No results from this design are published.

Visual briefFull-size diagram
A schedule of two bars across days 0 to 180. The now group attends the workshop on day 0, the later group on day 91; both count introductions from day 1 to day 90 in a shaded band labeled compare here, by invitation, and both have their introductions' stages read on day 180.
The design, not a result. No partner or SourceX results for this workshop test are published.

This is for the person who runs referral enablement at a firm or network: an advisory practice briefing its client partners, an association briefing chapter members, a fund briefing operating advisors. Every introduction still goes through someone who has signed the SourceX Channel Partner Agreement, and each one names a single company whose CEO agreed to it.

Turnout measures interest; the test measures what changed

Workshop reports usually count registrations, attendance and a satisfaction score. None of them says whether anyone later asked a CEO a well-judged question. Kirkpatrick Partners' model calls that Level 3, Behavior: whether participants apply what they learned once back at work, and it ties behavior to required drivers such as job aids, coaching and work review rather than to the event alone (paraphrase). An introduction is a behavior, and a verified application is the closest result a partner can observe.

The trap is self-selection. The colleague who books the first seat already has a CEO in mind. If you compare attendees with people who skipped, the workshop gets credit for that colleague's prior intent. Drawing groups before anyone is invited, and keeping every invitee in the group they were drawn into, removes that problem; the event-quality funnel covers what an event can show on the day itself.

What the workshop may teach, and the promises it must leave out

Both groups end up seeing the same session, so its content must be right before the draw.

The session mayThe session must never
Walk through who qualifies on screen and link itTell anyone that a named company qualifies
Say the CEO decides whether to talk and signs for the companySuggest the network, a board seat or the partner can decide for a company
Explain that SourceX decides fit and credit from dated recordsSay that sending a link secures credit
Say the partner may earn a reward from SourceX, disclosed to each CEOPresent the reward as income anyone can count on
Show how to describe records by type, years and systemAsk attendees to gather files, samples, exports or logins
Say nobody gets preferential access to a company's dataImply that SourceX endorses the host or its members
Invite attendees to raise SourceX only where it fits a real conversationSet targets, quotas or a "bring one company" ask

Two clauses of the sample Channel Partner Agreement shape the invitation. Section 4.5 bars either party from publicly identifying the other as a partner without written authorization, so do not bill the session as a SourceX partnership event unless SourceX has agreed in writing. Section 7.1 says the partner is not SourceX's agent and may not commit SourceX to prices, licenses or payouts, so no slide may estimate what a company would be paid.

Now group, later group: the draw and the clock

ElementSpecification
DecisionKeep running the workshop, rework it, or stop
HypothesisThe now group makes more qualified introductions per 10 invitees in days 1 to 90 than the later group
UnitOne invited person who could raise SourceX with a CEO they know
AllocationA logged draw before any invitation, done separately within each role list so both groups get a similar mix
Now groupAttends on day 0
Later groupKeeps the standard links and attends on day 91 or soon after
Counting windowIntroductions submitted from day 1 to day 90
Read dateDay 180, so an introduction made on day 90 has a full 90-day attribution window
AnalysisBy drawn group, whoever attended

Ask now-group attendees not to forward slides or notes until the later session. Some will anyway; the spillover question below measures it.

The workshop follow-through evaluation

Each stage has one definition, one piece of evidence and one thing that never counts. Copy SourceX's stage and status words exactly as the dashboard shows them; how it works lists the statuses as Estimated, Eligible, Approved and Paid.

StageCounts whenEvidenceNever counts
InvitedThe person was on a list before the drawThe logged drawPeople added afterwards
AttendedPresent for most of the sessionAttendance listRegistration alone
Asked a CEOThe invitee says they raised SourceX with a CEOAn optional one-line report at day 90A forwarded newsletter
CEO agreedThe CEO said yes in writing before any submissionThe dated email or noteA verbal "sounds interesting"
Introduction submittedOne company, submitted by a signed partnerThe firm's referral log or the partner's dashboardA link click or a page visit
Qualified introduction (primary)SourceX verified the application, credited it to the introduction and has not closed it by day 180Dashboard stageAn application still unverified
Closed or duplicateSourceX closed it, or found the company already knownDashboard stageYour own guess about fit

The report is one table, by group, per 10 invitees, with every column filled by count first and rate second. Until a run finishes, every cell reads "not yet collected"; nothing is estimated in advance.

Count at day 180Now groupLater group
InvitedNot yet collectedNot yet collected
Attended (the later group, after day 90)Not yet collectedNot yet collected
CEO agreed in writingNot yet collectedNot yet collected
Introductions submittedNot yet collectedNot yet collected
Qualified introductionsNot yet collectedNot yet collected
Closed or duplicateNot yet collectedNot yet collected
Side-effect count (next section)Not yet collectedNot yet collected

Where members are partners in their own right, you cannot see their dashboards. Ask for counts and copied stage words at day 180, record who did not answer, and report non-response beside the counts rather than filling the gaps.

Side effects worth more attention than the headline

Unwanted effectSignalTarget
A CEO learned of the introduction after SourceX didThe CEO's own reply, or SourceX telling youZero
PressureA CEO complains about being pushed or asked repeatedlyZero
A promiseA CEO says they were told the company qualifies, or that SourceX vouches for the hostZero
Records offeredAn attendee receives or forwards files, samples or loginsZero
DuplicatesIntroductions of companies already known to SourceXSimilar in both groups; a jump in the now group means attendees rushed familiar names
SpilloverLater-group invitees who saw the slides before day 91Reported, so the gap can be read as a floor

Information an attendee holds through a board or advisory seat may prompt one question to that company's CEO and nothing more. If the session gives anyone the idea of using board knowledge to suggest a different company, stop and rewrite it.

Floors, length and stop rules

Introductions are rare, so small groups decide nothing. Publish per-10 rates only when each group holds at least 20 invitees; below that, publish counts. Several runs of the same session, same draw rule and same read date may be pooled.

Stop rules.

  • An introduction reaches SourceX before its CEO agreed: pause new submissions from both groups and fix the consent part of the session.
  • Anyone collects or forwards company records because of the session: stop, and fix that slide before the later group attends.
  • A CEO reports pressure or a promise: pause and rewrite the session before day 91.
  • SourceX changes the terms or who-qualifies before the later session: teach the current version, note the change and treat the two groups as different versions.
  • Never end the count early because the now group looks ahead. Run to day 180.

Reading the difference between the groups

Before the draw, write down the smallest gap that would change your plans, for example one more qualified introduction per 10 invitees, and state uncertainty as a range.

Result at day 180Decision
Now group ahead on qualified introductions by more than your gap, side effects at targetKeep the workshop and run it for each new cohort
Now group ahead on introductions submitted, level on qualified onesThe session drives volume, not fit: rework the fit and consent parts
No clear gap either wayThe session is not what moves introductions; test a lighter driver, such as a one-page reminder or a short follow-up call
Any side effect above targetFix the session first; the comparison waits

The workshop's knowledge effect can be tested separately with the onboarding scenario cards; this design deliberately measures only what people did.

Where a workshop comparison misleads

  • Small numbers. One busy introducer can swing a group. Name outliers in the report instead of deleting them.
  • Spillover. Shared slides shrink the gap, so a small difference may understate the session's effect.
  • Facilitator effects. A charismatic presenter is part of the treatment. Running the later session with the same person keeps it constant.
  • Self-reported asks. The "asked a CEO" stage relies on invitees' word; the primary measure does not.
  • Review is SourceX's. A qualified introduction is a verified application still open, not an accepted company or a payable reward; a lead, meeting or signed agreement alone earns nothing payable. For running the session itself, the chamber workshop design shows a question-first format.

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 the draw, register as a partner and sign the Channel Partner Agreement, build the session's fit slide from the current who qualifies page and record the program terms version both groups were taught. More test designs are collected in the guides hub.

  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

Is it fair to make half the invitees wait?

Everyone gets the same session; the later group gets it about three months on. Nothing about SourceX is withheld in the meantime: the later group keeps the standard who-qualifies and terms links, exactly as before.

Why count invitees who never came?

Because the people who turn up are the ones most likely to introduce companies anyway. Comparing attendees with absentees measures their enthusiasm, not the workshop. Comparing the whole now group with the whole later group does not have that problem.

Should the workshop ask each attendee to bring one company?

No. A target turns the session into pressure on CEOs and fills the count with introductions nobody would otherwise make. The design measures what people choose to do, so it never sets quotas.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  4. kirkpatrickpartners.com/wp-content/uploads/2024/04/an-introduction-t…

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