A channel partner's business development lead often gets the opposite advice from habit: qualify by size of wallet. For this kind of introduction that filter points the wrong way.
Revenue is the wrong first number
Revenue measures what a company sells. Operating history is the trail its people leave while doing the work: work orders, project files, inspection logs, QA records, support threads. The two diverge all the time. A 300-person facilities contractor on thin margins can hold fifteen years of job records; a 25-person software reseller with large contracts may hold very little of its own. SourceX's published screening profile on who qualifies lists headcount at peak, years in operation, original documentation, rights, an authorized sponsor and relevance to current needs. Revenue is not on it, and the page on minimum revenue says so directly.
So the useful question is not "how big is this business" but "has this business been doing documented work, repeatedly, for years, and is anyone I know able to ask its CEO about it".
Start with the relationship path, then read the clue
A public signal is only worth reading if someone in your network can ask the company about it. Before you open a single database, write down who would make the ask: the colleague who handles the account, the partner who sits on its advisory board, the former employee who still talks to the CEO. If nobody fits, the company stays a research note however strong its footprint looks. Under SourceX's screening guidance, a company whose decision maker was never told about the introduction is usually not a fit, so a cold approach gains nothing.
The public-history signal checklist
Five footprints that date a company's work without saying anything about its sales. Each row says what the signal shows, what it cannot show, and the question it becomes.
| Signal | Where to look | What it shows | What it cannot show | Question for your contact |
|---|---|---|---|---|
| Federal award history | The recipient profile on USAspending, searched by name or UEI | That the entity received federal contracts, grants or loans, and the trend over time | Which records the work produced, who owns them under the award terms, or headcount | "Which system holds the project records for that work, and from what year?" |
| Workplace inspection record | OSHA's establishment search, which covers inspections since 1972 | That an establishment at an address was inspected on a date, and so was operating then | Size, the state of its own records, or even that it is the same company, since names are not unique | "How long have you kept your own safety and incident records, and where do they live?" |
| Archived website captures | The Wayback Machine, browsed by date for the company's own domain | Service lines, locations, team pages or a client portal login existing in a given year | That a service ran at any scale, or that records from then survive | "When did that service line start, and are its early records still in a system?" |
| Job posts that name a system | The company's careers page, current or archived | That a named platform was in use when the post went up | Whether older records were carried across when systems changed | "When you changed systems, did the history come with it?" |
| Dated material the company publishes about its own practice | Release notes, changelogs, published procedures, a dated knowledge base | A documented way of working, kept up over time | Who owns the internal records behind it, or whether they match | "Is the internal version of this kept in the same place, and since when?" |
How the checklist was built. Each row links a public source to one of the published fit facts, years of documented operating history, and to nothing else; sources were checked on 2026-10-27. The checklist does not estimate headcount, rights, record quality or demand. It has not been tested against outcomes; SourceX has not published how often companies found this way are accepted, so none is given.
Separate what you observed from what you inferred
Every footprint invites a leap. Write the observation with its source and date, the inference beside it, and leave the third column empty until the company fills it. Illustrative, for a generic environmental testing laboratory founded in the 1990s.
| Observed, with source | What you might infer | Confirmed by the company |
|---|---|---|
| Federal awards in most years from FY2011, on its USAspending recipient profile | A decade and more of funded testing work | Its own sample and QA records sit in a laboratory system used since 2009 |
| An inspection at its laboratory address in 2016, on OSHA's establishment search | Operating at that site since at least 2016 | Same site since 2004 |
| A "sample tracking portal" login on its site in 2012 captures | Years of chain-of-custody records | Correct, though result reports issued to clients belong to the clients |
| Eight people on the leadership page | A small company | 135 full-time employees at the 2022 peak |
The last row is a reminder that public pages mislead in both directions. Leadership pages list leaders, not staff, which is why headcount always comes from the company.
A clue-only case, a confirmed case and a no-fit case (Illustrative)
Public clue, no path. A regional fire-protection contractor shows federal awards every year since 2012 and archived pages for an inspection-booking portal since 2014. Nobody at your firm knows anyone there. It goes in a research file with its sources and dates. If a relationship appears later, the file saves an hour; until then, no approach.
Confirmed and routed. The testing laboratory above is a client of one of your partners, who has known the CEO for years. The partner asks one question: would the CEO want to hear about licensing records the laboratory created itself? The CEO says yes, confirms headcount and years, and flags that client result reports belong to clients. That account, in the CEO's words, is what travels.
Long history, no fit. A 45-person surveying firm has thirty years of public award history and an archived site going back two decades. It has never had 50 full-time employees, and its deliverables mostly belong to the agencies that commissioned them. A long footprint does not cure either. Record it and do not raise it.
From footprint to introduction: permission, checks and what travels
The person who owns the relationship raises it with the CEO, who authorizes a licensing discussion. Disclose that you could earn a reward if a license follows, paid by SourceX separately and never out of the company's payout. Then check the remaining published facts with the company: 50 or more full-time employees at peak, contractors excluded; rights to the records it would discuss; and location. 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.
Two program rules belong at this step. If the company has ever applied, held an account or exchanged email with SourceX, a later introduction is a duplicate and is not credited. And the partner who submits must already have signed the SourceX Channel Partner Agreement; a version signed when it was titled Channel Partner Non-Circumvention and Non-Disclosure Agreement still counts and stays in force as signed. When the company submits a verified application, credit is given to whichever valid introduction came first inside the 90-day attribution window. The footprints themselves stay in your notes; the introduction carries only what the company confirmed.
Where public-history signals mislead
- Name collisions. OSHA's own help page warns that establishment names are not unique and spellings vary. Match on address and dates before trusting a hit.
- The wrong entity. USAspending can group several registered entities under one parent. The entity with the award history may not be the one that keeps the records, or the one whose CEO you know.
- Gaps are not absence. The Internet Archive says some sites were never archived. No captures before 2018 does not mean the company started in 2018.
- Activity is not ownership. An award, an inspection or a portal shows that work happened. Whose records that work produced depends on contracts only the company and SourceX's review can read; the guide to public records versus licensable company data covers why being visible is not being licensable.
- Fit is not demand. A company that passes every published fact can still be declined, because relevance to current data needs is assessed in review.
For sector-specific examples of the records behind these footprints, see construction project records and recognizing several years of operating history; for company age from registries, the age-and-ownership worksheet; and for growth signals, the dashboard with no invented revenue numbers.
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 a public footprint has become facts the company itself confirmed, and its CEO wants to talk, sign up through partner registration, set those facts beside the criteria for qualifying companies and read the program's terms before you submit; the guides hub has the rest of the sourcing series.