# Data introduction friction index: what to measure | SourceX

Canonical: https://refer.sourcex.si/guides/the-data-introduction-friction-index-what-it-should-measure
Last updated: 2026-11-05

A data introduction friction index should measure what makes an introduction harder without showing up on a stage clock: how many people must agree before the CEO hears the request, how many fit facts are unknown at handoff, how many rights questions open, how often the authorized contact changes, how much rework the introduction needs and how often the company goes quiet. Elapsed time is already handled by stage-duration benchmarks. No index values exist yet, so publish the specification, weights and a sensitivity test first, and keep declined introductions in.

For a platform research director, the index answers a practical question the stage clock cannot: which friction can our network remove, and which is built into the relationship path?

## Why a second number needs a reason to exist

The live [stage duration benchmark](/guides/data-referral-stage-duration-benchmark) already measures how long each stage takes and treats open cases as censored. A friction index earns its place only if it adds dimensions that time cannot explain. Two introductions can both take 90 days, one because the CEO was on leave and one because three intermediaries had to agree and a rights question opened twice. The clock scores them the same; the network's options are very different.

| Type | Statement | Basis |
|---|---|---|
| Program fact | However much friction an introduction carries, credit follows the clock: the earliest valid one inside the 90-day attribution window takes it once the company files a verified application, and competing introductions go to duplicate review | SourceX terms, version 2026-10-22.2, since replaced by version 2026-11-04, checked 2026-10-26 |
| Program fact | Rights to license means the company can license the material without breaching client confidentiality, employee privacy or third-party contracts | SourceX who-qualifies page |
| Conditional | Whether a scored introduction is accepted or licenses records | SourceX review and a signed agreement |
| Proposal | Six non-time dimensions, scored 0 to 3 each, describe introduction friction well enough to compare relationship paths | This page's specification; untested |

## Definitions

| Term | Meaning here |
|---|---|
| Episode | One attempt to introduce one company, from the first ask of a relationship owner to a final status or the cutoff |
| Pre-handoff episode | An episode that stopped before anything was submitted, for example because an LP principal declined to ask |
| Dimension | One kind of friction, scored 0 to 3 from a written anchor |
| Raw score | The sum of six dimension scores, 0 to 18 |
| Index | The raw score rescaled to 0 to 100 (raw score times 100, divided by 18) |
| Profile | The six dimension scores shown side by side; always published with the index |

## The transparent friction index specification

| Dimension | Phase | 0 | 1 | 2 | 3 | Why time does not capture it |
|---|---|---|---|---|---|---|
| Consent layers | Before handoff | Partner asks the CEO directly | One intermediary | Two intermediaries | Three or more | A long chain can still move quickly |
| Authorization churn | Before handoff | CEO identified and unchanged | CEO identified late | Contact changed once | Changed twice, or no authorizer found | A change can restart work without adding much elapsed time |
| Fact gaps at handoff | Before handoff | All four fit facts known | One unknown | Two unknown | Three or four unknown | Gaps shift work to review rather than delaying the handoff |
| Rights questions | After handoff | None opened | One | Two | Three or more | Questions run in parallel with other work |
| Rework | After handoff | None | One resubmission, correction or duplicate-review event | Two | Three or more | Rework hides inside a stage |
| Silence | Either | No unanswered follow-up | Longest run of 1 to 2 unanswered | 3 to 4 | 5 or more | Silence is a behavior, not a duration |

The four fit facts are the program's: 50+ full-time employees at peak (contractors excluded), a qualifying location, years of the company's own records in a named system, and an authorized contact. Rights questions are counted at metadata level only, by type (client contracts, employee privacy, third-party system terms), never by reading a contract or a record.

**Aggregation.** Equal weights by default, summed and rescaled. The default is a choice, not a finding, so the specification fixes two alternatives in advance for the sensitivity test: double weight on fact gaps and rights questions (the two a partner can most reduce), and a geometric mean that stops a low score on one dimension from offsetting a high score on another.

**Missing values.** A dimension the scorer cannot assess is marked missing, not zero. Episodes with two or more missing dimensions get a profile but no index. The OECD and European Commission handbook on composite indicators says imputation approaches should be considered openly and that extreme values should be examined because they can become unintended benchmarks; one 18-point episode should not set everyone's scale.

## Sample, consent and cutoff

- **Frame.** Every episode a participating partner or platform team starts in a fixed quarter, including pre-handoff episodes. Those never reach SourceX, which is exactly why they need a partner-side log.
- **Consent.** Partners opt in and may withdraw their episodes before aggregation. No company is contacted for the study, and no company, relationship owner or partner is named in any output. No breakdown with fewer than five episodes is published.
- **Cutoff.** All episodes are scored on one date. Open episodes are scored to date and reported in their own column, never mixed with finished ones.
- **Record sources.** Consent layers, fact gaps and silence come from the partner's log; stage and duplicate-review events from the dashboard; rights questions from what the company or SourceX raised with the partner.

## Keep the failures in the denominator

An index computed only on introductions that went well describes the easy paths. Report every episode in the frame under one of five outcomes: stopped before handoff, declined by the company, not a fit after review, still open, or progressed. Then show the index distribution for each outcome. If declined episodes are left out, the index will look low across the board and tell a platform team nothing about where its paths break. The [rejection reasons study](/guides/data-referral-rejection-reasons-study) and the [conversion benchmark](/guides/data-referral-conversion-benchmark) set the same rule for their own measures.

Keep descriptive and causal claims apart. "Episodes with three or more consent layers more often stopped before handoff" is a description. "Consent layers cause introductions to fail" needs a comparison the frame cannot provide, because long chains also tend to reach less familiar companies.

## Two episodes scored (Illustrative)

Illustrative. Generic companies, invented scores, no results implied.

| Dimension | A: 210-person engineering firm, partner knows the CEO | B: 650-person logistics group, reached through an LP principal and a COO |
|---|---|---|
| Consent layers | 0 | 2 |
| Authorization churn | 0 | 2 (the COO left mid-episode) |
| Fact gaps at handoff | 0 | 2 |
| Rights questions | 1 | 2 |
| Rework | 0 | 1 |
| Silence | 0 | 2 |
| Raw score | 1 of 18 | 11 of 18 |
| Index | 6 | 61 |
| Status at cutoff | Not a fit: most project material belonged to clients | Still open |

Episode A is the counterexample that keeps the index honest: almost no friction, and still not a fit. A smooth path says nothing about whether the records belong to the company. Episode B is high-friction but alive, and its profile tells the platform team where the cost sits: the path, not the facts. Whether to approach through a sponsor or directly is weighed in [introducing through a sponsor or directly to the CEO](/compare/introduce-through-sponsor-or-directly-to-ceo).

Under the double-weight alternative, A scores 8 and B scores 63 (raw 2 and 15 of 24). The order holds, which is what the sensitivity test looks for across the whole frame, not in two rows.

## What must hold before any score is published

1. **Inter-rater agreement.** Two people score the same 20 episodes from the log without conferring; any dimension with poor agreement is rewritten before use.
2. **Weight stability.** Rankings of relationship paths under the default and both alternatives are compared; if they reorder, publish the profiles and no single index.
3. **A plain association check.** Whether higher scores go with episodes stopping earlier, reported as counts by outcome, with no causal language.
4. **A dated protocol.** The anchors, weights and frame are published before scoring starts; changes are logged as deviations.

**Methods note.** The specification draws on the program's fit criteria and attribution rules (SourceX terms and who-qualifies page) and on the OECD and Joint Research Centre handbook's construction steps, all checked 2026-10-26. It measures six kinds of introduction friction from partner logs and dashboard stages. It does not measure elapsed time, demand for any company's records, record quality, payout or any reward. For a different index on the main site, one that scores a company's records rather than the introduction, see the [business archive completeness index](https://sourcex.si/insights/business-archive-completeness-index).

## How a friction index goes wrong

- **Gaming and pressure on the numbers.** The World Bank discontinued its Doing Business report in 2021 after reports of data irregularities in the 2018 and 2020 editions led to reviews and audits of the report and its methodology. A partner-scored index faces a milder version of the same pressure: whoever is judged by the score also records it. Independent second scoring is the control.
- **Self-report.** Silence and consent layers come from the partner's own log; partners who forget follow-ups will look smoother than they were.
- **Thin samples.** A platform team may run a few dozen episodes a year. Profiles by relationship path will often fall under the five-episode floor and must be merged.
- **Shifting programs.** The who-qualifies page says criteria differ by program. A change in what SourceX is looking for can raise rights questions or rework across a whole quarter.
- **A single number hides trade-offs.** Two episodes with an index of 50 can have opposite profiles. That is why the profile is always published beside it.

## What the index cannot replace

Scoring friction never substitutes for fit. 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. The company needs 50+ full-time employees at peak, documented operating history, rights to license and a CEO who authorizes the discussion and signs for it; an introduction made without the CEO's knowledge is usually not a fit. Partners and platform teams log categories, not content, and never ask for files, samples or logins. Only SourceX's review settles whether the records match current demand and what any license would include. Whoever submits must have signed the SourceX Channel Partner Agreement, formerly titled the Channel Partner Non-Circumvention and Non-Disclosure Agreement. The [overview for venture platform teams](/for/venture-platform-teams) covers how a platform runs introductions day to day.

## 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 profile shows friction you can remove, such as fact gaps at handoff, fix it on the next introduction: [register for a partner link](/register), confirm the four facts against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you submit.

A friction score describes how your introductions move, not SourceX as an investment, which is a decision of its own; investor materials are available on request through the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://www.oecd.org/en/publications/handbook-on-constructing-composite-indicators-methodology-and-user-guide_9789264043466-en.html
- https://www.worldbank.org/en/news/statement/2021/09/16/world-bank-group-to-discontinue-doing-business-report
- https://sourcex.si/investors
