# Co-investor founder outreach: one contact plan | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-avoid-duplicate-founder-outreach-across-co-investors
Last updated: 2026-11-05

Agree a written contact plan before any co-investor writes to the founder. It names one sender, one channel and one send window, keeps every other investor silent until the founder replies, and hands them a single sentence to use if the founder brings SourceX up. The founder's answer is logged once and honored by all. Only one partner can be credited per company, so extra emails produce confusion and duplicate-review work, never extra credit.

Duplicate outreach rarely comes from bad intent. It comes from helpful people on different schedules: a portfolio newsletter, an aside at the end of a board call, a forwarded article marked "thought of you". Together they leave the founder with three descriptions of one program and no idea which investor to answer.

## Where the extra messages come from

List every channel through which an investor could reach the founder about SourceX, and who controls it. The founder gave each investor a relationship, not permission to pitch outside services; the CEO decides whether the company talks to SourceX, and SourceX's screening page counts introductions made without the decision maker's knowledge among those usually not a fit.

| Channel | Who controls it | How it turns into a second message | Plan rule |
|---|---|---|---|
| Portfolio newsletter or mailing | Each fund's platform team | A general paragraph lands beside another fund's personal email | Companies on a plan are left out of SourceX mentions until the founder answers |
| Board call or board dinner | Board members | A spoken aside, then a follow-up email with a link | Board members use the agreed line and nothing more |
| A partner's own inbox | Individual partners | A well-meant forward of the public SourceX site | No forwards; only the named sender writes |
| A co-investor's founder webinar | That fund's platform team | The founder signs up and hears a second pitch | The founder is invited only if the founder asks |
| A peer founder in the portfolio | Nobody on the investor side | One founder recommends SourceX to another | Outside the plan; the sender pauses and asks the founder |

## What the founder receives when nobody coordinates

Picture the founder's week: a newsletter paragraph on Monday, an email with a partner link on Wednesday, a board member on Friday asking about "the SourceX thing". Three wordings, perhaps three hints about what the company might earn. It reads like a campaign, and it invites a fair question: which of you gets paid for this?

The terms make the duplication pointless as well as awkward. Section 2 says "Only one partner is credited per company," and credit goes to the first valid introduction of a new company inside the 90-day window, once it files a verified application. A forward can also misfire quietly. If the founder reads a forwarded public page and applies alone, the company now has an application of its own, and section 3 is explicit: "Companies that already have an application, relationship or earlier valid introduction with SourceX are reviewed as duplicates and are not credited to a later partner." A direct application is a fine outcome for the company; the plan exists so that, if an investor introduces, it happens once and on the record.

## The shared permission-based contact plan

One page, agreed by every investor who knows the founder, before anyone writes. Each field has one owner, and every line depends on the founder's answer.

| Field | What it holds | Filled by |
|---|---|---|
| 1. Company and contact | Legal name, web domain, and the founder-CEO as the one person contacted | The sender |
| 2. Sender | One named person who has signed the SourceX Channel Partner Agreement | All investors on the plan |
| 3. Channel | The channel the founder already uses with the sender: a weekly call, a text thread or email | The sender |
| 4. Send window | Two or three dates clear of the founder's known crunch weeks | The sender, checked by the board member |
| 5. Message | Approved text: what SourceX does, that the first step is a few questions and no files, and that the sender is a registered partner who may receive a reward from SourceX | Drafted by the sender, read by the others |
| 6. Hold list | Every other investor on the plan, silent about SourceX with this founder until the founder answers or the plan closes | Each investor, confirmed in writing |
| 7. If-asked line | One sentence for held investors (below) | All investors on the plan |
| 8. Founder's answer | Yes, not now with the founder's own date, or no, plus the date it was given | The sender |
| 9. Record | The written, dated introduction, if the answer is yes | The sender |
| 10. Status rule | What the sender may pass to the others, and only with the founder's agreement | All investors, confirmed by the founder |
| 11. Close date | When the plan ends: an introduction, a no, or the founder's not-now date | The sender |

The if-asked line, word for word: "Yes, we know about it. [Name] is the one person from your investors who will walk you through it, whenever you want, and you are free to tell us you would rather not." It confirms, routes and releases, and it says nothing about the company's prospects.

The message in field 5 should fit on a phone screen and describe the first step accurately: SourceX's process page says a company starts with a few questions and no files, listing its systems, years of history and what can be exported. A message that promises a price or an acceptance breaks the plan as surely as a second sender.

## Choosing the sender without a contest

The sender is the investor the founder already talks to about running the company, not the largest stake or the earliest idea. That person signs the Channel Partner Agreement before submitting anything and knows whether their fund lets them accept a reward. If two investors want the role, settle it first with the nomination order in [one company, three funds](/guides/one-company-three-funds-who-makes-the-introduction); the plan starts once field 2 holds one name.

## Timing, quiet weeks and the founder's answer

Real urgency is a documented event with a date: a system migration, an archive deletion, a retention change. A quarter-end is not, and neither is a funding announcement, as [automatic outreach after funding news](/guides/why-funding-announcements-should-not-trigger-automatic-outreach) explains. Keep the send window away from a financing close, a layoff, a board meeting week or a sale process. If the company is being sold, the target's CEO decides until closing and the acquirer's CEO afterward, so a plan written before a sale may need a new contact in field 1.

The founder's answer binds everyone on the plan:

- **Yes.** The sender submits a written, dated introduction the same day. Section 1.2 of the agreement sample wants introductions in writing and gives an oral one no protection until it is confirmed in writing. SourceX may then talk to the company directly, and section 2.2 says the partner need not join every call or email.
- **Not now.** The founder names a date or a trigger, and the hold runs until then. Nobody checks in early.
- **No.** It is logged once, the plan closes, and no investor raises SourceX with this founder again unless the founder brings it up.

A [permission log](/guides/a-permission-log-for-investor-led-company-introductions) can hold field 8 if your platform team already keeps one.

## Status and compensation, settled before the message goes

The sender will learn little and should pass on less. Section 4.6 of the agreement sample gives a partner what it needs to follow its own referral, in generic stages or reference codes, and section 7 of the terms keeps partners out of each other's records. Field 10 usually allows two updates: an introduction was made, and later, it ended. Anything more reaches the board from the founder.

On money, the plan says three things. Only the sender can be credited, and only if theirs is the first valid introduction. No other investor receives a share, and nobody promises one. The founder hears in the first message that the sender may be rewarded by SourceX, which pays that reward separately; nothing for the partner is taken from the compensation in the company's signed agreement. Illustrative: if SourceX paid the company USD 100,000 on its first qualifying transaction, the credited sender's reward would be USD 55,000 and the other co-investors would receive nothing from SourceX. Whether a co-investor's fund lets its people accept such a reward is that fund's question, answered before it volunteers a sender.

## One plan that held, one that needed repair (Illustrative)

Illustrative. Both companies, every investor and every date are invented, and neither case predicts an outcome.

**The plan that held.** A 190-person commercial printing and packaging company has a lead investor with a board seat and two co-investors. The lead's board member, who speaks with the founder weekly about production, drafts the plan and names himself sender. Both co-investors confirm the hold in writing, and one pulls the company from a planned portfolio mailing about data partnerships. The message goes out on day 2. On day 9 the founder replies: not before the ERP cutover in March. The close date moves to March 15, and nobody writes in the meantime.

**The plan that needed repair.** A 260-person regional engineering consultancy received two emails a day apart, one from each co-investor's platform team, with different partner links. The founder asked both which investor to deal with. The platform leads agree one short reply that apologizes, names one contact and offers to drop the subject, and neither submits the company until the founder chooses. Each keeps its own dated emails unaltered; had both links already been used, SourceX would sort out the overlap in duplicate review from those records, and neither team should guess the result. The [pre-submission duplicate check](/guides/how-to-prevent-duplicate-claims-before-they-reach-sourcex) is the step both teams skipped.

## Fit questions the sender may ask

A contact plan is wasted on a company that cannot qualify. Before drafting it, the sender checks, at the level of descriptions: a full-time headcount that reached 50 or more at its peak, with contractors excluded; records the company created itself over several years; the right to license them; and a founder-CEO who decides. 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. The sender never asks for files, samples, logins or the company's inventory. Only SourceX's review can settle whether the records fit a current program, whether customer contracts limit them and whether the company already appears in SourceX's records.

## Where a contact plan falls short

Our working thesis: a founder who hears about SourceX once, from the investor they trust most, gives a more considered answer than one who hears it three times. No data on founder responses has been published. Where it can fail:

- **It binds investors, not SourceX or the company.** Section 2 of the terms lets SourceX talk to a referred company directly without affecting valid attribution, and the founder can apply alone at any time.
- **Unknown earlier contact.** Only SourceX can search its own records, and one earlier email from anyone at the company makes it a duplicate.
- **Mailings outlive plans.** A newsletter scheduled weeks ahead can break the hold; the platform team that sends it owns the exclusion.
- **Demand moves.** SourceX's requirements follow its current data needs, so a well-run plan can still end in "not a fit".

**Methods note.** The plan applies the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), the Channel Partner Agreement sample (version 2026-10-19), SourceX's screening page and its process page, all checked 2026-10-27. It does not measure founder sentiment, record quality, demand or payout. To test it, count for each company on a plan how many investors contacted the founder about SourceX, the days from plan to answer and how many holds were broken. Figures have not been published.

## 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 plan has one sender, a confirmed hold and a founder who has said yes, the sender should [register for a partner link](/register) if they have not, recheck the company against [who qualifies](/who-qualifies) and read sections 2, 3 and 7 of the [program terms](/terms) before submitting. Platform teams can find the wider program in the [overview for venture platform teams](/for/venture-platform-teams) and more coordination guides in the [guides library](/guides).

Keeping one founder from hearing three pitches is a referral question. Evaluating SourceX as a company to invest in is a separate one, and investor materials can be requested on the [SourceX investor page](https://sourcex.si/investors).

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.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/how-it-works
- https://sourcex.si/investors
