# Early data referral founder value | SourceX

Canonical: https://refer.sourcex.si/guides/the-first-ai-data-conversation-can-create-value-before-a-deal
Last updated: 2026-11-04

Run as discovery rather than a pitch, one permissioned, metadata-only conversation can tell a founder who controls each system, how many years of records survive, whether a retention setting is quietly deleting them and whether customer contracts limit reuse. Those answers help whether or not a license follows. They are learning, not financial value: only a completed, paid license creates a payout. SourceX has not published an approved real no-deal case, so the case below is Illustrative.

## What the company did not know before the conversation

Illustrative. A 160-person regional heating, cooling and plumbing services company has been run by its founder-CEO for 22 years. A peer-group chair who knows him well asks whether he would like a 45-minute conversation about whether the company's operating records might be licensed to train and evaluate AI systems. He agrees. Nothing changes hands except answers to questions about what exists. Were the company to apply later, SourceX would begin with a handful of questions and nothing uploaded; this conversation stays on that side of the line.

The founder walked in with five beliefs. The hour corrected or sharpened all five, and none of the corrections depended on a deal.

## Who owns the systems, and how much history survives?

The case asset is a before-and-after record of one hour. Every row is a question a partner can ask without seeing a single file.

| Question | What the founder believed | What the conversation surfaced | Decision it enabled |
|---|---|---|---|
| Who controls the field-service system? | "We do, it is our software" | The vendor-hosted system is administered by an outside implementation partner who holds the only admin login | Ask that partner to document admin access and export options, whatever happens next |
| How many years of records survive? | Ten years of everything | Work orders go back nine years; team chat keeps one year because a former IT contractor set a deletion rule | Review the retention setting with counsel before more history goes |
| How many full-time employees at peak? | "About 200 people" | 160 on payroll today and a peak of 174 full-time; 30 regular subcontractors do not count | Use 174 in any application; it clears the 50 threshold |
| Who can authorize a licensing discussion? | Perhaps the board | As CEO, the founder can authorize the discussion and sign | Nobody else's approval is needed to go ahead or to stop |
| Do contracts limit reuse? | Never considered | Service agreements with two property-management clients carry confidentiality clauses | Ask counsel to read them; rights stay unknown until review |

The chat row is not hypothetical as a mechanism. Slack keeps messages and files for the life of a workspace by default, but its help center says workspace owners can set content to be deleted after a chosen period, and the deletion is permanent. Microsoft documents that a Purview retention policy can retain content, delete it after a set period, or both. A founder who learns that a setting is erasing history has learned something with a deadline attached.

**Outcome.** The founder decided not to apply yet. He wanted the retention question and the contract clauses settled first. No application was submitted, so there was no review, no deal and no reward.

## Learning, readiness and a commercial outcome are different things

It is easy to blur these, and founders notice when a partner does. Keep them in separate columns.

| Level | What it means | Evidence | Money involved |
|---|---|---|---|
| Learning | The founder knows something new about records, owners or limits | The founder's own note of what changed | None |
| Readiness | Steps that make a later decision possible: an inventory owner named, retention reviewed, contracts read | Dated actions | None |
| Commercial outcome | A signed Dataset Deal Confirmation, data accepted at Closing and the company paid | Agreement and payment records | Only here; a partner reward can follow only after the company is paid |

In the case above the conversation produced learning and started readiness. It produced no commercial outcome, and calling it a success in money terms would be false.

## Decisions a founder can make after a no-deal conversation

- **Stop the loss.** Change or document a retention setting with counsel. Record-keeping and legal-hold duties come first; this is the company's decision, not the partner's.
- **Name an owner.** Give one person the job of keeping a metadata-only inventory: system, record type, years, approximate volume, administrator. The [metadata-only inventory guide](/guides/how-to-prepare-a-metadata-only-inventory-of-business-systems) has the columns.
- **Recover access.** Get written confirmation of admin rights from the implementation partner, which matters for audits, migrations and vendor changes as much as for licensing.
- **Read the contracts.** Ask counsel which client agreements restrict reuse of operational records.
- **Come back later, or never.** SourceX screens against the program in front of it, so a company that is wrong for today's need can be right for a later one. Deciding never to license is also a sound outcome.

The [value-killer checklist](/resources/what-reduces-data-value-for-ai-training) shows which of these findings tend to matter most if the founder returns.

## The real time cost, and what went wrong

A useful case records costs as carefully as benefits.

| Who | What they did | Time (Illustrative) |
|---|---|---|
| Founder | The 45-minute call, then 30 minutes confirming headcount and systems | 1 hour 15 minutes |
| Partner | The ask, scheduling, sitting in at the founder's request, a short follow-up note | 1 hour |
| Operations manager | Checking the chat retention setting and the admin login | 30 minutes |

Two negative moments belong in the record. The operations manager asked whether the call meant the company planned to replace staff with AI, and needed reassurance from the founder. The founder found the contract question unsettling, because he had assumed the records were simply his. Neither is a reason to avoid the conversation; both are reasons to warn the next founder what the hour may raise.

**How a real case would be collected.** SourceX has not published an approved real case, so here is the method. Get written consent from the founder and the partner before taking notes. Interview the founder within two weeks of the conversation and again at 90 days. Ask what they did not know before, what they did differently afterward and when, how many hours it took, what felt uncomfortable and whether they would take the conversation again. Keep dated evidence of each action, such as a retention change request or a contract review. Publish only with the company's approval. Until then, the figures are not published.

## When was the introduction useful enough to repeat?

Repeat the same kind of ask with a similar founder when all four hold:

1. The founder names at least one action taken within 90 days because of the conversation.
2. The founder's total time stayed inside what you agreed beforehand.
3. Nobody reported feeling pressed or misled.
4. You would ask the next founder the same way, with the same warning about what the hour may surface.

**A no-fit counterexample.** Illustrative. A 70-person outsourced bookkeeping firm agrees to the same conversation. Within twenty minutes it is clear that its richest records are its clients' books, and client-owned material is on SourceX's usually-not-a-fit list. The learning is narrower but real: the founder now separates the firm's own operating records from client data, and the partner knows not to approach similar firms on the strength of client records. Record it as a no-fit so the pattern is not repeated. If a referral is declined later in the process, [understanding why a referral was declined](/guides/how-to-understand-why-a-company-referral-was-declined) covers the usual reasons.

## Before you suggest the conversation

Check the published basics first: a peak of at least 50 full-time employees (contractors excluded), a documented operating history, rights to license, and a CEO who can authorize the discussion. 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. Keep to descriptions of records rather than the records themselves, and never introduce a company behind the CEO's back. Demand, rights and the scope of any license are SourceX's to assess after an application. The SourceX Channel Partner Agreement, once titled the Channel Partner Non-Circumvention and Non-Disclosure Agreement, has to be signed before a partner submits anyone. For a contrasting, explicitly hypothetical journey that does end in a paid reward, see the [Illustrative approved referral](/resources/approved-company-referral); to brief a founder before a call, use [how to help a founder prepare](/guides/how-to-help-a-founder-prepare-for-the-first-discovery-call). Peer-group chairs will find their own angle in the [CEO peer advisory page](/for/ceo-peer-advisory-group-chair-referral-opportunities).

| Term | Meaning here |
|---|---|
| Metadata-only conversation | Questions about what records exist, where, for how long and who controls them, with no records shared |
| Retention setting | A system rule that keeps or deletes content after a set period |
| Authorizer | The CEO, who can approve a licensing discussion and sign for the company |
| Actual Supplier Payout | The compensation SourceX pays the company itself for a completed, qualifying handoff; any partner reward is calculated on it |

## 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.

If a founder you know would benefit from an hour like this, [register for a partner link](/register), check the company against [who qualifies](/who-qualifies), read the [program terms](/terms), and agree how much of the founder's time the conversation may take before you ask.

## Sources

- https://slack.com/help/articles/203457187-Customize-data-retention-in-Slack
- https://learn.microsoft.com/en-us/purview/create-retention-policies
- https://sourcex.si/how-it-works
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
