The 90 days come from the attribution rule: credit needs a verified application within 90 days of the recorded introduction, one partner is credited per company, and the window does not extend. An introduction made into months the company cannot use can expire before it counts.
Which growth event is loading the company, and how you would know
Growth is the signal; the event behind it decides the workload, and sometimes sets a date after which records get harder to reach.
| Growth event | Where the signal usually comes from | Who it loads | Record clock? |
|---|---|---|---|
| Equity raise | The founder's update, or a Form D notice, due within 15 calendar days of the first sale | CEO, finance lead, counsel | Rarely |
| Acquisition and integration | An announcement, then board materials | CEO, counsel, IT | Often: the acquired company's systems get retired |
| System replacement | The IT roadmap or a vendor contract end date; seldom public | The system owner | Yes: the old system's switch-off date |
| Hiring surge | Job postings and the platform's own talent team | CEO, team leads | No |
| Seasonal peak | The company's calendar | Operations, finance | No |
| Contraction or restructuring | Notices and announcements | CEO, finance, counsel | Often: subscriptions end and system owners leave |
A Form D shows that securities have been sold, counted from the date the first investor is irrevocably committed; it does not show that the raise is over or that the CEO has time. Platform teams often see hiring first because they help run it: Andreessen Horowitz, for example, publishes executive hiring guides for technical, go-to-market and operational roles. Private signals time your own question; they never belong in a message to SourceX.
What a SourceX conversation asks of the company before any payout
The early work is light on hours but lands on specific people:
| Stage | Who at the company | What it needs | Timing SourceX states |
|---|---|---|---|
| Apply and qualify | The CEO, helped by whoever knows the systems | A few questions, no files: systems, years of history, what can be exported; SourceX then completes the inventory with the company and runs the rights check | Not stated |
| Rights triage | Counsel with a contracts lead | Which customer, vendor and employee terms touch each record family | Part of qualification |
| Master signature | The CEO | One agreement, signed once after qualification | Starts an assessment initially up to 30 days |
| Confirmation | The CEO | The exact dataset, payout, rights, route and deadlines | Before SourceX presents the opportunity externally |
| Preparation and delivery | The system owner or IT lead | Access and inputs for extraction and de-identification through approved routes | A target of 7 to 10 days once access and inputs are ready |
SourceX's workload and timing assessment states the test in one sentence: a data deal is too distracting when it needs scarce people at a time they are already committed and cannot be paused cheaply. Acceptance review (up to 30 days) and invoicing come later. In the first 90 days the scarce people are almost always two: the CEO and whoever knows the systems.
The timing-capacity decision matrix
Get both answers from the company, not from its news.
- Capacity. In the next 90 days, can the CEO give a first conversation and name someone who can answer metadata questions about systems and years of records?
- Record clock. Will a dated event in the next six months (this page's choice of horizon) delete, strand or move records: a system switch-off, a vendor contract ending, a retention purge or a divestiture?
| No record clock | Record clock running | |
|---|---|---|
| Capacity in the next 90 days | Introduce when the CEO wants the conversation | Introduce now, and lead with the date |
| No capacity in the next 90 days | Defer to a named trigger and a calendar date | Warn, do not introduce: two lines to the CEO about the date |
A fifth outcome sits outside the grid. If a fit fact already fails, such as a company that never reached 50 full-time employees or whose valuable records belong to its clients, the row goes to a revisit list whatever the timing.
The warning note is deliberately small. Illustrative wording: "Before the old ticketing system goes dark on February 26, it may be worth keeping its closed history readable. If a data licensing conversation ever makes sense, SourceX's screening looks at years of documented operating history. Happy to explain once the integration settles." It makes no submission, names no reward and starts no attribution clock.
Default placements for common growth events, before the CEO has answered:
| Growth event | Usual capacity | Usual record clock | Default cell | What moves it |
|---|---|---|---|---|
| Raise in progress | No, until it closes | No | Defer to a date after closing | The CEO raises the topic first |
| First six months after an acquisition | No | Often | Warn | The integration plan names who keeps the legacy systems |
| System cutover underway | The CEO maybe; the system owner no | Yes | Warn, or introduce if the CEO can answer the application alone | The cutover date moves |
| Hiring surge | Varies | No | Defer or introduce, by the CEO's answer | A hiring milestone passes |
| Seasonal peak | No during the peak | No | Defer to the week after it | The calendar |
| Contraction or restructuring | Varies | Often | Warn or introduce | Who controls the company; under court control the CEO alone may not be enough |
An acquirer mid-integration and a freight brokerage before its peak (Illustrative)
Illustrative. Generic companies, invented dates and facts, no outcome implied.
Company A is a 320-person managed IT services firm that closed the acquisition of a 90-person competitor four months ago. It plans to retire the acquired firm's ticketing system on February 26, 2027, migrating open tickets only. The CEO is consumed by integration, one head of service delivery runs both ticketing systems, and counsel is renegotiating the acquired firm's customer contracts.
Company B is a 160-person freight brokerage adding 60 people ahead of its October-to-December peak. Nothing is changing in its systems, and its CEO and operations lead have said they are busy until mid-January.
| Question | Company A | Company B |
|---|---|---|
| Can the CEO give a first conversation in the next 90 days? | No, by the CEO's own account | No, until mid-January |
| Who could answer metadata questions? | The head of service delivery, who is fully booked | The operations lead, after the peak |
| Is a record clock running? | Yes: closed tickets of the acquired firm, February 26 | No |
| Are the fit facts known? | Size yes; rights in the acquired records unknown | Size and history yes; rights likely the company's own |
| Cell | Warn now | Defer to January 19, 2027 |
| What would change it | The CEO decides to keep the old system readable, which removes the clock | A slower peak, or the CEO asking sooner |
Company A is the hard case: its busiest moment is also when history can disappear. Which entity now holds the acquired firm's records is a question for SourceX's rights review, and the acquisition lineage map shows how to trace it. For the reward cap, a parent and its subsidiaries count as one company. Company B costs nothing to wait for; introducing it in October would have spent the attribution window on a quarter the company could not use.
Whether the growth event adds history or only workload
Workload is temporary; what the event does to the records lasts.
| Event | Effect on operating history | Effect on rights and ownership |
|---|---|---|
| Acquisition | Adds years of another company's records | They may sit in a different entity, under contracts the acquirer did not write |
| System replacement | Can cut history short if only open items migrate | Usually none, unless a vendor holds the only copy |
| Hiring surge | Adds volume, all of it recent | None |
| Contraction or divestiture | Keeps old history, but people who understand the systems may leave | Divested records go with the buyer |
The fragmented systems risk map goes deeper on migrations and roll-ups.
Sequencing asks when several portfolio companies are busy at once
Work a dozen busy companies in this order:
- Warning notes first. Two lines each, this week; they cost almost nothing and protect the history.
- Then the go cells. Companies with capacity, starting with any whose record clock is running.
- Then capacity without a clock, ordered by how many fit facts are already confirmed.
- Deferred companies go in a calendar, each with its trigger and date, never in an open-ended "later" pile.
Three limits apply throughout: the relationship owner agrees to ask the CEO, the fund decides who submits because only one partner is credited, and the team's hours cap how many companies are in active preparation; the capacity-limited queue rubric handles that side. Growth-equity teams will find the same timing questions from the operating side in the portfolio operations guide.
Where the matrix gives the wrong answer
- Capacity judged from outside. Board materials show what a CEO is doing, not what they would make time for.
- Clocks move. Vendors extend contracts and cutovers slip; recheck the date before acting on it.
- Narrow can beat later. SourceX's own assessment suggests narrowing to one record family or one system when that avoids the constrained people. A CEO may start on one system mid-integration.
- Waiting has a price. Only the first valid introduction is credited, so another partner may reach the CEO first, and SourceX's current data needs can change in either direction while you wait.
- Demand is outside the matrix. Perfect timing does not make records relevant; SourceX checks that in review.
Methods note. The two matrix questions and the default placements are this page's method. The attribution rule comes from the program terms and the sample Channel Partner Agreement; the company-side steps from SourceX's published process and workload assessment; the Form D timing from the SEC. All were checked on 2026-10-26. The matrix does not measure demand, record quality or any payout, and SourceX has not published how often deferred introductions convert.
A measurable next step. For each company on your list with a live growth event, record the CEO's answers to the two questions and the cell they produce. Re-ask on each trigger date. After two quarters, count how many introductions in the go cells reached a verified application inside 90 days, compared with any made outside them.
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 CEO tells you the next 90 days have room for the conversation, register for a partner link, confirm the company still meets who qualifies and read the attribution rule in the program terms before you submit; the venture platform teams page explains how funds run the program.
Timing an introduction around a company's growth is referral work, kept apart from any view of SourceX as an investment; readers weighing the latter can request investor materials 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.