# Founder skepticism or a real no? Four tests | SourceX

Canonical: https://refer.sourcex.si/guides/the-difference-between-skepticism-and-a-genuine-no
Last updated: 2026-11-05

Skepticism asks for something: a fact, proof, a person or a condition. A genuine no asks for nothing; it states a decision about the company, and when the CEO says it, it is the company's answer. Sort every reply with four tests (does it ask, does it name a condition, who said it, has it been said before), answer an objection once with facts you can source, and treat anything that is neither as a no. Because your fund holds influence, lean toward reading a reply as a no.

An operating partner hears more polite replies than most introducers. That is the problem this guide is built for.

## Why the line matters more when your fund holds a board seat

A founder who would turn down a stranger in one line may dress the same refusal as a question when a board member raises the idea. That is our working hypothesis, not measured data, and nothing published tests it. But the cost of getting it wrong runs one way. Reading a no as an objection turns a referral into pressure from someone who votes on the company's budget. Reading an objection as a no costs one introduction that the founder can still start on their own.

Two program rules make the cost concrete. The CEO authorizes a licensing discussion and signs for the company, and SourceX's screening guidance lists introductions the decision maker never knew about among the cases that usually do not fit. An introduction that reached SourceX because the founder felt unable to refuse their investor has the same weakness, just better disguised.

## The concern underneath the founder's words

The same words can carry different concerns, and the concern depends partly on who is asking. When a stranger mentions licensing, "what would we get?" is usually about value. When the company's investor mentions it, the same question is often about incentive: why does the fund care?

| Surface question (Illustrative) | Concern it may carry | The fact that meets it |
|---|---|---|
| "Is this a real business?" | Legitimacy | SourceX is the company's counterparty from agreement through delivery and payment |
| "What would we get?" | Value, or the investor's incentive | No figure exists before a signed Dataset Deal Confirmation; earlier estimates are indicative |
| "What does the fund get?" | Incentive | A reward of the greater of $50,000 plus 5% and 15% of the company's Actual Supplier Payout, with no cap, paid separately by SourceX; nothing for the fund comes off the company's compensation |
| "Our clients' files are in there." | Rights | Material that belongs to clients is usually not a fit, and SourceX's rights review decides scope |
| "Do we lose the data?" | Control | The company keeps ownership of its original data; a license is exclusive for AI training for the records selected |
| "Who would know about this?" | Confidentiality | Partners never handle the records, and neither side publicizes a deal |
| "This sounds like a project." | Effort | The first step is a few questions and no files |

When you cannot tell which concern you heard, ask: "Is that about what the company would receive, or about why I'm raising it?" The founder's answer tells you which fact to offer. Fuller scripts for each concern sit in the [objection handling script template](/resources/objection-handling-script-template), and further founder-objection guides are listed under [guides](/guides).

## The objection-versus-decline classification guide

Four tests, applied in order to the reply as given, not to what you hoped it meant.

1. **The request test.** Does the reply ask for information, proof or a person? A request is an objection candidate.
2. **The condition test.** Does it name something that would change the answer: a date, a fact, someone else's view? A named condition is an objection with a condition attached, and the condition belongs to the company.
3. **The authority test.** Did the CEO say it, about the company? A decision stated by the CEO is the company's no. A no from someone else is one person's view, and you do not go around them to reach the CEO either.
4. **The repeat test.** Is this the same concern again, after you have already given one bounded answer? A repeated concern is a decline.

A reply that passes neither the request test nor the condition test is a decline. A reply that is unclear gets one question whose easiest answer is no ("Shall I leave this here?"), and silence after that is a no.

| Founder reply (Illustrative) | Tests it meets | Class | What you do |
|---|---|---|---|
| "Who actually pays for ten-year-old service tickets?" | Request | Objection | Answer once: SourceX licenses the records and pays the company; amounts are fixed only in a signed Confirmation |
| "Our customers would mind." | Request, implied | Objection | Say client-owned material is usually not a fit and SourceX's rights review sets scope; the company's counsel owns the question |
| "What do you earn from this?" | Request | Objection | State the reward plainly and in writing, before anything else |
| "Maybe after our ERP cutover in March." | Condition | Objection with a dated condition | Note the company's condition; the restart is the CEO's to make |
| "Let me think about it with the board." | Condition | Objection inside the CEO's own process | Leave it with the CEO; never lobby the board seat your fund holds |
| "My COO thinks it's a distraction." | Condition, relayed by the CEO | Objection | Offer the one fact on effort; do not contact the COO unless the CEO asks you to |
| "Send me something." | Request, weak | Unclear | One page with an easy pass, then wait |
| "We don't sell our data." | None | Decline | Acknowledge and stop |
| "I told you no in June." | Repeat | Decline | Apologize, stop and suppress the company across the fund |

The "board" row is where operating partners most often slip. How a CEO consults a board is the company's business; under the program the CEO is the one who authorizes. If your fund holds a seat, raising the idea there after the CEO hesitated is the board pressure this guide exists to prevent.

For the timing variant, [how to handle the "not now" objection](/guides/how-to-handle-not-now-objection) covers triggers, and for customer worries [what if our customers would be concerned](/guides/what-if-our-customers-would-be-concerned) routes each question to its owner.

## What you can say for certain, what depends on review, and what nobody has looked at

A bounded answer uses only the first group as fact.

**Known now, from SourceX's published terms and process:**

- The first step is a short set of questions with no files.
- The company keeps ownership of its original records; a license is exclusive for AI training for the records selected, and the term is set in the deal's Confirmation.
- The reward is paid by SourceX separately, and a lead, meeting or signature alone earns nothing.

**Conditional, decided only in SourceX's review and the company's own signed documents:**

- Whether the company fits a current program; requirements move with SourceX's current data needs.
- Which records are in scope after the rights review.
- Any payout, which stays indicative until a Confirmation is signed.

**Unreviewed, so never stated:**

- Whether anyone wants this company's records.
- What they would be worth.
- Whether customer contracts allow licensing them.

A founder who asks for a demand promise before agreeing to talk is asking for something in the third group. [The founder wants a buyer promised](/guides/the-founder-wants-guaranteed-demand-what-can-you-honestly-say) covers it: no partner can make that promise.

## One next step, with the decline built into it

Offer a single voluntary step and make passing cheaper than accepting. The step can be the [company fit checker](/tools/company-fit-checker), a preliminary, non-binding screen the CEO runs alone, or a reply asking to be introduced. Write the exit into the same message: "If you'd rather leave it, reply 'pass' and I won't bring it up again."

Each class has its own escalation path:

- **An objection about legitimacy, value or effort** goes to SourceX's first call, and only if the CEO chooses to have it.
- **An objection about rights** goes to the company's counsel and, later, SourceX's review.
- **An objection about incentive** you answer yourself, in writing.
- **A decline** goes nowhere. Close it the way [the respectful close when a founder declines](/guides/the-respectful-close-when-a-founder-declines) describes.

When a reply is not an objection or a decline but a fact that rules the company out, the stop rules in [when a referral partner should end the conversation](/guides/when-a-referral-partner-should-end-the-conversation) apply instead.

## Where this guide can misclassify, and how it was built

- **Politeness.** A no wrapped in a question will pass the request test. The repeat test and the one easy-no question are the guard, and neither is perfect.
- **Influence.** A founder may say yes to avoid friction with an investor. A yes that does not survive "this is entirely optional" is not a yes.
- **Demand.** A well-answered objection can still end without an offer: SourceX says qualifying is not an offer and positive interest is not yet a purchase.
- **Rights.** The guide classifies replies; it cannot tell whether the records are the company's to license.
- **Change.** SourceX may publish new versions of its terms, and every fact in the "known" group should be checked against the current version before you use it.

**Methods note.** The four tests were derived on 2026-10-27 from the program's published consent and authority rules (the terms, Version 2026-10-22.2, since replaced by version 2026-11-04, and SourceX's screening guidance) and from SourceX's process page. The founder replies are Illustrative, written for this guide; SourceX has not published a set of recorded founder questions, and no figures exist on how often each class occurs or ends in an introduction. To measure it, log every reply with its date, the speaker's role, the class you assigned, whether a bounded answer was given and what happened within 30 days, then report counts against the number of founders asked. Those figures are not yet published.

## 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 founder's question has been answered once and the CEO asks to go further, [create your partner account](/register), compare what the CEO has told you with [who qualifies](/who-qualifies) and keep the [program terms](/terms) open while you write the introduction.

Sorting founder replies is referral work; a reader weighing SourceX itself as an investment is making a separate decision and can request materials from the [SourceX investor overview](https://sourcex.si/investors).

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.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://sourcex.si/investors
