Portfolio operations analysts hear the same request from founders and deal partners: "just send them what we have." What the company has is usually an inventory built for IT, security or privacy work, and almost none of it helps a licensing screen.
Two documents with different owners and different jobs
The quickest way to see the difference is to ask what each document is for.
| Question | Data inventory | Referral metadata |
|---|---|---|
| Who owns it | The company, usually its IT, security or privacy lead | The company as well; the partner only carries it |
| Why it exists | Running, securing and governing systems, and answering auditors or regulators | Letting SourceX decide whether a first call makes sense |
| Level of detail | System, table and individual data element | Company and record family |
| Typical size | Dozens to hundreds of rows | Seven lines |
| Who may read it | Staff and advisers bound by confidentiality | SourceX, once the CEO has approved every line |
| Cost if it travels too far | System details and possibly customer information exposed | Low: it describes the company, not its records |
Inventories are built to a depth no referral needs. NIST's Privacy Framework has an Inventory and Mapping category whose subcategory ID.IM-P6 reads "Data elements within the data actions are inventoried." Article 30 of the EU's General Data Protection Regulation asks a controller to keep a record of processing that covers purposes, categories of data subjects and personal data, recipients and, where possible, time limits for erasure, and to make it available to the supervisory authority on request. Those are compliance artifacts written at the level of individual fields and processing activities. A first licensing screen asks company-level questions.
SourceX's own entry point for owners is light for the same reason: its referral site invites companies to start a short assessment with no uploads, and the data inventory builder in its partner tools is described as something to send the company that lists the data it has, again with no uploads.
What the analyst gathers first, and from whom
Before any field is written, collect five facts in conversation. Each has a natural owner inside the company.
- Peak full-time headcount and its year, from the CFO or HR lead. Contractors are excluded; a staffing firm counts only its own full-time employees, not workers placed at clients.
- When the company's own records begin, from the person who runs the oldest system still in use or archived.
- The kinds of work the records describe, from department or operations heads, in plain words.
- Whether customer or partner material is mixed in, from the CFO or general counsel.
- The CEO's position: whether the CEO knows about the idea and wants a conversation.
Board packs and information-rights reports stay out. Anything the fund learned that way can prompt a question to the CEO; it never becomes a line in the referral. For a deeper interview script per department, the business data inventory worksheet is written for the company to use itself.
Minimum viable referral fields
The test for every candidate line is one question: would SourceX's decision about a first call change if this line were missing? If not, it stays in the inventory. Applied to SourceX's published screening profile, the test leaves seven fields.
| Field | Screening check it serves | What the inventory holds | What the referral carries |
|---|---|---|---|
| 1. Company and peak headcount | Size: 50+ full-time employees at peak, contractors excluded | HR extracts, org charts, payroll counts by month | One number, its year and who supplied it |
| 2. Location and record language | Geography and the 70% English rule | Office lists, hosting regions, data residency settings | Where the company operates and the language most records are written in |
| 3. Record families | Original documentation, and relevance, which SourceX judges in review | Table names, schemas, field dictionaries | Three to five families named by the work they record |
| 4. Span of years | Operating history | Retention settings, purge logs, archive locations | A start and end year per family, with the basis for each |
| 5. Origin and control | Rights to license | Contract registers, personal-data tags on fields | Who created the records, and whether client material or personal data is present: yes, no or unknown |
| 6. CEO status | An authorized sponsor | Nothing; inventories do not record it | Whether the CEO knows, wants a call, and the date that was confirmed |
| 7. Open questions and dated events | None directly; it protects the other six | Risk registers, vendor renewal dates | Up to three questions, each with who can answer, plus any documented access date |
Field 2 exists because location and language decide fit before anything else does. 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.
Some inventory content never travels with a referral at any stage of the partner's work:
- credentials, admin account names and access lists;
- system versions, hosting details and security controls;
- schemas, field lists and row counts by table;
- sample records, screenshots and exports;
- names of customers, employees or suppliers;
- the terms of vendor contracts.
One inventory reduced to seven lines (Illustrative)
Illustrative. The rental company below is invented, its figures and people are fictional, and nothing here implies an outcome.
A 26-year-old industrial equipment rental company keeps an IT inventory of 27 systems in a spreadsheet with eleven columns: system, version, hosting, admin accounts, tables, approximate rows, personal-data fields, retention setting, integrations, backup schedule and vendor renewal date. A deal partner asks the platform team to "send it over." The analyst instead drafts seven lines from three conversations and sends them to the CEO for approval.
| Field | Referral line as approved | Label | Left in the inventory |
|---|---|---|---|
| Company and peak headcount | About 240 full-time employees at peak, in 2024; contractors excluded | Reported by the CFO from payroll | Monthly headcount by site |
| Location and record language | Operates in the U.S. only; records in English | Reported by the CEO | Hosting regions for 27 systems |
| Record families | Rental contracts and returns; inspection and repair work orders; damage claims with dispute notes; dispatch and delivery logs | Reported by the operations director | 400-plus table names and field lists |
| Span of years | Work orders 2009 to today in the current system; rental contracts 2003 to today, with 2003 to 2011 in a read-only archive | Work orders from a system report; contracts estimated by the IT manager | Retention settings and archive server details |
| Origin and control | Created by the company's own staff; driver and customer contact fields present; customer contracts carry confidentiality terms nobody has read for this purpose | Reported; contract terms open | Personal-data tags for 61 fields |
| CEO status | Knows about the idea and wants a first call, confirmed 2026-10-20 | Reported by the CEO | Not applicable |
| Open questions and dated events | Do archived contracts link to later work orders? Do customer terms limit reuse? No documented access date | Open: IT manager and general counsel | Vendor renewal dates, backup schedule |
Twenty-seven systems became four record families. Nothing in the seven lines would help an intruder, and every line names a person who can be asked.
Labels that keep seven lines honest
A short summary hides weak evidence easily, so every line carries one of four labels.
- Reported: name the person and the date, such as "CFO, from payroll, 20 October."
- Estimate: give a range and who estimated it. Never round toward a threshold; "45 to 55 full-time at peak" is more useful than a confident "50+."
- Constraint: something that could narrow what is licensable, such as confidentiality clauses or personal data, stated as present, absent or unknown.
- Open: the question, who can answer it and when you asked.
A fuller treatment of gap tracking sits in recording what you do not know about a dataset. Seven lines plus labels is the minimum; a company that wants a longer founder-approved document can use the one-page referral brief.
Handing over the seven lines
- The CEO approves every line in writing. A reply to an email that quotes the lines is enough; edits come back to you, not around you.
- Check for earlier contact. Ask whether anyone at the company has applied, corresponded or opened an account with SourceX before. Under the terms, any earlier lead, account or email correspondence makes the company a duplicate, and it is not credited.
- Register and sign first. Whoever submits needs a partner account and must have signed the SourceX Channel Partner Agreement before any introduction goes in.
- Let the company apply. Credit attaches when the company itself files a verified application, and only the earliest valid introduction made inside the 90-day attribution window, for a company new to SourceX, receives it.
A 30-minute first call between the CEO, the records owner and SourceX can confirm the seven lines, hear how SourceX checks history, systems and rights, assign each open question and leave the company to decide what further detail, if any, it shares. The partner's part ends at the introduction.
Where the minimum is too little, or too much
- Unusual records. One line can undersell a record family nobody expects. Add a sentence of plain description, never a sample.
- Rights. Field 5 records what people know. SourceX's rights review, and counsel reading the contracts, decide what is licensable.
- Demand. SourceX checks relevance to its current data needs in review, and programs change. A clean summary can still be declined, and a decline under today's program does not rule the company out of a later one.
- Inventory pressure. If SourceX asks early for detail the seven lines leave out, the summary was too thin for that program. That is a reason for the company to share more directly, not for the partner to forward the inventory.
Method note. The seven fields map one to one onto SourceX's published screening profile and the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), both checked 2026-10-27, plus one field for open questions. The NIST and GDPR references show what inventories are built to hold; they are not requirements for a referral. The method does not measure record value, demand or acceptance, and it has not been tested on a cohort; no figures on how summary length affects outcomes have been published. To test it, log for each introduction whether SourceX's first call asked for anything outside the seven fields, and which field it would have belonged to. Related templates live in the guides library, including the bundle inventory referral brief and preparing a metadata-only inventory.
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 the CEO has approved all seven lines and confirmed there has been no earlier contact, the summary is ready to travel: get your partner link, set the seven lines beside the qualification page and read the program terms so you can answer the CEO's questions before the company applies.
Drafting a referral summary is network work. Readers weighing SourceX itself as an investment can request materials through the SourceX investor overview, as a separate decision.
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.