# Briefing an assistant on a sensitive introduction | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-brief-an-assistant-who-coordinates-sensitive-introductions
Last updated: 2026-11-05

An assistant who coordinates a sensitive introduction needs four things: who is being introduced to whom, how to reach each office, which times work, and a neutral title for the meeting. Everything else stays with the partner: the company's records and figures, anything learned in confidence, the partner's possible reward and every judgment about fit. Brief the assistant in writing before the first email, check what delegated inboxes and calendar titles already expose, and name the moments when the assistant stops and hands back. The company's CEO decides whether any conversation happens.

## Three assistants, three principals

One introduction usually involves three assistants, and each works for someone different.

| Assistant | Works for | Coordinates | Never carries |
|---|---|---|---|
| Your executive assistant or a fund's platform coordinator | You, the partner | Holds, your drafted note, filing the CEO's dated reply | Company facts beyond a name and contact route; your reward; board material |
| The CEO's assistant | The CEO and the company | The CEO's diary and whether the call happens | Anything from you except your note and the scheduling thread |
| SourceX's side | SourceX | Its own calls once the company applies | Company facts from your office: the company describes itself to SourceX |

Your brief governs only the first row; the CEO's office answers to the CEO. [Who qualifies](/who-qualifies) says: "Under the program, opening a licensing discussion and signing for the company fall to the CEO." It also lists introductions made without the decision maker's knowledge as usually not a fit, so an assistant who writes to a company or to SourceX before the CEO agrees works against the introduction.

The purpose is one CEO, one conversation, if that CEO wants it. Agreeing to talk is not agreeing to share records, to be named or to anything SourceX proposes later; each is the CEO's separate decision. A CEO who wants to stay unnamed at first has its own route, in [an anonymous first conversation](/guides/when-a-founder-wants-an-anonymous-first-conversation).

## What a delegated inbox and a shared calendar already reveal

**Delegated email.** Google's Gmail help says a delegate can read, send and delete the owner's messages (paraphrase). If your assistant manages your inbox, every reply, attachment and SourceX message about the referral reaches them, whatever your brief says. Keep a thread they should not see out of the delegated inbox; asking them not to look is not a control.

**Calendar visibility.** Google Calendar's help says a private event "hides all details from everyone except you and people you've given "Make changes to events and see event details" and higher access permissions," and adds: "Even if you set your event as private, some details might still be visible to others when you invite guests or book rooms." Edit rights reveal the private event anyway, and the title travels furthest.

| Calendar field | Says too much | Says enough |
|---|---|---|
| Title | "SourceX data licensing: [company] support archive" | "Introduction call: [CEO first name] and [your name]" |
| Description | Headcount, system names, years of records, an estimate | "Requested by [CEO first name]; the CEO sets the agenda" |
| Guests | Colleagues who might find it interesting | The CEO, you, and whoever the CEO asks for |

## The coordinator access and handoff guide

Give your assistant this guide in writing, dated, before the first scheduling email. It sorts each item into handle, hand back or never receive.

| Item | Assistant's access | Handoff rule |
|---|---|---|
| The CEO's and the CEO's assistant's names and work emails | Handle, once the CEO agreed to hear from you | Scheduling only; never added to a list or campaign |
| Time zones, availability, video link | Handle | Neutral title; guests limited to whom the CEO asked for |
| Your introduction note | Send exactly as you wrote it | Any reply that raises substance comes back to you |
| The CEO's yes or no, with its date | File it | Copy the date and wording to your introduction record, with no comment |
| The introduction record's fields | Draft them for you | Section 3.3 of the sample agreement lists "the company, domain, Partner, opportunity, introduction method and timestamps"; you submit from your own partner account |
| Any file, sample, screenshot or data room link from the company | Never receive | If one arrives, leave it unopened, forward it to nobody and tell you that day; the rest is [the procedure for confidential files sent unasked](/guides/what-to-do-when-someone-sends-confidential-files-unasked) |
| Headcount, systems, record years, customer names | Not needed to schedule | The company describes itself to SourceX when it applies |
| Board packs, information-rights material, investment memos | Never receive | Who qualifies calls a fund's knowledge "a reason to ask the CEO, never material to pass along" |
| Your possible reward and any estimate | Knows it exists; never discusses it | You disclose it to the CEO yourself; money questions come straight to you |
| SourceX dashboard labels | Only the phrases you set | Outside your office, use the outward wording in the [referral status glossary](/resources/referral-status-glossary) |
| Questions from reporters, LPs or other founders | Never answers | Hand back; the CEO decides what the company says |

Why so little? For information SourceX gives you, section 4.2 of the sample Channel Partner Agreement allows disclosure to "employees, professional advisers and service providers who need the information for the permitted purpose," and makes you responsible for your representatives. What the company tells you falls under your own duties to it, which your counsel or the company's reads. The guide keeps the assistant clear of both. Which fields a record needs is set out in [the minimum information for a useful referral](/guides/the-minimum-information-needed-for-a-useful-referral).

The published terms do not settle delegated submissions: section 1 requires an approved partner account with accurate details and is silent on assistants, so SourceX decides; ask before handing that step over.

## A nine-line written brief (Illustrative)

Illustrative: written for this page for a fictional partner introducing the CEO of a 240-person freight broker. It is not a real brief.

1. Purpose: one introduction call between me and [CEO], at [CEO]'s request.
2. You may use [CEO]'s and [CEO's assistant]'s names and emails, my calendar and the video link.
3. Calendar title: "Introduction call: [CEO first name] and [my name]". No company detail in the description.
4. Guests: [CEO], me and anyone [CEO] adds. Ask me before adding anyone from our side.
5. Send my note exactly as drafted. If a reply mentions money, data, terms or SourceX, forward it to me unanswered.
6. If an attachment or a link to company material arrives, leave it unopened, forward it to nobody and tell me today.
7. File [CEO]'s reply with its date in the introduction record, with no notes on the business.
8. If [CEO] says no or not now, cancel the hold, file the date and send nothing more.
9. Nobody outside this thread, inside or outside the firm, hears about the call from you.

A standing instruction such as "handle my SourceX introductions" would hand the assistant judgments that belong to you.

## Cut the scheduling email to what the CEO's decision needs

The CEO's office decides only whether to take a call; anything more in a scheduling email is exposure. Three drafts and fixes (Illustrative):

| Draft sentence from an assistant | What it exposes | Fix |
|---|---|---|
| "[Partner] thinks your 14 years of claim files could be worth a lot to SourceX." | Company facts and a value claim nobody can support | "[Partner] would like 20 minutes to explain an idea; you decide whether it is worth pursuing." |
| "SourceX will definitely want this kind of data." | An acceptance promise; only SourceX's review decides fit | Delete |
| "[Partner] gets a fee if it works out, but it costs you nothing." | A reward described in the assistant's words | Delete; [Partner] explains it in person |

On the third row: the reward does not change what the company receives, since terms section 4 says "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation." That belongs in the partner's own disclosure, not a scheduling thread.

## Escalation, withdrawal and publication each need their own answer

**Escalation.** The assistant hands back when a reply asks about money, rights, records, timing or SourceX; when someone new asks to join; when a file arrives; when an outsider asks about the company; and when the company announces a sale (before closing the target's CEO decides, once acquired the acquirer's CEO does). If the CEO's office brings in its privacy officer or counsel, see [the referral conversation with a privacy officer](/guides/the-referral-conversation-with-a-privacy-officer) and [keeping privileged material out of referral discussions](/guides/how-to-keep-privileged-material-out-of-data-referral-discussions).

**Withdrawal.** "Not now" ends the coordination: holds cancelled, date filed, no reminder unless the CEO asked for one. A request not to mention the introduction reaches everyone in your office who knew.

**Publication.** A call is not consent to be named. Section 4.5 of the sample agreement reads: "Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required." On those words, a public mention of SourceX as your partner waits for SourceX's written authorization, and any mention of the company waits for its CEO. Your counsel reads the version you signed.

## Fit, credit and SourceX's review sit outside the brief

The brief governs information flow; fit is decided elsewhere. SourceX looks for companies whose full-time staff peaked at 50 people or more (contractors do not count), that hold years of their own records along with the right to license them, and whose CEO agrees to talk. 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. Demand and rights stay unknown until SourceX reviews them.

An assistant's early email can still affect credit. Under the terms, the earliest valid introduction earns credit once the company files a verified application inside the 90-day attribution window, and section 2 adds that "an earlier link click alone does not decide credit." Section 3 treats a company as a duplicate if SourceX already had an application from it, a relationship or a lead, an account, or even an exchange of emails with it. Writing to SourceX before the CEO agrees creates exactly that early contact.

SourceX's own process for companies opens with "A few questions, no files, and an indicative licensing estimate," and its trust page says "The supplier decides which systems, records and date ranges are in scope. Everything else stays out." Your own signature on the Channel Partner Agreement comes before you submit anything.

## Where a coordinator brief falls short

- **Shared assistants.** An assistant serving several partners may schedule two approaches to one company, or to one corporate group, which shares a single reward cap. The assistant flags it; SourceX decides overlapping credit in duplicate review.
- **The other office.** Nothing here binds the CEO's assistant.
- **Tool settings.** The behavior above is from Google's help pages, checked 2026-10-28; other products and administrator policies differ.
- **Your signed documents.** Your signed Channel Partner Agreement, any Schedule A or addendum, and your duties to the company govern; this page reads the unsigned sample.
- **No measurements yet.** No fund has reported results; a team can count each quarter its handbacks and the files that arrived unasked.

**Method note.** Built on 2026-10-28 from terms version 2026-10-22.2, since replaced by version 2026-11-04 (sections 1 to 4), sample agreement sections 1.2, 3.3, 4.2, 4.5 and 4.6 (version 2026-10-19), who qualifies, SourceX's company and trust pages, and Google's delegation and visibility help. Each row asks whether the item is needed to schedule one call. Untested with any fund; it interprets nobody's duties.

More partner guides: the [guides library](/guides).

## 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.

Write the nine-line brief before the first scheduling email; then [register as a partner](/register) and sign the Channel Partner Agreement, check the company against [who qualifies](/who-qualifies), and keep the version of the [program terms](/terms) you read beside the brief.

Briefing an assistant is partner housekeeping; anyone assessing SourceX itself as an investment should 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://sourcex.si/how-it-works
- https://sourcex.si/trust
- https://support.google.com/mail/answer/138350?hl=en&co=GENIE.Platform%3DDesktop
- https://support.google.com/calendar/answer/34580?hl=en&co=GENIE.Platform%3DDesktop
- https://sourcex.si/investors
