# Referral network escalation ownership map | SourceX

Canonical: https://refer.sourcex.si/guides/a-referral-network-needs-an-escalation-owner
Last updated: 2026-11-05

Name one escalation owner for the whole network: the person who receives every issue that partners, companies or SourceX raise, routes it to whoever actually decides, keeps the clock and writes the closing note. The owner decides very little. SourceX decides attribution, eligibility and rewards; the company's CEO decides whether the company takes part; counsel advises on rights and contracts. What the owner prevents is an issue with two half-owners, or none.

The role matters more as a network grows, because issues multiply faster than introductions. Every new partner adds new ways to misstate the terms, overlap with a colleague or approach a CEO badly, and a network with no single owner handles each of those by whoever happens to notice.

## Why issues stall in a growing partner network

Most partner programs fail at coordination before they fail at demand. In a PartnerStack and Wynter survey of 100 senior leaders at B2B SaaS companies with $50M or more in revenue, team alignment was the most cited blocker to partner-driven revenue, at 37%, ahead of no clear partner program at 20%; lack of executive support drew 9%. The survey is vendor-run and covers software partner programs, not data referrals, but it points the same way as most referral networks' experience: problems sit between teams more often than inside one.

Two definitions keep the escalation work honest:

- **An activated partner** has signed the SourceX Channel Partner Agreement and made at least one introduction the CEO knew about and wanted.
- **Referral quality** is measured by what goes wrong as well as what goes right: the share of introductions that close without a single issue, and the number of issues per CEO-authorized introduction.

SourceX has published no figures for either, so the escalation log becomes your own evidence.

## One idea worth borrowing from incident response

Google's site reliability book, paraphrased, says a clear separation of responsibilities lets everyone in an incident know their role without straying onto someone else's turf. One incident commander holds the high-level state and any role not yet delegated, hands off pieces as the load grows, and keeps a live record of the incident. Operational work, communication and planning sit with others.

A referral network borrows the separation, not the urgency. The escalation owner is the commander: they hold the state of every open issue, decide where it goes and keep the record. The deciders stay separate, and most of them sit outside your firm. The point of the borrowing is that the person holding the record should not quietly become the person deciding credit.

## The issue routing responsibility map

Nine issues cover most of what a referral network sees. For each, the map names who usually raises it, the owner's first move, who decides and what "closed" means.

| Issue | Usually raised by | Owner's first move | Who decides | Closed when |
|---|---|---|---|---|
| 1. Two of your partners claim the same company | The partners | Freeze further contact; collect each side's dated records | SourceX, from the dated records | SourceX's decision is in the register and both partners have it |
| 2. A CEO says they never agreed to an introduction | The company | Apologize, stop all contact, withdraw anything submitted | The CEO, and SourceX on whether a submission stands | The CEO confirms nothing more will happen |
| 3. A partner asked a company for files, samples or logins | The company or a colleague | Stop the request; confirm nothing changed hands or that copies are deleted | Your firm on the partner's standing; the company on its own data | Written confirmation, and a recorded decision on the partner |
| 4. A partner promised a payout, an acceptance or a timeline | The company | Correct it in writing from the published terms | Your firm, on the correction | The company acknowledges the correction |
| 5. A reward has passed its payment deadline | The partner | Find which condition is still open | SourceX finance | Paid, or the open condition named in writing |
| 6. SourceX flags a company as a duplicate | SourceX | Tell the partner; gather evidence only if a dispute is warranted | SourceX, through its dispute review | The decision is recorded and nobody resubmits |
| 7. A company wants to pause or stop | The company | Stop all outreach; the company tells SourceX directly | The CEO | The CEO's choice is recorded |
| 8. A partner discloses a conflict late, such as a board seat at the company | The partner or the company | Pause the introduction and make sure the CEO knows | The CEO on continuing; your firm on the partner | The disclosure and the CEO's answer are on file |
| 9. A partner leaves with introductions in progress | Your firm | Give every CEO in conversation one named contact | Your firm on contacts; SourceX on credit | No CEO in conversation is left without a contact |

**Rows that need a published rule at hand.** Row 4 exists because the Channel Partner Agreement says a partner must not tell a company that an estimate, positive interest, a signature or an upload ensures a purchase or a reward. Row 5 turns on the terms' deadline: count 60 calendar days from the later of two events, completed handoff or the Acquisition Partner's final written acceptance of the complete, validated dataset. Payment itself waits on that acceptance plus four more conditions: SourceX's cleared receipt of payment, the company's compensation having been paid, finance approval, and the partner's tax and payment details. A condition still open at the deadline is paid promptly once met, with no new 60-day period. Row 3 is serious because the agreement gives a partner no authority to share a company's records or raw data.

**Method note.** The map was built from the program terms (version 2026-10-22.2, since replaced by version 2026-11-04) and the Channel Partner Agreement sample, both checked 2026-10-26, sorted by who holds each decision under those documents. It does not rank issues by frequency; nobody has published how often each occurs.

## How far an issue climbs

Most issues should close at the bottom of this ladder. Write down which level closed each one; the pattern tells you where training is missing.

1. **Level 0, the partner.** Questions about the terms are answered from the published text, with the version number.
2. **Level 1, the escalation owner.** Routes, freezes contact where needed and sets a first-move time your firm commits to, such as two working days.
3. **Level 2, the decider.** SourceX's dispute review, reached by emailing hello@sourcex.si with supporting evidence; or the company's CEO.
4. **Level 3, the formal process.** The agreement provides 30 days of good-faith written discussion, then confidential binding arbitration under JAMS rules seated in Wilmington, Delaware. An owner who reaches this level often is routing badly.

The [written introduction versus link page](/proof/written-introduction-vs-referral-link-attribution) covers the evidence a credit dispute turns on, and [how attribution works across the website and portal](/guides/how-referral-attribution-works-across-a-website-and-a-partner-portal) explains where those dates come from.

## Three issues through the map (Illustrative)

Illustrative. Invented partners, companies and counts; no benchmark is implied.

**An underperforming cohort.** One recruiting campaign added twelve partners. In their first quarter they produced seven issues (four misstated terms, two requests for records and one CEO complaint) and a single CEO-authorized introduction. Seven issues for one authorized introduction marks the cohort, not the owner, as the problem. The owner pauses new submissions from the cohort, runs a session on Level 0 answers and recommends offboarding the partner who asked for records.

**A duplicate risk.** Two partners in different offices both know the CEO of a 300-person insurance services firm and plan to submit in the same week. The owner sees both names against one company in the register, asks the CEO which person they want as their contact, and only that partner submits. Had both already submitted, SourceX would decide from the dated records, and the owner's job would have been to supply evidence, not a ruling.

**A capacity limit.** The owner sets aside about four hours a week for issues. When open issues stayed above ten for two weeks, the oldest passed fifteen days without a first move. The rule written afterward: no recruiting while the oldest open issue is older than the first-move commitment.

## Four load signals the escalation log shows

| Signal | How to measure it | Gate before the network grows |
|---|---|---|
| Capacity | Open issues, and the age of the oldest | The oldest open issue is within your first-move commitment |
| Support | Share of issues closed at Level 0 | Stable or rising; a fall means partners lack a shared answer sheet |
| Concentration | Share of issues coming from the two busiest partners | Under half; above that, coach or offboard before adding anyone |
| Overlap | Companies claimed by two partners in a month | Each one caught in the register before submission |

These gates are your own; no benchmark has been published. The [screening delegation guide](/guides/how-to-delegate-referral-screening-without-delegating-judgment) shows how to train the people who will close Level 0 questions.

## Monthly review: misroutes, overreach and the gates for growth

Review the log monthly with one question per issue: did it go to the party that holds the decision? Two kinds of miss need correcting in writing:

- **Misrouted.** An issue sent to the wrong decider, such as a CEO asked to settle a credit question. Re-route it and tell everyone who received the first message.
- **Overreach.** The owner, or anyone else, decided something only SourceX or the CEO can decide, such as telling a partner the credit was theirs. Withdraw the statement, say who decides and pass the decision on when it arrives.

Before expanding the network, look for three things across two quarters: issues per authorized introduction falling, no CEO complaint still open, and every overlap caught before submission. Name a backup owner as well; the [leave handoff page](/guides/the-platform-manager-s-handoff-when-taking-leave) shows how a cover person takes over open items. Declined companies leave a trail too, and the [decline log guide](/guides/how-to-track-declined-and-ineligible-referrals-respectfully) keeps it minimal. For the partner role the owner is protecting, see the [referral partner overview](/proof/what-is-a-referral-partner).

## 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 escalation owner and the routing map are in place, have each new partner [register for a partner link](/register) and read [who qualifies](/who-qualifies) and the [program terms](/terms) before their first introduction, so most questions close at Level 0.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sre.google/sre-book/managing-incidents/
- https://partnerstack.com/resources/research-lab/the-state-of-partnerships-in-gtm-2026
