This path fits when
- Clients or partners have experienced your work.
- A real result or positive experience can be verified.
- You can judge the relationship and timing yourself.
- You can take over promptly after the introduction.
Path fit
Use the Referral Engine when a real result has created readiness
Good delivery creates the reason to refer. A clear system creates the moment, permission, handoff, and follow-through.
Choose another path when
- Delivery or client experience still needs repair.
- The result is vague or invented.
- You want the other person to sell for you.
- You only want automated or mass outreach.
The base one-to-one engine
Deliver, Detect trigger, Ask, Introduce, Follow up
Keep the base relationship loop simple. Launch campaigns are a separate optional lane, not a requirement.
Deliver
Meet expectations and create a real positive experience or result.
Detect trigger
Notice a genuine moment of readiness and apply human judgement.
Ask
Make the referrer the hero and keep the request easy to decline.
Introduce
Check permission, open a shared connection, and take over.
Follow up
Thank the referrer, help the referred person, and close the loop.
Readiness before request
Ask because the moment is real, not because the target is due
The human decides whether the relationship is ready. A note can surface a possible trigger, but it cannot supply judgement or permission.
Result trigger
The client reaches a meaningful outcome and can describe what changed.
Experience trigger
The client gives specific positive feedback or expresses genuine satisfaction.
Reflection trigger
A progress review, testimonial conversation, workshop, or feedback session naturally brings the change into view.
Write two lines before asking: Why is this person ready now? What would make me wait?
The referrer stays the hero
Make the door easy to open, then take responsibility
The referrer's job is to help, check permission, and make the introduction. They do not have to explain, persuade, or sell.
Real client win
Human readiness decision
Easy ask
Permission and introduction
You take over
“Taken care of for you” matters because it protects the referrer's helpful role and makes clear that the work after the introduction belongs to you.
Samples to model, from Marc
Use the mechanic, but write from the real relationship
These samples come from Marc's own referral teaching and operating library. Write your rough version first, then use them to sharpen the structure.
Feedback-session question
“Who do you know that might be facing similar challenges that we've helped you overcome?”
Use only when the challenge and progress are real.
After-win ask
“Can you do me a favour? It will help me help more people just like yourself... Do you know 2-3 others who could benefit from this? I'll personally make sure they are taken care of for you.”
Use only after a confirmed win.
Permission and handoff
“Thanks so much! What usually works best is this - just ask if it's okay to connect us together. If they say yes, create a group chat with us on WhatsApp or Telegram. You don't have to do anything else because I'll take it from there. Sound good?”
Use the shared channel the parties actually use.
Transparent on-behalf request
“Hey [name], quick one. I'm helping [person] with [specific outcome], and thought of you because [reason]. Would it be okay if I sent you a short note from them to see if this is relevant? All good if not :)”
Never pretend the sender has lived the outcome. Make the sender's role completely clear.
Optional and separate
A referral launch is not a simple client ask
Marc also teaches a separate launch structure. Open that lane only after the base relationship engine works and the campaign has the operational capacity to support it.
Advanced referral launch structure
Offer first
The lead offer must work on its own.
The lead offer must work on its own.
Two reward layers
Low-barrier milestones plus a wider competition.
Low-barrier milestones plus a wider competition.
Campaign cadence
Regular progress updates and occasional activation moments.
Regular progress updates and occasional activation moments.
This lane needs separate economics, current-tool verification, delivery capacity, and professional advice where needed. It is never a prerequisite for the base engine.
Marc's reported examples
Use the evidence to understand the mechanism, not forecast a result
Base referral observation
Marc reports that referrals have been his highest-converting lead source since 2021 because trust exists before the first conversation.
This result is self-reported by Marc. No channel ledger or denominator is attached.
Advanced launch example
Marc reports 10,000 organic signups in four days for a 2020 referral-led summit run by a team of four.
This result is self-reported by Marc. This belongs to the advanced launch lane and is not an expected outcome.
Your implementation outputs
Build one complete referral plan
The work is finished when readiness, the ask, permission, introduction, follow-up, and next dates fit together.
Trigger mapReal moments in the client journey where readiness may appear
One readiness decisionThe person, evidence, timing, and reason to wait if needed
One rough askTruthful, easy to decline, and centred on the referrer's helpfulness
One handoff planPermission, shared introduction, and clear ownership after
Follow-up trackerBoth people, status, owner, next date, and three real trigger moments
Human review
AI can prepare, but readiness belongs to you
No generated note can know whether a client relationship is ready, whether the result is true, or whether a care promise can be honoured.
AI may help you
- Organize real result and feedback notes.
- Surface possible trigger moments for review.
- Sharpen your rough ask and handoff.
- Track both people and next dates.
You remain responsible for
- Delivery quality and the client experience.
- Readiness, truth, timing, and tone.
- Final editing and every external send.
- Permission, response, thanks, and follow-through.
No auto-sending, invented results, assumed permission, impersonation, or universal reward formula.
Three-use rhythm
Review three real trigger moments before changing the system
Keep no response, a decline, and an unmade ask separate. Each one teaches something different.
| Use | Trigger date | Readiness evidence | Ask sent by you | Permission | Introduction | Follow-up | Next date |
|---|---|---|---|---|---|---|---|
| 1 | |||||||
| 2 | |||||||
| 3 |
After use three, choose whether to keep, trim, switch, or stop the base system. Do not add launch mechanics to avoid fixing the relationship loop.
Keep it sharp
Two light tune-ups
Bring back your real plan and commitment. Work from what happened, not from what was supposed to happen.
Day 7
Paste your plan and tracker, then name the promise you made. Look at the latest trigger moment and tighten one part of the ask, handoff, or follow-up.
Day 21
Paste the completed tracker and your promise. Compare all three trigger moments, then keep, trim, switch, or stop based on the healthiest relationship evidence.
Key takeaways
Keep referrals earned, easy, and human
- Deliver: readiness begins with a real result or positive experience.
- Detect trigger: the human decides whether now is appropriate.
- Ask: make the referrer the hero and give room to decline.
- Introduce: use permission, then take over the work.
- Follow up: thank both sides, track next dates, and close the loop.