The time cost of a data introduction: a platform team time-diary study that logs each episode of work on the day it happens, keeps the hours spent on companies that never qualify in the total and publishes no figures until the cohort closes

Short answer

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.

Visual briefFull-size diagram
An Illustrative one-week diary grid for one platform team member, Monday to Friday, with short colored blocks for screening, relationship owner, CEO call, introduction and overhead; one Monday block for a company that later fails the size check is outlined in orange and labeled still counted; a Wednesday column reads 0 min; a panel on the right reads hours per verified application equals all logged hours divided by verified applications, not yet measured, above a legend of the five block colors.
Illustrative diary week. Blocks and codes follow the instrument on this page; no diaries have been kept.

The design starts where a planning model stops. The zero-revenue hours model 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 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 and, for advisory firms, by the handoff benchmark.

What each diary term means

TermMeaning in this study
EpisodeA continuous block of at least five minutes spent on one company, or on one overhead task
Company codeA label the team assigns to each company it discusses; the key stays with the team
Activity codeOne code from the codebook below, chosen for each episode
Borrowed timeEpisodes logged by consenting relationship owners outside the team, such as an LP or a portfolio founder
Terminal statusWhere 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 applicationEvery 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:

FieldEntry
DateThe day the episode happened
DurationIn five-minute units
PersonA role code, such as platform lead or analyst
CompanyA company code, or "overhead"
ActivityOne code from the codebook
With whomAlone, relationship owner, CEO or the CEO's office, SourceX, colleague
ChannelCall, meeting, email or message, document
NoteTen words at most, with no client facts and no names

The activity codebook.

CodeActivityExample
SUProgram setupReading the terms and the Channel Partner Agreement, signing it, checking fund policy
DCDisclosure and complianceDrafting a disclosure, answering a compliance officer
DKDesk checkMatching what the team already knows against the published fit facts
RLFinding the relationshipWorking out who can ask the CEO
RORelationship ownerBriefing the LP, founder or executive who holds the CEO relationship
CECEO conversationThe call or meeting in which the CEO hears the idea, or arranging it
INIntroductionWriting and submitting the introduction once the CEO agrees
FUFollow-upAnswering questions from the company or SourceX after submission
TRTrackingChecking status and reporting internally
CLClosing a rowRecording a decline, a no-fit or a decision not to ask
OHTeam overheadTraining 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.

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

DayMinutesCompanyCodeTerminal status later
Monday25C-07DKFailed the size check; never asked
Monday15OverheadDCNot a company
Tuesday40C-11ROVerified application
Thursday30C-11CEVerified application
Friday20C-11INVerified 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 showThe reading
Most hours fall in DK and RL, before any CEO hears the ideaThe cost sits in finding the right companies; better screening matters more than better messaging
Borrowed hours rival team hoursRelationship owners carry the program, and their goodwill is the scarce input
Most hours land on companies that never applyEffort is going to rows a desk check could have closed earlier
Sealed estimates sit far from diary totalsPlanning models built on estimates, including the hour assumptions in planning pages, need logged data before anyone relies on them
Teams with similar portfolios differ widelyProcess 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, and how the work compares with other founder services is weighed in comparing 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 first, confirms the fit facts against who qualifies and keeps the terms to hand; the guides hub 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.

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.

  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

Why not ask each team member for a monthly estimate instead?

Estimates from memory smooth over the short calls and dead ends that make up much of this work. The design does collect one estimate from each person before the study starts, but only to compare it with the diary afterwards.

Do diary notes ever describe what a CEO said?

No. A diary line records how long, with whom, through which channel and under which activity code. Conversation content, company names and client facts stay out, and the key that links company codes to companies never leaves the team that holds it.

Does the study count any money?

No. It measures hours only. Rewards depend on licensing deals that complete long after most of the logged work, so they belong to a different question.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  4. bls.gov/tus/atususersguide.pdf
  5. sourcex.si/investors

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