How to pause an introduction without losing trust: a reason-and-restart log in which every pause names who at the company can lift it, and a no is closed instead of parked

Short answer

Pause an introduction by writing down three things the day you stop: the reason, as one code; who can lift the pause, which is always someone at the company, never you; and the observable event that would let them. Then tell the founder, once, that nothing moves until they say so. If no company-owned restart condition exists, you are holding a decline, not a pause, so close it. The 90-day attribution window keeps running either way, and that cost stays with you.

Visual briefFull-size diagram
A state diagram: an introduction in progress moves to paused with a logged reason, returns only when a company-owned event is met and the company asks again, or moves to closed when no restart condition exists; a bar beneath shows the 90-day attribution window running on through the pause.
The log on this page in one picture. The window bar is schematic: the terms say the 90-day window does not extend.

Trust is lost in pauses, not in noes. A founder who said "not yet" and then hears from you every few weeks learns that "no pressure" meant the opposite, and an investor's ask already carries weight it does not intend.

Who asked for the pause changes what you owe

Pauses come from four directions, and each sets different duties.

Who stopped itWhat they usually sayWhat you oweWhat you never do
The founder you know"Let me raise it with our CEO first"Silence until the founder or CEO comes backContact the CEO yourself
The CEO"Not until the migration is done"One check at the event they namedWrite before the event
A company process"It has to go to our AI committee or board"Wait for the company to reportAsk who on the committee is for or against
You"Our fund is negotiating with them right now"End your own hold and say so onceBring the program up during the conflict

Investors forget the fourth row. While your fund is leading a round, sitting in a board dispute or renegotiating with a founder, any mention of a referral can sound like a condition. Holding your own ask then keeps any later conversation voluntary.

Pause or decline: three questions before you log it

A row belongs in the pause log only if all three answers are yes.

  1. Is there a restart condition the company owns? A dated event, an approval, an answer from counsel. "When things calm down" is not one.
  2. Is there a named person at the company who decides whether to resume? Under the program that is the CEO, or a new CEO after a change of control.
  3. Did the company ask for the pause, or agree to it? For a hold you started yourself, the company's agreement comes later, when it chooses whether to pick the subject up.

Any no means a decline, and a decline is closed the same day. Parking a no in the pause log is how polite follow-ups turn into pressure. The company controls whether to proceed at every stage, and a founder who changes their mind owes nobody a reason; the question on owners changing their minds covers what that means for any reward, and making an ask easy to decline covers the wording that keeps a no cheap.

The pause-reason and restart criteria log

One row per company. The code fixes the restart criterion and the check rule, so nobody improvises a follow-up later.

CodeReasonRestart criterionWho decides to resumeCheck ruleWhat stays frozen
P1Founder interested; CEO not yet askedThe CEO says the company wants the conversationThe CEOThe founder or CEO tells you; you never ask the CEOAll contact with the CEO and SourceX
P2Company event under way: migration, audit, sale processThe dated event is complete and the CEO confirmsThe CEOOne message after the event dateEvery message before that date
P3Internal approval pending: policy committee, board, co-foundersThe approval exists in writingThe CEO, after the named approverThe company reports backAny submission
P4Rights question open: client contracts, privacyThe company's counsel has answeredThe CEO, on counsel's adviceThe company reports backAny metadata beyond what was already shared
P5Your own conflict: financing round, board disputeYour conflict has endedThe founder or CEO, freelyOne note that your hold is over, with no askEvery mention of the program
P6Decision-maker changing: CEO departure, acquisitionA new CEO is in placeThe new CEOOne message raising the topic once the change is announcedEverything, including earlier permissions
DDeclineNoneNobody; the row is closedNeverEverything, unless the company raises it

Each row also carries four dates: paused, check date, restarted or closed, and the date of any message you sent. Attribution is decided from dated records, so a log kept at the time is worth more than recollection.

What the founder hears when you pause

One message, sent the day you pause, in plain words. Three cover most cases.

Your own conflict (P5).

I mentioned a SourceX introduction a few weeks ago. While our financing conversation is open, I'm going to leave it alone, so nobody could read one as connected to the other. I won't raise it again during the round. If you ever want to pick it up, it's yours to raise.

Interest ahead of authority (P1).

Thanks for being open to it. Let's go no further until {CEO} has decided whether the company wants the conversation. I won't contact {CEO} or SourceX. If the answer is yes, either of you can tell me.

Closing a decline (D).

Understood, and thank you for telling me plainly. I've closed it on my side and won't bring it up again.

When the company itself asks for time and names terms for the wait, the follow-up after a company asks for more time gives the one message to send on their date.

One platform team's log, sixty days on (Illustrative)

Illustrative. The companies below are generic and their facts invented; no outcome is implied for any of them.

CompanyCodeRestart criterionSixty days later
230-person freight brokerage; the COO co-founder is keenP1The CEO wants the conversationThe CEO said yes on day 21; permission reconfirmed and the introduction restarted
310-person dental support organization moving to a new ERPP2Migration complete and the CEO confirmsStill paused; the cutover is planned for day 75
140-person engineering consultancy whose bridge round the fund is leadingP5The round has closedClosed on day 40; one note sent; the founder has not raised it, so the row closes at the check date
180-person regional law firm; the managing partner and CEO said noDNoneClosed on day 0; no contact since

Two of the four rows will never restart, and the log treats that as normal. The delayed referrals guide shows how to report paused rows as open cases rather than losses.

What a pause does to credit and contact

Credit under the terms belongs to one partner per company: the partner whose valid introduction of a company new to the program came first inside the 90-day attribution window, and only once that company submits a verified application. The terms add that the 90-day window does not extend because contact protection under the agreement continues. A pause therefore stops nothing on the program's side. A P2 row paused in month one for a migration in month four may well outlast your window, and the right response is to accept that, not to bring the restart forward.

If you already submitted the introduction, the terms let SourceX communicate with the referred company directly without affecting valid attribution. Tell SourceX the company asked for quiet and agree who, if anyone, speaks next, so the company hears from one person. If the company later applies through another route, duplicate review decides from the dated records. The attribution window question and attribution versus contact protection explain the two clocks.

Waiting does not change the reward either. It stays at the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, with the USD 50,000 floor applying once per referred company, paid by SourceX separately and never deducted from what the company receives.

Restarting means asking again, not resuming

When a restart criterion is met, treat it as a new ask on a known subject. Confirm with the CEO what may be passed on now, because a permission given before a migration, a round or a change of CEO may have narrowed. Hand SourceX only that approved context. The pause itself, its code and its reason stay in your log unless the CEO wants them shared. Record the restart date beside the pause date.

Recheck the fit facts at the same time. Full-time headcount at peak does not fall with later layoffs, so a company that reached 50 or more full-time employees at peak keeps that history. Ownership may have moved: once a company is acquired, the acquirer's CEO decides. Records can disappear in a migration. 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. Partners ask about records at metadata level and never handle them; whether they match a current program stays unknown until SourceX reviews them.

Where the log can fail, and how we built it

Method. The seven codes come from the program terms and the screening profile, both checked on 2026-10-26, and from the ways authority and permission separate in an investor relationship. They were not derived from founder interviews; none on this question have been published, and SourceX has not published how often paused introductions restart. To measure your own, count pauses by code each quarter and the share restarted within 180 days, and keep declines in the denominator.

  • A polite reason may be a no. The log records your conduct, not the founder's state of mind. If a P2 event passes and nothing follows, close the row.
  • Your hold does not move authority. Delaware's corporate statute puts a corporation's business and affairs under the direction of its board unless the statute or the certificate of incorporation says otherwise, and the program names the CEO as the one who authorizes. Pausing or restarting your ask changes neither.
  • The investor's leverage never fully disappears. A P5 hold reduces the risk that an ask reads as a condition; it does not remove it. Some founders will never raise the subject with their lead investor, and that is their right.
  • The window cost is real. Long pauses will sometimes mean no credit. The log is designed to accept that cost rather than spend trust avoiding it.
  • Criteria move. Fit follows the specific program, so a company paused for a year may face different criteria when it returns.

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.

Before you resume any paused row, register for a partner link if you have not, recheck the company against who qualifies and reread the program terms, then ask the CEO again rather than picking up where you stopped. Platform teams running several founder relationships can start from the venture platform overview or the guides.

Keeping a pause log is referral work; evaluating SourceX as a possible investment is a separate decision, and anyone weighing it can ask for SourceX's investor materials through the 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

Can I pause an introduction to protect my attribution?

No. The terms say the 90-day attribution window does not extend because contact protection continues, so a pause neither stops the clock nor reserves credit. If the company applies after your window, that cost is yours; rushing the company to beat it costs more.

What if the founder never comes back after a pause?

Then the log's check rule decides. Most codes allow one check at the restart event, or none at all. If the company does not pick it up, close the row with the date and do not write again unless the company writes first.

Should I tell SourceX about a pause?

Only if you have already submitted the introduction. SourceX may contact a referred company directly, so tell it the company asked for quiet and agree who, if anyone, speaks next. If nothing was submitted, there is nothing to tell.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. refer.sourcex.si/how-it-works
  4. delcode.delaware.gov/title8/title8.pdf
  5. 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