A fund network can collaborate without a shared database: a minimal shared-state model in which each fund keeps its own notes and only four fields about any company ever pass between funds

Short answer

Coordinate the ask, not the data. A network of funds needs to know one thing per company: which single person is asking its CEO, and where that ask stands. Everything else, from fit notes to board knowledge to SourceX's updates, can stay in each fund's own system. A pooled spreadsheet of companies adds confidentiality exposure, invites claims SourceX's terms never honor and goes stale as the people who wrote it move on. Four shared fields, sent only between funds that already know the company, do the coordination job.

Visual briefFull-size diagram
Three fund nodes in a triangle, each beside its own private record store; a crossed-out shared database sits in the middle, and a small four-field card, company, asker, state and next date, travels only along the one edge between the two funds that both know the company.
The minimal shared-state model. Funds and the card's fields are placeholders, not a real network.

The temptation is understandable. A group of funds agrees to help one another's portfolios with data licensing introductions, and someone offers to "set up a shared base so we don't step on each other". Before long it holds company names, CEO emails, headcounts copied from board decks and a column titled "claimed by". Each of those columns causes a problem the network never meant to create. Trading the screening criteria without trading names is covered in exchanging referral criteria without client lists; this page is about the state the funds still have to share once a company is in play.

What a pooled company list quietly turns into

A shared database of network companies becomes five things nobody voted for.

What it becomesWhy that is a problemSource
A pretend attribution registerA "claimed by" column decides nothing. In the terms' words, attribution "is decided from dated records, including written introduction evidence, existing applications and preexisting relationships"Program terms, section 2
A store of other funds' confidential knowledgeBoard-deck headcounts and system notes usually arrived under information rights. NVCA's model management rights letter makes what an investor learns under those rights subject to the confidentiality provisions of the company's investor agreement, and keeps that duty alive after the rights end (paraphrase)NVCA model letter
A channel for SourceX's confidential updatesOnce someone pastes a status into the base, every member reads it, but the agreement lets confidential information reach only employees, professional advisers and service providers bound by equally protective dutiesAgreement sample, section 4.2
A window into other partners' referralsThe terms say partners never receive access to other partners' records; a shared status column gives exactly thatProgram terms, section 7
A growing pile of personal dataCEO names and emails, copied once per fund, then kept foreverICO guidance, below

None of the five is a reason to stop collaborating. They are reasons to share less, on purpose.

The minimal shared-state operating model

The model has one rule: only the state of the ask crosses between funds. Four fields carry it.

FieldWhat it holdsWho writes itWhere it lives
CompanyThe name both funds already use for itThe asking fundIn each fund's own system
AskerOne named person at one fund, who has signed the SourceX Channel Partner Agreement or will before submittingThe asking fund, once the CEO has accepted that messengerIn each fund's own system
StateHolding, asked, not now, introduced or closedThe askerIn each fund's own system
Next dateWhen the state will be checked again, or when it closesThe askerIn each fund's own system

The fields travel as short messages, not as rows in a shared table, and only to funds that already know the company. A fund that does not know it never learns it from the network. What never crosses: fit notes, headcounts, system descriptions, anything the CEO said, SourceX stage codes, estimates, reward figures, and the names of other companies.

The states run in one direction, each with an exit:

StateEntered whenMessage goes toLeft when
HoldingThe asker plans to raise it with the CEO by a stated dateFunds that already know the companyThe asker asks, or the date passes and the asker drops it
AskedThe question has been put to the CEOThe same fundsThe CEO answers
Not nowThe CEO declines or defers; no reasons are passed onThe same fundsThe CEO's own date arrives, or the matter closes
IntroducedThe written introduction is submitted after the CEO's written yesThe same fundsThe asker's part ends
ClosedThe CEO stopped, no application arrived within 90 days, or the matter endedThe same fundsFinal

The design borrows a principle from data protection. The ICO's UK GDPR guidance on data minimisation asks organizations to identify the minimum personal data their purpose needs and hold that much but no more, not to collect data on the off-chance it proves useful, and to review and delete what they no longer need (paraphrase; the ICO notes the guidance is under review after the Data (Use and Access) Act). Whatever any law requires of a given fund, which is for that fund's counsel, the purpose here is narrow, preventing two investors from asking one CEO the same question, and four fields serve it.

Method note. The model was designed on 2026-10-27 from SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04), the unsigned Channel Partner Agreement sample (version 2026-10-19), NVCA's model management rights letter and the ICO's data minimisation guidance. Each field exists because a coordination failure needs it: no asker means double asks, no state means repeated questions, no date means stale holds. It has not been tested in a live network, and nobody has published data on how often fund networks collide on one company.

The CEO is the only complete index

A shared database promises to show every overlap. The company's CEO already knows them all: who sits on the cap table, who emailed last week, which investor raised data licensing a month ago. So the asking fund uses the CEO as the index rather than building one.

Before asking, the would-be asker puts two questions to the CEO: "Has another investor raised this with you?" and "Who would you rather hear about it from?" If another fund already asked, the would-be asker stands down and, at most, sends that fund a "holding" message saying it will not ask. If the CEO prefers a different investor, that investor becomes the asker. Either way the CEO decides, which fits SourceX's screening page: a company whose chief executive never heard about the introduction is one of the poor fits it lists.

Funds still message the co-investors they already know from the company's financing documents. That is pairwise knowledge each fund holds anyway; the model only adds a format for it.

One asker per company, named in the first message

Every holding message names one person. Two reasons make that non-negotiable. SourceX credits a single partner per company: the first valid introduction of a new company within the 90-day attribution window, once the company submits a verified application. A second fund that submits anyway creates an overlapping case that SourceX settles in duplicate review, and the CEO receives two pitches. And if the company already had any application, relationship, lead, account or email correspondence with SourceX, nobody is credited at all, however clean the network's messages were.

The named asker also owns the record SourceX does rely on. Section 3.3 of the agreement sample lists what each introduction record identifies: the company, its domain, the partner, the opportunity, the introduction method and timestamps. That record lives with the asker and SourceX, never in the network. When two introductions do arrive for one company, when two partners refer the same company explains what happens next.

The two lines every holding message carries

A holding message is three lines of state plus two lines that settle status and money before anyone calls the CEO.

Status. "Further messages from me will be state changes only. I will not pass on anything SourceX tells me." The full sorting of what may follow, row by row, is in what to share with a co-investor.

Money. "SourceX pays any reward to the credited partner alone; there is no network share unless members sign a separate agreement, and none exists." No partner can commit SourceX to a payout (section 7.1 of the sample), so a network cannot promise one either. Each fund also answers to its own documents on outside compensation; SEC scrutiny of private fund fees covers why a private fund adviser treats that as a conflicts question.

Pooled database or minimal state: five criteria

The comparison uses five criteria stated in advance. Ratings are reasoned from the sources above, not measured.

CriterionPooled databaseMinimal shared state
Confidential material exposed to other fundsHigh: board knowledge and status pasted by any member reach all membersLow: four fields, sent only to funds that already know the company
Risk of treating a row as creditHigh: "claimed by" reads like a reservationLow: messages say who asks, not who owns
Personal data held across the networkGrows with every member and every companyStays with each fund that already had it
StalenessHigh: rows outlive the people who wrote themBounded: every state carries a next date
Effort to runOne setup, then constant upkeep and access reviewsA short message per state change

The pooled database wins on one point: a newcomer can see everything at a glance. That is precisely the property a confidential relationship business should not want.

Four funds, three companies, one week of messages (Illustrative)

Illustrative. Four seed and growth funds, W, X, Y and Z, agree to the model. Three companies come up in one week.

DayCompanyWhat happenedMessage sentSent to
MonA 210-person claims administratorFund W's partner asks the CEO who else has raised it; nobody has; the CEO is happy to hear it from W"Company: claims administrator. Asker: W's partner. State: holding. Next date: Friday."Fund X, the only other fund that knows it
WedSameW asks; the CEO says yes in writing; W submits"State: introduced. Next date: my part closes in 90 days if no application arrives."Fund X
WedA 75-person software companyFund Y's partner learns from the CEO that Fund Z raised it last monthNone from Y; Y stands downNobody
ThuA 400-person staffing firmFund Z's partner asks; the CEO says not now, ask in the spring"State: not now. Next date: April 1."Fund W, which co-invested
FriAll threeNo shared table was created or updatedNoneNobody

Each fund holds its own notes on the companies it knows. Fund Y never learned the staffing firm's name, Fund Z never learned about the claims administrator, and no SourceX status crossed between any of them. On the staffing firm, Fund Z's notes record its own full-time staff separately from the workers it places with clients, since only the former count toward the 50 full-time employees at peak that the screen looks for.

Where four fields are not enough

  • Big networks. Pairwise messages are light for a handful of funds and heavy for fifty. A larger network may need a coordinator who relays state messages without keeping a copy, and that person's role should be written down.
  • Members who skip messages. The model relies on courtesy. A fund that asks without a holding message causes the double ask the model exists to prevent; the remedy is a conversation, not a database.
  • CEO fatigue. "Has another investor raised this?" is an easy question once and an irritating one five times. Only the fund that intends to ask should put it.
  • Automation creep. A tool that "just syncs" the messages rebuilds the shared database by the back door. Decide what to automate with the workflow automation boundary map.
  • Outcomes outside the network's control. Duplicate review, rights review and SourceX's current demand decide what happens after an introduction, whatever the messages said.

A measurable next step. Run the model for two quarters and count three things: holding messages sent, double asks that still happened, and states left past their next date. If double asks persist, the problem is discipline, not tooling, and the fix is the CEO-first question. The portfolio view of the program is set out for venture platform teams.

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 your network's first holding message names one asker and the CEO has picked that person, the asker can sign up as a partner, screen the company against who qualifies and read the program terms before writing to the CEO.

Coordinating referrals across funds is one decision; looking at SourceX as a potential investment is another, and materials for that are available on request from 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

Can a network keep one shared sheet if it only holds company names?

A names-only sheet still tells every member which companies other funds are working on, and it soon collects a status column. If members need to find overlaps, let the CEO tell each fund who else has raised it, and send the four-field message only to funds that already know the company.

Does a 'holding' message reserve the company for that fund at SourceX?

No. SourceX decides credit from its own dated records: the first valid introduction within the 90-day window, credited once the company submits a verified application. A message between funds is a courtesy that prevents double asks; it records nothing SourceX relies on.

Who keeps the message history?

Each fund keeps the messages it sent and received in its own system, next to its own notes. Nobody holds the whole network's history, which is the point.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. refer.sourcex.si/who-qualifies
  4. nvca.org/wp-content/uploads/2019/06/NVCA_Model_Manage…
  5. ico.org.uk/for-organisations/uk-gdpr-guidance-and-resou…
  6. 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