FIELD MANUAL / ISSUE 07

Referral Engine Blueprint

How to turn existing customers into a predictable acquisition channel without making the relationship feel like a sales script.

01
THE PATH

A referral begins with a true sentence.

The customer must be able to say what changed, why it changed, and who else might benefit. Everything else—timing, incentive, tracking, follow-up—is a way to preserve the truth of that sentence as it moves from one person to another.

STEP 01 / VALUE PROOF

Earn the right to ask

Trigger the referral ask only after the customer can point to a real result, milestone, or avoided problem. Satisfaction language is weaker than evidence of value.

outcome → fit → permission
02
THE METHOD

Five questions before the invitation.

A referral request is a small act of social risk. The customer is lending their reputation to the recommendation. The operator’s responsibility is to make the recommendation accurate enough that the customer does not have to apologize for it later.

QUESTION 01What result can the customer name?

Do not settle for “they liked it.” Find the milestone, avoided problem, changed behavior, or business consequence.

QUESTION 02Who is the plausible recipient?

Define the situation, constraint, role, and urgency. “Anyone who needs this” is a request to broadcast noise.

QUESTION 03Why is this the right moment?

Use a first win, recent intensive use, renewal, expansion, or recognized recovery. A calendar date is not a reason by itself.

QUESTION 04What would help the recipient act?

Design the benefit around risk reduction and fit. Test a recipient benefit, sender benefit, two-sided exchange, or useful non-cash benefit.

QUESTION 05What happens after the introduction?

State the owner, response time, consent, qualification path, attribution rule, and reward trigger before the message leaves the system.

03
THE LEDGER

Record the exchange, not just the click.

A referral program can look successful while producing low-fit accounts, expensive rewards, duplicate claims, and a damaged customer experience. The ledger keeps the channel honest.

ADVOCATEWho shared?

Customer identity, relationship health, realized outcome, segment, recent use, and permission state.

RECIPIENTWho was introduced?

Recipient identity, fit, need, consent, source, existing-lead status, and context.

ECONOMICSWhat did it cost?

Reward liability, sales effort, delivery cost, refund behavior, contribution after reward, and retention.

LEARNINGWhat changes next?

Trigger quality, message quality, incentive architecture, routing speed, and the health of the referring customer.

Weekly review: eligible customers reached; referral initiation; completed introductions; response time; qualified opportunity; close; reward payment; contribution; referred retention; and referrer retention. Compare cohorts with consistent definitions. Volume is a leading indicator; healthy retained contribution is the result.

04
THE INVITATION

Make the ask generous, precise, and easy to decline.

“Do you know anyone who needs this?” shifts the work to the customer and creates no reason to act. A better invitation begins with the customer’s own outcome, identifies a person who may face the same constraint, and gives the recipient a useful next step.

MESSAGE SHAPEResult → recipient → benefit → permission

“You mentioned that the new process removed the weekly bottleneck. If someone on your team is dealing with the same issue, I can send them the short diagnostic we used. If not, no problem.” The specific wording should fit the offer, but the sequence protects the relationship.

SUPPRESSIONNever ask through an open fault.

Pause the request for unresolved support, weak activation, payment trouble, a recent complaint, or uncertain fit. Repair the relationship first.

DIGNITYDo not turn friendship into inventory.

Recipient-first framing can reduce awkwardness because the customer is sharing something useful rather than announcing a bounty. Incentives should support the exchange, not explain why the customer should pretend to care.

05
QUESTIONS

Field questions for the weekly review.

Are referrals actually cheaper?

They can have lower media cost, but they still carry reward expense, sales effort, delivery cost, tracking cost, and relationship risk. Compare contribution and retention, not just acquisition spend.

When should the reward trigger?

At the economically meaningful event you can verify: a qualified payment, completed onboarding milestone, or retained period. Choose the event that protects your category’s margin and customer quality.

Should the sender or recipient receive the reward?

Test the architecture. Recipient-first incentives can reduce uptake friction; sender benefits can compensate effort; two-sided benefits can make the exchange clear. There is no universal winner.

How often should the ask repeat?

Use a suppression period, stop after decline, and trigger from new value rather than a fixed barrage. A customer who has already shared should not be treated as an unlimited audience.

What is the first process fix?

Define the handoff owner and response time. A thoughtful introduction that disappears for a week teaches the customer not to recommend you again.

CLOSING NOTE

Build the channel customers can trust.

Prove value. Choose the moment. Make the recipient’s benefit clear. Then measure what happened after the introduction.

Return to the path