Test whether better intake reduces unnecessary calls: a call-efficiency measurement plan that codes every platform call by what could have settled it first, alternates a four-question request with an open booking link, and audits each founder the request routed away

Short answer

Define an unnecessary call before testing anything: a call whose outcome a published page, SourceX itself, or a fact the founder already knew could have settled without it. Then alternate two intake routes in fixed blocks, the open booking link you use now and a four-question request that routes each enquiry, code every call by what could have settled it, and audit each founder the request routed away. Better intake wins only if unnecessary calls fall and no company whose CEO wanted the conversation is lost.

Visual briefFull-size diagram
Incoming requests pass through a four-question request and split three ways: a published page link, SourceX directly, or a booked call; a dashed audit loop runs from the two routed-away exits back to a day-30 check, and a tally beside the call exit separates calls that were needed from calls a page or SourceX could have settled.
The routing and audit loop follow the measurement plan on this page; no requests have been counted.

Two neighbors measure different things. The company fit checklist test asks whether a self-check improves application quality, and the platform time-diary study records where hours go without changing anything. This page changes one thing, the route into a call, and counts the calls.

What makes a call unnecessary

Code each call once, from its outcome, within a day of holding it.

CodeThe call ended because...What could have settled itBetter route
N1The question had a published answer: how the reward works, what credit needs, what fitsA SourceX program pageSend the link
N2The question belonged to SourceX: fit in review, rights, what a license would cover, what the company would be paidSourceX itselfThe company applies, or contacts SourceX directly
N3A published fact the founder already knew decided itThe published criteria, read by the companyPoint to them and let the company decide
N4The CEO did not know about the request or was not part of itThe CEOWait until the CEO wants the conversation
N5The company had already applied to, or corresponded with, SourceXThe terms' duplicate ruleThe company carries on with SourceX directly
U1The CEO wanted the relationship holder's own account: why the fund raised it, the fund's interest, how an introduction worksNothing elseA call
U2The CEO wanted help deciding whether to apply, with questions the platform can answerNothing elseA call

N3 covers facts such as full-time headcount that never reached 50 at its peak, records that start only a year or two ago, a location outside SourceX's published geography, or records already licensed for AI training (SourceX asks suppliers to confirm their data has not been licensed for AI training before). On geography the published sentence is: 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. N5 rests on terms section 3, which treats any earlier application, lead, account or email correspondence with SourceX as an existing relationship that is not credited to a later partner.

After every call, the person who held it asks the founder one question: "Was this call worth your time?" A call coded N1 that the founder valued is reported both ways. "Unnecessary" is a platform judgment, and the founder's answer keeps it honest.

Two routes, both truthful

Route A, the control. The booking link the platform already sends.

Route B, the four-question request.

  1. Who is asking, and does the CEO know about this request?
  2. What would you like to know, in a sentence?
  3. Has the company already applied to SourceX or been in touch with it? Yes, no or not sure.
  4. Have you looked at SourceX's published fit criteria yet? Yes or not yet, with a link to who qualifies and the company fit checker, whose answers the company keeps.

Within two business days the platform replies with a page link, a pointer to SourceX or a booked call. "Not sure" on question 3 always gets a call offered. A founder who asks for a call gets one. The request never asks for headcount, revenue, systems, samples or files, and a company's fit is never judged by the platform: SourceX's fit checker is a preliminary, non-binding screen, and acceptance is decided in SourceX's review.

The call-efficiency measurement plan

MeasureDefinitionCounted fromRead
Unnecessary calls (primary)Calls coded N1 to N5 per 10 requestsCall outcome codesEnd of the test
Needed callsCalls coded U1 or U2 per 10 requestsCall outcome codesEnd of the test
Founder's viewShare of calls the founder said were worth the time, by codeThe one post-call questionEnd of the test
Platform minutes per CEO-agreed introductionTotal call minutes divided by introductions the CEO asked forCalendar and introduction logDay 90 after the last request
Time to the CEO's decisionDays from request to the CEO's yes, no or laterRequest logEnd of the test
Routed-away audit (guard)Requests closed without a call whose founder later asked for one, or said at day 30 something was missingRequest log and one day-30 messageDay 30 and day 90
CEO-agreed introductions (guard)Introductions the CEO asked for, per 10 requestsIntroduction logDay 90
Form complaints (guard)Founders who said the request felt like screening or gatekeepingAny channelThroughout

Coding. The person who held the call writes the code and a one-line outcome note, no company facts. A second person codes the same note with the route label removed; disagreements are settled by the two together and both codes are kept.

The day-30 message. Every founder whose request closed without a call gets one note: "Did you get what you needed, and is there anything you'd still like from us?" No reminder follows.

Method note. The codes come from SourceX's published rules (the duplicate rule in terms section 3, credit at a verified application in section 2, the published fit criteria) and from where questions belong: program facts on SourceX's pages, review questions with SourceX. The plan has not been run, and its margins below are set by each platform team before launch.

Hypothesis, unit, allocation and floors

  • Hypothesis. "Route B produces fewer calls coded N1 to N5 per 10 requests than Route A, without fewer CEO-agreed introductions per 10 requests."
  • Unit. The request. A company's first request counts; later requests from the same company stay with its first route.
  • Allocation. Alternating two-week blocks, with a coin toss choosing the route for the first block, recorded before launch. The same people answer both routes.
  • Floors. At least 20 requests per route before any comparison; with fewer, report counts only. The test runs until both floors are met or six months pass, and introductions are followed for 90 days after each request.
  • Partner terms. Whoever submits an introduction that comes out of either route signs the SourceX Channel Partner Agreement first.

When to pause Route B, and when it replaces Route A

Written and dated before the first block:

  1. A request arrives with records, attachments or figures nobody asked for. Stop Route B, delete the material under your own policy and reword the request.
  2. A founder says the request implied the company does not fit, or that the fund decides. Pause Route B and rewrite it.
  3. The audit finds a routed-away company whose CEO wanted the conversation and felt turned away. Pause Route B.
  4. SourceX objects to any routing reply. Pause both routes until it is answered.

Route B replaces Route A only if unnecessary calls per 10 requests fall by a margin written down before launch, CEO-agreed introductions per 10 requests fall by no more than a second written margin, and the audit finds no company turned away. Otherwise Route A stays, or a revised Route B runs another round.

A month of requests, coded (Illustrative)

Illustrative. Invented requests at a generic platform team.

RequestRouteWhat the founder raisedCodeWhat happened
1AHow the reward worksN125-minute call; the founder said a link would have done
2AAn operations lead asks whether to apply; the CEO has not heardN4Call ends with a plan to raise it with the CEO
3BWhat SourceX would pay for the company's recordsN2Reply points to SourceX's own application; no call
4BThe company applied to SourceX in the springN5Reply explains there is no introduction to make; the CEO takes a short call by choice and calls it worthwhile
5BThe CEO wants to hear why the fund is raising thisU1Call booked within the week
6BLink sent for a question about creditRouted awayDay 30: "got what I needed"

Request 4 shows why the founder's view sits beside the code: the call was avoidable for the platform and still worth something to the CEO.

Screening vocabulary, and its limits

An intake route is a screen, and screens make two kinds of error. StatPearls' chapter on health screening notes that an ideal test would minimize both missed cases and false alarms and that no ideal test exists (paraphrase). Here, an unnecessary call is a false alarm and a routed-away company whose CEO wanted the conversation is a missed case. Report both counts; a route that cuts calls by turning companies away has only moved the error.

Missing, declined and unsuccessful requests

Withdrawn requests, no-shows and founders who never answer the day-30 note stay in every denominator. Blocks are not randomized per request, so treat a difference between routes as description unless the blocks were balanced and nothing else changed between them; list every portfolio event, newsletter and SourceX terms update that fell in each block. If Route B loses, publish that too, and for the step after intake, test the referral form before sending more traffic covers what the company meets at SourceX's application.

Where the test can mislead

  • Calls build relationships. A call coded N1 can still strengthen the founder's trust in the platform, which nothing here measures.
  • Blocks absorb the calendar. A demo day or a portfolio offsite in one block can swamp the routes.
  • Forms select founders. Founders who fill in a request may differ from those who book directly, and Route B may lose some of them.
  • Outcome notes reveal the route. Removing the label does not always hide which route a call came through.
  • Fit is not the platform's call. Pointing a company to the published criteria leaves the decision with the company and with SourceX's review; the request must never tell a company it does not qualify.

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 request ends in a call the CEO asked for and the company wants to go further, register for a partner account, have the CEO look at who qualifies and read the program terms before you submit anything.

Running intake is referral work; anyone evaluating SourceX as an investment is asking a separate question and can request materials through 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

Can the request ask for headcount so the team can skip small companies?

No. The request asks about the request, never about the company's records or figures. Founders who want to check fit for themselves can use the published criteria or SourceX's fit checker and keep the answer; whether a company fits is decided in SourceX's review.

What if a founder insists on a call after being sent a link?

Book it. The request routes, it never refuses. A call a founder insisted on is coded like any other, and the founder's own view of whether it was worth the time is recorded beside the code.

Why alternate two-week blocks instead of choosing at random per request?

Because one platform inbox cannot easily run two intake routes for the same week without founders seeing both. Blocks keep each route clean; the price is that anything else happening in one block, such as a portfolio event, can tilt the comparison, so every block's calendar goes in the report.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/how-it-works
  4. ncbi.nlm.nih.gov/books/NBK436014
  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