How to answer a founder who hears 'data broker': a five-line introduction script that names the counterparty, bounds the claim and sends every harder question to the person who can settle it

Short answer

Ask what the phrase made them picture, then answer that picture and nothing wider. Founders who hear "data broker" usually imagine profiles of strangers for sale, records resold without limit, or a go-between skimming a cut. SourceX's published model answers each in bounded terms: the company licenses selected records it created to SourceX under an agreement it signs, SourceX pays it, and any onward license to AI developers is SourceX's own. Questions about state law, buyers or price go to the founder's counsel or to SourceX.

Visual briefFull-size diagram
The phrase data broker fans out into three pictures a founder may have, profiles of people, endless resale and a middleman's cut, each answered by one bounded line from SourceX's published model, with a bar beneath sending state law to counsel and buyer or price questions to SourceX.
The three pictures and answers follow the script on this page; the answers rest on SourceX's published pages, checked 2026-10-27.

For a CFO or general counsel who asks about brokers in general, the broker question guide has the fuller explanation card. This page is for the moment the phrase itself stops the conversation, and for the operating partner who has to keep it honest without arguing.

Why the phrase lands so hard

The words carry an enforcement history. In January 2024 the Federal Trade Commission announced an order barring X-Mode Social and its successor Outlogic from selling sensitive location data, describing it as its first settlement with a data broker over sensitive location information; the raw location data was tied to mobile advertising IDs and could be matched to individual people. A founder who has read stories like that hears "data broker" as surveillance, and is right to want no part of it.

The words also carry legal definitions, and those do not turn on the verb. Vermont defines a data broker as a business that "knowingly collects and sells or licenses to third parties the brokered personal information of a consumer with whom the business does not have a direct relationship" (9 V.S.A. § 2430, in the version marked effective until January 1, 2027). "We license, we don't sell" is therefore no answer at all. What separates a company licensing its own work records from that definition is the subject matter: whose information is in the records, and whether the company is collecting facts about people it never dealt with. Whether any state's law reaches a given dataset is a question for the company's counsel, reading the current text.

Hear which picture the founder has

Each picture gets a one-line answer, and each answer has a boundary. Cross it and a true statement turns false.

What the founder saysThe pictureThe bounded answerIt becomes untrue if you add
"Are we selling information about our customers?"Profiles of peopleThe candidates are records the company created doing its own work, with personal details removed through approved processing routes; personal consumer data is usually not a fit"Customer data is fine," or anything about a consumer dataset
"Will it be resold to anyone who pays?"Endless resaleThe company approves the scope and signs before delivery; the license is exclusive for AI training on the selected data, with its term set in the company's Confirmation"Nobody else will ever see it": SourceX's right to distribute or sublicense the de-identified dataset is unaffected
"So you are a middleman taking a cut?"A go-betweenSourceX is the counterparty: the company signs with SourceX and is paid by SourceX, and SourceX has fees of its own"SourceX makes nothing," or "you will deal with the lab"
"And what is in it for you?"A hidden incentiveSourceX pays the partner a reward separately, never deducted from the company's compensationSilence

The direct-counterparty introduction script

The script runs in three parts: the words in your first note, five lines for the moment the phrase comes up, and the handoffs for anything you cannot answer.

Part 1: the first note. Most "data broker" reactions are invited by the introducer's own shorthand. Swap it before you send.

Shorthand that invites the phraseWording that matches the published model
"They buy company data""SourceX licenses selected records a company created, under an agreement the company signs; the company keeps its original data"
"Monetize your customer data""Your own operating records, such as tickets or project histories, with personal details removed"
"A marketplace for AI data""SourceX is the party you would contract with and be paid by"
"I can connect you with AI labs""SourceX handles the onward license in its own name and may not name the developer"
"They pay well""A short assessment with no files; any figure stays indicative until a signed Confirmation"

Part 2: five lines when the phrase comes up. Say them in order and stop wherever the founder is satisfied.

LineWhat you sayRests onIf they push further
1. Ask"When you hear data broker, what are you picturing?"Nothing yet: listenLet them finish
2. Name the counterparty"Your company would sign with SourceX, and SourceX would pay your company."SourceX's process pageBuyer questions go to SourceX
3. Bound the records"What's in scope is records your company created, with personal details removed. Data about consumers is usually not a fit."Screening and process pagesState-law questions go to your counsel
4. Admit the fees"SourceX has its own fees in the deal. Your payout would be fixed in a Confirmation you sign before anything is shown outside."Program terms; process pagePrice questions go to SourceX's assessment
5. Disclose and offer"If it ever closed, SourceX would pay me a reward on top, never out of your payment. Want the assessment link, or shall I drop it?"Program termsA no ends the thread

Part 3: the handoffs. Some questions are not yours to answer, however well you know the program.

QuestionWho settles itWhat you say meanwhile
Could a data broker or privacy law apply to us?The company's own counsel"That's for your counsel; I won't guess."
Who would end up using the records?SourceX, which may not disclose it"SourceX answers that, and it may not name the developer."
Do our customer contracts allow this?The company's counsel, then SourceX's rights check"Nobody needs to send contracts to me."
What would we be paid?SourceX's assessment, then the signed Confirmation"Any number comes from SourceX, not from me."
Should we go ahead?The CEO"It's your call, and no is fine."

The guide on who will ultimately use the data covers the buyer handoff in depth.

What is known, what is conditional, what nobody has reviewed

StatusStatementBasis
KnownThe company contracts with SourceX and is paid by SourceX; it keeps ownership of its original dataSourceX process page
KnownThe onward license to AI developers is SourceX's ownSourceX investor page
KnownThe company confirms its data has not been licensed for AI training beforeSourceX process page
ConditionalWhether the company fits: 50 or more full-time employees at peak, documented history, rights, a CEO who wants the conversationSourceX screening page and terms
ConditionalWhether any state data broker or privacy law reaches its recordsThe company's counsel
UnreviewedRights under customer contracts, demand for the records and any priceSourceX review and the company's signed agreements

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.

A founder email, answered (Illustrative)

Illustrative: the administrator, its counsel and the email are invented. The founder-CEO of a 240-person payroll and benefits administrator forwards a note from the company's general counsel: "This reads like a data broker deal, and we hold pay records for our clients' employees. Hard no?"

"Your counsel is right to ask, and on those records the answer is no. Pay records you hold for clients look like their material, and SourceX's screening treats client-owned material and personal data about consumers as usually not a fit. What might be in scope is narrower: your firm's own operating records, such as support tickets and implementation project histories, with personal details removed. Whether even those fit, and whether any state law touches them, is for SourceX's review and your counsel. The assessment asks a few questions and needs no files; if the narrower version doesn't interest you, I'll drop it."

The bounded answer concedes most of the ground here, and that is the point. A partner who defends the payroll records loses the founder's trust on everything else. When an owner's worry is specifically about customers, the customer-data boundary script goes further. If the founder declines, switch off follow-ups; the guide to a respectful close shows how.

Where the script fails, and how to test it

  • The records really are about people. If the valuable data is consumer or client personal information, no wording rescues the introduction. Stop.
  • Definitions move. The Vermont section quoted here is marked effective until January 1, 2027, with a revised version set out after it. Never present a legal definition as settled for a particular company.
  • Accuracy does not fix reputation. Some founders will decline on optics after a correct answer. That is a legitimate decision, not an objection to overcome.
  • Onward licensing is real. SourceX may distribute or sublicense the de-identified dataset as the agreement allows. "Only one company will ever see it" is false, and the comparison of data brokers and data licensing explains what the license does restrict.
  • A clear answer creates no offer. SourceX's process says qualifying does not guarantee an offer, and demand is assessed only in review.

Method note. The script lines and the status table come from SourceX's process, investor and screening pages and the program terms, checked 2026-10-27, plus the Vermont definition and the FTC announcement cited here. The script has not been tested with founders, and SourceX has not published data on how founders respond. To test it, log for each conversation the founder's first words, which picture they had, the line at which they were satisfied or declined, and whether the company applied within 30 days.

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 the founder has heard a bounded answer and the CEO still wants to talk, register for a partner link, sign the Channel Partner Agreement, check the company against who qualifies and read the program terms; more founder conversations sit in the guides hub.

If your interest is in SourceX as a company rather than in referring one, that is a separate decision: request investor 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 I just say SourceX licenses data rather than selling it, so it is not a data broker?

No. Vermont's definition covers a business that sells or licenses brokered personal information, so the verb settles nothing. The honest distinction is whose records they are and what is in them: a company's own work records with personal details removed, not information about people the company never dealt with. Whether any state law reaches a particular dataset is for the company's counsel.

Should I tell the founder which AI developer would use the records?

No. You do not know, and SourceX describes Acquisition Partner anonymity, meaning a developer can source data without revealing its identity. Say the onward license is SourceX's own and that SourceX, not you, answers questions about use.

What if the founder still says no after a clear answer?

Accept it and close the thread. A founder can decline on reputation alone, and an introduction made without the decision maker's real interest is usually not a fit anyway.

Sources

  1. sourcex.si/how-it-works
  2. sourcex.si/investors
  3. refer.sourcex.si/who-qualifies
  4. refer.sourcex.si/terms
  5. legislature.vermont.gov/statutes/section/09/062/02430
  6. ftc.gov/news-events/news/press-releases/2024/01/ftc-…

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