The study is for a partner research lead at a network of accounting, consulting, IT services or legal firms who wants to know where introductions leak between a client conversation and an application, without ranking firms on guesses.
Where an advisory firm's handoff can break
Where an advisory firm runs one partner account for the whole firm, the person who knows the CEO and the person who submits are often different people. An engagement lead hears the CEO's interest; a practice leader or business development manager, who signed the Channel Partner Agreement, submits the introduction from SourceX's dashboard; then the company applies itself. That gives three seams: lead to submitter, submitter to SourceX, and submission to the company's own application.
Patient safety work offers a parallel. AHRQ's patient safety primer on handoffs describes one provider updating another in order to hand over responsibility, treats handoffs as a known source of error, and notes that guidance centers on standardizing the process with accurate written information (our paraphrase). An advisory referral carries no clinical risk, but the borrowed point holds: responsibility moves, and facts drop out where it moves.
The program sets what a handoff must preserve. Section 2 of the terms decides attribution from dated records, including written introduction evidence, and credits the first valid introduction only when the company submits a verified application inside the 90-day window. A handoff that loses the date of the CEO's yes, or reaches SourceX before the CEO knows, damages the very record credit depends on, and SourceX's fit guidance warns that a company whose decision maker never heard about its own introduction is seldom a fit.
| Term | Definition used in the study |
|---|---|
| Start event | The CEO's written yes to an introduction, with its date |
| Submission | The firm's introduction through SourceX's dashboard |
| Application | The company's own application, as the dashboard stage shows it |
| Carry items | Facts the handoff must hold, listed in the methodology |
| Restraint items | Material the handoff must never hold, listed in the methodology |
| Peer set | Firms of the same type and size band, compared only with each other |
The peer-comparable handoff methodology
Peer sets. Firms are grouped by type (accounting and tax, management consulting, IT and managed services, legal) and by their own headcount band. A set is read only when five or more firms each contribute at least three handoffs in the study period. Smaller sets are counted and reported as "too few", never merged into a neighboring set to make the numbers work.
Measures for every handoff.
| Measure | Definition | Source record | Reported as |
|---|---|---|---|
| Lead time | Days from the CEO's written yes to the firm's submission | The firm's handoff log and dashboard date | Median and range per firm, then per set |
| Company time | Days from submission to the company's application, within 90 days | Dashboard stage dates | Median per firm; open cases counted as open |
| Carry check | All five carry items present: CEO named; dated written yes; how and when the CEO heard of SourceX; the reward disclosed to the CEO; one firm contact named for the CEO | The handoff log | Share of handoffs complete |
| Restraint check | All four restraint items absent: company records or samples; figures from engagement work; any promise of fit; information about another client | The handoff log, reviewed by a second person at the firm | Count of flags, never averaged away |
| Outcome | Verified application inside the window: yes, no or still open | Dashboard stage | Verified applications per CEO yes |
The restraint check matters as much as speed. SourceX's process page says partners do not need to export, upload or describe confidential records, and advisory firms hold more client material than most introducers. A handoff that forwards a client's figures to speed things up fails the check however fast it was.
Readings. Each firm's measures roll up to firm-level medians and shares. Each peer set reports the median and interquartile range of those firm-level readings. A firm sees its own position against its set privately; no published table names a firm or lets a reader work out which firm a row belongs to.
The handoff log and the CEO check-back
Two instruments feed the measures, and both stay small on purpose.
- The handoff log, one row per CEO yes, kept by the firm: the dates of the yes, the submission and any application; the five carry items ticked; the four restraint items ticked by a second person; the relationship type (current client, former client, network contact). It holds no client name once it leaves the firm; rows are coded before they reach the study.
- The CEO check-back, optional, two questions sent by the firm a week after submission: "Did you know about the introduction before we sent it?" and "Do you know whom to contact at our firm?" Answers are recorded as yes, no or no reply, and a CEO who prefers not to answer is never asked again.
For what the packet itself should contain, the handoff checklist after a company accepts already sets out the parcels; this study measures whether firms actually carry them, not how to build them.
Sampling frame, consent and the cases that went nowhere
- Frame: every CEO yes recorded by a participating firm during two study quarters, including yeses that never became a submission.
- Kept in the count: CEOs who changed their mind, companies that never applied, introductions SourceX treated as duplicates under section 3, and handoffs still open on the read date.
- Consent: each firm agrees in writing, and a firm subject to professional rules on referral arrangements settles those with its own adviser before joining; the study records only that the firm has done so.
- Exchange: firms contribute exactly the fields they receive back as comparisons. APQC's discussion of its benchmarking code puts the principle plainly: "Don't ask for information you aren't willing to share."
- Read date: 120 days after the last CEO yes in the frame, so every window has closed.
Readings stay descriptive
A peer set where faster submission goes with more verified applications shows an association among those firms. It does not show that speed caused the applications: client mix, relationship type and the CEO's own pace differ between firms. The report therefore breaks every reading out by relationship type and states, beside each one, that it is descriptive. Company time is reported separately from lead time because it belongs to the company; a firm cannot shorten it without pressing the CEO, and the study does not reward that.
The reporting template, empty until peer sets fill
| Measure | Peer set median | Interquartile range | Firms | Handoffs |
|---|---|---|---|---|
| Lead time | Not yet read | Not yet read | Not yet read | Not yet read |
| Company time | Not yet read | Not yet read | Not yet read | Not yet read |
| Carry check complete | Not yet read | Not yet read | Not yet read | Not yet read |
| Restraint flags per 10 handoffs | Not yet read | Not yet read | Not yet read | Not yet read |
| Verified applications per CEO yes | Not yet read | Not yet read | Not yet read | Not yet read |
| CEO knew before submission | Not yet read | Not yet read | Not yet read | Not yet read |
Released with the readings: the peer-set definitions, the log template, counts of firms and sets refused a reading, every restraint flag by type and the handoffs still open on the read date.
What a firm can do before any reading exists
Keep the handoff log for your own firm from today; it costs a few minutes per CEO and gives you your own lead time and carry rate. Put the CEO's written yes first in every handoff and make sure one named person at the firm owns the next step. Where referral work sits inside an engagement, fitting it into advisory work shows where the question belongs in the year. And before asking a client CEO for anything more, checking the company's satisfaction comes first. Firms that also score individual introducers can set this study's measures beside a scorecard that includes company feedback.
Where a handoff comparison misleads
- Speed can be gamed. A firm that submits before the CEO is ready improves its lead time and harms the introduction; the CEO check-back exists to catch this.
- Small sets reveal firms. Five firms in one city and one type can still be recognized; sets are defined broadly enough that they cannot.
- Volunteers differ. Firms that agree to be compared may already hand off well.
- Company time is not the firm's. It is reported for context, never as a firm's score.
- SourceX's review is excluded. The handoff ends at the company's application or day 90, so nothing here describes SourceX's own steps.
- Programs move. Whether a company's records fit a current program is settled in SourceX's review and can change during the study; outcomes are read with that in mind.
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.
A firm that wants its handoffs to be measurable later can register, have whoever submits sign the Channel Partner Agreement first, screen each client company against who qualifies, read the program terms on dated records, and start a handoff log with the next CEO yes; other designs are in the guides hub.