# Angel network to platform team referral handoff | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-referral-moves-from-an-angel-network-to-a-platform-team
Last updated: 2026-11-05

Credit does not travel in a handoff. SourceX credits the first valid introduction of a new company by a partner who has signed the Channel Partner Agreement, once the company files a verified application, and the terms describe no way to pass that credit from one partner to another. So before the platform team does anything, find out whether the angel already introduced the company. If so, the team supports and never re-submits. If not, the CEO picks one messenger, and the transfer carries only what she has said.

The pattern is common after a priced round. An angel who backed the founder early, often through a formal group, knows the company's history; the lead fund's platform team now handles day-to-day investor support. The Angel Capital Association describes many angels joining formal angel groups to share expertise and pool capital (paraphrase of its handout). That leaves the relationship with one member, a screening process with the group, and a fund team that arrived later with a different job.

## Three hands on one company after the round

Each party around the company knows something different and may do something different in a SourceX introduction.

| Party | What it usually knows | What it can do in a SourceX introduction | What it cannot do |
|---|---|---|---|
| The angel | The founder, the early years, how the company keeps its records | Introduce the CEO, if the angel holds a signed partner agreement and the CEO agrees | Hand its credit to someone else |
| The angel network | Screening memos, committee notes, member threads | Nothing directly; it is not a party to the introduction | Release what members shared for investment screening |
| The lead fund partner | Board materials, the CEO's priorities | Ask the platform team to help; introduce, if the fund is a partner and the CEO agrees | Pass board material to anyone |
| The platform team | The company's current needs and systems roadmap, as the CEO describes them | Introduce or support, depending on where the introduction stands | Submit a company the angel already introduced |
| The company's CEO | Everything that matters | Decide whether to talk to SourceX and who introduces | Be bypassed: SourceX treats introductions without her knowledge as usually not a fit |

Two control facts sit above the table. The company's CEO authorizes a licensing discussion; if the company has since been acquired, the acquirer's CEO decides for it. And funding never establishes fit: SourceX's screening guidance says no check it runs mentions funding, so a priced round makes a company neither more nor less likely to pass.

## Where the introduction stands decides what moves

Before any note changes hands, put the company in one of four states. The angel can tell you which, except for the last, which only SourceX can see.

| State | How you know | Platform team's move | Angel's move |
|---|---|---|---|
| A. The angel already introduced the company | A dated portal submission or written introduction the angel can point to | Submit nothing; answer the CEO's program questions only if she asks | Remains the introducer of record |
| B. The angel mentioned it; nothing was written | Only a conversation | Agree with the angel that the CEO picks one messenger | Writes the introduction if chosen, or stands aside in writing |
| C. The network flagged the company; nobody asked the CEO | A screening note or member thread | Nothing to carry but the idea; the first ask is still ahead | Checks the group's own rules before using member deal flow |
| D. The company already has history with SourceX | SourceX's records, or the CEO remembering an earlier exchange | Do not introduce | Do not introduce |

State B turns on one rule: the partner agreement says an introduction has to be recorded in writing, and an oral one protects nothing until it is confirmed in writing (1.2). State D turns on section 3 of the terms: a company with an earlier application, valid introduction or relationship with SourceX is a duplicate, any earlier lead, account or email exchange counts as a relationship, and a company in that state is credited to nobody, whoever introduces it.

One case stays open. If the angel has left the program, or stops responding, while an introduction sits in review, the terms do not spell out what happens to it. SourceX settles that on its own records; neither the angel nor the fund should treat the answer as known.

## The network-to-platform transfer checklist

Ten lines for the transfer note. Each says whether the line crosses from the angel's side to the platform team's, who confirms it and why.

| # | Line | Crosses over? | Who confirms | Why |
|---|---|---|---|---|
| 1 | The CEO's dated answer and her chosen messenger | Yes | The CEO, in writing | The CEO authorizes; nobody else can choose for her |
| 2 | Introduction status: submitted or not, when, by whom | Yes, as a fact | The angel | Sets state A to D and stops a second submission |
| 3 | Whether the angel signed the partner agreement, and when | Yes or no only | The angel | Partners sign before submitting; it tells you whether a state A record can count |
| 4 | Fit facts in the CEO's words: peak full-time headcount, years of records, systems | Yes | The CEO | These are the published screening tests |
| 5 | A dated event: a migration, an archive retirement | Yes, if the CEO named it | The CEO | Documented timing is the only honest urgency |
| 6 | Network screening memos, committee notes, member threads | No | The network's own rules | Shared for investment screening, not for referrals |
| 7 | The angel's credit or reward position | No | SourceX, from its records | One partner per company; the terms offer no transfer |
| 8 | SourceX's stage updates | No | SourceX | They go to the partner SourceX credits, as generic stages or reference codes |
| 9 | Who answers the CEO's questions from now on | Yes: one named person | The angel and the platform lead together | The CEO should never wonder whom to ask |
| 10 | Company records, samples, logins, data room access | Never, in either direction | Nobody | The partner agreement gives a partner no authority to share a company's records |

Line 7 has a contract behind it. The partner agreement bars either party from assigning it without the other's written consent, apart from a merger, acquisition or sale of substantially all relevant assets where the successor takes on the obligations, and says assignment must not defeat existing attribution or payment rights (7.6). A note between an angel and a fund is none of those, so it moves nothing SourceX has recorded. If both sides want a change, they ask SourceX in writing, and SourceX decides.

**Method.** The ten lines cover what an angel and a platform team typically hold about one company, and each was checked on 2026-10-27 against SourceX's program terms (sections 1 to 4), partner agreement (preamble, 1.2, 2.2, 4.2, 4.6 and 7.6) and screening guidance. The checklist records permissions and facts; it does not estimate the company's chances, which SourceX assesses only in review, and SourceX has published no data on how handoffs between investors turn out.

## The CEO hears from one person after the handoff

Three arrangements work; a fourth, two people asking, does not.

1. **The angel stays the introducer.** The platform lead answers program questions only when the CEO raises them, and says so to the angel in writing.
2. **The angel steps aside.** Available in states B and C only. The CEO names the platform lead, the angel confirms in writing that it will not introduce, and the fund, signed up as a partner, makes the introduction.
3. **The CEO goes to SourceX herself.** That is her right. No partner is credited, and nobody should talk her out of it.

After the introduction, nobody needs to stay in the room. SourceX may communicate directly with a referred company without affecting valid attribution, and the partner agreement says a partner need not join every call (2.2). The named contact from line 9 handles anything the CEO asks the investors. For pacing asks so founders are not worn down by platform offers, see [avoiding founder fatigue](/guides/how-to-avoid-founder-fatigue-from-repeated-platform-offers).

## Who hears progress, and who is paid, once the handover is signed

**Progress.** SourceX sends updates to the partner it credits, as generic stages or reference codes (4.6). The partner agreement limits who may receive SourceX's confidential information to the partner's own employees, professional advisers and service providers (4.2), so an angel who stayed the introducer does not forward updates to the fund, and the fund does not forward them to the network. The CEO can tell her investors whatever she likes.

**Pay.** One partner is credited per company, and SourceX pays the reward to that partner, separately from the company's compensation and never out of it. Illustrative only: an Actual Supplier Payout of USD 100,000 on a company's first qualifying transaction would mean a USD 55,000 reward to the credited partner and nothing to anyone else. Decide before the CEO hears from anyone new who that partner is, and whether it is a person or the fund: the partner agreement can be signed by an individual or an entity. If a fund's rules bar staff from taking outside compensation, the choice is between the firm signing as the partner, where its rules allow that, and staying out; an angel group's rules on members' outside pay are the group's to apply. Any thank-you between angel and fund sits outside the program.

## An angel, a platform lead and a 240-person software company (Illustrative)

Illustrative: a 240-person field-service software company founded in 2012, with twelve years of support tickets, implementation runbooks and QA records it created itself. An angel backed it in 2013 through her angel group; a fund led its growth round in 2021, and the fund's platform lead now supports the CEO. The angel tells the platform lead she mentioned SourceX to the CEO over dinner last month. Nothing was written, and the angel never registered as a partner: state B.

The completed transfer note, one week later:

| Line | Entry |
|---|---|
| 1. CEO's answer | Day 5: the CEO writes to the angel that she would rather hear from the platform lead, who handles her investor admin |
| 2. Status | No introduction recorded before day 6 |
| 3. Angel's agreement | None signed; she confirms on day 5, in writing, that she will not introduce |
| 4. Fit facts | In the CEO's words: about 240 full-time staff, never more than 260; tickets and runbooks back to 2012 in two systems |
| 5. Dated event | The CEO mentions retiring the older ticketing system next year |
| 6. Network notes | The group's 2013 screening memo stays with the angel |
| 7. Credit | Not applicable: nothing recorded on the angel's side |
| 8. Updates | Will go to the fund, as the partner that introduced |
| 9. Contact | The platform lead, named in the CEO's email |
| 10. Records | None requested, none offered |

On day 6 the platform lead, under the fund's signed partner agreement, writes to the CEO, receives her written yes naming him and submits the introduction. One open item remains for SourceX's review: whether customer contracts limit what the company may license from its support tickets.

## Where a handoff should not happen

- **The angel already introduced the company and wants to stay on.** There is nothing to hand over. The platform team supports, if asked.
- **The founder no longer runs the company.** Find the current CEO first; after an acquisition, that is the acquirer's CEO.
- **The network's rules close the door.** If the group restricts members from using deal-flow information outside investing, state C ends there.
- **The records belong to customers.** SourceX's screening guidance treats client-owned material as usually not a fit, which matters for any software company whose most visible data sits in customer accounts.
- **Demand moves.** Requirements vary with SourceX's current data needs and are checked in review, so a careful handoff can still end without a license.
- **The cost to the relationship.** An angel who feels pushed aside may say so to the founder. No data on how angels or founders react to handoffs has been published; record what happens in your own notes.

For the week-by-week rhythm of a platform team's first referrals, see the [first-month plan for venture platform teams](/guides/a-first-month-referral-plan-for-venture-platform-teams), and before any submission run the [duplicate-claim checklist](/guides/how-to-prevent-duplicate-claims-before-they-reach-sourcex).

## 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 an angel's lead reaches your platform team, settle the state first and fill the ten lines before the CEO hears a new voice; then [register the fund as a partner](/register), check the company against [who qualifies](/who-qualifies) and keep sections 1 to 3 of the [program terms](/terms) beside the transfer note. The [overview for venture platform teams](/for/venture-platform-teams) covers the program from the fund side.

Handing over a referral is program work; evaluating SourceX as a company to invest in is a separate decision, and readers weighing it can request materials through the [SourceX investor overview](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://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/who-qualifies
- https://www.angelcapitalassociation.org/data/Documents/Public%20Policy/ACA_Public-Policy_Handout_v2.pdf?rev=5CAA
- https://sourcex.si/investors
