Fatigue is a total, and the founder pays it
A platform team sees programs: the newsletter, the perks catalog, the talent network, the LP survey, events, vendor introductions, and perhaps a data licensing referral track. A founder sees one inbox in which all of them arrive from "the fund". Each team can be disciplined about its own sends while the founder still receives an ask every few days.
The founder benefit of a data licensing mention is specific: a CEO learns whether the company's own records could be licensed for AI training and evaluation, and gets an introduction to SourceX only if they want one. The constraint is attention, the founder's first and the platform's second. That makes data licensing an opt-in program by nature; the comparison of opt-in and mandatory portfolio programs puts a data licensing review in the opt-in group because the company decides and signs. Repeated nudges turn an opt-in into pressure, and pressure defeats the program's own rule: an introduction the decision maker never knew about is usually not a fit for SourceX, and one a CEO accepted only to make the emails stop is not much better.
The 90-day offer and consent audit
Build one log, one row per ask, across every sender in the fund. Ninety days is long enough to catch quarterly programs and short enough to pull from memory and inboxes.
| Field | What to record | Why it matters |
|---|---|---|
| Founder and company | One row per founder per ask | Counts by person, not by program |
| Sender | Platform team, investing partner, vendor through the platform, another founder | Founders attribute all of it to the fund |
| Date | When the ask went out | Builds the 90-day window |
| Ask type and points | FYI 1; click or RSVP 2; written reply 3; meeting or call 4; pull in a colleague 5 | Weighs effort, not just count |
| Consent signal | Requested it; opted into this category; no signal; said "not now" | Separates wanted asks from pushed ones |
| Outcome | Acted, declined, no response | Silence is information too |
| Nudges | How many follow-ups on the same ask | Repetition tires people faster than variety |
Then apply four rules, set before anyone looks at a founder's numbers. The figures are Illustrative starting points, since nobody has published a benchmark for founder ask load:
- Budget. No more than 30 ask points per founder per 90 days.
- Consent share. No more than one ask in three sent with no consent signal at all.
- Pause. A "not now" pauses that whole category, from every sender, for 90 days.
- Nudges. One follow-up on any ask the founder did not request, then stop.
A data licensing mention gets a single slot, and only when four things are true: the desk screen on what the fund already knows passes the published fit facts; the founder has room under the budget; the person who owns the CEO relationship raises it inside a conversation already on the calendar, not in a blast; and no pause covers third-party offers. After one mention and at most one follow-up, the topic comes back only if the founder raises it. The portfolio referral screen covers the desk screen itself, and a double opt-in introduction covers the moment a CEO says yes.
Three founders in one quarter's audit (Illustrative)
Illustrative. Generic companies, invented counts, window ending 26 October.
| Founder | Asks in 90 days | Ask points | Asks with no consent signal | Asks acted on | Verdict on a data licensing mention |
|---|---|---|---|---|---|
| A. CEO of a 210-person logistics software company | 6 | 11 | 1 of 6 | 4 | Room: the partner raises it at next month's check-in; the full track would bring A to 23 points |
| B. CEO of a 95-person clinic operations company, mid-fundraise | 14 | 33 | 9 of 14 | 2 | Over budget on both counts: suppress every optional ask for the quarter, the platform's own first |
| C. CEO of a 70-person construction estimating firm | 4 | 7 | 0 of 4 | 3 | Blocked by consent, not load: said "not now" to third-party offers on 12 September, so wait for the pause to lapse or for C to raise it |
Founder B is the case the audit exists for. No single team sent B too much; together they sent 14 asks in a quarter while B was raising money, and B acted on 2. Adding a data licensing mention, however well screened, would make the fund's fifteenth request. Founder C shows why load alone is not enough: C's numbers are low, but C has already said what C wants.
Work at each referral stage, in founder minutes and ask points
Platform hours are only half the cost. The other half is what each stage asks of the founder. The model below books referral income at zero, because nothing the fund does triggers a payment: the default reward is the greater of $50,000 plus 5% and 15% of what SourceX actually pays the referred company, with no cap and funded separately from the company's payout, and nothing comes due until two things are done (the handoff, and a final written acceptance of the complete, validated dataset from the Acquisition Partner), and even then only with cleared payment to SourceX, payment of the company, SourceX finance approval and the partner's tax and payment details in place.
Illustrative planning numbers for one company that goes all the way to an introduction:
| Stage | Who works | Platform minutes | Founder minutes | Ask points added |
|---|---|---|---|---|
| Desk screen from data the fund already holds | Platform analyst | 20 | 0 | 0 |
| Relationship owner raises it in a scheduled check-in, with a yes or no question | Partner or platform lead | 10 | 5 | 3 |
| First conversation about records, metadata only | Platform lead and CEO | 45 | 30 | 4 |
| One follow-up for a missing fit fact | Platform lead | 10 | 10 | 3 |
| Introduction with the CEO's consent, through the partner link | Platform lead | 15 | 10 | 2 |
| Through the introduction | Everyone above | 100 | 55 | 12 |
The founder's time in SourceX's own review is not estimated here, because SourceX runs that process and the fund should not guess at it for the CEO. Even without it, a full track costs a founder close to an hour and 12 ask points, more than a third of the quarter's budget. The audit itself has a cost too: the first pass across 25 founders, pulling sends from email, the newsletter tool, event RSVPs and partner calendars, takes roughly 6 platform hours in this Illustrative setup, and about 2 a quarter once every team writes to a shared send log. For platform hours per qualified introduction in more detail, see whether data referral work is worth a platform team's time.
There is also a lower-load route. A short opt-in session at a CEO summit lets interested founders come forward without anyone receiving an individual ask; CEO summit agenda ideas sketches one.
Expand, pause or stop
Read these at each quarterly audit. As with the budget, the thresholds are starting points a fund should set for itself before it sees results.
| Reading at the quarterly audit | Expand the mention to more founders | Pause | Stop the track |
|---|---|---|---|
| Founders over the 30-point budget | None | One or two, brought under by suppression | Three or more, two quarters running |
| "Not now" requests honored across all senders within 10 business days | All | One late, and the process fixed | Any repeat miss |
| Founders who asked for the SourceX conversation after a single mention | Two or more | One | None after two quarters |
| Founders who asked to stop all third-party offers after a mention | None | One | Two or more |
| Median founder rating of the first conversation, 1 to 5 | 4 or higher | 3 | 2 or lower |
The 10-business-day line has an outside reference. For commercial email, the FTC's CAN-SPAM guide requires opt-out requests to be honored within 10 business days and the opt-out method to keep working for at least 30 days after sending. Whether a given platform message counts as commercial is for counsel to judge, but treating every "not now" as binding within that window, across every sender, is a cheap way to make the question moot.
A track that should stop (Illustrative). Over two quarters a fund mentions data licensing to nine founders who passed the screen and had room in their budgets. One asks for a conversation and rates it 2 out of 5; two ask to be taken off all third-party offers. Three rows hit "stop" at once. Close the track, keep each company's screening notes with the condition that would reopen it, and raise the topic again only when a founder brings up their records or a documented event, such as a system retirement, appears. SourceX notes that a company which does not fit one program may fit another later, so the notes keep their value.
What a founder hears about fit, and what stays with SourceX
When a founder does want the conversation, keep it to facts the founder can check. The company must have peaked at 50 or more full-time employees, contractors not counted, and have an operating history it can document and the rights to license its records; in this program the CEO is the authorized contact, the one who authorizes a licensing discussion and signs. 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. Funding stage plays no part.
SourceX decides in its own review whether the records match its current data needs and whether rights in client contracts allow licensing. The platform team never asks for files, samples or logins; its questions stay at metadata level: which records, roughly how many, over which years, in which system, owned by whom.
Where the audit can mislead
- Unlogged channels. Dinners, texts and partner calls rarely make it into a send log. Record what you can and note what the log misses.
- Points are a proxy. A five-point ask the founder wanted is not fatigue; the consent column exists to catch that.
- Silence is ambiguous. Some founders read everything and act months later.
- Stale consent. A category a founder opted into two years ago may not reflect what they want during a fundraise.
- Small numbers. Twenty-five founders over one quarter cannot support firm thresholds; treat the first two audits as calibration.
- Demand outside the fund's control. SourceX checks relevance to its current data needs in review, so a well-timed, welcome mention can still end in a no.
Methods note. The audit fields, point weights and budget are this page's own design, built from SourceX's referral terms (Version 2026-10-22.2, since replaced by version 2026-11-04), its who-qualifies page and the FTC's CAN-SPAM guide, all checked on 2026-10-26. Every count and minute in the tables is Illustrative; nothing was measured. Not measured: founder sentiment beyond a single 1 to 5 question, the effect of any ask on a founder's relationship with the fund, and reward income.
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 the audit shows a founder with room, consent and a company that passes the screen, get your partner link, hold the company up against who qualifies one more time and read the program terms yourself before the relationship owner says a word to the founder. The venture platform teams page covers the program from the portfolio side.
Auditing founder asks is a referral-side decision. Anyone weighing SourceX as a possible investment should treat that as its own review, starting from the investor materials offered 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.