This handbook is for the operations lead who has just hired, transferred or borrowed someone to work on referrals at a consultancy, accounting firm, managed service provider, fund platform or agency. It is deliberately thin: a sequence and a lookup, not a summary.
Before the first record: the basics and your firm's agreement
Four published pages and one signed document come first, because every operations guide assumes them.
- How it works for the stages a referral passes through and who controls each one.
- Who qualifies for the screen a company is measured against.
- The program terms, version 2026-10-22.2, since replaced by version 2026-11-04 as of today, for attribution, duplicates, rewards and payment timing.
- The Referral Partner Handbook for the program overview in one place.
- Your firm's signed Channel Partner Agreement. Partners sign it before submitting introductions; one signed under its earlier title, the Channel Partner Non-Circumvention and Non-Disclosure Agreement, remains in force as signed. Ask who signed for your firm and whether a Schedule A or addendum changes the defaults.
Three decisions sit outside your new colleague's job, and it helps to say so on day one. The company's CEO decides whether the company talks to SourceX at all. SourceX decides whether a company fits and whether an introduction is credited, from dated records. The company and SourceX agree what the company is paid, and the company receives the same amount with or without a partner; in the words of terms section 4, "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation."
The four-week reading path
Each row names a guide and the moment it becomes useful. Read the row's guide when that moment arrives, or in the week shown if it has not arrived yet.
| # | Week | Guide | Open it when |
|---|---|---|---|
| 1 | 1 | The referral CRM: companies, permissions and next steps | Before you create, import or rename a field; the other guides assume its record shape |
| 2 | 1 | A stage model that does not imply revenue | The first time a report or a colleague asks where a referral stands, or wants a figure beside it |
| 3 | 1 | The referral note format | Straight after a call, email or meeting about a referred company, before you type anything |
| 4 | 1 | A queue without uploading client data | When someone from paid client work wants to add a company to the queue |
| 5 | 1 | Avoiding a shadow data room in your CRM | The day an email-logging, recording or notetaker integration is switched on, or a file turns up in the CRM |
| 6 | 2 | The first-response checklist for an interested owner | When an owner writes back with interest and you are drafting the reply |
| 7 | 2 | Several contacts with different permissions | When a CFO, IT lead, assistant or outside adviser starts answering for the company instead of the CEO |
| 8 | 2 | Deduplicating legal entities and brand names | Before you create a company that may already sit in the CRM under a brand, domain or parent |
| 9 | 2 | The handoff after a company accepts | Once the CEO's written yes is in hand and the introduction is about to go to SourceX |
| 10 | 3 | When no one owns the next step | When an owner field says "team", "us" or nothing |
| 11 | 3 | Questions waiting on the company | Whenever your next move depends on an answer only the company can give |
| 12 | 3 | Escalating without repeated messages | When you are about to send the same message a second time |
| 13 | 3 | The weekly pipeline meeting | Before you run, or first sit in on, the weekly meeting |
| 14 | 3 | Keeping a pipeline current with limited staff | When upkeep has to fit into a few minutes a day, or the team gets smaller |
| 15 | 3 | A contact email change during review | When an unfamiliar address writes to say it now speaks for the company |
| 16 | 3 | Moving a referral between managers | When a referral is handed to you, or taken off your desk |
| 17 | 4 | Recording a decline without private reasons | As soon as a CEO says no, not now or not this year |
| 18 | 4 | Stalled or closed | When a record has gone quiet and someone proposes shutting it |
| 19 | 4 | Closing a record after SourceX review | When the portal shows that SourceX has recorded an outcome |
| 20 | 4 | Reconciling manual introductions with the portal | At month-end, or after any introduction made by phone or email |
| 21 | 4 | A dashboard for a small advisory practice | When a partner at a small firm asks how the firm's introductions are doing |
| 22 | 4 | The repeat partner activity worksheet | When one firm follows several introductions and wants each company's cap use on one sheet |
| 23 | 4 | The operating handoff when a partner firm merges | When your firm combines with another partner firm, or is bought by one |
| 24 | 4 | The quarterly data-quality cleanup | In the last week of every quarter |
The order is not a ranking. Week 1 comes first because guides 2 to 24 all write to, or read from, the record that guide 1 defines.
Who reads what first: a role map
Not everyone needs the whole path at the same depth. The numbers refer to the table above.
| Role at your firm | Read closely | Read once, keep nearby | Usually first needed |
|---|---|---|---|
| Operations lead | All 24 | None | Guide 1, before the hire starts |
| Relationship owner, the person the CEO knows | 3, 6, 7, 9, 17 | 1, 2, 8, 12, 15 | Guide 6, the day an owner replies |
| Coordinator working records day to day | 1 to 5, 10 to 16, 18 to 20, 24 | 6 to 9, 17, 21, 22 | Guide 3, after the first call they log |
| Finance or office manager | 2, 21, 22 | 19, 20 | Guide 2, the first time someone wants a forecast |
If one person holds several roles, use the union of their rows and keep the week order.
Three moments from a first month (Illustrative)
Illustrative. A generic 40-person accounting firm and a new coordinator; invented events, no outcomes implied.
- Day 6. A client's CFO emails that "we're in". The coordinator finds the situation in the when-to-open column: guide 7, because the CFO is not the CEO, then guide 6 for the reply. Nothing goes to SourceX that day.
- Day 15. In the weekly meeting, two records show "us" as the owner of their next step. Guide 10's row matches, and the coordinator takes both to the operations lead with that guide open.
- Day 27. The quarter ends on day 30, so guide 24 comes up a week early. The coordinator runs it with the operations lead rather than alone, because the first cleanup is where a newcomer learns how the records actually look.
In each case the handbook did one thing: it pointed to the right guide at the right moment. The guide did the rest.
When guides seem to disagree, or say nothing
- The terms and your agreement outrank every guide. The guides explain practice. The published terms govern attribution and rewards, and a signed Schedule A prevails over them on rate, calculation base and cap. When a guide and the terms appear to differ, follow the terms and tell the operations lead which guide needs a second look.
- Some questions are open on purpose. Whether an earlier contact by a parent company, or another partner's introduction of a sister company, affects credit is not settled in the terms; SourceX looks at each such case in duplicate review, and no guide should be read as deciding it. The same applies to a partner who leaves while introductions are still in review.
- New guides join the path. Add each new operations guide to the table in the week where its moment usually falls, and re-check the terms version whenever someone new starts.
More operations and relationship guides are listed in the guides library.
Where a reading path falls short
- Reading is not practice. A newcomer who has read guide 12 will still be tempted to resend a message; the first real case teaches more than the page.
- The guides are written for many kinds of firm. An MSP, a fund platform and a two-person consultancy will skip different rows, and the role map is a starting point, not a prescription.
- Some guides assume a CRM. A firm working from a shared sheet will need to translate field names on its own.
- Nobody has measured onboarding time. If you want to know whether the path helps, log two dates per row for each new person: the day the guide was read and the day they first handled that situation without help. No figures are published yet.
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.
If your firm has not yet signed, register as a partner before the new colleague's first introduction, keep who qualifies open beside week 2, and print the current program terms as page one of the handbook.