How to tie referral timing to company milestones without pressure: a milestone permission calendar in which the CEO names the milestone, the company signals when it is done, every entry expires and no milestone the fund controls ever carries the ask

Short answer

Tie the timing to a milestone the CEO names, not one you notice and never one you control. Ask the CEO once whether any point in the company's year would suit a licensing conversation, write the answer down in their words, wait for the company to say the milestone is done, then ask one question and let the entry expire if the moment passes. A milestone your fund controls, such as a tranche or a follow-on decision, never carries the ask.

Visual briefFull-size diagram
A timeline from left to right: a pin where the CEO names a milestone, a pin where the company says it is done, a short settle band, a single ask window and an expiry flag; below the line, a fund tranche pin is crossed out and marked never carries the ask.
Illustrative. The calendar's sequence on one row; the settle band and expiry are this page's defaults, not SourceX rules.

This playbook is for VC portfolio engagement leads. Events you learn about from the news or a network are sorted in the trigger-based referral calendar; this page handles the narrower case where the company itself sets the date. Payout milestones, the steps between a company's agreement and its payment, are a different subject, covered in explaining payout milestones.

When a company milestone turns into investor leverage

A milestone is a better clock than a calendar date because it belongs to the company. "After the new claims system goes live" respects the CEO's priorities in a way that "in Q3" does not. The risk comes from the investor's side of the table.

Venture funds can tie their own money to milestones. NVCA, which publishes model financing documents, says its updated models include mechanics for tranched financings, making funding released on a time or milestone basis more efficient (our paraphrase of a search excerpt from NVCA's model documents page). When a fund's next tranche and a referral question hang off the same milestone, a CEO cannot tell whether saying no costs anything. Even an honest ask then reads as a condition.

The same goes for what the fund learns in the boardroom. SourceX's screening page says a board seat "does not let the fund start that discussion," and that what a fund knows through board materials "is a reason to ask the CEO, never material to pass along." A milestone the board discussed, but the CEO never mentioned to you in connection with this idea, is not a permission.

What a milestone moves, and the facts it leaves where they were

A milestone can make a conversation welcome. It cannot make a company fit, and the calendar never treats it as if it could.

InputChanged by a milestone?Why
The CEO's attention and calendarYesA go-live, a close or a launch frees or consumes it
Which systems are live and settledYesThe company decides its own projects
Who could join a first callSometimesA new hire or a reorganization changes the cast
Peak full-time headcount, contractors excludedNoIt is a historical high point
Years of records the company createdNoHistory does not grow at a milestone
Rights to license those recordsNoSettled in SourceX's review and with the company's counsel
Who decidesNo, unless the CEO changesUnder the program, licensing discussions and signatures belong to the CEO
Earlier contact with SourceXNoSection 3 of the terms makes any earlier application, lead, account or email a duplicate

If the CEO changes before the milestone arrives, the row lapses with them; the succession handoff checklist covers what to do next.

The milestone permission calendar

One row per company, nine fields, filled only from what the CEO said or what the company announced. No file, board pack or system is consulted.

FieldWhat to writeRule
1. Company and entityThe entity that holds the recordsOne row per company; sister companies in one group sit together
2. Milestone, in the CEO's wordsThe sentence as saidOnly a milestone the CEO named in answer to your question
3. Named on, and to whomDate and the person who heard itThat person owns the row
4. Done signalHow the company will let you know: an announcement, or the CEO raising it at a scheduled check-inNever inferred from board material, never asked about ("is it live yet?")
5. Settle periodThe time the CEO suggested, or a default you setWe use one month after the done signal
6. Earliest askDone signal plus settle periodNo ask before it
7. ExpiryA date you set when the row opensWe use twelve months; no done signal by then closes the row
8. Fund-controlled?Yes or noYes means the row is rewritten around a company milestone or closed
9. OutcomeAsked, declined, introduced, expired or withdrawn, with the dateCloses the loop

Four disciplines keep the calendar from becoming a nag list:

  • One ask per row. A decline closes it. A "not yet" opens a new row only if the CEO names a new milestone.
  • One slip. If the milestone moves, the row moves once. A second slip closes it as "no window now"; the CEO can reopen it at any time.
  • No re-dating. An expired row stays expired. Re-dating it to keep it alive defeats the expiry.
  • A crisis overrides everything. Layoffs, a dispute, illness or an investigation hold every row until the company says the matter is closed.

Method note. The nine fields, the one-month settle period, the twelve-month expiry and the slip rule are this page's design, built from SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and screening page and NVCA's model documents page, all read on 2026-10-28. They are not SourceX rules. Record demand, quality and any payout are left to SourceX's review.

Three milestones, three treatments (Illustrative)

Illustrative. Generic companies and invented facts; nothing here implies an outcome.

CompanyMilestone and who named itDone signalWhat happened
A 160-person claims-processing company"After the new policy system goes live in Q2," said by the CEO in MarchGo-live announced in JuneAsked once in July; the CEO agreed to an introduction
A 230-person managed-services firm"Once we've closed the acquisition we're negotiating," said by the CEO in JanuaryNone by October; the deal slipped twiceClosed as "no window now"; nobody chased
A 300-person software company"When we confirm the next tranche," proposed by a fund partnerNot applicable: fund-controlledNo row; the pairing was dropped

The claims company shows the before and after. In March the CEO was mid-project with no room; the facts that matter for fit were already what they would be in July. In July the project was done, the CEO had time, and one question fitted. Nothing about the company's records, headcount or rights had changed in between.

A badly timed version. The software company is due to receive its second tranche when it reaches a revenue milestone. A fund partner suggests raising SourceX "at the board meeting where we confirm the tranche, while they're in a good mood." The CEO would hear a licensing idea from the people releasing their money, in the same meeting. The repair is simple: no row. If the CEO later names a company milestone of their own, that can start one.

Rechecking authority and capacity when the done signal arrives

A done signal opens the window; it does not send the question. The row's owner confirms, from the relationship and public facts:

  1. The CEO who named the milestone still holds the role.
  2. The signal came from the company, in an announcement or from the CEO, not from a board pack or a colleague's guess.
  3. The settle period has passed and nothing new has filled the CEO's calendar.
  4. No crisis override applies.
  5. No earlier SourceX contact has come to light, and the published fit checks still hold or remain open: peak full-time headcount of 50 or more, contractors excluded, and years of records the company created and can license.
  6. Only one person will ask. Anyone else in the fund who knows the CEO hears that the row is taken.

Asking with the milestone the CEO named

Quote the CEO's own words back, ask once and name your interest:

In March you said a conversation about SourceX would make more sense once the new policy system was live. You announced the go-live in June, so I'm asking once, as you suggested. SourceX licenses records a company created in its own work for AI training and evaluation, and decides fit after its own review. If an introduction from me led to a license, SourceX could pay me a referral reward, separately from what it pays your company. If now still isn't right, I'll take that as the answer.

The reward line rests on section 4 of the terms: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation." Record the answer in field 9. A yes means you sign the SourceX Channel Partner Agreement before submitting, make the introduction and let the company apply itself.

Submit only after that yes. Section 2 credits "The first valid introduction of a new company within the 90-day attribution window" once the company submits a verified application, and "The 90-day window does not extend because contact protection under the agreement continues." An introduction filed when the milestone was first named, months earlier, would introduce a company that had not yet agreed to anything. A no is handled as in an ask that is easy to decline; a fresh "not yet" as in when a founder says the timing is wrong.

Where a milestone calendar backfires

  • Dates harden into duties. A row is permission to ask once, not an obligation to.
  • The calendar drifts into a file on the company. Keep it to the CEO's words and the company's announcements; board information never goes in.
  • Fund milestones creep back. A follow-on, a tranche or a board vote can sneak into field 2 as "the company's" milestone; field 8 exists to catch it.
  • Several owners, one CEO. Two colleagues who each heard a different milestone create two rows; merge them under one owner.
  • No outcome data. SourceX has published no figures on milestone-timed introductions. To test the calendar, count rows opened, done signals received, asks made, CEOs who agreed and rows that expired.

For other ways to time a question, browse the guides hub.

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 row reaches its earliest ask and the CEO says yes, register as a partner, compare the company with the screening profile and read the attribution section of SourceX's referral terms before you submit.

Scheduling a referral question is network work. Diligence on SourceX as a possible investment sits apart from it, and materials for that can be requested on 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

The CEO never named a milestone. Can we pick a sensible one for them?

No. A milestone you choose is a reminder for you, not permission from the CEO. Without one, there is no row; the next ordinary conversation can ask whether any point in the year would suit.

Should we submit the introduction when the CEO first names the milestone, so it is on record early?

No. Submit only after the CEO says yes at the milestone. Section 2 of the terms counts credit within a 90-day attribution window that does not extend, so an early submission helps nobody and introduces a company that has not agreed.

Our fund releases the next tranche at a revenue milestone. Is the day it is released a good moment, since the CEO will be in a good mood?

It is the worst moment. When the fund's money and the referral question share a milestone, the CEO cannot tell whether a no costs anything. Keep the two apart permanently.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. nvca.org/model-legal-documents
  4. 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