How to report referral pipeline without inflating it: a deduplicated waterfall that turns 31 logged entries into 17 introduced companies and keeps every unresolved case on the page

Short answer

Count companies, not entries, and count each one once, at the furthest stage it has reached by a fixed cutoff date. Remove duplicate entries, fold group entities into one reporting unit, move companies SourceX already knew into their own row, and show unresolved cases with the date or decision that will resolve them. Report introductions, credited companies, supplier payments and paid rewards as separate counts, each with its denominator, and attach no dollar value to any stage before payment.

Visual briefFull-size diagram
An Illustrative horizontal waterfall: 31 logged entries lose 6 duplicates, 3 group merges and 5 never-introduced names to leave 17 introduced companies, which split into 9 credited, 5 unresolved and 3 not credited or lapsed.
Illustrative quarter for one fund. Counts only, no dollar values; not SourceX data.

A referral log is a list of names someone typed. A pipeline report is a claim about companies. The gap between the two is where inflation lives, and in a fund it usually comes from good intentions: two colleagues log the same founder's company, a platform analyst counts a parent and its subsidiaries separately, a dashboard estimate is summed as "potential". (For the other meaning of pipeline, the route records take from a company's systems to a buyer, see what a data pipeline is.)

Seven ways a referral pipeline inflates

Each trap below is common, each makes the channel look busier than it is, and each has a rule that removes it.

TrapHow it inflates the reportRule that removes it
Entry countingThe same company appears twice because two people logged it, or once under an old nameOne row per company, keyed on legal name and primary domain
Group splittingA parent and its subsidiaries count as three winsOne reporting unit per group; entity count in a note
Known-to-SourceX companiesA company with an earlier lead, account or email with SourceX is reported as pipelineIts own row, "not credited", never in the active count
Stale introductionsAn introduction with no verified application inside 90 days stays "active"Mark it lapsed on the day the window closes
Estimates as valueDashboard estimates, or names multiplied by the reward floor, are summed into a "potential" figureCounts only until a reward is paid
Cumulative as periodicA running total since launch is presented as this quarter's activityCohorts by introduction date, measured at a stated cutoff
Small-number ratios"Two of three applied" becomes 67%, then a run rateCounts with denominators; no percentages under 20 cases, no annualizing

Two of these rules come straight from the program terms. Each company yields credit for one partner only, the partner behind the first valid introduction of a company new to SourceX, and that credit depends on the company submitting a verified application inside the 90-day attribution window. And section 3 classes a company as a duplicate when SourceX already has any earlier lead, account or email correspondence with it, and a later partner gets no credit for a duplicate. A report that ignores either rule is counting companies the program will never credit.

Stages, populations and the cutoff date

Fix three things before counting anything.

The population is every unique company introduced during the cohort window, here the third quarter, by anyone reporting to the fund. Logged names that never became an introduction are counted on the way in, then removed.

The cutoff is the date the report reads statuses, here October 15. Every company sits at the furthest stage it reached by that date, and later events wait for the next report.

The stages, with the evidence a fund can actually hold:

StageDefinitionEvidence
LoggedA name entered in the fund's trackerYour tracker
IntroducedA written introduction sent with the CEO's agreement, by someone who has signed the Channel Partner AgreementThe dated introduction record
CreditedA verified application within 90 days, and the first valid introductionSourceX status, by reference code
In reviewSourceX is assessing the companySourceX's generic stage
DeclinedReview ended without a dealSourceX's recorded outcome
SignedThe company says it signed its Master agreement and a ConfirmationThe company's word
Supplier paidSourceX has paid the companyReward status moves past Estimated
Reward paidThe reward reached the partnerStatus Paid, and your bank record

The partner agreement helps here. It requires every introduction record to identify the company, its domain, the partner, the opportunity, the introduction method and timestamps, which is exactly the key a deduplication needs. It also limits what you will see: generic stages and reference codes, not the Acquisition Partner's name, price or acceptance evidence, and never another partner's records. Where a stage is not visible to you, the cell says "not known", which is a fact, not a guess. Where a partner can see the current stage covers the dashboard side.

The deduplicated pipeline waterfall (Illustrative)

Illustrative. One fund's third-quarter log, read on October 15. Generic companies, invented counts, no outcomes implied for any real company.

StepCountRemovedRule appliedEvidence
Entries logged in the quarter31Starting countRaw tracker rowsTracker export, dated
Less duplicate entries256Same legal name or domain, logged twiceName and domain match
Less entities folded into a group223Parent and subsidiaries become one reporting unitThe CEO's description of the structure
Less names never introduced175No written introduction with the CEO's agreementAbsence of an introduction record
Introduced companies1714 in allThe report's denominatorIntroduction records

Then every one of the 17 lands in exactly one outcome row:

Outcome on October 15CompaniesWhat resolves it
Not credited: earlier relationship with SourceX2Resolved
Lapsed: no verified application within 90 days1Resolved
Unresolved: window still open, no application yet4The application, or the window closing on its dated day
Unresolved: in duplicate review1SourceX's decision
Credited9Moves on through review
Total17Must equal introduced companies

And the 9 credited companies, by furthest stage: 6 in review, 1 declined, 2 signed by the company's account, 0 supplier paid, 0 rewards paid.

Set that beside the version that tends to circulate: "31 opportunities, 9 deals in progress, 2 closed, $1.55 million potential." Every word of it can be defended by a spreadsheet, and almost none of it describes companies. The 31 includes duplicates and names nobody introduced; "closed" means two companies say they signed, which earns nothing on its own; and $1.55 million is 31 names multiplied by the USD 50,000 floor on a first qualifying transaction, a number this pipeline cannot support, because the floor is paid only once a company's first qualifying transaction is paid, and most rows will pay nothing. The deduplicated report says 17 companies introduced, 9 credited, 5 unresolved and $0 paid, and each figure survives a question.

Every company in one row, every open case rolled forward

Three checks keep the report honest from one quarter to the next.

  1. Each company appears in exactly one outcome row, and the rows sum to the denominator. If they do not, a duplicate slipped through or a company fell out.
  2. Every unresolved row names its resolver. A window that is still open carries the date it closes; a duplicate review carries "SourceX". Nothing stays unresolved without a reason.
  3. Unresolved cases roll forward, never drop out. The next report opens with them.
Third-quarter cohortOctober 15January 15
Introduced companies1717
Credited911
Not credited23
Lapsed13
Unresolved50
Of credited: in review, declined, signed, supplier paid6, 1, 2, 04, 2, 3, 2
Rewards paid00

Between the two dates, two open windows produced verified applications and two closed without one, and the duplicate review went against the fund. The denominator never moved. That is the property that makes cohorts comparable: the third quarter is always 17 companies, however its outcomes develop. Join your rows to SourceX's statuses by reference code rather than by company name, which avoids the errors that come with renamed or re-registered companies; when a company registers twice and preventing duplicate claims cover the upstream fixes.

A one-page quarterly report, with income left at what was paid

A quarterly referral report fits on one page:

  • Counts with denominators. "17 companies introduced; 9 of 17 credited; 5 of 17 unresolved: 4 windows closing by December 29 at the latest, 1 in SourceX's duplicate review."
  • What moved since the last report, by cohort, never pooled across quarters to make a ratio look sturdier.
  • Why companies fell out, in your own words where SourceX shares a reason; the rejection reasons study offers a taxonomy.
  • What the fund will change. In the Illustrative quarter, six of the fourteen removals were duplicate entries and two companies were already known to SourceX, so the fix is upstream: one shared tracker and a check before anyone writes to a CEO.
  • Income, as paid rewards only. Estimates do not appear, and nothing is multiplied by four.

Attribution method is a reason to be strict. PartnerStack's State of Partnerships in GTM 2026 research found that 42% of surveyed B2B SaaS companies use multi-touch attribution for partner revenue, 31% first-touch, 19% last-touch and 8% other or no tracking. A fund that borrows its CRM's touch model will count differently from the program. For SourceX introductions, use the program's own rule: first valid introduction, verified application, one partner per company. The stage-to-cash reconciliation carries the report past signature into payment, and the address-book waterfall covers the step before introduction.

Where this report could still mislead

  • Small cohorts. With 17 companies, one outcome moves every line. Printing counts rather than rates is the defense, not a cure.
  • Long resolution. The credit window closes 90 days after the recorded introduction, though duplicate review can run longer, and payment depends on acceptance, cleared funds and the supplier being paid. A cohort can look idle for months and still pay later.
  • Thin visibility. Partners see generic stages. A company stuck "in review" may be waiting on its own CEO, and the report cannot tell.
  • Changing terms. The terms carry a version history; record the version in force at each cutoff, because a rule change can move a company between rows.
  • Counts are not founder value. A clean pipeline can still be a program founders find tiresome. Measure that separately, as separate founder and revenue scorecards describe.

Methods note. The traps, stages and checks are built from the program terms (version 2026-11-04), the rewards page and the unsigned Channel Partner Agreement sample, all checked 2026-11-04. The waterfall and roll-forward are invented to show the arithmetic. Nothing here measures how many introduced companies are credited, accepted or paid across the program; SourceX has not published those figures.

Which companies belong in the denominator at all

Only companies someone actually introduced, with the CEO's agreement, belong in the count. A company is a plausible introduction when it has 50+ full-time employees at peak (contractors excluded), years of records it created itself, the rights to license them, and a CEO who decides whether the company discusses licensing and signs for it. 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. Partners screen at metadata level and never handle records or credentials. Funding status plays no part, so a report sorted by valuation measures the wrong thing. Related reporting guides sit 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.

Once your tracker counts each company once and a CEO has agreed to the conversation, get a partner link, run the company through the who qualifies criteria and note the program terms version on the report.

Reporting the fund's own referral channel is separate from judging SourceX as a company to invest in; readers doing the second can request investor materials through the SourceX investor overview, where SourceX says it shares company and commercial metrics with investors directly.

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

Should a fund report a pipeline value next to its referral counts?

No. Before SourceX pays a company, any reward is an estimate, and the terms call portal and calculator estimates projections. Report counts by stage and income only once a reward is paid.

How do we count a parent company and two subsidiaries that were all logged?

As one reporting unit in the headline, with the entity count in a note. A parent and its subsidiaries count as one referred company, so the USD 50,000 floor on a first qualifying transaction applies once to the group. How credit works when different people introduce sister companies is decided by SourceX in duplicate review, so do not count the extra entities as extra wins.

What happens to an introduction that is still inside its 90-day window at the report date?

It goes in the unresolved column with the date the window closes. It is neither a success nor a loss until a verified application arrives or the window ends, and the next report rolls it forward.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. refer.sourcex.si/rewards
  4. partnerstack.com/resources/research-lab/charts/multi-touch-is…
  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