# Investigate record growth without record access | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-investigate-record-growth-without-asking-for-record-access
Last updated: 2026-11-04

Ask the company's own people to read you numbers their systems already show: the number on the newest ticket or order, the date of the first record, file counts in an admin report, and who created the records. Never ask for files, samples, exports or logins. Growth found this way is a reason to talk, not proof of fit. SourceX screens on full-time headcount at peak, years of the company's own records, rights, an authorized CEO and current needs, and a flat or shrinking company can pass every one of them.

The interview below is for platform research leads. It fits one call with someone the CEO nominates, and nothing in it needs access to a single record.

## Record growth is a lead you date and source, not a verdict

Record growth means more records created by the company's own work each year: tickets, work orders, claims, project files. It differs from [headcount growth](/guides/headcount-growth-can-signal-new-records-and-new-ownership-questions), which counts people, and from a [surge in transactions](/guides/a-surge-in-transactions-is-not-the-same-as-licensable-data), which often runs through records customers own. Note where each growth claim came from.

| Where you heard it | What it can tell you | What it cannot tell you | How to use it |
|---|---|---|---|
| Board packs or information-rights reporting | Trends the company reports to its investors | Anything you may repeat; SourceX's screening page calls fund knowledge a reason to ask the CEO, never material to pass along | Ask the CEO whether the company wants to look at licensing |
| The founder or CEO in conversation | Rough scale and direction | Exact counts, or who owns each record type | Book the metadata interview |
| Public product or hiring announcements | That a team or product line exists | Whether it produces records the company owns | A reason to ask, never an answer |
| The company's admin reading a counter or report | A dated number with a named source | Record quality, rights or demand | The only answer the interview accepts |

The interview accepts one kind of answer: a number or date a named person at the company read from its own system on a stated day.

## The metadata growth interview guide

Twelve questions in four blocks, for the person the CEO nominates, usually an operations lead or system administrator. Record each answer with its system, the person who read it and the date.

| # | Question | Who can usually answer | A usable answer looks like | Never ask for |
|---|---|---|---|---|
| 1 | What number does the newest record carry in each main system? | System administrator | "Ticket 81,240, read on 14 October 2026" | Screenshots of tickets |
| 2 | What number did the first record carry, and on what date? | System administrator | "Ticket 1, June 2021" | The first record itself |
| 3 | How many files does the document store hold, and across how many sites? | IT administrator, from an admin report | "About 410,000 files on 37 sites" | A file listing |
| 4 | When did the company start keeping this record type at all? | Operations lead | "2014, in an older helpdesk" | Old files |
| 5 | Has the record type changed systems, and where does the older history live now? | System administrator | "The old helpdesk, read-only until March 2027" | A login to the archive |
| 6 | Were records ever bulk deleted, merged or moved between projects? | System administrator | "Two projects merged in 2023" | Audit logs |
| 7 | Roughly how many records a year now, and three years ago? | Operations lead | "About 25,000 now, about 6,000 in 2022" | Monthly exports |
| 8 | What drove the change: new customers, a new team, a new product or a change in what gets logged? | CEO or COO | "A managed-services line launched in 2023" | Customer names |
| 9 | Who creates these records: employees, contractors or clients' staff? | Operations lead | "Our own support staff" | Staff lists |
| 10 | Do any of the records sit in clients' systems or belong to clients under contract? | CEO, with counsel if unsure | "Product data sits in client tenants; tickets are ours" | Contracts |
| 11 | What was full-time headcount at its peak, contractors excluded, and when? | CFO or CEO | "180 in 2025" | Payroll files |
| 12 | Does the CEO want a conversation about licensing, and who has time for follow-up questions? | CEO | "Yes; the COO will handle it" | A commitment |

**Counters do most of the work.** In Jira, for example, a work item's key combines the project key with a sequential number, so the number on the newest item in a project is a rough count of items created there. Atlassian also documents how administrators can start a project's counter at a custom number, which is why question 2 asks what the first record carried, not only the newest. Question 6 catches the merges and deletions that distort the arithmetic, and the [metadata-only Jira inventory template](/resources/a-metadata-only-jira-inventory-template-for-company-introductions) lists record types and date ranges.

**Admin reports do the rest.** Microsoft documents a SharePoint site usage report in the Microsoft 365 admin center that lists file counts, active files and storage used for each site, and can be exported. An administrator can read those totals without opening a file, though a file count measures scale, not volume. Which system is authoritative for each record type is covered in [what a system of record is](/questions/what-is-a-system-of-record).

The company's person reads every number, never you. If a question would need a file, a sample or a login, mark it unknown and leave it for SourceX's review, which itself starts with a few questions and no files.

## Two growth patterns under the same twelve questions (Illustrative)

Illustrative. Two invented companies, as a research lead would record them after one call with each nominee.

| Block | Company A: fast-growing implementation firm | Company B: flat claims administrator |
|---|---|---|
| Volume now | Ticket 81,240; about 410,000 files in its document store | Claim number 158,300; adjuster notes in the same system |
| Start and breaks | Current helpdesk since June 2021; tickets from 2014 to 2021 in an old helpdesk, read-only until March 2027 | One claims system since 2009, never migrated |
| Rate | About 25,000 tickets a year now, about 6,000 in 2022 | Steady at about 9,000 claims a year |
| What drove it | A managed-services line launched in 2023 | Nothing changed |
| Who creates the records | Its own support staff; product data sits in client tenants | Its own adjusters |
| Peak full-time headcount | 180 in 2025 | 140 in 2016; 135 today |
| CEO wants the conversation | Not asked yet | Yes, after a call from an LP who sits on its board |
| What the guide shows | Fast growth, about five years in the live system and seven more in an archive with a switch-off date | No growth, about seventeen years in one system and a CEO who has agreed |

A growth screen would put A first and never look at B. The twelve questions reverse that order for now: B answers every knowable question and has a willing CEO, while A holds the more urgent fact, the March 2027 switch-off, and a CEO nobody has asked. Neither result says anything about demand, which SourceX checks in review.

Growing or flat, both companies face the same fit facts: 50+ full-time employees at their peak (contractors excluded), operating history they can document, rights to license, and an authorized CEO. 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.

## Does the growth expose operating history worth a conversation?

Run four tests before a rising count earns a place on your shortlist.

1. **Is the growth in records the company creates, in systems it controls?** SourceX's screening page lists material that belongs to the company's clients as usually not a fit. A's tickets pass; its product data does not.
2. **Is there a long tail behind the curve?** The oldest years often matter more than the newest. SourceX lists historical depth as a fit signal alongside volume, so ask question 4 before you admire question 7.
3. **Do the records show how work ended?** A ticket with a resolution and a claim with a decision carry an outcome, another of SourceX's fit signals. A log of open requests does not.
4. **Did the growth split the history?** A system change leaves years in one place and months in another, and the old system's switch-off date is real timing, unlike a quarter-end. The [role-change-to-access record chain](/guides/role-change-to-access-record-linkage) shows what a broken join between systems looks like at metadata level.

A flat or falling count is tested the same way. SourceX's referral site says operating, acquired or wound down companies can all qualify, though not every company does, and its process page says size alone does not determine value; actual Acquisition Partner demand and due diligence do.

## Order conversations by path, ownership and the company's time

Order the finished interviews by five keys you can check, in this sequence:

1. **CEO path.** A relationship owner has agreed to ask, or the CEO has already said yes.
2. **Ownership clear.** The growing records are created by the company's employees in its own systems.
3. **History dated.** A first-record date for each main record type.
4. **A dated event.** A switch-off, migration or retention change with a date attached.
5. **Capacity.** Someone at the company can answer follow-ups within a month, and your own research hours stay under a cap you set.

Growth rate comes last, as a tiebreaker.

| Rank | Company (Illustrative) | CEO path | Own records | History starts | Dated event | Growth |
|---|---|---|---|---|---|---|
| 1 | B, claims administrator | Yes | Yes | 2009 | None | Flat |
| 2 | A, implementation firm | Not asked | Tickets yes, product data no | 2014 in the archive | Archive switch-off, March 2027 | Fast |
| 3 | 95-person inspection firm, down from a 2019 peak of 230 | Yes | Unknown: client reports | 2006 | None | Falling |
| 4 | 60-person software company doubling its tickets each year | Founder interested | Yes | 2024 | None | Fast |

Company A moves to first the day its CEO agrees, because March 2027 puts its oldest tickets on a clock. The fourth row has two years of records against a screening profile that looks for several years in operation; mark it revisit, with the year that would change it. No benchmark for research hours has been published, so set your cap from your own time logs. The columns match the [metadata-only opportunity map](/guides/metadata-only-referral-opportunity-map).

## What counters and growth curves cannot tell you

- **Counters drift.** Custom starting numbers, merged projects and deletions bend the arithmetic; file counts measure storage habits.
- **Growth can sit in material clients own.** Fast-growing product data is often the least licensable part of a company.
- **Board knowledge stays confidential.** It can start a question to the CEO; it never goes into a message to anyone else.
- **Programs and demand move.** SourceX checks relevance to current needs in review, and a company that misses one program today could still match a different program later.
- **Market demand is a separate question.** Whether demand for AI training data is rising is analysis that belongs on sourcex.si; this guide stays on whether to ask one CEO for a conversation.

**Method note.** The twelve questions apply SourceX's published fit criteria and attribution terms, its screening page and its process page, all checked on 26 October 2026, together with Atlassian's and Microsoft's documentation of what work item keys and admin usage reports show. The guide has not been tested on a real cohort, SourceX has published no conversion data, and Companies A and B are invented. It captures what a company can tell you before any introduction, and leaves record quality, rights and demand to SourceX's review.

**A measurable test.** Interview five growing and five flat companies, then count full answers and CEOs who agree to a conversation in each group. If the growing five do not outscore the others, drop growth from your screen. A company that is ready applies itself through your partner link; its verified application is what triggers credit; a single partner per company earns it (the one behind the first valid introduction during the 90-day attribution window), and the submitting partner signs the SourceX Channel Partner Agreement first. See also [venture platform teams](/for/venture-platform-teams) and the [guides library](/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.

When the interview shows records the company created itself, a dated history and a CEO who wants the conversation, [register for a partner link](/register), compare the answers with [who qualifies](/who-qualifies) and keep the [program terms](/terms) beside your notes.

Reading a company's record growth for an introduction is referral work; evaluating SourceX's own business is a separate exercise, and readers doing it can request investor materials 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://refer.sourcex.si/
- https://sourcex.si/how-it-works
- https://support.atlassian.com/jira-software-cloud/docs/what-is-a-work-item/
- https://support.atlassian.com/jira/kb/set-jira-project-issue-key-counter-to-a-custom-starting-number/
- https://learn.microsoft.com/en-us/microsoft-365/admin/activity-reports/sharepoint-site-usage-ww?view=o365-worldwide
- https://sourcex.si/investors
