The original brief called this page "the referral friction map". No map exists yet; what follows is the method that would draw one.
Why the study starts at a yes and stops at day 90
Messages that never earn a reply belong to a different instrument, built for owners who left an offer unanswered. This study begins where interest is on the record: a CEO's written agreement to a conversation, followed by the partner's dated introduction. Starting there makes the denominator countable and consent straightforward, because every company in it has already said it wants to hear more.
It ends at a verified application or at day 90 after the introduction, whichever comes first. Ninety days is the window SourceX's terms use: the first valid introduction "receives credit when that company submits a verified application", within the attribution window (section 2). One last read at day 120 records any later application as an outcome for the company, though it would not be credited.
Six stages, each opened by a dated event
| Stage | Opens when | Recorded by |
|---|---|---|
| S0 Yes | The CEO agrees in writing and the partner submits the introduction | Partner log |
| S1 First look | The company's contact first reads SourceX's public pages or writes to SourceX | Journey log |
| S2 Inside check | The CEO brings in anyone else: finance, operations, counsel, the board | Journey log |
| S3 Started | The company begins SourceX's application | Journey log |
| S4 Submitted | The company submits the application | Journey log |
| S5 Verified | SourceX verifies the application | The partner dashboard's stage, or the company's report |
Four endings other than S5 stay in every count: paused (the contact says the company will resume), stopped (the company decides not to go on), out of fit (the company concludes it falls outside SourceX's screen) and silent (no entries or replies for 30 days). Out of fit is not friction. A company that finds it is too small, or that its records belong to its clients, has reached a correct answer early.
A link click is never a stage. It shows nothing about what a company decided, and SourceX's terms say a click alone does not decide credit.
The friction taxonomy: six families, twelve codes
| Code | Family | What the contact describes | Default verdict | Who could act on it |
|---|---|---|---|---|
| U1 | Understanding | Unclear what SourceX does or what the company is being asked to do | Avoidable | The partner's wording; SourceX's pages |
| U2 | Understanding | Unclear who decides, who pays whom, or whether the partner's reward reduces the company's payout | Avoidable | The partner, quoting the terms |
| E1 | Effort | Time spent assembling facts the application asks for, such as peak headcount or years of records | Partly protective | The company |
| E2 | Effort | Steps, logins or forms that slowed the contact | Avoidable | SourceX |
| A1 | Authority | The CEO was unavailable, or the contact was unsure whether to proceed | Protective while the CEO has not decided | The company |
| A2 | Authority | A control question: a parent, an acquirer, a board or a formal process | Protective | The company and its counsel |
| R1 | Rights | Doubt whether records are the company's own or its clients' | Protective | The company's counsel; SourceX's review |
| R2 | Rights | Confidentiality or privacy concerns about the records | Protective | The company's counsel; SourceX's review |
| T1 | Trust | Doubt about SourceX or about the partner's motive | Avoidable when it comes from missing information | The partner; SourceX |
| T2 | Trust | Concern about how licensed data would be used | Protective | SourceX's published materials |
| C1 | Context | A competing event: an audit, a migration, a sale, a busy season | Record only | Nobody |
| C2 | Context | Changed circumstances: the contact left, the company was acquired | Record only | Nobody |
The verdict column is the point of the taxonomy. Protective friction does work that ought to happen: counsel checking whether service records contain client material, or a CEO taking a week to decide. Removing it to lift a completion figure would produce applications that fail in review or should never have been filed. Avoidable friction is confusion or effort that serves nobody, such as a finance lead unsure whether the partner's reward comes out of the company's payment, when the terms answer that in one sentence: the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation." Two coders assign the verdict case by case; the default is only a starting point.
The journey study protocol
| Instrument | Completed by | When | Never collected |
|---|---|---|---|
| Partner log | The introducing partner | At the introduction and whenever a status changes | Anything from the company's records |
| Journey log | The company's named contact, with the CEO's consent | A two-minute entry at each stage event, plus a weekly prompt for 90 days | Records, samples, system contents, figures |
| Exit interview | The contact or the CEO | Within two weeks of a stop, or at day 90 | Anything the company has not chosen to say |
| Stage dates | SourceX, if it runs the study | From its own dated records, reported in aggregate | Other partners' records |
A journey log entry has six fields: the date, the stage, what happened in one sentence, any obstacle in the contact's own words, the roles involved, and whether it was resolved. The format follows the diary study, which Nielsen Norman Group describes as a qualitative way to gather behavior over time and in context, with participants reporting as things happen over days to a month or more (our paraphrase). Here the diary covers one decision for 90 days.
The exit interview asks five questions, in order: "Walk me through what happened after your CEO agreed to talk." "Where did it slow down?" "Was there a point where you nearly stopped, and what decided it?" "What did you need that you didn't have?" "Is there anything you would want the person who introduced you to do differently?"
Enrollment and consent. Every introduction made by participating partners during one enrollment quarter is eligible. The CEO agrees for the company and the contact agrees personally; either may stop at any time; partners see only aggregate results; and taking part has no bearing on SourceX's review. Companies that decline to be studied are counted, never followed.
Measures, with every company kept in the denominator
- Completion. The GOV.UK Service Manual divides completed transactions by all transactions started, partly completed and failed ones included (our paraphrase). Here: verified applications within 90 days, divided by every company enrolled at S0, including the paused, stopped, out-of-fit, silent and withdrawn.
- Stage progression. The share moving from each stage to the next, with every company that entered the stage in the denominator.
- Time between stages. Companies still inside a stage at day 90 are counted as open at that point, never dropped, as in the stage-duration benchmark.
- Friction. Codes by stage, by family and by verdict, and how often each appears among companies that reached S5 compared with those that stopped.
Reporting rules. Every table shows the number enrolled. Cells with fewer than five companies are folded into "other". Anything not in the dated pre-registration is labeled exploratory. A code reported more often by companies that stopped is associated with stopping, nothing more: stoppers may simply have more to say. A causal claim needs a test that changes one thing at a time.
One journey logged, one that stopped (Illustrative)
Illustrative. Generic companies and invented days; no outcome is implied for any real company.
Case 1, a 210-person facilities services company.
| Day | Stage | Log entry | Code and verdict |
|---|---|---|---|
| 0 | S0 Yes | The CEO agrees; the partner submits the introduction | None |
| 5 | S1 First look | The contact reads SourceX's terms and screening page | None |
| 8 | S2 Inside check | The finance lead asks whether the partner's reward comes out of the company's payment | U2, avoidable |
| 19 | S2 Inside check | Counsel asks whether service records include client material | R1, protective |
| 37 | S3 Started | Application begun | None |
| 41 | S3 Started | The contact is unsure whether contractors count toward headcount | U1, avoidable |
| 49 | S4 Submitted | Application submitted | None |
| 60 | S5 Verified | Verification shown on the dashboard | None |
Two of the three codes were avoidable and could be answered from published pages: SourceX's terms on who pays, and its screening page, which excludes contractors from the headcount. The rights question was protective and took eleven days; a partner should expect it, not shorten it.
Case 2, a 160-person distributor. The CEO agrees on day 0 and the contact reads SourceX's pages on day 12. On day 23 the owner announces a sale process (C1), and the contact notes that the buyer's CEO will decide once the deal closes (A2, protective), which matches SourceX's screening page. The company stops on day 30. The exit interview confirms nothing in the introduction would have changed the outcome.
What a partner could change because of a result
Each row is conditional. No result exists.
| If the study finds | A partner might | A partner should never |
|---|---|---|
| Avoidable understanding codes clustered at S1 and S2 | Rewrite the introduction and resource page, then test the rewrite | Answer with figures or promises about review |
| Avoidable effort codes at S3 | Pass the pattern to SourceX | Fill in or prepare the application for the company |
| Protective rights or authority codes | Say early that rights are reviewed and that the CEO decides | Treat them as obstacles to argue away |
| Context codes | Wait, and note the date to revisit | Chase a company that stopped for its own reasons |
Testing the application path before sending more companies to it is a separate exercise, set out in testing the referral form before sending more traffic.
Which companies enter the study
Only companies that already passed the partner's screen against SourceX's published profile: at least 50 full-time staff at their high point, contractors left out; years of records they produced themselves; the right to license that material; and a CEO who asked for the conversation. Whether the records match current demand, and whether customer contracts allow licensing, stay unknown until SourceX's review, and the study does not try to answer either. The partner never sees the company's records: the how it works page says partners need not export, upload or describe confidential material, and the journey log describes events, never contents. Partners who enroll companies have signed the Channel Partner Agreement before making any introduction.
Where the friction study can mislead
- Logging changes the journey. A contact who writes entries may move faster than one who does not.
- Missed weeks. Weekly prompts reduce gaps; missing weeks are shown as missing, never filled.
- Who agrees to be studied. CEOs willing to be followed may differ from those who decline, so the decline count is published beside the results.
- One process, one period. If SourceX's application changes during enrollment, the change is dated and results are split at that date.
- Context that wording cannot touch. In case 2 the company stopped for a sale; counting it as friction to fix would mislead.
How this study joins a yearly census of outcomes is described in the annual research blueprint, and what may be cited about results in the meantime in the partner results research guide. More designs are in the guides hub.
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.
If your next introductions are the ones you would study, screen each company against who qualifies, read the program terms so you can answer who pays whom in one sentence, and register as a partner before the first CEO's yes.