Shorter means fewer agenda items, not a promised number of minutes. SourceX has not published how long first calls take or how much a summary changes that, so this page measures something you can count yourself: questions asked on the call that a summary line had already answered.
Which first-call questions can be settled before anyone dials in?
Any question whose answer the company holds today. A question that depends on SourceX's own review cannot be settled in advance, and a summary that tries only adds a guess someone has to unwind on the call.
SourceX's published first step draws the line. The applying company lists its systems, its years of history and what each system can export; SourceX checks fit, completes the inventory with the company, runs its rights check and decides how the data would be processed, all before any records change hands. The company's half is what a good summary pre-answers; SourceX's half is what the call is for.
| Kind of question | Examples | Where it belongs |
|---|---|---|
| Known to the company today | Peak full-time headcount, the year its own records begin, which systems it runs, who wrote the records | Settled in the summary by the person who knows |
| Estimable by the company | Record counts, whether a system exports cleanly, which contracts might touch the records | In the summary with an estimate or open label, confirmed on the call |
| Answerable only in review | Fit with a current program, the outcome of the rights check, the processing route, whether a range can be indicated | On the agenda, never in the summary |
Machine learning has a precedent. The Datasheets for Datasets paper argues that every dataset should carry documentation of why it was made, what it contains and how it was collected, and accepts that creators will not answer every question, asking them to answer as many as they can. The same rule about gaps applies here: an honest blank beats a confident guess.
The call-ready context checklist
Twelve lines, in the order a reviewer tends to need them. The third column names the question each line takes off the call. The fourth names who in the company can confirm it, which is never the analyst.
| # | Summary line | Question it takes off the call | Confirmed by | If nobody knows yet, write |
|---|---|---|---|---|
| 1 | The CEO's name, and that the CEO asked for the call | Is the person who can say yes involved, and willing? | The CEO | Nothing: without the CEO's yes there is no summary to send |
| 2 | Peak full-time headcount and the year it peaked, contractors left out | Does the company clear the size bar of 50? | CEO or HR lead | "Payroll today is 74; the peak has not been checked" |
| 3 | The year the company's own records begin | How much history exists? | Operations lead | "Founded 2009; earliest record year not checked" |
| 4 | Each system in use, one per line, with the years it holds | Where would the records come from? | IT lead or each system's administrator | "Ticketing since 2016; CRM start year open" |
| 5 | Whether each system can export, as its administrator understands it | Can the records be pulled out without new tooling? | System administrator | "Export not tested" |
| 6 | A rough record count per system, with its basis | Is there enough to matter? | System administrator | "Order of magnitude only" |
| 7 | Who created the records: staff, customers or vendors | Are these the company's own records? | CEO or operations lead | "Mixed; share unknown" |
| 8 | Contracts that might limit reuse, named but not read | What could narrow the rights? | Counsel, later | "Customer agreements exist; none read for this" |
| 9 | Where the company operates and the language of its records | Which country rules apply? | The CEO | "Offices in two countries; language mix not measured" |
| 10 | Kinds of personal information inside the records | What has to come out before anything moves? | Operations or privacy lead | "Customer names and phone numbers appear in tickets" |
| 11 | Any earlier contact with SourceX by anyone at the company | Is this a new company for SourceX? | The CEO | "Not yet asked", and ask before submitting |
| 12 | A dated event such as a migration, a tool shutdown or a scheduled deletion | Is there a real deadline? | IT lead | "None known" |
Line 11 matters more than it looks. Section 3 of the terms reads an earlier relationship broadly: "A relationship includes any earlier lead, account or email correspondence between SourceX and the company, however it began." A CEO who once filled in a form is worth knowing about before anyone writes an introduction.
Left off the checklist on purpose: samples, exports, screenshots, board materials, payout guesses and any sentence saying the company qualifies. Each one either puts records in the analyst's hands or answers a question that belongs to SourceX.
Collecting the context without opening a single record
The context comes from one conversation with the CEO or the operations lead, about twenty minutes, and from what the company says about itself. Four lines are the minimum before a summary is worth sending: the CEO's yes (line 1), peak headcount (line 2), the systems list (line 4) and who created the records (line 7). Without those four, the first call turns back into a screening call.
What the fund already knows from board packs or information rights stays out, because it came in confidence. If a fact matters, ask the CEO to state it and label it as theirs.
A filled summary, line by line (Illustrative)
Illustrative. A generic company with invented facts; no outcome is implied. A 140-person commercial HVAC service company, founder-led, with the fund as a minority investor.
| # | Line as sent | Label |
|---|---|---|
| 1 | The founder-CEO asked for a call after the platform lead raised data licensing at a quarterly check-in | Confirmed |
| 2 | Full-time headcount peaked at 152 in 2023 and is 140 today; seasonal contractors excluded | Confirmed |
| 3 | The company's own service records start in 2011 | Confirmed |
| 4 | Accounting system since 2011, shared drive of job reports since 2013, parts inventory since 2015, field-service platform since 2017, customer helpdesk since 2019 | Confirmed |
| 5 | The administrator believes the field-service platform and helpdesk have built-in exports; the drive is plain files | Estimate: not tested |
| 6 | About 90,000 work orders in the field-service platform; helpdesk volume not counted | Estimate: one count in 2025 |
| 7 | Work orders and job reports are written by the company's own technicians; customers only sign off | Confirmed |
| 8 | Customer service agreements exist; nobody has read them with data reuse in mind | Open: counsel |
| 9 | Operates in two U.S. states; records are in English | Confirmed |
| 10 | Work orders contain customer names, site addresses and phone numbers | Confirmed |
| 11 | The CEO says nobody at the company has contacted SourceX | Confirmed |
| 12 | The field-service contract renews in March and the CEO is weighing a switch | Estimate: undecided |
Eight lines are confirmed, three are estimates and one is open. Those four labeled lines, plus four questions only SourceX can answer, make the agenda:
- Confirm what the field-service platform and helpdesk actually export (line 5).
- Agree how volume will be counted, and by whom (line 6).
- Decide whether the March renewal changes the timing (line 12).
- Name who will read the customer agreements (line 8).
- SourceX's view of fit with its current programs.
- What the rights check will look at.
- How the data would be processed if a deal went ahead.
- What an indicative range would depend on, and when one could be given.
Sixteen questions would have reached the call without the summary; eight remain. That is the whole claim, and your next call can check it.
Labels that stop an estimate hardening into a fact
Every line ends with its label, and forwarding never changes it. An estimate names its basis, such as an administrator's recollection or one count taken last year. An open line names who will answer it. A constraint the company sets, such as "no HR records", is a confirmed fact about scope. The CEO's edits win, and the summary carries its approval date. How to label estimates in a founder referral brief goes deeper, and what founders think data licensing means before the first call helps when the CEO's picture of licensing needs checking.
The handoff, in the order it happens
- The CEO approves the text in writing. A reply to the draft is enough.
- The person who will submit has signed the SourceX Channel Partner Agreement. Section 1 of the terms requires it before any introduction.
- The introduction is submitted with the approved summary pasted in. Nothing is attached.
- The company applies itself through the partner link, describing its own systems.
- The analyst steps back. SourceX and the company hold the call.
A good summary earns nothing by itself: credit follows dated records and a verified application under section 2, and section 3 treats a company SourceX already knew as a duplicate. If a portfolio review is about to cancel tools, the archive context checklist for portfolio operations reviews handles the timing.
Where a short summary backfires
- An estimate repeated as fact. A volume figure in an introduction gets repeated; if review finds a tenth of it, the next introduction pays for it. The basis note on every estimate is the defense.
- Confidential knowledge leaking into a line. A sentence that could only have come from a board pack is a breach, however useful it looks.
- Rights read too early. Naming a contract in line 8 is not clearing it. FTC staff warned in February 2024 that moving to looser data practices, AI training included, through a quiet retroactive change to terms or a privacy policy may be unfair or deceptive. Customer-facing promises can narrow what a company is free to license, and only counsel and SourceX's rights check can judge them.
- Demand moves. The screening profile says requirements follow SourceX's current data needs, so a flawless summary can still meet "not now".
- The CEO may want to tell it. Then the twelve lines become the CEO's notes, which is a fine outcome.
Methods note. The checklist was built on 2026-10-27 from SourceX's published apply-and-qualify step, the screening profile on who qualifies, sections 1 to 3 of the program terms and the question families in Datasheets for Datasets. It does not measure call length, acceptance or payout, and SourceX has published no baseline for any of them. To test it, count on each of your next five calls the questions a summary line had already answered; more than two per call means the lines are too vague. The company fit checker is a quicker, non-binding screen when even the four minimum lines are missing.
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 the CEO has approved all twelve lines and asked for the call, register as a partner, hold each line up against the published screening profile and keep the program terms open while you submit. Platform teams setting this up across a portfolio can start from the overview for venture platform teams.
Preparing a referral summary and judging SourceX as a possible investment are two different pieces of work; for the second, go to the SourceX investor overview and request investor materials there.
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.