This page is for the venture relationship partner whose own seats, colleagues' seats, LPs or co-investors reach companies that compete with each other.
Where rivals meet in one network
A venture network crosses competitors more often than its maps admit. Five patterns cover most cases.
| Overlap | Example (generic) | What you hold from each side | The temptation |
|---|---|---|---|
| 1. Your seat at one, a colleague's seat at its rival | You sit on A's board; a partner at your fund sits on B's | A's board material; whatever your colleague lets slip about B | Comparing notes on which of the two holds more |
| 2. Seats of your own at both | You are a director or observer at A and at B | Board material from both | Letting one company's plans shape the ask to the other |
| 3. A portfolio company and an LP-owned rival | You sit on A's board; one of your LPs chairs B | A's board material; the LP's remarks about B | Asking the LP to sound out B while A is still deciding |
| 4. An advisory role at one, a seat at the other | You advise A and sit on B's board | Advice-meeting material from A; board material from B | Using A's archive story to open B's door |
| 5. A co-investor's rival | A co-investor backs B, a rival of your portfolio company A | Little directly, plenty of deal-room talk | Trading introductions between funds |
Pattern 2 raises a question that comes before any introduction. The FTC's glossary entry on interlocking directorates explains that, with some exceptions, Section 8 of the Clayton Act prohibits the same individual from serving as an officer or director of two competing corporations (our paraphrase). Whether any seat in your network raises that issue is for counsel. This page gives no advice on board duties or conflicts; it takes the seats as they are and asks a narrower question: how to handle a data introduction across them without carrying anything from one company to the other.
What a data introduction can carry between rivals
An introduction is a small act, but it can move five kinds of information across a line that should hold.
- That a rival is talking to SourceX. "Your competitor is already looking at this" is pressure, and the fact was never yours to share.
- What a rival holds. Systems, years of records and volumes usually reach a director through board packs. SourceX's screening page says a fund's knowledge of that kind is a reason to ask the CEO, never material to pass along.
- A rival's answer. A yes or a no from one company, used to nudge the other in either direction.
- Timing that gives the game away. Two CEOs asked the same week by the same person can each guess at the other.
- The other company's progress. The terms close one route here: "Partners never receive access to other partners' records, applicant documents or confidential buyer information" (section 7). Whatever your own company tells you about its progress stays with you.
A CEO may also worry that licensing helps a competitor. Point them to whether licensing data helps competitors, and make no promises of your own about who would see what.
The conflict-aware introduction protocol
Eight steps, in order. A stop at any step ends the ask until it clears.
| Step | What you do | What must not cross | Stop when |
|---|---|---|---|
| 1. Map the overlap | List which companies in your reach compete, and which seat, role or tie reaches each | Nothing leaves your own notes | You cannot tell whether two companies compete; then treat them as rivals |
| 2. Settle the seats | Read your fund's conflict policy and each company's rules on outside activity; take open questions to counsel or compliance | No ask while a seat question is open | Counsel or compliance has not answered |
| 3. One asker per company | Where possible, whoever holds each relationship asks only that company, and the two askers do not compare | Neither asker hears the other company's answer | One person would have to ask both and cannot keep the two apart |
| 4. A reason from outside both boardrooms | Base each ask on public facts or that CEO's own words | Board packs, meeting remarks or data-room material from either company | The only reason you can give came from the other company |
| 5. One company per conversation | Never raise it with both in one room, never mention the other, and let each conversation run on its own clock | The other company's name, plans or decision | A CEO asks what the rival is doing; say it is not yours to tell |
| 6. Disclose every interest | Name your seat, equity, fees and the possible reward in the first message | Any hint that the seat makes the company's answer matter to you | You would rather leave an interest out |
| 7. A written yes, a single record | The CEO agrees in writing, and the person who signed the SourceX Channel Partner Agreement submits only that company, filed apart from the other | Nothing from one company's record in the other's | The yes came from someone other than the CEO |
| 8. Afterward | Hear progress only from your own company, and pass it to no one at the other company, its board or your co-investors | Progress, outcomes or amounts | Anyone asks you to relay either company's news |
Two rivals are two companies: two introductions, two separate credit decisions under the attribution rule and, unless one parent owns both, two first qualifying transactions that each carry their own USD 50,000 floor, with no cap on either. SourceX credits each company to one partner, the earliest valid introducer inside that company's 90-day attribution window, once the company has filed a verified application.
Method note. The protocol applies the program terms (version 2026-10-22.2, since replaced by version 2026-11-04, sections 1, 2, 4 and 7), SourceX's screening page and the FTC's description of interlocking directorates, all checked 2026-10-27. It describes a handling sequence; it does not assess anyone's legal position, and it does not measure how often overlapping networks lead to introductions, for which no figures have been published.
Who asks each company
The cleanest answer to an overlap is usually a different person for each company.
| Overlap pattern | Who asks company A | Who asks company B | Your part |
|---|---|---|---|
| 1. You at A, a colleague at B | You | Your colleague, separately | Neither of you asks how the other's conversation went |
| 2. You at both | Counsel first; then only on a relationship that stands apart from both boardrooms | The same test, separately | Consider staying out and letting each company find the program itself |
| 3. Portfolio A, LP-owned B | You, as A's director | The LP, only if the LP chooses to | Never ask the LP to sound out B on your behalf |
| 4. Advisor at A, seat at B | Only from your own relationship, as the board advisor checklist describes | Never on the strength of anything from A | Keep the two files apart |
| 5. A co-investor's rival | You, for A | The co-investor, for B, if it wants to | No swapping of introductions |
Board observers sit in a similar position; the observer signal worksheet shows what an observer can use. If the company itself asks whether its board must approve a license, board approval for data licensing covers where that authority usually sits.
Investment, endorsement and pay stay in their own lanes
- No fundraising rides along. The ask is not a co-investment pitch, a word about your next fund or a conversation about investing in SourceX.
- No endorsement and no favored access. Mentioning SourceX does not mean either company fits, that SourceX endorses your fund, or that a seat at both tables gives either company a better position or a view of the other.
- Nothing is gathered. No board material, system list or headcount goes from you to SourceX, and every introduction covers a single company whose own CEO asked for it.
- Pay is disclosed. The company's amount does not change because you are involved: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation" (terms, section 4). A director who could be paid for introducing a company faces disclosure questions of their own, set out in whether a portfolio company board member can earn a referral reward and the guide to a sponsor-appointed director's duties. This page offers no legal advice on either.
Two rivals in one network (Illustrative)
Illustrative. Generic companies and people; every fact is invented and no outcome is implied.
A. Pattern 3, handled cleanly. You sit on the board of a 260-person regional freight broker in your portfolio. One of your LPs chairs a 340-person rival. On a one-to-one call, your CEO says the company has kept its dispatch exception logs since 2011 and asks what you know about data licensing. You answer for her company only, disclose your interests, and she asks in writing for an introduction, which you submit, registered and signed. You never raise the subject with the LP. Months later the LP asks whether "your freight company did that AI data thing." You tell him it is not yours to share, the same answer you would give anyone about his company.
B. The board-meeting tip. At a board meeting of company A, management mentions that rival B is retiring an old dispatch system next spring. That is A's board material and a rumor about B. It cannot open B's door, now or later.
C. Pattern 2, counsel first. You are an observer at two software companies that have drifted into the same market. Before anything else, you ask your fund's counsel about the seats themselves. Until that is answered you raise data licensing with neither company; either can find the program and apply on its own.
Where the protocol can fail
- The seats themselves may be the issue. No handling sequence fixes a seat that should not be held; that is counsel's question, asked first.
- Small sectors leak. In a niche where everyone talks, even a clean protocol cannot stop people guessing. Sometimes the right move is to ask neither company and let each find the published pages itself.
- Board confidentiality runs deeper than this page. SourceX's screening page warns that a fund partner who describes a company's systems from board materials may breach a duty. Treat anything from a boardroom as off limits for every introduction, not only the rival's.
- Competitor fears are real. A CEO who suspects a rival might learn something may simply decline. Accept the no, record nothing about why, and never revisit it through the other company.
- Our thesis is untested. We expect partners who map overlaps first to make fewer and cleaner asks. To test it over two quarters, count overlaps mapped, asks made per company, CEOs who asked to hear more, complaints and any leak caught. No figures have been published.
More relationship playbooks are in the guides library.
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.
Once the seat questions are settled and one company's CEO asks in writing to hear more, register as a partner, check that company alone against who qualifies and read the program terms before you submit.
Handling an introduction across rival companies is referral work. Assessing SourceX itself as an investment is a separate decision; readers weighing it can ask for materials through the SourceX investor overview, where the company says it shares company and commercial metrics with investors directly.
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.