Build a watchlist of operational change, not unicorn rankings: seven families of dated events that move records or change who controls them, each with a source, a fit question and an expiry

Short answer

A referral watchlist should follow dated events that change what happens to a company's records or who controls them, not valuation rankings. Seven families cover most of them: system retirements and migrations, acquisitions and integrations, site closures and mass layoffs, ownership and leadership changes, retention changes, wind-downs, and headcount milestones. Log each event with a primary source, the fit question it raises, an expiry date and the person who owns the CEO relationship; SourceX's screening ignores round size, press coverage and growth.

Visual briefFull-size diagram
Seven swimlanes, one per event family, run across twelve months for an Illustrative distributor, with dated events and the window each one leaves open; a final lane for a valuation ranking holds no events at all.
Illustrative. Events and dates are invented; the seven families follow the taxonomy on this page.

A ranking moves when investors change their minds. A watchlist entry moves when something happens to the records, and that is the only kind of movement a data introduction depends on.

What a valuation ranking watches, and what it leaves out

A list ranked by private valuation records the price at which investors last bought shares. It rises with financings and sentiment, and it is silent between rounds. SourceX's who-qualifies page is blunt about its weight in the decision: none of the checks SourceX screens on mentions funding, and round size, press coverage and growth appear nowhere in the decision.

Such a list also leaves out, by construction, the companies a data program often finds first: firms that never raised outside capital, subsidiaries, family-owned businesses and companies that have shrunk from their peak. The headline audit counts which fit facts each headline source reveals. The growth signal dashboard stores public fields and the change between two observations of them. A watchlist does a third job: it stores single dated events, each with a window that closes.

The change-event monitoring taxonomy

Seven families, each defined by what the event does to the records or to authority over them.

FamilyExample eventPrimary source to watchQuestion it raisesWindow closes when
1. System retirement or migrationAn ERP, CRM or helpdesk replacement; a vendor end-of-support dateThe vendor's lifecycle page; the company's own announcementWhich history moves, and which is archived or dropped?The old system is decommissioned
2. Acquisition or integrationAn add-on acquisition; two companies merged onto one platformCompany releases; the acquirer's filingsWhich entity owns the records now, and who is its CEO?The integration ends and old systems are retired
3. Site closure or mass layoffA plant closing; a warehouse consolidationState WARN listings; company statementsDoes the company operate elsewhere, and what was its peak full-time headcount?Systems at the site are switched off
4. Ownership or leadership changeA founder retiring; a new CEO; a sale to a sponsorCompany announcements; the relationship ownerWho authorizes now, and does anyone in your network know them?The new CEO has set priorities, a judgment call
5. Retention changeA new retention policy; a plan change that deletes older historyThe company's policy notes; the software vendor's plan termsWhat is deleted, and on what date?The purge date
6. Wind-downA board decision to close; an assignment or insolvency filingCourt or state filings; the company's advisorsWho controls the assets and records today?The records are destroyed or the estate closes
7. Headcount milestoneFull-time headcount passes 50 for the first timeCompany statements; annual reportsDoes the company now meet the size test at peak?Never: a peak, once reached, stays

A funding round is not an eighth family. Log it only as context, or file it under the family it pays for, as when a release says the money funds an ERP replacement.

Two families need care with their sources. For family 3, the Department of Labor says the federal WARN Act requires employers with 100 or more employees, generally not counting those who have worked less than six months in the last 12 months or who average under 20 hours a week, to give 60 days' notice of plant closings and mass layoffs, and some states have their own laws. A WARN filer is usually a larger employer, but federal coverage counts people differently from the program, so confirm the company-wide peak of full-time employees, contractors excluded; the WARN notice guide covers approaching a company through its advisors. For family 1, read lifecycle dates on the vendor's own page; the Dynamics GP end-of-life page shows how one retirement plays out.

Methods note. The taxonomy sorts events by what they do to records or to authority, taking its fit facts from SourceX's who-qualifies page and its attribution rules from the terms in Version 2026-10-22.2, since replaced by version 2026-11-04 (both checked 2026-10-26), with the Department of Labor's WARN summary behind family 3. It does not score demand, record quality or payout, and it does not predict which companies SourceX accepts. Windows are reading aids, not deadlines set by SourceX.

Two companies through the same taxonomy (Illustrative)

Illustrative. Two generic companies with invented events; no outcomes implied.

Company A is a growth-stage software company that appears high on a valuation list. Its records start in 2020. Over twelve months it raised a round and logged no operational event. Company B is a 45-year-old building-products distributor with about 500 employees that has never appeared on any list. Over the same twelve months it filed a WARN notice for one plant, announced an ERP replacement for next year and named a successor to its retiring founder-CEO. A board member at one of the fund's LPs knows the founder.

FamilyCompany ACompany B
System retirement or migrationNoneERP replacement announced for next year
Acquisition or integrationNoneNone
Site closure or mass layoffNoneWARN notice for one plant
Ownership or leadership changeNoneFounder retiring; successor named
Retention changeNoneUnknown; ask through the board member
Wind-downNoneNone
Headcount milestonePassed 50 full-time employees in 2024Peak far above 50
Watchlist statusContext only; rescreen when an event landsThree live events; the board member asks the founder

Company A is not a bad company; nothing is happening to its records. Company B has three events at once, which is also a capacity problem: a plant closure and a CEO succession both consume leadership time. Keep the ask small, route it through the board member, and expect that the successor may be the CEO who authorizes by the time a conversation happens. The founder retirement guide covers that handover.

Does each event reveal operating history?

Each family says something specific about history, which is why it earns a lane. A migration reveals which systems hold how many years and which part of them will not move. An acquisition reveals more than one record set and a question about which entity owns each. A closure reveals servers about to be switched off. A leadership change reveals who knows where the archives are, before they leave. A retention change reveals a deletion date. A wind-down reveals who now controls the records. A headcount milestone reveals that the size test is met at peak.

A ranking reveals none of these. Several years in operation is SourceX's screening baseline, and some programs set higher thresholds, so the history question always comes back to span: how many years, in which systems, still readable.

Acquisitions add an entity rule. Once a deal closes, buyer and target are one company for the reward: a parent and its subsidiaries count as a single referred company, so the USD 50,000 floor applies once across the group, to its first qualifying transaction, and later qualifying transactions first agreed within 12 months of that first Closing pay 15%. Whether a parent's earlier contact with SourceX, or another partner's introduction of a sister company, affects credit is not settled in the terms; SourceX decides it in duplicate review. The post-acquisition questions help find out which entity holds what.

Run the watchlist: sources, cadence and the order of asks

Three habits keep a watchlist useful rather than large.

  • Cadence. Scan the sources for families 1, 3 and 6 weekly: vendor lifecycle pages for the systems your companies run, state WARN listings, court and state filings. Review open entries with relationship owners monthly. Give every entry an expiry date when you log it.
  • Archive, do not delete. SourceX's guidance says failure is dated, not permanent. An expired entry, or a company that failed a check, stays on file with the condition that would reopen it, such as full-time headcount passing 50 (family 7) or a new system announced (family 1). The peak headcount guide explains how a peak is documented.
  • Order of asks. No relationship owner, no ask. Among entries that have one, sort by the window that closes first where records are at risk, then by fit facts known, then by the CEO's capacity. Set a ceiling on how many asks each relationship owner carries per quarter.

Fit facts decide what the event cannot, and there are four of them: a full-time headcount that reached 50+ at its peak, contractors not counted; an operating history the company can document; the rights to license; and an authorized contact who can speak for the firm. 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 CEO authorizes a licensing discussion and signs for the company; in a wind-down controlled by a trustee, an assignee or a court, the CEO alone may not be enough. Questions stay at metadata level, never files, samples or logins. The venture platform overview covers how platform teams run this alongside portfolio support.

Where the watchlist could be wrong

  • Coverage bias. Public events skew toward larger employers: the federal WARN rule starts at 100 employees, and many system migrations are never announced publicly. A watchlist built only on public sources over-represents big companies; relationship owners fill the gap.
  • Windows close. An event can expire before anyone acts. Wound-down companies can still qualify if the records survive, so an expired window lowers the odds rather than ending them, but SourceX's review decides.
  • Demand. SourceX checks in review whether a company's material matches a real program with AI developers. A company with three live events can still be declined.
  • Rights and regulation. Providers of general-purpose AI models in the EU must publish a sufficiently detailed summary of their training content, under rules that apply from 2 August 2025. As scrutiny of training data provenance rises, records that changed hands in an acquisition or a wind-down face a closer rights review.
  • Relationship cost. Raising data licensing during a layoff or a succession can look opportunistic. No data on how CEOs respond has been published; record it in your own log.

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 watchlist entry has a live window, known fit facts and a relationship owner ready to ask, register for a partner link, compare the company with who qualifies and read the program terms before the relationship owner makes the call. The submitting partner signs the SourceX Channel Partner Agreement beforehand. The rest of the signal series sits in the guides hub.

A watchlist of operational change is a referral tool. Anyone assessing SourceX as a company to invest in is making a separate decision and can request materials through the SourceX investor overview, where the company says it 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Should a funding round go on the operational change watchlist?

Only as context, or filed under the event it pays for, such as an ERP replacement or an acquisition. A round on its own moves no records and changes no one's authority, and SourceX's screening does not look at funding.

How long should an event stay on the watchlist?

Until its window closes: the old system is decommissioned, the purge date passes, the site's servers are switched off or the estate closes. Archive expired entries rather than deleting them, because a company that failed a check once can be rescreened when something changes.

Who should act on a watchlist entry?

The person who owns the relationship with the company's CEO, and only after the platform team has checked the fit facts it can see. The watchlist finds the moment; it never sends anything by itself.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. dol.gov/general/topic/termination/plantclosings
  4. digital-strategy.ec.europa.eu/en/faqs/general-purpose-ai-models-ai-act-que…
  5. sourcex.si/investors

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment