For a portfolio operations analyst, the summary is usually the only thing about the company that leaves the room, so write it as if the company's customers were reading over your shoulder.
The altitude test: four ways to describe the same history
Every sentence about a company's records sits at one of four altitudes. The bottom two carry the records' content. The top two describe the records without carrying them, and a referral summary lives there.
| Altitude | What it contains | Example (Illustrative) | In the summary? |
|---|---|---|---|
| 1. Record | A file, export, screenshot, login or sample | "Attached: 50 closed work orders, names removed" | Never |
| 2. Excerpt | A quoted note, a customer or employee name, an amount, a contract term | "Their biggest hospital client logs every chiller fault with them" | Never |
| 3. Fact | A count range, a year span, a system type, who created the records | "Several hundred thousand work orders since 2012, written by its own technicians" | Yes, labeled reported or estimated |
| 4. Category | The kind of work the records follow | "Commercial HVAC repair and maintenance, from call to closure" | Yes |
Redaction does not move a sentence up the ladder. A work order with the names blacked out is still a record: it keeps the fault, the fix, the timing and often enough detail to identify the site.
There is a legal reason for the top two rungs too. Under 18 U.S.C. 1839(3), information is a trade secret only if its owner has taken reasonable measures to keep it secret and it derives independent economic value from not being generally known. A fact-altitude summary says the records exist without circulating the content that gives them value. Whether particular records qualify is for the company's counsel; this is general information, not legal advice. The SourceX Channel Partner Agreement points the same way, keeping confidentiality obligations for three years, and longer for trade secrets while they remain legally protected.
Seven facts to collect, and who supplies them
The summary needs seven facts, given in conversation by the CEO or by someone the CEO names. None comes from board decks, data rooms or monthly reports. SourceX's who-qualifies guidance treats what a fund learned through board packs or information rights as a reason to ask the CEO, not as material to pass on.
| Fact | Ask it as | Write it as | Leave out |
|---|---|---|---|
| Peak headcount | "What was full-time headcount at its peak, and when?" | "About 260 full-time at peak (2024); contractors not counted" | Payroll figures, names |
| Work recorded | "Which work do your records follow from start to finish?" | A category, in the company's own words | Example records |
| Start year | "Since when have you kept those records yourselves?" | A year, plus any system change | Gaps you have not asked about |
| Volume | "Roughly how many? A range is fine" | An order of magnitude, labeled as an estimate | Counts by customer |
| System | "What kind of system holds them, and is the old one still readable?" | A system category, current and retired | Hostnames, admin accounts, settings |
| Creator | "Who writes them: your staff, your customers or vendors?" | "Its own technicians and dispatchers" | Individual names |
| Authorization | "Do you want a licensing conversation, and has the company spoken with SourceX before?" | "CEO wants the call; no earlier contact known" | Anything the CEO has not approved |
The last row affects credit. Under the program terms, an application, lead, account or email correspondence the company already has with SourceX makes it a duplicate, and a later partner gets no credit for it. Record the CEO's answer in the summary rather than finding out after the introduction.
History summary examples: one company drafted three ways (Illustrative)
Illustrative: the contractor below is invented, and nothing here predicts how a review would end.
The company is a 260-person commercial HVAC service contractor, founded in 2007 and still run by its founder as CEO. Three drafts describe it.
Draft A, exposed. "Great fit. They service two hospital systems and a university, named in full here. Attached are 50 work orders from last month with technician names removed, plus a screenshot of their dispatch board. Their ops lead can give SourceX a read-only login. Margins are thin, so they'd love the revenue."
The faults: customer names, attached records, a screenshot, an offer of credentials and a remark the CEO never approved.
Draft B, hollow. "Huge amounts of valuable data, perfect for AI. Very established. Owner is keen."
The fault: nothing in it can be tested, and "keen" is not the CEO's approval.
Draft C, useful. Six lines, approved by the CEO on the date shown at the top:
- Company. Commercial HVAC service contractor in the U.S., founded 2007; about 260 full-time employees at peak (2024), contractors not counted.
- Work recorded. Service calls from request to closure: dispatch, technician notes, parts used, follow-up visits and customer sign-off.
- Span and volume. Company-created records since 2012 in its current field-service system; several hundred thousand work orders (CEO estimate, order of magnitude).
- Older history. 2007 to 2012 sits in a retired system kept read-only; whether it still opens is unknown.
- Unknowns. Service contracts with large customers contain confidentiality clauses nobody has read for this purpose; technician notes may name site contacts.
- Authorization. The CEO wants a conversation and approved this text; no earlier contact with SourceX is known.
| Draft A sentence | Draft C rewrite | What changed |
|---|---|---|
| "They service two hospital systems and a university" | "Commercial HVAC service contractor in the U.S." | Excerpt to category |
| "Attached are 50 work orders" | "Several hundred thousand work orders since 2012 (CEO estimate)" | Record to fact |
| "A screenshot of their dispatch board" | "Current field-service system; retired system kept read-only" | Record to fact |
| "Their ops lead can give a read-only login" | Removed | Credentials never travel |
| "They'd love the revenue" | "The CEO wants a conversation and approved this text" | Opinion to authorization |
Two shorter summaries show how line 5 changes with the business model (Illustrative):
- A 140-person freight audit and payment firm. Work recorded: carrier invoice audits, disputes and resolutions since 2014. Line 5: much of the audit trail may belong to shipper clients under their service agreements, and client-owned material is usually not a fit; the firm's own dispute procedures and quality reviews are its own.
- A 95-person claims administrator. Work recorded: claim handling for insurer clients since 2010. Line 5 carries the decisive point: most claim files are held for clients, so the summary describes only what the company created for itself, such as procedures, quality reviews and training material.
The honest fifth line saves everyone's time: stated up front, the client-ownership question lets SourceX decide quickly.
Label every line as reported, estimated or unknown
Each fact carries one of three labels, and the summary says whose word it is.
| Label | Meaning | Example (Illustrative) |
|---|---|---|
| Reported | Stated by the CEO or someone the CEO named, not checked | "Founded 2007" |
| Estimated | An order of magnitude or a range, never a count | "Several hundred thousand work orders" |
| Unknown | Nobody at the company has answered yet; counsel or SourceX's review will | "Whether customer contracts limit reuse" |
Five unknowns turn up in almost every summary: what customer contracts allow, how much personal information sits in free-text notes, whether migrated history is complete, whether retired systems still open, and whether the records match a current program. The last is never the partner's call; SourceX checks relevance to its current data needs during review.
The context lines matter for a second reason. Among the ways AI risks differ from traditional software, NIST's AI Risk Management Framework lists that datasets used to train AI systems may become detached from their original and intended context. Lines 2 to 4 record that context while the people who know it are still at the company; that is a reason to keep them accurate, not a claim about how any reviewer or Acquisition Partner uses them.
Method note. The altitude test, the seven facts and the drafts were built from the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's who-qualifies page, 18 U.S.C. 1839 and NIST AI 100-1, all checked on 2026-10-27. They have not been tested with CEOs or reviewers, and SourceX has not published how summary quality affects review; those figures are not yet published. To measure it, record for each introduction the lowest altitude any line reached and whether review had to ask for a correction.
The approved handoff and a first-call agenda
The summary goes out once, in the CEO's words, to the people the CEO agreed to.
- CEO approval. Send the draft to the CEO, accept every edit and keep the approved version with its date.
- Who submits. Agree in writing which person submits the introduction. Credit goes to a single partner, the one whose valid introduction comes first inside the 90-day attribution window, and it attaches when the company submits a verified application. The submitting person signs the SourceX Channel Partner Agreement before submitting.
- What travels. The six lines and the CEO's contact details, with permission. No attachments.
- What the company does next. It applies itself, and SourceX's review takes over.
A 30-minute first call between the CEO and SourceX can follow the summary's own order.
| Minutes | Item | Who leads |
|---|---|---|
| 0 to 5 | What the CEO wants from the conversation | CEO |
| 5 to 15 | Lines 2 to 4: work, span and systems, corrected where wrong | CEO, with SourceX asking |
| 15 to 22 | Line 5: which unknowns matter first and who at the company can answer them | SourceX |
| 22 to 27 | How review, rights checks and any agreement would proceed | SourceX |
| 27 to 30 | Next step and who follows up | Both |
The analyst need not join the call. If the CEO later wants a fuller internal document, SourceX's one-page ten-year history brief on its main site is written for company leadership. For the questions behind lines 3 and 4, see the data inventory interview questions; for the note that asks the owner first, the warm introduction brief.
Where a careful summary still misleads
- Estimates harden. "Several hundred thousand" becomes "400,000" two forwards later. Keep the label with the number.
- Altitude creeps. A follow-up asking for "an example" pulls the thread down to excerpt altitude. Answer with a category.
- Secrecy turns on facts. Whether records are trade secrets depends on facts only the company's counsel can weigh; the summary avoids harm but establishes nothing.
- Rights stay open. The summary flags customer contracts but cannot read them, and client-owned material is usually not a fit; SourceX's rights review sets the scope.
- Demand moves. SourceX applies each program's criteria, and a company that fits no program today may fit one later, so a flawless summary can still be declined.
- The fit facts still apply. History is only one of the checks. The company also needs a peak of 50 or more full-time employees (contractors left out), rights to license and an authorized contact, and its operating history has to be documented. 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.
Platform teams applying this across a portfolio can begin with the overview for venture platform teams; related walkthroughs are in the guides library.
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 a six-line summary that stays at fact and category altitude, open a partner link through registration, weigh the company's fit on who qualifies, and study the program terms before the introduction is sent.
Writing a company's history summary is referral work; judging SourceX itself as a possible investment is a separate decision, and investor materials can be requested through the SourceX investor overview.
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.