# Investor network referral signals: quarterly memo | SourceX

Canonical: https://refer.sourcex.si/guides/a-quarterly-brief-on-network-signals-worth-following
Last updated: 2026-11-05

The signals worth following in an investor network are dated events that change a company's records or who controls them: a system's end-of-support date, a WARN notice, a sale or merger, a CEO handover, a change to how long archives are kept. Funding rounds and leaderboard ranks say a company is growing, not that it holds licensable history. Once a quarter, log each event with its source and date, test the company against the fit facts, and name one relationship owner for every row worth a conversation.

Growth is a discovery signal. It does not establish that a company qualifies or that its records have value, and a mature or shrinking business can warrant the first review.

## Signals that change the records, and signals that only change the headline

Sort every signal by what it changes. An event that moves a deadline, a controller or an archive changes the case for a conversation. An event that moves a valuation or a rank does not.

Two public examples show the kind of date worth writing down. Microsoft says product enhancements, tax updates and technical support for Dynamics GP end on December 31, 2029, after it moved that date from September 30, 2029, with security updates continuing until April 30, 2031. A company that has run its finance and operations on that system for fifteen years will migrate before then, and a migration is when old history gets left behind. Second, the Department of Labor says most employers with 100 or more employees must give 60 calendar days' written notice of a plant closing or mass layoff under the WARN Act. A notice dates a deadline at a company that was, at some point, large.

| Signal | Where it is dated | What it changes | Fit fact it touches | Memo action |
|---|---|---|---|---|
| System end-of-support | The vendor's lifecycle page | A migration that can strand old history | Documented operating history | Follow |
| WARN notice | A state workforce agency listing | A shutdown or layoff deadline | Size at peak; history at risk | Follow, through advisors or the board |
| Sale or merger | The company's or acquirer's announcement | Who controls the records and who signs | Authorized CEO; rights | Follow |
| CEO handover | The company's announcement | Who authorizes a licensing discussion | Authorized CEO | Follow |
| Archive or retention change | The relationship owner, dated | A deletion date | Documented operating history | Follow |
| Funding round | A press release or securities filing | Cash and, often, CEO capacity | None | Log only |
| Leaderboard rank or award | The publisher's list | Growth rank among entrants | None | Log only |
| Headcount growth | Job pages and estimates | Today's size, not peak | Size, partly | Log; ask for the peak |

WARN filers deserve their own care: the [WARN notice guide](/guides/warn-notice-data-licensing-opportunity) explains why the route runs through advisors, lenders or the board and never through employees being laid off.

## The quarterly signal memo template

One page, written by the platform research lead in the last week of the quarter and read by everyone who owns a relationship in it.

| Section | What to write | Example entry (Illustrative) |
|---|---|---|
| 1. Period and cutoff | Quarter, author, date events were last checked | Q4 2026; cutoff 2026-12-31 |
| 2. Followed events | Company code, event, source, date checked, deadline | Company S: sale process under way, owner's note dated 2026-11-04 |
| 3. Fit facts | Peak full-time headcount, record span, whose records, location: known or unknown | Peak 340 (2016); records since 2009; own transactions; US |
| 4. Relationship owner | Who will ask the CEO, and whether they have agreed | LP principal holding a minority stake; agreed |
| 5. Decision | Ask now, metadata first, hold until a named trigger, or drop | Ask now, before signing changes the controller |
| 6. Logged, not followed | Signals seen and set aside, with the reason | Company G: Series C; no fit fact changed |
| 7. Carry-over | Last quarter's rows and any submitted introduction still inside 90 days | Company K: introduced 2026-10-02; application pending |
| 8. Not checked | What the memo did not verify | Customer contracts; record quality |

Three rules keep it honest. Each followed event carries a source and the date you checked it. Each decision names a person, not "the team". And section 6 is never empty: if nothing was set aside, the memo was not looking widely enough.

**Methods note.** The signal categories and fit facts restate the program terms (version 2026-10-22.2, since replaced by version 2026-11-04) and the who-qualifies screening profile, checked 2026-10-26, with two public sources for dated events: Microsoft's Dynamics GP lifecycle page and the Department of Labor's WARN page, both checked the same day. The memo records events and fit facts. Demand for a company's records, the quality of those records and any likely payout sit outside it; only SourceX's review can judge them. It is an internal research note, distinct from the [quarterly LP letter template](/resources/quarterly-investor-letter-template-private-equity), which reports a license after it exists.

## A funded company and a shrinking one in the same memo (Illustrative)

Illustrative: two invented companies, run through the same sections in one quarter.

**Company G** is an eight-year-old vertical software company in the portfolio. It raised a Series C this quarter, appeared on a growth list and has 260 full-time employees, its peak so far. Much of its workflow data sits in customers' accounts.

**Company S** is a 28-year-old regional building-products distributor owned by its founder-CEO, with an LP holding a minority stake. It peaked at 340 full-time employees in 2016 and has 150 today. It has run Dynamics GP since 2009 and its owner is exploring a sale.

| Memo question | Company G | Company S |
|---|---|---|
| Events this quarter | Funding round; growth-list rank | Sale process; system support ends December 31, 2029 |
| Followed or logged | Logged only | Followed |
| Peak full-time headcount | 260 now, rising | 340 in 2016 |
| Record span | About eight years | Seventeen years in one system |
| Whose records | Largely held in customers' accounts | Its own orders, invoices and returns |
| Path to the CEO | Board member; CEO busy after the round | LP principal, agreed to ask |
| Decision | One metadata question on company-created records; revisit next quarter | Ask now, before a buyer controls the decision |

Company G grew and Company S shrank, and the same questions put S first. Nothing about G's growth is held against it; its round simply answered none of them.

## Does a dated event tell you how much history exists?

No. An event dates a change, not a span. The Dynamics GP date tells you when Company S must move, not how many years of usable records the system holds, and a WARN notice dates a layoff, not the start of an archive.

So every followed event triggers the same metadata questions, asked through the relationship owner: full-time employees at peak and the year of the peak; the earliest year of company-created records; which system holds the daily work, who administers it and when it is due to change; and whether any records belong to clients. Nobody asks for files, samples or logins. The decision to discuss licensing, and the signature, belong to the CEO. Three things remain open until SourceX's own review: whether a current program has a use for these records, whether customer contracts get in the way of reuse, and what any license would cover.

Location is a fit fact too. 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.

## Sequencing the memo's asks by controller, owner and capacity

Order section 5 on five keys:

1. **Controller.** A pending sale means the current CEO decides only until signing; after it, the acquirer usually does. [Who controls a startup's data after it is acquired](/questions/who-owns-startup-data-after-acquisition) covers the common structures.
2. **Relationship owner agreed.** One person, named, who will ask the CEO first. An introduction the CEO has not been told about is usually not a fit.
3. **Fit facts known.** Four of four beats three of four.
4. **CEO capacity.** A sale, a layoff or a fresh round all compete for the same calendar. Ask the relationship owner when there will be room, and record the answer as a trigger.
5. **Deadline.** A support end date, a WARN date or a stated archive deletion is real urgency; a quarter-end is not.

Before anyone asks, check credit. The terms treat a company as a duplicate if SourceX already had a lead, an account or email correspondence with it, and no later partner is credited for a duplicate. If the company is new to SourceX, credit goes to the first valid introduction inside the 90-day attribution window once the company files a verified application, and no company carries credit for more than one partner. Sign the SourceX Channel Partner Agreement before the first submission; if your fund signed it when it was still titled the Channel Partner Non-Circumvention and Non-Disclosure Agreement, that copy continues to apply as signed. After an introduction, the [follow-up guide](/guides/how-to-follow-up-on-an-introduction-with-the-company-owner) covers the next contact with the owner.

## How a signal memo goes wrong

- **Sensitive events handled as leads.** A layoff or a sale is a hard period for the people inside. Route through the board, the owner or the company's advisors, and drop the row if the relationship owner says no.
- **Stale dates.** Published dates move; Microsoft's own GP date moved by three months. Re-check every followed date each quarter.
- **A memo that becomes a list.** The memo is internal research. Sending its rows outside the fund, or contacting companies without the CEO's knowledge, defeats its purpose.
- **Confirmation bias.** Teams follow the events they already watch. Section 6 exists to show what was set aside.
- **Demand and rights.** SourceX checks relevance to its current data needs and rights in review; client-owned material is usually not a fit. A followed row is a candidate, not an acceptance.

For the program from the fund's side, see the [venture platform overview](/for/venture-platform-teams); related methods sit in the [guides index](/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 a memo row reads "ask now" with an agreed relationship owner and four known fit facts, [register for a partner link](/register), test the row once more against [who qualifies](/who-qualifies) and study the [program terms](/terms) before the owner raises it with the CEO.

Watching network signals is referral research; whether SourceX itself deserves attention as an investment is a different matter, handled through the [SourceX investor overview](https://sourcex.si/investors), where investor materials can be requested.

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://learn.microsoft.com/en-us/dynamics-gp/terms/lifecycle
- https://www.dol.gov/general/topic/termination/plantclosings
- https://sourcex.si/investors
