# Refresh a referral shortlist without re-pitching | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-refresh-a-referral-shortlist-without-repeating-old-outreach
Last updated: 2026-11-04

Refresh the evidence before you refresh the outreach. For each row, pull the last contact date, what was said and why the row stalled, then look for a dated fact that has changed since and answers that stall. A row comes back only when such a fact exists and the person who would ask still has permission to. Recorded noes stay noes, companies already known to SourceX are left to SourceX, and any message you send opens with the new fact, never the old pitch.

An old shortlist is a record of what you did, not of what the companies are now. Treat it as a ledger of past contacts and questions, and rebuild each row's present state from fresh facts before anyone picks up the phone.

## Why a second pitch costs more than the first

The contact has already heard the idea. Sending it again tells them nothing has changed except your interest, and it spends the relationship holder's credibility with no new reason attached. Going around the CEO is one of the things SourceX's screening guidance lists as usually not a fit, and pressing a contact who has already passed does nothing to change what the CEO knows or wants.

The program adds two reasons to look before re-asking. Section 3 of the terms says: "A relationship includes any earlier lead, account or email correspondence between SourceX and the company, however it began." If the first round led a company to write to SourceX or to apply, a fresh introduction from you does not present a new company. Section 2 adds: "The 90-day window does not extend because contact protection under the agreement continues." An introduction from last year does not quietly hold its place. The terms do not spell out how a repeat introduction from the same partner is treated once the window has passed; SourceX decides that from the dated records in duplicate review, so no refresh should assume a reset.

## Rebuild each row from its clue, its path and its last touch

Before any gate, put six facts on every row:

- **Original clue and date:** what put the company on the list, and when you saw it.
- **Relationship holder:** who knows the CEO's circle, and whether that person is still in touch.
- **Last touch:** the date, the channel, who made it and exactly what was asked.
- **Outcome code:** no reply, not now (with any date given), revisit after a named event, a fit fact failed, declined, or do not contact.
- **Permission date:** when the contact last agreed to hear from you or your holder, if they ever did.
- **SourceX status, as far as you know:** link shared, company applied, or nothing.

Rows with no recorded last touch go to the back. A refresh cannot judge what changed since a contact nobody can date. The [industry shortlist guide](/guides/how-to-build-an-industry-specific-shortlist-of-suitable-introductions) covers building the list in the first place.

## The changed-facts and consent review

Six gates, in order. A row re-enters the outreach queue only if it clears all six.

| Gate | Question | Passes when | If it fails |
|---|---|---|---|
| 1. Recorded no | Did anyone at the company decline, or ask not to be contacted? | No such record exists | The row stays out unless the company itself reopens it |
| 2. Already with SourceX | Did the company apply, or correspond with SourceX, after the first round? | Nothing on record | Leave it to SourceX; no second introduction |
| 3. Stall reason | Why did the row stop? | The reason is written down | Find it first; a row with no reason cannot be refreshed |
| 4. Changed fact | Has something changed since the last touch, with a date and a source you can name? | One dated, sourced change | The row stays parked |
| 5. Relevance | Does that change answer the stall reason? | It does, such as a dated migration for a timing stall | Parked; an unrelated change is not a reason |
| 6. Current permission | Will the relationship holder ask again, and is any consent you rely on still current? | Yes to both | Parked until both are true |

Gates 1 and 2 run first because they are about the company's wishes and SourceX's records, not about your list. The [suppression pass for declined contacts](/guides/a-network-inventory-that-excludes-people-who-declined) handles gate 1 for a whole inventory. Gates 4 and 5 do the real filtering: a change only matters if it answers the reason the row stopped, which is why a headline event with no bearing on that reason never reopens anything.

Gate 6 is the easiest to skip. Permission has a shelf life in some places. The CRTC's guidance under the Canadian anti-spam law (CASL), for example, treats implied consent from an existing business relationship as generally lasting two years after the event that created it, or six months after a mere inquiry, while express consent lasts until it is withdrawn. In a 2019 enforcement decision the CRTC put the point plainly: "the date on which consent was obtained is essential to proving the existence of either valid express consent, or implied consent." Rules differ by country and by channel, so ask counsel how they apply to your firm. The habit worth keeping everywhere is recording when permission was given, right beside the date of the fact.

## New fact or old guess? Labeling lines before a row re-enters

Illustrative. Six lines a partner might add while refreshing, and whether each can carry a row back in.

| Line in the refreshed row | Type | Source and date | Reason to re-ask? |
|---|---|---|---|
| A new CEO was appointed where the old CEO said "not now" | Observed | Company announcement, 2026-09-15 | Only for a "not now", and only through the relationship holder |
| Headcount "grew to 80" | Inferred | Undated profile count | No; it may include contractors and is not the peak full-time figure |
| ERP migration set for the first quarter | Told by the CFO | Call on 2026-10-02 | Yes, for a row that stalled on timing |
| "Everyone is talking about AI now, so they'll be more open" | Inference | None | No |
| SourceX's screening criteria changed | Observed | The who-qualifies page, dated | Yes, but only for rows that stalled on that criterion |
| The company raised a growth round | Observed | Press release | No; funding answers no stall reason |

The first line is the subtle one. A "not now" was tied to a moment and a person, so a new CEO is a fair reason to ask the holder whether a fresh conversation would be welcome. A recorded no is the company's answer and stays in place until the company says otherwise. When a refreshed row also changes the facts in a brief you already sent, the [versioned brief routine](/guides/how-to-update-a-referral-brief-after-material-facts-change) covers telling SourceX.

## A 24-row shortlist after one refresh pass (Illustrative)

Illustrative. A consultant reruns a shortlist first worked a year ago.

| Outcome | Rows | What happens next |
|---|---|---|
| Recorded no or do not contact | 4 | Out; nobody writes |
| Already applied or in contact with SourceX | 2 | Left to SourceX |
| No dated change since the last touch | 9 | Parked with a named trigger |
| A change that does not answer the stall | 5 | Parked; the change is noted on the row |
| A relevant change, but the holder will not ask yet | 2 | Parked until the holder agrees |
| A relevant change and a holder ready to ask | 2 | Re-ask, leading with the new fact |
| Total | 24 | Two asks instead of twenty-four |

Sixteen rows stay parked, four are out for good unless the companies reopen them, two belong to SourceX already and two messages go out. That is the refresh working as intended. The parked rows are not lost: each carries the trigger that would bring it back, such as a dated migration, a new CEO after a "not now" or a criteria change.

## The re-ask: the holder asks, the new fact leads

For the rows that clear all six gates:

1. The relationship holder asks, not you, unless you are the holder.
2. The message opens with the dated new fact, says in one line why it may matter now, asks one question and makes a no easy. The [easy-to-decline ask](/guides/how-to-make-a-referral-ask-easy-to-decline) shows the shape.
3. Nothing from the first round is re-sent: no old deck, no forwarded thread.
4. If the CEO wants the conversation, share your partner link so the company applies itself. Questions stay at metadata level, and files, samples and logins stay with the company.
5. Whoever submits must have signed the SourceX Channel Partner Agreement.

If the reply is another "not now", record the date and any condition it names, and the row returns to the parked group with that condition as its trigger. A follow-up should only ever add something, as the guide to [follow-ups that add a useful answer](/guides/the-follow-up-that-adds-a-useful-answer) explains.

## How often to refresh, and what the review cannot see

Refresh when facts change, not when the calendar says so. A light quarterly pass over gates 1 to 4 keeps a list current; a full pass makes sense only when several triggers have fired. Running it more often than facts move just produces more parked rows.

The review has blind spots. Outreach that colleagues never logged will not show up at gate 1. Public facts lag reality. You cannot see SourceX's records, so gate 2 is only as good as what you know, and the terms note that SourceX checks its own records before inviting an introduced company in any case. For how long the attribution window runs and when it starts, see [the attribution window explainer](/questions/referral-attribution-window-length). SourceX has not published response rates for refreshed outreach, so measure your own: re-asks sent, replies, CEOs who wanted the conversation and any complaints.

## 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 clears all six gates and its CEO wants the conversation, [register as a partner](/register), recheck the company against [who qualifies](/who-qualifies) and read sections 2 and 3 of the [program terms](/terms) on attribution and duplicates before the holder sends a word. Guides on building and pruning the list itself sit alongside this one in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://crtc.gc.ca/eng/com500/guide.htm
- https://crtc.gc.ca/eng/archive/2019/2019-111.htm
