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.
| Code | The call ended because... | What could have settled it | Better route |
|---|---|---|---|
| N1 | The question had a published answer: how the reward works, what credit needs, what fits | A SourceX program page | Send the link |
| N2 | The question belonged to SourceX: fit in review, rights, what a license would cover, what the company would be paid | SourceX itself | The company applies, or contacts SourceX directly |
| N3 | A published fact the founder already knew decided it | The published criteria, read by the company | Point to them and let the company decide |
| N4 | The CEO did not know about the request or was not part of it | The CEO | Wait until the CEO wants the conversation |
| N5 | The company had already applied to, or corresponded with, SourceX | The terms' duplicate rule | The company carries on with SourceX directly |
| U1 | The CEO wanted the relationship holder's own account: why the fund raised it, the fund's interest, how an introduction works | Nothing else | A call |
| U2 | The CEO wanted help deciding whether to apply, with questions the platform can answer | Nothing else | A 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.
- Who is asking, and does the CEO know about this request?
- What would you like to know, in a sentence?
- Has the company already applied to SourceX or been in touch with it? Yes, no or not sure.
- 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
| Measure | Definition | Counted from | Read |
|---|---|---|---|
| Unnecessary calls (primary) | Calls coded N1 to N5 per 10 requests | Call outcome codes | End of the test |
| Needed calls | Calls coded U1 or U2 per 10 requests | Call outcome codes | End of the test |
| Founder's view | Share of calls the founder said were worth the time, by code | The one post-call question | End of the test |
| Platform minutes per CEO-agreed introduction | Total call minutes divided by introductions the CEO asked for | Calendar and introduction log | Day 90 after the last request |
| Time to the CEO's decision | Days from request to the CEO's yes, no or later | Request log | End 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 missing | Request log and one day-30 message | Day 30 and day 90 |
| CEO-agreed introductions (guard) | Introductions the CEO asked for, per 10 requests | Introduction log | Day 90 |
| Form complaints (guard) | Founders who said the request felt like screening or gatekeeping | Any channel | Throughout |
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:
- 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.
- A founder says the request implied the company does not fit, or that the fund decides. Pause Route B and rewrite it.
- The audit finds a routed-away company whose CEO wanted the conversation and felt turned away. Pause Route B.
- 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.
| Request | Route | What the founder raised | Code | What happened |
|---|---|---|---|---|
| 1 | A | How the reward works | N1 | 25-minute call; the founder said a link would have done |
| 2 | A | An operations lead asks whether to apply; the CEO has not heard | N4 | Call ends with a plan to raise it with the CEO |
| 3 | B | What SourceX would pay for the company's records | N2 | Reply points to SourceX's own application; no call |
| 4 | B | The company applied to SourceX in the spring | N5 | Reply explains there is no introduction to make; the CEO takes a short call by choice and calls it worthwhile |
| 5 | B | The CEO wants to hear why the fund is raising this | U1 | Call booked within the week |
| 6 | B | Link sent for a question about credit | Routed away | Day 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.