# Data introduction time study: a diary method | SourceX

Canonical: https://refer.sourcex.si/guides/the-time-cost-of-a-data-introduction-a-platform-team-study
Last updated: 2026-11-05

That nobody has measured it, and that estimates made from memory will not answer it. Recall turns a scattered week of short calls and abandoned checks into a tidy guess. This study design has every platform team member, and every outside relationship owner who agrees, log each episode of introduction work on the day it happens, coded by activity and by company, including work on companies that never qualify. Hours per verified application are reported only after the cohort closes. No diaries have been kept and no results exist.

The design starts where a planning model stops. [The zero-revenue hours model](/guides/is-data-referral-work-worth-a-platform-team-s-time) asks whether this work deserves a platform team's time and runs on assumed hours per stage that it tells readers to replace with their own logs. This page is the log: a way to measure where the hours actually go, who spends them and how many land on companies that never reach an application.

## Why the question needs a diary

Effort on an introduction comes in small, scattered pieces: twelve minutes checking what you already know about a company, a call to the LP who knows its CEO, an email that goes unanswered, a second call a month later. Asked at the end of a quarter, people remember the meetings and forget the fragments, and they forget the companies they dropped.

Government time-use surveys face a version of the same problem. The Bureau of Labor Statistics' American Time Use Survey asks respondents to recall their activities over a full 24-hour day, and its user guide says: "Interviewers are trained to ensure that respondents report activities (and their durations) actually done on the previous (diary) day, not activities done on a 'usual' day." Each reported activity is then coded against the survey's activity lexicon. This design borrows both ideas: same-day logging of what actually happened, and a fixed activity codebook applied to every line.

It is also not a case diary. [The cost of an unqualified introduction](/guides/the-cost-of-an-unqualified-introduction) follows single introductions and the minutes a partner, an owner and a reviewer spend on each, to price an introduction that should never have been made. This study follows a team's working days instead, so it captures the hours that belong to no single company (setup, compliance, tracking) and the companies dropped before anyone was asked, and it divides by what the team produced.

It measures effort, not elapsed time. How many calendar days pass between stages is a separate question, covered by [the stage duration benchmark](/guides/data-referral-stage-duration-benchmark) and, for advisory firms, by [the handoff benchmark](/guides/the-referral-handoff-benchmark-for-advisory-firms).

## What each diary term means

| Term | Meaning in this study |
|---|---|
| Episode | A continuous block of at least five minutes spent on one company, or on one overhead task |
| Company code | A label the team assigns to each company it discusses; the key stays with the team |
| Activity code | One code from the codebook below, chosen for each episode |
| Borrowed time | Episodes logged by consenting relationship owners outside the team, such as an LP or a portfolio founder |
| Terminal status | Where each company ended by the cutoff: not asked, CEO declined, no reply, duplicate, verified application, a later stage SourceX reports, or still open |
| Hours per verified application | Every logged team hour on companies in the cohort, divided by the number of those companies that submitted a verified application |

The last definition is what keeps failures in the count. Hours spent on a company that later failed the size check, or whose CEO said no, stay in the numerator. Dividing only the hours spent on successful companies by their number would make the work look cheaper than it is.

## The time-diary study instrument

**The diary line.** One line per episode, entered before the end of the working day:

| Field | Entry |
|---|---|
| Date | The day the episode happened |
| Duration | In five-minute units |
| Person | A role code, such as platform lead or analyst |
| Company | A company code, or "overhead" |
| Activity | One code from the codebook |
| With whom | Alone, relationship owner, CEO or the CEO's office, SourceX, colleague |
| Channel | Call, meeting, email or message, document |
| Note | Ten words at most, with no client facts and no names |

**The activity codebook.**

| Code | Activity | Example |
|---|---|---|
| SU | Program setup | Reading the terms and the Channel Partner Agreement, signing it, checking fund policy |
| DC | Disclosure and compliance | Drafting a disclosure, answering a compliance officer |
| DK | Desk check | Matching what the team already knows against the published fit facts |
| RL | Finding the relationship | Working out who can ask the CEO |
| RO | Relationship owner | Briefing the LP, founder or executive who holds the CEO relationship |
| CE | CEO conversation | The call or meeting in which the CEO hears the idea, or arranging it |
| IN | Introduction | Writing and submitting the introduction once the CEO agrees |
| FU | Follow-up | Answering questions from the company or SourceX after submission |
| TR | Tracking | Checking status and reporting internally |
| CL | Closing a row | Recording a decline, a no-fit or a decision not to ask |
| OH | Team overhead | Training colleagues, team meetings about the program |

Codes DK and RL cover work the team does with knowledge it already holds. SourceX's screening guidance says the fit questions are answered from conversations, never from files, samples or logins, and nobody in the study handles company records.

**The schedule.** Every working day is a diary day for weeks one to eight, when setup and first asks happen. From week nine to week 26, two working days per person per week are drawn at random in advance, and those days are logged in full; their totals are scaled up by the sampling fraction. A day with no episodes is logged as zero, because a missing day and a zero day mean different things. At each week's end, each person checks the diary against their own calendar and sent messages, which nobody else sees, and adds any missed episode marked as late.

**The baseline estimate.** Before logging starts, each person writes down how many hours they expect one introduction to take. It is sealed and opened only after the cohort closes, to compare with the diary.

**Borrowed time.** Relationship owners outside the team who consent log only episodes about cohort companies, through a two-field form: duration and activity code. Where they decline, the team records the episode as having happened, with duration unknown.

## Sample, consent and privacy

- **Teams.** At least five platform teams, from different funds, each with every member logging. One team measures one team's habits.
- **Cohort.** Every company a team first discusses in weeks one to twelve. Each is followed until it reaches a terminal status or until 180 days after its first logged episode, whichever comes first.
- **Consent.** Each person consents before logging and may stop at any time; the rules for what happens to lines already logged are written down in advance.
- **Privacy.** Diaries hold codes, durations and activity labels only. No conversation content, no company names, no CEO names. Each team keeps its own key, and pooled analysis uses codes alone.
- **SourceX's role.** None. The study is run by the teams that take part, and nothing about any company passes to SourceX through it.

## Analysis and how results will be reported

The analysis is descriptive. Planned outputs, fixed now:

1. Total team hours by activity code, and the share of all hours each code takes.
2. Hours per company discussed, per CEO asked, per introduction submitted and per verified application, each with every logged hour in the numerator.
3. The share of hours spent on companies whose terminal status fell short of a verified application.
4. Borrowed hours, reported separately from team hours and never added to them.
5. The distribution across teams: median, quartiles and range, never a single average.
6. Sealed estimates against diary results, person by person.

Release rules: nothing is published until the last cohort company reaches a terminal status or its 180 days pass. Cross-team figures appear only when at least five teams complete the study. A figure resting on fewer than ten companies is shown as "under 10". Terminal statuses come from what partners can see, which under section 4.6 of the sample Channel Partner Agreement is generic stages or reference codes. No team or fund is named.

Differences between teams will be described, not explained. A team with fewer hours per verified application may have a portfolio of larger, older companies rather than a better process.

## Counting a dead end (Illustrative)

Illustrative. One person's invented week; codes and companies are labels only.

| Day | Minutes | Company | Code | Terminal status later |
|---|---|---|---|---|
| Monday | 25 | C-07 | DK | Failed the size check; never asked |
| Monday | 15 | Overhead | DC | Not a company |
| Tuesday | 40 | C-11 | RO | Verified application |
| Thursday | 30 | C-11 | CE | Verified application |
| Friday | 20 | C-11 | IN | Verified application |

If this were the whole cohort, one company reached a verified application and 115 minutes were spent on companies: hours per verified application would count the 25 minutes on C-07 alongside the 90 on C-11. The 15 minutes coded DC sit in the overhead line, reported on their own. That bookkeeping is the whole point: the minutes on C-07 are part of what an application costs.

## What the diaries could overturn

| If the diaries show | The reading |
|---|---|
| Most hours fall in DK and RL, before any CEO hears the idea | The cost sits in finding the right companies; better screening matters more than better messaging |
| Borrowed hours rival team hours | Relationship owners carry the program, and their goodwill is the scarce input |
| Most hours land on companies that never apply | Effort is going to rows a desk check could have closed earlier |
| Sealed estimates sit far from diary totals | Planning models built on estimates, including the hour assumptions in planning pages, need logged data before anyone relies on them |
| Teams with similar portfolios differ widely | Process differences are worth a separate, designed comparison |

How the measured hours should shape a team's calendar is the subject of [allocating partner manager time across funds](/guides/how-to-allocate-partner-manager-time-across-funds), and how the work compares with other founder services is weighed in [comparing data referrals with other platform benefits](/guides/how-to-compare-data-referrals-with-other-platform-benefits).

## Where a diary undercounts or distorts

- **Logging burden.** Diaries cost time and people skip lines on busy days; the end-of-week calendar check narrows that gap without closing it.
- **Logging changes behavior.** People who record their time may work differently while they do.
- **Sampled days.** Scaling up from two random days a week adds error to later-stage totals.
- **Volunteer teams.** Teams that agree to log may already be the most organized.
- **Short horizon for money.** A reward becomes payable only after the Acquisition Partner's final written acceptance and completed handoff, and "a lead, meeting or signed agreement alone does not earn a payable reward," so the study says nothing about what the hours earn.
- **Coarse endings.** Generic stages may hide why a company stopped.

**Methods note.** The design draws on SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04) and who-qualifies page, both read on 2026-10-28, on the sample Channel Partner Agreement, and on the BLS American Time Use Survey user's guide for same-day logging and fixed activity coding. It measures team and borrowed hours by activity and company outcome. It does not measure elapsed time between stages, record quality, demand, licensing outcomes or rewards. No diaries have been kept and no figures exist.

## 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.

When a diary-week row turns into a CEO who wants the conversation, the person submitting signs the Channel Partner Agreement and [registers](/register) first, confirms the fit facts against [who qualifies](/who-qualifies) and keeps the [terms](/terms) to hand; the [guides hub](/guides) holds the other platform research designs.

Measuring a team's hours is a referral-program question; whether to invest in SourceX is a separate one, and investor materials for that are available on request from 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://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://www.bls.gov/tus/atususersguide.pdf
- https://sourcex.si/investors
