Where and why company introductions stall: an observational study design with a clock for each stage, a reason codebook applied blind to outcomes and every open case kept in the count, with no ranking of reasons until the cohort closes

Short answer

No published list of stall reasons exists for SourceX introductions, and this page does not offer one. It specifies an observational study that would produce the evidence: a cohort of introductions followed from the CEO's first yes, a clock at each stage that marks a stall only after a fixed number of days without a dated event, a reason codebook applied by two coders who cannot see outcomes, and censoring for introductions still open on the read date. Until the cohort closes and is analysed, there are no results to report.

Visual briefFull-size diagram
Six clock faces in a row, one per stage of an introduction from CEO asked to company signed, each with a shaded arc up to that stage's stall threshold in days, 21, 30, 30, 45, 60 and 90, and a blank tag beneath each reading reason, question mark; a footer says thresholds are study settings, not SourceX deadlines.
Thresholds are parameters the study would fix before the cohort opens. No introduction has been timed or coded.

The study would need data held by SourceX and by partners who consent, linked by introduction. Partners never see company records at any point, and the study adds no follow-up to any company.

A stall is a missing event, not a decision

Introductions end in a handful of ways that someone decides: the CEO says no, SourceX reaches an outcome in review, or the company turns out to be one SourceX already knew, which section 3 of the terms treats as a duplicate credited to no later partner. A stall is different. Nothing is decided; the next dated event simply does not arrive. That makes stalls hard to study from one side. From the partner's inbox, a company waiting on its own counsel looks the same as a company waiting on a SourceX step, and both look like a CEO who has lost interest.

The study therefore defines a stall mechanically and leaves the reason for a separate, evidence-bound step.

TermDefinition used in the study
StageA span between two dated events, listed in the stage table below
StallNo dated event at the current stage for longer than that stage's threshold, with no ending recorded
EndingA CEO's no, a SourceX outcome, a duplicate ruling, or a recorded payout
RestartA dated event that moves a stalled introduction on
CensoredStill open, neither stalled nor ended, on the read date
Reason codeThe category assigned to a stall from the codebook, backed by a named record

For keeping a partner's own records straight in the meantime, the stalled-versus-closed status rules set how a quiet row is labelled; this study uses its own definitions so that both sides' records can be coded the same way.

Six stages, each with its own clock

Thresholds are study settings chosen so stalls can be counted the same way across partners. They are not SourceX service levels or commitments, and the analysis repeats every count with thresholds half as long and half as long again, to show how much the picture depends on them.

StageStarts withEnds withStall thresholdWhose record dates it
1. CEO askedThe partner's dated question to the CEOThe CEO's answer21 daysPartner log
2. CEO agreedThe CEO's written yesThe company's application30 daysPartner log, then SourceX
3. AppliedThe applicationSourceX's verification of it30 daysSourceX
4. VerifiedVerificationA first conversation between SourceX and the company45 daysSourceX
5. In discussionThat conversationThe company decides on scope and terms, or stops60 daysSourceX
6. SignedThe company's signed agreementAcceptance and completed handoff90 daysSourceX

Stage 2 sits inside a published clock of its own: section 2 credits the first valid introduction of a new company within the 90-day attribution window once the company submits a verified application, and the window does not extend. After handoff, the payment stage follows the deadline in section 5, 60 calendar days after the later of the Acquisition Partner's final written acceptance and completed handoff, so it is reported against that published rule rather than a study threshold.

The stall-reason codebook

Every code needs a named, dated record before a coder may use it. Where no record names a reason, the code is unknown, and unknown is expected to be common.

SideCodeDefinitionRecord required
CompanyDeferred to a dated eventThe CEO named an event and a date to wait forThe CEO's own message
CompanySponsor unavailableThe person the CEO named to carry it left or was reassignedA dated note from the company
CompanyRights question openCounsel or a customer contract is being readThe company's statement to SourceX
CompanySilentNo reply after the last dated contactThe last dated contact
PartnerNo owner for the next stepNobody was named to take the next stepThe partner's log shows no named owner
PartnerMessage misreadThe CEO took the note to mean something it did not sayThe CEO's words in a dated reply
SourceXReview step pendingThe next step sits with SourceX's reviewA SourceX stage record
SourceXProgram fit pendingRelevance to a current program has not been settledA SourceX stage record
EitherUnknownNo dated record names a reasonNone, by definition

Coders record only the code and the record it rests on, never the private reasons behind a company's choices. The partner-side codes connect to practical fixes elsewhere: the next-step owner triage for unowned steps, and the requested-delay follow-up for companies that named their own date.

  • Cohort: every introduction submitted from the dashboards of consenting partners during one entry window of two quarters, plus every application SourceX credits to those partners in that window.
  • Sources: SourceX's dated stage records, and the partners' dated logs of asks and answers, linked by introduction. Only dates, stages and codes are extracted; no company records, documents or figures enter the dataset.
  • Consent: partners agree in writing before their logs are used. Company-side information is limited to what SourceX already records in the normal course of its review.
  • No exclusions after entry: duplicates, declines and introductions that never received an answer all stay in, each with its own ending.
  • Read date: 180 days after the entry window closes.

Analysis: time in stage, with open cases censored

For each stage, the analysis estimates how long introductions take to reach the next event, treating cases still open on the read date as censored rather than counting them as stalled or as moving. The report then gives, stage by stage, how many introductions entered, moved on, stalled, restarted, ended or remained open, followed by the distribution of reason codes among stalls as counts.

Two coders assign reason codes independently without seeing how the introduction ended; disagreements are reconciled and the agreement rate is reported per side. The report would follow the STROBE checklist for observational studies, whose site describes 22 reporting items, 18 of them shared across cohort, case-control and cross-sectional designs, and notes that it is not a tool for grading study quality (our paraphrase of a search excerpt).

Everything here is descriptive. If introductions from one kind of partner stall less at stage 1, that is an association among these introductions. It does not show that the partner type caused the difference: companies, timing and relationships differ too.

The table that stays empty until the cohort closes

StageEnteredMoved onStalledRestartedEndedOpen (censored)
1. CEO askedNot yet countedNot yet countedNot yet countedNot yet countedNot yet countedNot yet counted
2. CEO agreedNot yet countedNot yet countedNot yet countedNot yet countedNot yet countedNot yet counted
3. AppliedNot yet countedNot yet countedNot yet countedNot yet countedNot yet countedNot yet counted
4. VerifiedNot yet countedNot yet countedNot yet countedNot yet countedNot yet countedNot yet counted
5. In discussionNot yet countedNot yet countedNot yet countedNot yet countedNot yet countedNot yet counted
6. SignedNot yet countedNot yet countedNot yet countedNot yet countedNot yet countedNot yet counted

Released with the results: the codebook with its version history, both coders' raw codes, the agreement rates, the threshold sensitivity runs and the complete table, zeros included. SourceX-side reasons appear only in aggregate. An annual view of every disposition, of which stalls are one part, is laid out in the State of Company Data Introductions blueprint.

Where a stall study misleads

  • Thin partner logs. A partner who logs only some contacts will show false stalls. Partners whose logs fall below a completeness check are reported separately.
  • Silence gets blamed on the wrong side. Linking both sides' records reduces this; the unknown code absorbs what linking cannot settle.
  • Thresholds are judgment calls. The sensitivity runs show how much the counts move when thresholds change.
  • Coders who know endings. Hiding the outcome field keeps hindsight out of the codes.
  • Consenting partners differ. Partners who share logs may keep better records and stall less than those who do not.
  • The calendar. An entry window that spans year-end will show seasonal stalls; the report notes the window's dates.
  • Programs move. Program criteria can change during the window, and SourceX's screening page says a company that misses one program may suit another later; a change mid-cohort is reported as a dated event.

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.

Partners who want their introductions to be measurable later can register, sign the Channel Partner Agreement before submitting anything, and date every ask and answer from the first message; screen each company against who qualifies and the program terms, and find other study designs in the guides hub.

  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

Does a stalled introduction count as a failure in this study?

No. A stall is a state, not an ending: an introduction past its stage threshold is marked stalled, and if a dated event later moves it on, the study records a restart. Only a CEO's no, a SourceX outcome, a duplicate ruling or a recorded payout ends an introduction.

Can a partner guess the reason when the CEO simply goes quiet?

No. The codebook has an explicit unknown code, and coders use it whenever no dated record names a reason. A study that filled silence with guesses would rank the guesses.

Why not just publish the reasons partners report today?

Because partners see only their own side. A company waiting on its counsel and a company waiting on SourceX look the same from the partner's inbox. The study links both sides' dated records before coding anything.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/how-it-works
  3. refer.sourcex.si/who-qualifies
  4. strobe-statement.org/checklists

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