# Data referral brief template a CEO approves | SourceX

Canonical: https://refer.sourcex.si/guides/the-one-page-data-referral-brief-a-founder-can-approve
Last updated: 2026-11-05

A data referral brief is one page that the company's CEO approves line by line before anything about the company reaches SourceX. It holds metadata only: full-time headcount at peak, record types, years, systems, who owns the records, known constraints, what the CEO wants to learn and the questions nobody can answer yet. Every line is tagged with who supplied it and whether it is a fact, an estimate or an open question. Nothing from board materials, and no records, samples or logins, goes on it.

A portfolio operations analyst often knows more about a portfolio company than any outside introducer: headcount from board packs, systems from operating reviews, history from diligence. The brief is the one document where that knowledge must not appear unless the CEO restates it. It does not sell the company. SourceX's first step is a few questions with no files, so the brief exists to make that conversation faster and more honest, and to carry the unknowns forward.

## Who drafts it, who approves it and where it goes

| Role | Does | Does not |
|---|---|---|
| Analyst | Drafts from a conversation with the CEO or the person the CEO names, and tags every line | Fill gaps from board packs, diligence files or guesses |
| CEO | Approves, edits or strikes each line, and authorizes the discussion | Approve the page in one click without reading the lines |
| Relationship owner | Sends the approved page with a dated, written introduction, after signing the SourceX Channel Partner Agreement | Add commentary, a valuation or a forecast |
| SourceX | Reviews fit, completes the inventory with the company and runs the rights check | Receive a conclusion it is expected to confirm |

If one person plays two roles, the CEO's approval still comes before anything leaves the fund.

## What the analyst may use, and what stays out

| Where the fact came from | On the brief? | Tag it as |
|---|---|---|
| The CEO, in writing or on a call they agreed to | Yes | CEO-stated |
| A sponsor the CEO named, with the CEO's approval | Yes | Sponsor-stated, CEO-approved |
| A public record, such as the company's site or a registry filing | Yes, once the CEO confirms it is current | Public, with the date checked |
| Board packs, investor updates or information-rights reports | Only if the CEO restates it for the brief | Never "from our files" |
| The analyst's own impression or estimate | Only as an open question | Open |
| Customer names, employee names or the contents of any record | No | Not applicable |

The reason for the fourth row is contractual as well as courteous. NVCA's model management rights letter, for example, provides that information an investor receives under it is governed by the confidentiality terms of the Investors' Rights Agreement, and that those obligations survive after the management rights end (a paraphrase of the letter's terms as excerpted). Your fund's own documents decide the details. The working rule does not change: board knowledge is a reason to ask the CEO, never content for the brief.

## The founder-approved referral brief

Fourteen lines in three groups. Each line gets a tag and a box for the CEO's tick.

| No. | Line | What to write | Allowed tags |
|---|---|---|---|
| 1 | Operating entity | The legal entity that employs the staff and holds the records | Fact |
| 2 | Location and record language | The entity's country and the language most records are in | Fact |
| 3 | Full-time employees at peak | The peak number and its year, contractors excluded | Fact or estimate |
| 4 | Operating history | Year founded and the earliest year records survive | Fact or estimate |
| 5 | Record types | Plain names: work orders, QA records, support tickets, project files | Fact |
| 6 | Systems and administrators | System type and who administers it, by role | Fact |
| 7 | Rough volumes | Counts or ranges, each with its basis | Estimate |
| 8 | Ownership | Whether the company created the records, and any material that belongs to clients | Fact or open question |
| 9 | Known constraints | Customer contract terms, privacy duties, any earlier license for AI training | Fact or open question |
| 10 | Earlier contact with SourceX | Any application, account, lead or email exchange, as far as the CEO knows | Fact or open question |
| 11 | The authorizer | The CEO's name and the date the CEO agreed to a conversation | Fact |
| 12 | Company-side contact | Who prepares, if the CEO names someone | Fact |
| 13 | What the CEO wants to learn | Two or three questions in the CEO's own words | CEO-stated |
| 14 | Left out on purpose | Records, samples, exports, credentials, board materials, customer and employee names | Standard |

Under the table, two lines close the page. A disclosure: "The sender is a registered SourceX partner and may receive a referral reward if a licensing deal with this company is completed and paid; SourceX pays it separately and it never comes out of the company's payment." And an approval line: "Approved by the CEO on [date]. Recheck after 60 days."

Lines 1 to 4 carry the published fit facts: 50 or more full-time employees at peak, contractors excluded, and years of records the company created itself. Line 2 settles location. 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. Line 10 exists because the terms treat any earlier application, relationship, lead, account or email correspondence with SourceX as making a company a duplicate; the CEO may not know about every email a colleague sent, so "as far as the CEO knows" is the honest tag, and SourceX checks its own records. If the operating entity sits inside a group, note it on line 1: a parent and its subsidiaries share one reward cap.

Lines 8 and 9 deserve the most care. NIST's AI Risk Management Framework puts it this way: "Maintaining the provenance of training data and supporting attribution of the AI system's decisions to subsets of training data can assist with both transparency and accountability." It also notes that training data may be subject to copyright and should follow applicable intellectual property rights laws. Rights get examined closely downstream, which is why a brief that guesses at them does the company no favors.

## Label estimates, constraints and unanswered questions

Four rules keep the tags honest:

1. **An estimate names its basis and its author.** "About 90,000 work orders, the IT manager's figure from the system's record counter."
2. **A constraint is written as the CEO stated it.** Do not soften "two customer contracts restrict sharing" into "minor contract questions."
3. **An open question names who can answer it.** The CEO, the company's counsel or SourceX in review.
4. **No tag is upgraded in transit.** An estimate stays an estimate through every forward, and the approved brief is never edited afterward to match what review found.

**A completed brief (Illustrative).** A portfolio company: a 175-person contract packaging manufacturer. Generic facts, no real company.

| No. | Entry | Tag | Supplied by |
|---|---|---|---|
| 1 | The operating company; its holding company holds no records | Fact | CEO |
| 2 | United States; records in English | Fact | CEO |
| 3 | 175 full-time employees at peak in 2025; about 40 seasonal contractors not counted | Fact | CEO, from payroll |
| 4 | Founded 2009; quality records survive from 2012 | Fact | Quality manager, CEO-approved |
| 5 | Batch records, non-conformance reports, corrective actions, maintenance work orders | Fact | Quality manager |
| 6 | An ERP and a quality management system, both run by the IT manager | Fact | IT manager |
| 7 | About 14,000 non-conformance reports and 90,000 work orders | Estimate | IT manager, from record counters |
| 8 | Records written by staff; some batch specifications come from customers | Open | Company counsel to say which |
| 9 | Two customer contracts restrict sharing of specifications | Open | Counsel, then SourceX's rights review |
| 10 | No application or account; the CEO knows of no earlier emails | Open | SourceX checks its own records |
| 11 | The CEO agreed to a conversation on the approval date | Fact | CEO |
| 12 | The quality manager prepares | Fact | CEO |
| 13 | What would leave the building and who would see it; how much quality-team time it takes | CEO-stated | CEO |
| 14 | No records, samples, exports, credentials, board materials, customer or employee names | Standard | Template |

Three of the fourteen lines are open, and that is a strength. The CEO struck one draft line, a revenue figure the analyst had taken from an investor update, because it did not belong on the page.

## Prepare the authorized handoff and first-call agenda

The handoff runs in four steps. The CEO approves each line, by initials or by a reply listing what to strike. The registered partner sends the page with a dated, written introduction. That date matters later. If credit is due, SourceX decides it from dated records: it goes to the first valid introduction made inside the 90-day attribution window, and only once the company submits a verified application. The company then applies itself, which means a few questions and no files. The analyst files the approved page, and nothing else, in the fund's records.

A suggested agenda the CEO can bring to the first call; SourceX sets its own format.

| Minutes | Item | Led by |
|---|---|---|
| 5 | The CEO's questions from line 13 | CEO |
| 10 | What qualification covers: the inventory, the rights check and the processing route, with no records shared at that stage | SourceX |
| 10 | The open questions on lines 8 to 10, and who will answer each | CEO and SourceX |
| 5 | What happens if it is not a fit, and the next decision with its owner | Both |

Related: a workflow-specific [commission reconciliation brief template](/resources/broker-commission-reconciliation-referral-brief-template), the [warm introduction brief](/resources/a-warm-introduction-brief-for-a-business-owner) that goes to the owner first, the [brief generator](/tools/client-opportunity-brief-generator) and [preparing a founder for the first call](/guides/how-to-help-a-founder-prepare-for-the-first-discovery-call).

## Where a one-page brief misleads

- **It can read as an endorsement.** A page from a fund about a portfolio company can look like a claim that the company fits. Fit is decided in SourceX's review, and funding status is not one of the checks.
- **Estimates harden.** After two forwards, "about 14,000" becomes "14,000". Keep the tags in the words, not in a color.
- **Approval under pressure.** A CEO approving an investor's draft may leave in lines they would rather strike. Offer a shorter page and mean it.
- **Facts go stale.** Headcount, contracts and system owners change; recheck an approved page after 60 days.
- **Rights and demand are unknown.** Client-owned material is usually not a fit, and relevance to current data needs is checked only in review. A brief declined for one program can still be worth keeping, since a later program may suit the company.

**Methods note.** The template was built on 2026-10-27 from the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's who-qualifies and process pages, NVCA's model management rights letter and NIST AI 100-1. It has not been tested in a measured study. To test it, track three things across a fund's briefs: how often SourceX's review changed a line tagged as fact, how many open questions were resolved and by whom, and how many briefs led to a verified application. Those figures are not yet published. Questions about companies SourceX may already know are answered in [what happens if the company was already known to SourceX](/questions/what-happens-if-the-company-was-already-known-to-sourcex), and the portfolio view of the program is in the [overview for venture platform teams](/for/venture-platform-teams). More templates sit in the [guides](/guides).

## 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 a CEO has approved every line, [register for a partner link](/register), check the page against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you send the brief with your written introduction.

Readers looking at SourceX as an investment, rather than as a program for portfolio introductions, can request investor materials separately 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://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://nvca.org/wp-content/uploads/2019/06/NVCA_Model_Management-Rights-Letter.doc
- https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf
- https://sourcex.si/investors
