# Founder data licensing willingness: interviews | SourceX

Canonical: https://refer.sourcex.si/guides/what-makes-a-founder-say-yes-to-a-data-licensing-conversation
Last updated: 2026-11-05

No one has published evidence on why founders agree to a data licensing conversation, and SourceX has not run founder interviews, so a confident list of reasons would be a guess. Four factors are the strongest candidates to test: whether the request is clearly about this company, whether the company keeps control, whether the process is plain, and how much work it asks. This page publishes a decision-interview protocol that tests them on founders who agreed, hesitated or declined, and counts every one of them.

It is written for business network owners and strategic partners who introduce founders to SourceX and want to get better at it without guessing. Program facts come from SourceX's how-it-works page, who-qualifies page and terms (Version 2026-10-22.2, since replaced by version 2026-11-04), all read on 26 October 2026. The protocol, the coding frame and the reporting template are this page's own; the examples are Illustrative, and no results are reported because none exist yet. Two related studies on this site look at other moments: [what founders believe before the first call](/guides/what-founders-think-data-licensing-means-before-the-first-call) and [which message features make an introduction feel trustworthy](/guides/what-makes-a-company-introduction-feel-trustworthy). This one asks founders afterwards, about a decision they actually made.

## The founder's first reading of the offer

A founder hears "license your company's records to AI developers" and fills the gaps with whatever they already know. Partners trade stories about the usual first readings, but stories are not counts. What can be stated is the published fact that answers each reading, whether or not it changes anyone's mind.

| First reading | The published fact that answers it | Where it is stated |
|---|---|---|
| "They want our customers' data" | Material that belongs to clients and personal consumer data are usually not a fit | SourceX's who-qualifies page |
| "It's a pitch with strings attached" | Going ahead, the scope on offer and the terms accepted all stay the company's call, and nothing is shared without its approval | SourceX's how-it-works page |
| "The introducer is paid out of our money" | The referral reward is paid separately by SourceX and is never deducted from the company's agreed compensation | SourceX's terms |
| "Someone will want our files first" | The partner does not export, upload or describe confidential records; the company applies itself | SourceX's how-it-works page |
| "It's a quick payment for a file" | Businesses that only want to sell a one-off file with no documentation or context are usually not a fit | SourceX's who-qualifies page |

Whether hearing these facts moves a founder toward yes is precisely what the interviews below are meant to find out. A founder who hears "is this selling my customers' data?" answered well may still decline, and that answer is worth as much as a yes; the live page on [that exact question](/guides/when-an-owner-asks-is-this-selling-my-customers-data) covers the reply itself.

## Four candidate factors, and what each one asks of the company

Each factor is a question the founder is quietly answering. The table separates what an introducer can say today from what only SourceX's review can settle.

| Factor | The founder's question | What an introducer can state now | What only review answers |
|---|---|---|---|
| Relevance | "Why us, specifically?" | Company-specific facts: years of the company's own records, the system they live in, full-time headcount at peak | Whether the records match a current program |
| Control | "Who decides what leaves the building?" | The company decides scope and terms, and nothing is shared without its approval | Exactly what a license would cover |
| Clarity | "What happens, in what order?" | Review, then agreement, delivery and payment, under written terms | Price, timing and the rights questions |
| Effort | "What will this take from my team?" | SourceX manages the agreement, rights review, data preparation, delivery and payout; the company still decides scope, and the work is real | How much preparation a given dataset needs |

A fifth factor is about the messenger rather than the offer: what the introducer did. Disclosing the reward, making a no easy and avoiding any pressure may raise trust; a vague pitch or a nudge from someone with leverage may lower it. The protocol codes it separately, so a founder's view of the introducer does not get mixed up with their view of licensing.

## The consented founder decision interview protocol

**Who is invited.** Every founder or CEO your network asked about a SourceX introduction during a fixed period, whatever they answered. Fix the list before the first interview and sort it into three groups by what each founder decided: agreed to a conversation, undecided (said "later" or never replied), or declined. Invite all of them.

**How consent works.** Ask for the interview separately from any referral conversation. Say it is optional, that declining changes nothing in the relationship, that any question can be skipped, that nothing is recorded without agreement, and that quotes appear only with written permission. The U.S. federal rule on informed consent for human-subjects research, 45 CFR 46.116, asks the investigators it covers to seek consent in circumstances that minimize the possibility of coercion or undue influence. A business network is not bound by it. The principle fits here, which is why the next rule exists.

**Who interviews.** Not the person who made the ask. A colleague or an outside interviewer holds the conversation; the introducer sees only coded results.

**What is asked.** NN/g's guidance warns that a leading question builds the hoped-for answer into its wording. The ten questions below are open and run from the first impression to the decision.

| # | Question | Factor it usually informs |
|---|---|---|
| 1 | When you first heard about it, what did you think was being proposed? | First reading |
| 2 | What, if anything, made it seem connected to your company in particular? | Relevance |
| 3 | What did you want to know about who decides what is shared? | Control |
| 4 | What did you expect it would take from your team? | Effort |
| 5 | Which parts, if any, were unclear? | Clarity |
| 6 | What did the person who raised it do that made you more or less comfortable? | Introducer |
| 7 | What did you decide, and what tipped it? | All |
| 8 | What would have changed your decision? | All |
| 9 | Who else at the company weighed in? | Authority |
| 10 | Is there anything we did not ask that mattered? | Open |

**How answers are coded.** Two coders work independently. Each answer gets one or more factors and a direction: toward yes, toward no, or neutral. Disagreements are resolved by discussion, and the number of disagreements is reported with the results.

## Comparing founders who agreed, hesitated and declined

A study that interviews only the founders who said yes learns what yes-sayers have in common, not what tipped their decision. The comparison across all three groups is the point, and so is an honest count of who never took part.

AAPOR's Standard Definitions, the survey-research reference now in its tenth edition (2023), sorts cases into interviews, non-respondents, cases of unknown eligibility and ineligible cases, and defines several response rates depending on how those cases are treated. Borrow the discipline: report every disposition, not just the interviews.

| Disposition | Agreed | Undecided | Declined |
|---|---|---|---|
| Invited to interview | Not yet published | Not yet published | Not yet published |
| Interviewed | Not yet published | Not yet published | Not yet published |
| Declined the interview | Not yet published | Not yet published | Not yet published |
| Did not respond | Not yet published | Not yet published | Not yet published |

| Factor | Mentioned toward yes | Mentioned toward no |
|---|---|---|
| Relevance | Not yet published | Not yet published |
| Control | Not yet published | Not yet published |
| Clarity | Not yet published | Not yet published |
| Effort | Not yet published | Not yet published |
| Introducer | Not yet published | Not yet published |

Reporting rules, fixed before the first interview: counts always shown with their denominator; no percentages for groups too small to bear them; decliners' reasons reported with the same weight as agreers'; no company names or identifying details; no quote without written approval; and no sentence that turns what founders said into a claim about the market.

## Whose answer speaks for the company

A founder's view and the company's decision are not always the same thing. In this program it is the CEO who authorizes a licensing discussion and signs on the company's behalf, so code the CEO's interview as the company's decision and any other founder's or executive's interview as a personal view. A co-founder's enthusiastic yes, when the CEO declined, is a personal yes and a company no. The live question page on [who can say yes for a hotel company's service recovery records](/questions/who-can-license-service-recovery-approvals-records) shows how structure can add other parties to check before a CEO's answer counts.

The interviews are not a fit screen either. However warm the interview, the company still has to show a peak of at least 50 full-time employees (contractors are not counted), years of records it created itself, the rights to license those records and an authorized contact. 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. Relevance to current data needs is checked in SourceX's review, whatever a founder said in an interview.

## A clearer introduction while the results are pending

Every candidate factor maps to something already true and published, so an introducer can act on all of them before a single interview is coded. The worked lines below are Illustrative, for an invented 160-person regional insurance broker.

| Factor | A line that tends to blur it | A clearer line |
|---|---|---|
| Relevance | "AI companies are paying a lot for data right now." | "You've kept twelve years of your own claims-handling notes in one system, which is the kind of record SourceX reviews." |
| Control | "They'll take care of everything." | "Your company decides whether to go ahead, what to include and on what terms." |
| Clarity | "It's simple, just apply." | "SourceX reviews first; an agreement, delivery and payment come later, under written terms." |
| Effort | "It's no work at all." | "It isn't effortless. SourceX manages the agreement, rights review and preparation, and your team decides the scope." |
| Introducer | (Reward not mentioned) | "If this goes ahead I may receive a referral reward from SourceX; it never comes out of your payment, and no is a fine answer." |

Making a no easy has its own playbook in [making a referral ask easy to decline](/guides/how-to-make-a-referral-ask-easy-to-decline). Disclosure of the reward should be plain and early, not a footnote.

## Where interview evidence misleads

- **Memory rewrites reasons.** Founders explain decisions made weeks earlier, and the explanation can tidy up what actually happened.
- **Politeness shades answers.** A founder connected to the introducer may soften criticism, even with a neutral interviewer.
- **One network is not a market.** Findings describe the founders a particular network reached, not founders in general.
- **Decliners answer less often.** That is why non-response is reported by group; a high non-response rate among decliners weakens every comparison.
- **Factors overlap.** A founder who found the process unclear may also have doubted control; coders will disagree, and the disagreement count belongs in the report.
- **No results exist yet.** SourceX has not published founder decision data, and this page reports none.

**Methods note.** The protocol applies SourceX's how-it-works page, who-qualifies page and terms (Version 2026-10-22.2, since replaced by version 2026-11-04), AAPOR's Standard Definitions, the consent principle in 45 CFR 46.116 and NN/g's guidance on leading questions, all checked on 26 October 2026. It measures what founders say about their own decisions; it does not measure demand for any company's records, acceptance by SourceX or any reward. Results will be published only after real, consented interviews exist.

## 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 who is also the CEO has heard a specific, honest pitch and asks for the conversation, the introducer's remaining homework is short: [register](/register) for a tracked partner link, measure the company against [the qualification rules](/who-qualifies) and read the [terms](/terms) before the introduction is sent. The stages that follow are laid out on [how it works](/how-it-works), and more playbooks sit in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/how-it-works
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://aapor.org/wp-content/uploads/2023/05/Standards-Definitions-10th-edition.pdf
- https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-A/part-46/subpart-A/section-46.116
- https://www.nngroup.com/articles/leading-questions/
