# A shareable referral summary for a founder's team | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-founder-wants-a-summary-they-can-share-internally
Last updated: 2026-11-05

Draft it for the CEO to own, not for you to circulate. Keep it to one page: what SourceX does in its own published words, what the company would decide and who decides it, the published fit criteria, what stays unknown until SourceX reviews, what you may be paid and that it never reduces the company's payment, and where to take questions. Leave out anything you know from board materials, any estimate and any talk of buyers. Label it for the company only, send it to the CEO alone, and let the CEO decide who reads it.

This page is for the counsel liaison or platform lead at a fund whose portfolio or network CEO has said some version of "send me something I can forward to my team." The request is a good sign and an information risk at once. A partner's summary, once forwarded, speaks for the partner in rooms the partner never enters, to readers it cannot correct. If the founder would rather explore SourceX without naming the company yet, that is a different request, covered in [when a founder wants an anonymous first conversation](/guides/when-a-founder-wants-an-anonymous-first-conversation).

## Who reads it after the CEO

The CEO decides the audience, but the drafter should know who it is likely to be, because each reader brings a different question.

| Reader | Why the CEO might send it | What they need from the brief | What must never be in it for them |
|---|---|---|---|
| Leadership team | To test interest and gauge the work involved | What SourceX does, what the first step asks of the company, what is unknown | Estimates of what the company might receive |
| Board | To inform directors or gather views | Who decides, and the drafter's financial interest stated plainly | Anything taken from the fund's own board materials or about other investors |
| Heads of the teams that keep the records | To prepare for questions about systems | That the company describes its own systems when it applies | Any request for files, samples or access |
| Company counsel | To look at rights and contracts | Links to SourceX's terms and process page | A legal view from the drafter, who gives none |

The board row needs a second look. Boards often include other investors, so a brief sent to directors may reach other funds. Nothing in it should describe the fund's other companies, its other investors or its expectations of reward beyond the plain disclosure.

## The approved internal briefing template

Eight blocks, in this order. The draft wording rests on SourceX's published pages, so the CEO can check every line; the CEO may cut or reword anything, and once edited it is the company's document.

| Block | Draft wording | Rests on | Who may change it |
|---|---|---|---|
| Header | "Prepared by [name, firm] at [CEO]'s request on [date]. For [Company] internal use; [CEO] decides any wider circulation." | This page's method | The CEO |
| 1. What SourceX does | "SourceX licenses records that companies created in their own work, for AI training and evaluation, and deals with the company directly." | SourceX's process page | The CEO |
| 2. The first step | "We would apply ourselves. It starts with a few questions, no files are needed, and no records are shared at that stage. We would approve scope and terms, and sign, before any data is delivered." | SourceX's process page | The CEO |
| 3. Who decides | "Our CEO decides whether we talk to SourceX and signs for the company." | SourceX's screening page | Nobody |
| 4. Fit as SourceX publishes it | The size rule, records over several years, rights to license, the location sentence below, and "may be a fit; SourceX decides after review" | SourceX's screening page | Nobody, beyond trimming |
| 5. What nobody knows yet | "Whether we would be accepted, which records would be in scope, and any payout. A payout is fixed only in a signed Dataset Deal Confirmation; earlier estimates are indicative." | SourceX's process page | The CEO |
| 6. The drafter's connection | "[Firm] has signed SourceX's Channel Partner Agreement and may receive a reward from SourceX if [Company] completes a qualifying licensed transaction. SourceX pays it separately and it never reduces what [Company] is paid. The formula and cap are in section 4 of SourceX's program terms." | Terms sections 1 and 4 | The CEO may move it, never delete it from a version the drafter sends |
| 7. What the drafter has not shared | "[Firm] holds none of [Company]'s records and has given SourceX nothing about [Company] that [CEO] did not approve." | Sample agreement section 4.2 | Nobody |
| 8. Questions | "Program questions: SourceX's terms and process page. Questions about our rights to our records: our own counsel." | This page's method | The CEO |

Block 4 should carry SourceX's location rule word for word, since a paraphrase is where errors creep in: 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. The size rule is 50 or more full-time employees at the company's peak, contractors not counted.

Block 6 rests on section 4 of the terms, which says the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation." A company receives the same amount whether or not a partner was involved, and the people deciding should know that the person who drafted their briefing may be paid.

The header borrows an idea from security teams. FIRST's Traffic Light Protocol gives shared information a label for how far it may travel, and its version 2.0 definitions say that "TLP:AMBER+STRICT restricts sharing to the organization only," while plain AMBER also allows need-to-know sharing with the recipient's clients (paraphrase). The colors are beside the point; what is worth copying is that the label names the circle and that the source, here the CEO, is the one who can widen it. A label is a request, not a contract, and it binds nobody.

**Method note.** The template was assembled on 2026-10-28 from SourceX's process page for companies, its screening page, the program terms (version 2026-10-22.2, since replaced by version 2026-11-04) and sections 1.9, 4.2, 4.5 and 4.6 of the unsigned sample Channel Partner Agreement (version 2026-10-19), with the labeling idea from FIRST's TLP 2.0. Each block was kept only if a reader in the table above needs it to decide something. No company has reported using it, and it interprets no one's confidentiality duties.

## What stays out, even when the founder asks for it

Founders often ask for exactly the lines that would make the brief misleading. Each request below has a reason to decline that the founder can check.

- **"Add what we might earn."** No one can support a figure. SourceX's process page says the payout is fixed in the signed Dataset Deal Confirmation, the terms call portal and calculator estimates projections, and section 4.6 of the sample agreement bars a partner from telling a referred company that an estimate or a show of interest secures a purchase or a reward.
- **"Say who would buy the data."** A partner does not know. Section 1.9 of the sample agreement says the Acquisition Partner's identity and contract may remain confidential.
- **"Put in what the board saw about our systems."** The CEO may write that in the company's own words. The drafter does not, because SourceX's screening page treats what a fund knows from board packs or information rights as a reason to ask the CEO, never as material to pass along.
- **"Add the SourceX logo so it looks official."** Section 4.5 of the sample agreement grants no trademark license. SourceX's name in plain text, with links, does the job.
- **"Say SourceX recommends this for us."** SourceX has recommended nothing; it decides after review.
- **"Just say we qualify."** "May be a fit; SourceX decides after review" is the screening page's own wording, and it is the accurate one.

The same discipline applies to rights and legal questions: a brief that says the company's contracts allow licensing makes a promise the drafter cannot keep, as [what not to promise about legal compliance](/guides/what-not-to-promise-about-legal-compliance-in-an-intro-email) explains.

## A request, a draft and three edits (Illustrative)

Illustrative. The founder-CEO of an invented 180-person regional field-services company asks a fund's platform lead for "a page I can send my leadership team." The platform lead sends the eight-block draft to the CEO only, with the header filled in. The CEO edits it.

| Line in the draft | The CEO's edit | What the drafter does |
|---|---|---|
| Header: "For [Company] internal use" | Adds "leadership team and board" | Accepts; mentions that the board includes outside investors, and the CEO keeps the change |
| Block 6, the drafter's connection | Asks to drop it: "the team doesn't need that" | Asks to keep it, since readers should know who may be paid; the CEO keeps it, shortened |
| Block 5, what nobody knows yet | Asks to add "expected payout range" | Declines, citing the process page and section 4.6; the CEO leaves block 5 as drafted |

The CEO also adds the head of operations as the internal contact for questions. That is the CEO's choice and changes nothing about who decides: block 3 still names the CEO. Briefs that executives find credible tend to be short and checkable; [what makes a referral brief credible to an executive](/guides/what-makes-a-referral-brief-credible-to-an-executive) sets out a way to test that.

## If it goes further: questions, a no, or an announcement

**Readers ask questions.** Program questions go to SourceX's published pages, and questions about this company's records go to SourceX once the company applies. The drafter answers neither on the company's behalf.

**The CEO decides against it.** The brief stays the company's. The drafter's record shows the date of the answer and nothing else, and no follow-up campaign starts.

**Someone wants to announce it.** The brief is never quoted in public. SourceX's process page says "Neither side publicizes the deal," and section 4.5 of the sample agreement requires written authorization before either side publicly identifies the other as a partner. If a company later approves a case study, [using it without promising the same result](/guides/how-to-use-an-approved-referral-case-study-without-promising-the-same-result) covers the next step.

**The CEO withdraws after an introduction.** Tell SourceX only that the CEO asked to stop.

## Where the template can mislead

- **A label is not a lock.** A company-only header asks; it does not prevent forwarding, and a forwarded brief still carries the drafter's name.
- **Briefs go stale.** Section 11 of the terms says SourceX may publish new versions. Date the brief, and redraft rather than re-send an old one.
- **Groups complicate the audience.** A parent and its subsidiaries share one reward cap, and if the brief reaches a parent's board, credit questions among related companies are for SourceX to decide in duplicate review.
- **Rights are not settled by a brief.** Whether the company can license its records is decided in SourceX's rights review and by the company's own counsel, not by anything a partner writes.
- **Nothing here is measured.** Whether a short internal brief changes how leadership teams respond has not been published; a fund could record, per brief, whether the CEO edited it and whether the company applied.

## 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 asks for something to share, [register as a partner](/register) first if you have not signed, build block 4 from [who qualifies](/who-qualifies) and block 6 from section 4 of the [program terms](/terms), and send the draft to the CEO alone. Related questions sit in the [guides hub](/guides).

Preparing a founder's internal brief is part of making an introduction; assessing SourceX as a possible investment is a separate exercise, and materials for it can be requested through 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://www.first.org/tlp/
- https://sourcex.si/how-it-works
- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/investors
