Shrinking companies stay on the board: the size check counts 50 or more full-time employees at peak, contractors excluded, as the peak headcount guide explains. The growth-versus-suitability plot shows why growth should never be the score. This page is the data layer underneath both: what to collect, from where, and what to refuse to collect.
What counts as a growth signal, and which source may carry it
A field earns a place on the dashboard when three things hold: its value comes from a public source you can link, it carries the date it describes, and it informs one of the published fit checks. Growth is then a derived reading, the difference between two observations of the same field from the same kind of source. A headcount from an annual report minus an estimate from a profile site is not growth; it is two different measurements subtracted.
Revenue fails the third test. The screening profile on who qualifies asks about size, history, rights, an authorized sponsor and program relevance, and says outright that venture backing does not make a company eligible. The reward is calculated on the Actual Supplier Payout, the compensation SourceX actually pays the company, never on the company's sales or SourceX's fees. A modeled revenue figure informs no decision here, and it travels badly: a screenshot of a cell labeled "est. revenue" reads as a fact about a company that never published one.
Three rules follow:
- Every cell carries its source and two dates: when you retrieved it and when the value was true. An annual report filed in March may describe headcount at the previous December.
- "Not public" is a value. A blank means nobody has looked; "not public" means someone did and found nothing. Private companies collect many of these, and that says nothing about their records.
- No composite score includes growth or revenue. The fields feed the five checks; ordering happens later, on the status rules below.
The public-source signal dashboard specification
Ten fields come from public sources. The eleventh stays inside your team.
| # | Field | Public source | Unit and definition | Fit check it informs | What it cannot tell you |
|---|---|---|---|---|---|
| 1 | Reported employees, U.S. public filers | Annual report business description; Regulation S-K Item 101(c) asks for human capital resources, including the number of persons employed | Persons employed as stated, with the as-of date | Size at peak | Whether staff are full-time, or whether foreign staff are counted |
| 2 | Average employees, UK companies | Notes to the annual accounts under Companies Act 2006 section 411 | Monthly average of people employed under contracts of service in the financial year | Size at peak | The peak month, which sits at or above the average, and the full-time share |
| 3 | WARN notice | State postings under the federal WARN Act, which covers employers with 100 or more employees and requires 60 calendar days' notice of covered closings and mass layoffs | Notice date, site, affected count, effective date | Size, plus a dated event for records | Who owns the records or whether the CEO wants a conversation |
| 4 | Open roles | The company's careers page, saved as a dated snapshot | Count of open roles by function | Recent activity | Headcount; postings include replacements and contract roles |
| 5 | First year of operation | The company's history page or registration record | Year | Operating history | How long records were kept |
| 6 | Named systems | Job postings and product documentation naming the ERP, helpdesk or dispatch system | System name and earliest dated mention | Operating history and where records sit | Retention, exports or record counts |
| 7 | Ownership events | Company announcements and filings | Buyer or target, date, closed or pending | Which entity holds the records and whose CEO decides | How far integration has gone |
| 8 | CEO and tenure | Leadership page or filings | Name and start date | Authorized path | Whether the CEO wants the conversation |
| 9 | Where customer data lives | Product documentation and terms of service | Company-held operating records, records in customer accounts, or both | Rights | Contract terms; only SourceX's rights review settles rights |
| 10 | Headquarters and working language | Registration record and company site | Country, and languages used with customers | Location and language | The English share of the records actually offered |
| 11 | Relationship owner, private | Your own CRM | The person in your network who can ask the CEO | Authorized path | Nothing public; never publish it |
Field 10 reads against the published geography: 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.
Fields the dashboard never carries. Modeled or third-party revenue estimates. Valuation, round size or share price, because funding plays no part in fit. Positions on growth rankings, which measure attention rather than records. Any projected dataset value, payout or reward. Anything from inside a company: files, samples, screenshots or logins. Discovery stays at metadata level: which records exist, roughly how many, over how many years, in which system, owned by whom.
Method note. Each field maps to one check in the published screening profile and program terms, checked 2026-10-26. The public sources were checked the same day: Regulation S-K Item 101 on eCFR, the SEC Investor Advisory Committee's human capital recommendation, section 411 on legislation.gov.uk and the Department of Labor's WARN overview. The dashboard does not measure demand for a company's records, their quality or any payout; SourceX checks relevance to its current data needs in review.
Two growth patterns run through the same five checks (Illustrative)
Illustrative. Two generic companies with invented values; no outcome is implied.
The first is a U.S. freight platform whose annual reports show 610 persons employed at one fiscal year-end and 1,050 two years later, with 85 open roles on its careers page. The second is a UK engineering consultancy whose accounts show an average of 340 employees four years ago and 190 in the latest year. On a growth screen the first wins easily. On the dashboard they read like this:
| Fit check | Freight platform, headcount up 72% | Engineering consultancy, average down 44% |
|---|---|---|
| Size at peak | 1,050 persons employed at the latest year-end; full-time share not stated | An average of 340 in its largest year, so at least one month at 340 or more; full-time share to confirm |
| Operating history | Founded 2012; dispatch system named in postings since 2016 | Founded 1994; project system named in postings since 2008 |
| Rights | Product documentation says shipper data sits in customer accounts on the platform: flagged | Client deliverables likely belong to clients; its own QA records and procedures are its own |
| Authorized path | CEO since 2019; no relationship owner yet | Owner-CEO since 2002; a co-investor sits on the board |
| Location and language | U.S. | UK, so the 70% English rule applies; working language English, share to confirm |
Neither column is a verdict. The freight platform may hold years of its own exception and claims records beside the customer-held data; the consultancy may find most of its project files belong to clients. The dashboard shows which unknown to resolve first.
Does headcount growth reveal operating history?
Mostly it reveals recent history. Fields 1 to 4 describe the present and the last year or two; the 440 people the freight platform added have, by definition, work records no more than two years old. Depth comes from fields 5 to 7: when the company started, when its systems first appear in dated public material, and whether an acquisition brought older records in. Read the two groups separately, and never let a strong reading in one cover for a blank in the other.
Contraction runs the other way. A falling headcount deletes no records by itself, though departures and system retirements can, which is why field 3 and any announced migration are dated events: they mark when records could be lost. That is real urgency; a quarter-end is not. The WARN notice guide covers approaching a company in that position through its advisors rather than its departing staff.
Queue conversations by evidence, ownership and the CEO's bandwidth
Order rows by status first, then within each status. Growth direction never decides the order.
| Status | Test | Company (Illustrative) | Next action |
|---|---|---|---|
| Ready | Fields 1 to 10 sourced, no rights flag, relationship owner willing to ask | Engineering consultancy | The co-investor asks the CEO whether a conversation is wanted |
| Source missing | One fit field still unchecked or flagged | Freight platform | Resolve the customer-data flag at metadata level before anyone asks |
| Ownership moving | A sale or acquisition announced and not yet closed | 300-person packaging distributor | Wait for closing; the buyer's CEO will decide |
| Bandwidth hold | A dated event absorbing leadership: a WARN effective date, an integration, a financing | 520-person print operator closing one site | Reach its advisors first and offer to wait |
Within "Ready", put rows with a dated record-risk event first, then rows where the relationship owner's ask is a single call. Capacity applies on your side too: set a written limit on how many asks each relationship owner carries at once. For the portfolio side of the program, see the overview for venture platform teams.
What the dashboard cannot see, and how it misleads
- Headcount definitions differ. The SEC's Investor Advisory Committee said companies report headcount inconsistently, some combining full-time and part-time staff and some counting only domestic workers. Treat field 1 as a lead for the size check, not as the check.
- Averages hide peaks, and filings lag. Section 411 asks for a yearly average, and every filed figure describes a year that has already ended.
- Private U.S. companies leave most cells "not public". An empty-looking row can belong to a company with twenty years of well-kept records. The dashboard measures what is visible, not what exists.
- Rights and demand sit outside it. Field 9 raises flags; only SourceX's review settles rights, and relevance to current data needs is checked in review. Criteria are set per program, so a row that misses one program's bar could still line up with a later one.
- The revenue column will be requested, because every other dashboard has one. It still informs no check here.
A measurable next step. Fill the dashboard for 20 companies and count the share of cells marked "not public". After one quarter, count by status how many CEOs agreed to a conversation. If "Ready" rows convert no better than "Source missing" rows, the fields are not earning their place; change them and record why. SourceX has not published conversion figures by status or by growth pattern, so those counts would be the first evidence anyone has.
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 a row reaches "Ready", the submitter can register for a partner link, run the company past who qualifies and the company fit checker, and study the program terms, all before the relationship owner makes the ask. Whoever submits the introduction signs the SourceX Channel Partner Agreement first.
Tracking other companies' signals is referral work; judging SourceX itself as an investment is a different decision, and investor materials are 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.