When growth creates too much work for a referral conversation: a timing-capacity matrix that weighs the CEO's next 90 days against the date records disappear

Short answer

Growth creates too much work when the two people a data conversation needs first, the CEO who authorizes it and the person who knows the systems, are committed for the next 90 days to an integration, a system cutover, a raise or a hiring push. Then introduce only if a dated event threatens the records, and even that starts as a short note to the CEO. Otherwise defer to a named trigger and date: SourceX credits an introduction only when the company applies within 90 days.

Visual briefFull-size diagram
A two-by-two matrix of the CEO's time in the next 90 days against a running record clock, with four verdicts: introduce when ready, introduce now, defer to a dated trigger, and warn without introducing; Illustrative company B sits in defer and company A in warn.
Illustrative companies A and B from this page. Real placement depends on what the CEO says about the next 90 days and on dates the company sets.

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 eventWhere the signal usually comes fromWho it loadsRecord clock?
Equity raiseThe founder's update, or a Form D notice, due within 15 calendar days of the first saleCEO, finance lead, counselRarely
Acquisition and integrationAn announcement, then board materialsCEO, counsel, ITOften: the acquired company's systems get retired
System replacementThe IT roadmap or a vendor contract end date; seldom publicThe system ownerYes: the old system's switch-off date
Hiring surgeJob postings and the platform's own talent teamCEO, team leadsNo
Seasonal peakThe company's calendarOperations, financeNo
Contraction or restructuringNotices and announcementsCEO, finance, counselOften: 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:

StageWho at the companyWhat it needsTiming SourceX states
Apply and qualifyThe CEO, helped by whoever knows the systemsA few questions, no files: systems, years of history, what can be exported; SourceX then completes the inventory with the company and runs the rights checkNot stated
Rights triageCounsel with a contracts leadWhich customer, vendor and employee terms touch each record familyPart of qualification
Master signatureThe CEOOne agreement, signed once after qualificationStarts an assessment initially up to 30 days
ConfirmationThe CEOThe exact dataset, payout, rights, route and deadlinesBefore SourceX presents the opportunity externally
Preparation and deliveryThe system owner or IT leadAccess and inputs for extraction and de-identification through approved routesA 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 clockRecord clock running
Capacity in the next 90 daysIntroduce when the CEO wants the conversationIntroduce now, and lead with the date
No capacity in the next 90 daysDefer to a named trigger and a calendar dateWarn, 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 eventUsual capacityUsual record clockDefault cellWhat moves it
Raise in progressNo, until it closesNoDefer to a date after closingThe CEO raises the topic first
First six months after an acquisitionNoOftenWarnThe integration plan names who keeps the legacy systems
System cutover underwayThe CEO maybe; the system owner noYesWarn, or introduce if the CEO can answer the application aloneThe cutover date moves
Hiring surgeVariesNoDefer or introduce, by the CEO's answerA hiring milestone passes
Seasonal peakNo during the peakNoDefer to the week after itThe calendar
Contraction or restructuringVariesOftenWarn or introduceWho 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.

QuestionCompany ACompany B
Can the CEO give a first conversation in the next 90 days?No, by the CEO's own accountNo, until mid-January
Who could answer metadata questions?The head of service delivery, who is fully bookedThe operations lead, after the peak
Is a record clock running?Yes: closed tickets of the acquired firm, February 26No
Are the fit facts known?Size yes; rights in the acquired records unknownSize and history yes; rights likely the company's own
CellWarn nowDefer to January 19, 2027
What would change itThe CEO decides to keep the old system readable, which removes the clockA 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.

EventEffect on operating historyEffect on rights and ownership
AcquisitionAdds years of another company's recordsThey may sit in a different entity, under contracts the acquirer did not write
System replacementCan cut history short if only open items migrateUsually none, unless a vendor holds the only copy
Hiring surgeAdds volume, all of it recentNone
Contraction or divestitureKeeps old history, but people who understand the systems may leaveDivested 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:

  1. Warning notes first. Two lines each, this week; they cost almost nothing and protect the history.
  2. Then the go cells. Companies with capacity, starting with any whose record clock is running.
  3. Then capacity without a clock, ordered by how many fit facts are already confirmed.
  4. 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.

  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

Why not introduce a busy company now and let it apply when it is ready?

Because credit attaches only if the company submits a verified application within 90 days of the recorded introduction, and the terms say the window does not extend. An introduction the company cannot act on for months can lapse before it counts.

Is a warning note to the CEO an introduction?

No. A note that names a date and suggests keeping old records readable involves no submission to SourceX and starts no attribution clock. It keeps the option open until the CEO has time to decide.

What if the CEO says the timing is fine during an integration?

Then the CEO's answer wins. The matrix replaces your guess about their capacity, not their judgment; narrowing the first conversation to one system that the busiest people do not run is often enough.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. refer.sourcex.si/who-qualifies
  4. sourcex.si/how-it-works
  5. sourcex.si/insights/data-licensing-operational-distraction
  6. sec.gov/resources-small-businesses/exempt-offerings/…
  7. a16z.com/executive-hiring
  8. 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