1. Name The Commercial Thread Owner
Decide whether the buyer owner carries the thread directly or if the original referrer stays visible only for warm context.
Open Partner Intro Referral ConversionClient-referral owner path page
Before a referred deal moves, name who carries the thread, who approves, and who actually pays.
Referral deals often feel strong on fit but weak on ownership. The buyer is interested, the referrer is nearby, and the next step looks commercially real, yet nobody has made the control model explicit. This page resolves that before the deal drifts: commercial owner, buyer owner, approver, payer, and how visible the original referrer should stay.
- 1 commercial thread owner
- 1 approval and payer path
- 0 shared ambiguity
Referral Owner Map
Use one sequence from referred buyer engagement to a clean owner path.
2. Separate The Buyer Contact From The Approver
The person replying first is not always the person who can say yes. Make that distinction explicit before scope or payment drift.
Open Partner Intro Referral Approval Pack3. Name The Payer Early
The buyer owner, approver, and payer can be different people. If that is true, the transfer path should already reflect it.
Open Partner Intro Referral Approval To Payment4. Set The Visibility Boundary
Decide whether the referrer stays copied for trust only, goes quiet, or stays visible through startup and delivery.
Open Partner Intro Referral Visibility Open Partner Intro Referral Scope5. Route To The Right Next Stage
Once owner, approver, and payer are clear, the next move should be obvious: approval pack, payment routing, or live activation.
Open Partner Intro Referral Approval Pack Open Partner Intro Referral Activation6. Escalate To Handoff Only After The Deal Is Real
If payment proof and execution context are already in play, step into the referral handoff packet. Do not use handoff pages too early.
Open Partner Intro Referral HandoffOwner Models
Most referral deals collapse into one of these operating patterns.
Buyer Direct
The referral opened the lane, then the buyer carries the deal directly while the referrer steps back.
Buyer Plus Quiet Referrer
The buyer stays in front while the referrer is only available for context or trust if a specific issue comes up.
Approver Split
One person owns the discussion while another person must approve budget, risk, or the first paid step internally.
Payer Split
The person aligned on scope is not the same person or entity that actually sends the funds, so routing matters early.
Execution Escalation
The owner model is resolved and the deal is paid or nearly paid, so the next stage becomes packet depth and kickoff speed.
Short Lines
Use short lines that force ownership clarity without adding friction.
Thread Line
Before we push this further, the clean move is naming who carries the thread from here so the referral does not turn vague.
Approver Line
If someone else still has to say yes, we should separate the buyer contact from the actual approver now.
Payer Line
If the scope is directionally right, the next question is who pays and how that approved step reaches the payer cleanly.
Boundary Line
We should make the visibility boundary explicit now instead of discovering later whether the referrer stays visible or goes quiet.