What if our customers would be concerned? Split the worry before answering it: an escalation table that routes eight customer questions to the partner, the company, SourceX's review or a stop

Short answer

Take the concern at face value, then split it before answering. "Our customers would be concerned" usually bundles four questions: is it their material, what did we promise them, could they be recognized in it, and would they find out. An operating partner can answer only from published facts: client-owned material is usually not a fit, personal details are removed as the data is prepared, and nothing is shared without the company's approval. The company's own contracts and notices, read by its counsel, and SourceX's rights review answer the rest, and some answers end the conversation.

Visual briefFull-size diagram
A customer concern enters a four-step escalation: the partner answers from published facts, the company checks its own promises, SourceX's review settles rights and de-identification, and the last step is a stop when the records are the customers' material.
The escalation levels from the table on this page. Not legal advice; the company's counsel reads its own commitments.

The wrong move is to persuade. A founder who raises customers is often protecting the most valuable thing the company has, and a partner who argues past that concern teaches the founder that the partner's interest and the company's have come apart. Routing the concern to the person who can actually answer it does the opposite.

Four questions inside "our customers would be concerned"

  • Ownership: is it ours to license at all? Some records a company holds are really its clients' material, kept on their behalf.
  • Promise: what did we tell them? Contracts, confidentiality clauses and privacy notices can rule a use out before anyone looks at the records.
  • Recognition: could a customer be identified? Names and emails are the obvious part; a distinctive project or a single large account can be recognizable from its content alone.
  • Discovery: would they find out, and how would it feel? This one is about the relationship more than the records, and no document settles it.

Each has a different first answerer. Mixing them is how a partner ends up giving a legal-sounding answer to a relationship question, or a reassuring answer to a contract question.

The concern-to-review escalation table

Four levels, used in order. Level 1, the partner: published program facts only. Level 2, the company: its CEO and its counsel, reading its own commitments and judging its own relationships. Level 3, SourceX's review: rights, de-identification and scope, after the company applies. Level 4, stop: the answer rules the records out, or the company decides it does.

#What the founder saysThe question underneathFirst answererWhat can be said todayEscalates toStop when
1"Those records are really our customers'."OwnershipLevel 1, the partnerMaterial that belongs to clients is usually not a fit; only what the company owns or may license is in playLevel 3, rights reviewMost of the records turn out to be client-owned
2"Our contracts promise confidentiality."PromiseLevel 2, the company's counselRights review asks whether licensing would breach a client's confidentialityLevel 3, rights reviewCounsel finds a commitment that covers the records
3"Our privacy notice says we never share data."PromiseLevel 2, the company's counselThe supplier confirms personal data was collected lawfully; that is the company's statement to make, not the partner'sLevel 3, rights reviewThe notice rules the use out
4"Their names and emails run all through it."RecognitionLevel 1, the partnerCustomer details are removed, and records are de-identified through approved processing routes as part of preparationLevel 3, de-identification reviewThe records are mostly personal consumer data
5"A client could recognize its own project."Recognition by contentLevel 2, the CEOThe company approves the scope, so a record set or a client can be left outLevel 3, scope agreed with SourceXThe CEO will not accept the remaining risk
6"They would find out."DiscoveryLevel 1, the partnerSourceX's standard terms say neither side publicizes a deal; no partner can promise what a customer will learnLevel 2, counsel on noticesGoing ahead depends on a promise of secrecy nobody can give
7"Our biggest customer would be furious."RelationshipLevel 2, the CEONothing SourceX publishes measures how customers reactLevel 2, the CEO's judgment, which may include telling customersThe CEO decides the relationship outweighs the license
8"Other vendors promise customers they won't train AI on their data."Market normLevel 2, the company's counselSome vendors write such commitments into their customer terms; whether this company has one is a question for its own paperLevel 3, rights reviewThe company has made a commitment that covers the records

Row 8 deserves a concrete example. Zoom's published terms of service, to take one vendor, state that it does not use customer audio, video, chat or similar communications content to train its own or third-party AI models (our paraphrase). A company that has signed customer agreements containing a commitment like that has already answered part of the founder's question, and only its counsel can say how far the commitment reaches.

Method note. The table maps four kinds of concern onto the answerers SourceX's published pages assign: its screening guidance for ownership and rights, its process page for de-identification, scope approval and publicity, and its customer-disclosure guidance for notices, all checked 2026-10-27. The eight rows are typical phrasings written for this page, not quotations from founders, and no survey of founder concerns has been published. The table does not decide any company's rights; only counsel and SourceX's review do.

Published facts, pending answers and the part nobody can know

Published, and safe for a partner to say. The company must own the records or be able to license them without breaking a client's confidentiality, staff privacy or another party's contract. Client-owned material and personal consumer data are usually not a fit. The company approves the scope and terms and signs before any data is delivered, nothing is shared without its approval, and customer details are removed. SourceX's guidance on customer disclosure adds that disclosure terms with the Acquisition Partner are agreed rather than left open.

Pending, and not the partner's to answer. Whether a specific contract, notice or commitment allows the use; whether de-identified records could still point to one client; which record sets the CEO wants in scope.

Unknowable in advance. How any particular customer would react. SourceX publishes no data on it, and a partner who predicts it is guessing.

Further reading on the same boundary: the customer data objection response, whether customer consent is needed, customer contract data-use restrictions and the three-line script in when an owner asks whether this sells customers' data.

A founder with one demanding customer (Illustrative)

Illustrative. An invented company and an invented exchange; no outcome implied.

The founder-CEO of a 260-person managed IT services firm tells the fund's operating partner: "Our ticket history is full of client environments. If our largest client, a regional credit union, heard we licensed any of it, we would lose them."

The operating partner does not argue. "That is three questions, and I can answer one of them. SourceX usually turns down material that belongs to clients, and customer details are removed when the data is prepared. Whether your client contracts allow it is for your counsel, and whether the credit union matters more than any license is your call. You also choose the scope, so its tickets could stay out altogether."

The escalation runs from there:

  1. Level 1. The partner sends nothing but the published facts above, and mentions once that a reward exists if the firm licenses through this introduction.
  2. Level 2. The CEO decides the credit union's tickets stay out whatever happens, and asks counsel which of the other client agreements would matter.
  3. Level 3. If the CEO then applies, SourceX's rights review works from counsel's answer and the scope the CEO sets. The partner sees none of it.

If counsel finds the firm's standard agreement treats ticket content as the client's, the table says stop, and the partner records the date and closes the file.

A next step the founder can take or refuse

Offer one step and make the refusal just as easy. The lightest is the company fit checker, a preliminary, non-binding screen the founder can run alone; it settles nothing about customers but tells the founder whether the rest of the conversation is worth having. A founder who says "not while this client matters to us" has given a complete answer: note the date and the reason, and raise it again only if the founder does.

Where this table could steer a founder wrong

  • De-identification is not permission. Removing names answers row 4 and leaves rows 2 and 3 open. De-identification versus permission to license separates the two.
  • Commitments hide in paper nobody rereads. An AI-training clause can sit in a customer agreement signed years ago or in an order form's linked terms, as the Zoom example shows such clauses exist. The table only works if counsel actually reads them.
  • Relationship risk is real and unmeasured. A license can be lawful and still cost a customer. Nothing SourceX publishes quantifies that risk, and the table cannot.
  • Disclosure terms are agreed, not published. SourceX's guidance says disclosure terms with the Acquisition Partner are agreed, but their content is not public, so no partner can describe it in advance.
  • The partner is not neutral. A partner who stands to earn a reward has a reason to hear customer concerns as obstacles. Disclose the reward early, and let the founder decide whether the concern ends things.

How a fund runs this conversation across a portfolio is described for venture platform teams.

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 every customer concern the founder raised has an answer or a named answerer, and the founder still wants to talk, register as a partner, recheck the company against who qualifies and read the program terms before sending your link. Related founder-objection guides are in the guides library.

Routing a founder's customer concerns belongs to referral work; deciding whether SourceX itself merits an investment is a different exercise, and the SourceX investor overview is the place to request materials for it.

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

Should the company tell its customers before it licenses anything?

That is the company's decision, made with its counsel. SourceX's own guidance notes that some companies choose to tell customers and that counsel can advise on notices; a referral partner neither pushes for it nor talks the company out of it.

Can a partner promise that customers will never find out?

No. SourceX's standard deal terms say neither side publicizes a deal, but a partner has no basis to promise what any customer will or will not learn, and should say so.

Do customer concerns make a company a poor candidate?

Not by themselves. What decides it is whose material the records are and what the company has promised. A concern sent through the table can end in a narrower scope, a stop, or no change at all.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. refer.sourcex.si/how-it-works
  4. sourcex.si/how-it-works
  5. sourcex.si/insights/will-my-customers-find-out-i-licens…
  6. zoom.com/en/trust/terms
  7. 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