A portfolio operations analyst usually meets this problem late. The company fits, the CEO wants the conversation, the brief is nearly done, and the line for "how many records" is blank. The temptation is to write "millions" and move on. This page is about not doing that.
The count can wait; the fit facts cannot
Volume is the one number everyone asks about and nobody needs before a first call. The published screening profile on who qualifies lists operating maturity, original documentation, rights to license, an authorized sponsor and relevance to current data needs. A record count is not among them. SourceX's data volume estimator frames the question the same way: it says Acquisition Partners look for depth, several years of complete records from start to finish, and asks about completeness and the number of systems a history spans alongside a rough count in bands. It also says it does not estimate a price.
So the facts that must be settled before an introduction are the ones that are cheap to confirm: a peak of 50 or more full-time employees, contractors excluded; years of records that are the company's own; who owns them; and a CEO who knows about and wants the conversation. Location belongs on the same list: 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 minimum context around the volume line is short. Collect, as the company states it: the legal name of the entity that owns the records, the CEO, peak full-time headcount and the year it was reached, the record types (tickets, work orders, project files, claims), the system that holds each and the year each starts. Nothing in that list needs a file.
The unknown-volume disclosure examples
Five honest forms, in descending order of what a reviewer can plan from. Every example is Illustrative, built for this page.
| Form | Example volume line (Illustrative) | What a reviewer can plan from it | What it still cannot show |
|---|---|---|---|
| 1. Dated count | "Closed service tickets, March 2014 to October 2026: 212,400, from the helpdesk admin report run on 14 October 2026 by the support operations lead." | The scale of one system on a known date, and who can rerun the report | Duplicates, how many tickets carry full resolution notes, how much text is the customers' own |
| 2. Counter reading | "Newest work order is number 188,201; numbering started at 1 in 2012, per the operations manager. Voided and test numbers not known." | An upper bound and a start year | Gaps, voids, and orders deleted under a retention rule |
| 3. Estimate with its basis | "Roughly 1.2 million to 1.8 million load records: about 30 dispatchers, 20 to 30 loads each per working day, 250 days a year, 8 years. An estimate, not a count." | Order of magnitude, and a basis anyone can challenge | Whether every load produced a stored record, and how many systems they span |
| 4. Band | "10,000 to 100,000 project files, the CEO's band on SourceX's volume estimator. No count run." | Which band to plan around | Anything inside the band |
| 5. Named unknown | "Not known. The 2015 to 2019 archive sits on a retired file server nobody has opened since a 2020 migration; the outside IT provider can report a file count by 15 November 2026." | Where the answer is, who holds it and when it can arrive | Size, content and condition of the archive |
The estimate in row 3 shows its arithmetic on purpose: 30 × 20 × 250 × 8 gives 1.2 million, and 30 × 30 × 250 × 8 gives 1.8 million. A reader who knows that the dispatchers worked shifts of different lengths can fix the inputs instead of distrusting the whole line.
Weak volume lines, and what to write instead
| Weak line | Why it misleads | Rewrite as |
|---|---|---|
| "Millions of records" | No unit, no basis, no date; it reads as a count | Form 3 with the arithmetic, or form 5 |
| "About 5 TB of data" | Storage size is not a record count; attachments and recordings dominate it | "5 TB on the file server, per the IT provider in October 2026; record count not known" |
| "1,248,331 records" | Exact digits imply someone counted, but the source and date are missing | Form 1 with who ran which report and when, or round it into form 4 |
| "Every email since 2009" | A scope claim that hides client correspondence and personal data | "Email archive from 2009, size not known; mixes client and internal mail" |
| "Enough for any AI lab" | A demand claim nobody outside SourceX's review can make | Delete it |
Three checks before any number goes into the brief
Name the unit. One support ticket can hold a dozen messages and five attachments. "212,400 tickets" and "2.5 million messages" can describe the same archive. Say which one you mean, and never add units together.
Look for double counting. A company that migrated systems often holds the same records twice: once in the old export and once in the new platform. Ask whether the old system was retired after import or still holds copies. The companion guide on investigating record growth covers reading counters and first dates without asking for access.
Ask whose records they are. A large count made mostly of client-owned material adds little; the screening profile says client material is usually not a fit. If the company can say roughly what share of a system is its own work, put that beside the count, labeled as the company's estimate.
Method words, ranges and owners for every figure
Measurement scientists hold themselves to a stricter version of the same discipline. NIST's policy, set out in its Technical Note 1297, treats a measurement result as complete only when a quantitative statement of its uncertainty comes with it, and asks the report to say how that uncertainty was evaluated. A referral brief needs much less rigor than a laboratory, but the habit transfers.
- A method word on every figure. Counted, read from a counter, estimated, banded or unknown. Never leave a bare number.
- Ranges stay ranges. Do not turn 1.2 million to 1.8 million into "1.5 million". A midpoint loses its uncertainty the moment it is copied into another document.
- Constraints next to the count. "Tickets older than seven years are purged each January, per the support lead" belongs on the volume line, not in a footnote.
- Unknowns get an owner and a date. Who can close the gap, and by when. For a full grid that gives every gap a status, see recording what you do not know about a dataset; for the date side of the same problem, see describing an archive's time coverage.
The people who eventually use licensed data will ask harder questions than "how many". NIST's AI Risk Management Framework, under MAP 2.3, asks organizations to identify and document data collection and selection considerations such as availability, representativeness and suitability. A count answers none of those. It is one input among several, which is another reason not to inflate it.
Handing over a brief with a blank count
The brief goes forward as a short summary the CEO has read and approved, with the volume line in one of the five forms and no records attached. The one-page brief a founder can approve shows the surrounding format. Whoever submits must have signed the SourceX Channel Partner Agreement, and a copy signed when it was still called the Channel Partner Non-Circumvention and Non-Disclosure Agreement holds exactly as signed. Any credit is decided by order: the valid introduction that arrived first within the 90-day attribution window earns it, once the company submits a verified application.
A first call built around an unknown volume can follow five items:
- Confirm the fit facts as the company stated them: headcount at peak, years, location and language.
- Walk through the volume line, its form and its basis.
- Name the person who could run a count if SourceX asks, and what report they would use.
- Raise the ownership questions already noted, especially client material inside the main systems.
- Leave the next step to SourceX and the CEO. The partner does not run counts, receive exports or relay samples.
Where an unknown-volume line can mislead
- Anchoring. An estimate repeated in three documents starts to read as a fact. The method word is the defense; drop it and the line becomes a claim.
- Volume is not value. SourceX's estimator states plainly that it does not estimate a price, and no page here should suggest that a bigger count means a bigger payment.
- The count may be the wrong material. A big archive of client-owned files or personal data can sit beside a small, licensable body of the company's own procedures. Size points the wrong way in that case.
- Programs differ. SourceX applies the criteria of each program, and some programs set higher thresholds. A program could weigh volume more heavily than the general profile suggests, and a company can be declined in review whatever its brief says.
- Old estimates go stale. A band given in October may be wrong by March after a purge or migration. Date every line and recheck before any later introduction.
Methods note. The five forms and the weak lines were written for this page from SourceX's published screening profile and the bands in its volume estimator, both checked on 2026-10-27; every example company and number is Illustrative. This page does not measure how often introductions arrive without a count, whether the form of the volume line affects acceptance, or how volume relates to payment. SourceX has not published those figures, so none are given. A team that wants to test the method can log the form used in each brief it sends and the questions SourceX's review raised afterwards, as a quality measure rather than a volume measure.
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.
If the fit facts hold and the only gap is the count, write the volume line in one of the five forms, collect your tracked link through registration, confirm the company meets the published criteria and read the terms of the program before the CEO's introduction goes out; related brief-writing guides are collected in the guides hub.
Writing a volume line is referral work; judging SourceX as a company to invest in is a different exercise, and investors can request materials through the SourceX investor overview, which says SourceX shares company and commercial metrics with investors directly.
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.