Referral Request

A Referral Spends Someone Else’s Trust

A customer says the pilot saved the operations team hours on its last security review. The result is real, the conversation is warm, and asking, “Do you know anyone who might be interested?” would still be a poor referral request.

The customer would have to guess what “interested” means, search an entire network, and attach their name to a pitch they did not write. A vague ask feels small to the founder because it contains few words. It feels large to the person receiving it because all the judgment has been left to them.

Do that judgment first. A useful request tells the referrer what evidence prompted the ask, whom you hope to meet, why that person is likely to recognize the problem, and what will happen after an introduction. It gives them a note they can forward without editing and an easy way to decline.

Earn the Moment

Ask after the person has something credible to refer: an outcome they observed, a problem they described with unusual clarity, a pilot they can judge, or enough direct knowledge of the target workflow to recognize a good match. Enthusiasm helps, but it is weaker than a specific event.

Listen for a natural opening:

• “Our other regional teams have the same problem.”
• “I used to do this with two people at my last company.”
• “The compliance lead in our founder group would understand this immediately.”
• “You should speak to the teams that still manage this in spreadsheets.”

These remarks reveal a network and a reason for entering it. Ask while the context is fresh. Do not ask merely because a call is ending, an automated sequence says it is time, or the account has crossed a usage threshold that you have not interpreted.

Wait when the promised value has not appeared, the relationship is repairing a failure, the person is not close enough to the workflow to judge a match, or you cannot yet describe the next person precisely. A request made too early does more than produce a weak lead: it asks the customer to certify a claim they cannot support.

Define the Match Before Asking for a Name

Describe a situation the referrer can recognize rather than a demographic label broad enough to fit anyone. “Another SaaS founder” forces a search through a category. “The person who owns security reviews at a B2B SaaS company and still chases approved evidence across shared drives” creates a picture.

A workable match has four parts:

• Role: the person who experiences, owns, or pays for the workflow.
• Situation: the observable problem or current alternative.
• Timing: a reason the problem is active now.
• Exclusion: a nearby contact who would waste both sides’ time.

For the evidence-request tracker, the founder might seek an operations or security lead at a small B2B software company that has begun receiving repeated customer questionnaires, still assembles responses manually, and is not looking for a consultancy to write its policies. The description is narrow enough to prompt recognition and honest enough to prevent an attractive but irrelevant introduction.

Ask for one person first. “One or two” may be reasonable when the referrer immediately sees several matches, but a request for a list turns a thoughtful introduction into prospect mining.

Give the Referrer Control of the Door

The safest default is a forwardable note. It lets the referrer decide whether to send it and lets the prospective contact decide whether to respond. Do not ask for private contact details so that you can approach someone under the referrer’s name. Do not draft praise the referrer could not honestly make.

Use this request after observed value:

Hi [Name],

When [specific workflow event happened], you said [specific outcome or change].
I am trying to learn whether that result holds for [precise role] who are
[recognizable situation or timing].

Does one person come to mind who would have direct experience of that problem?
If so, would you be comfortable forwarding the note below? No introduction is
needed if the fit or timing feels uncertain.

Forwardable note

Hi [Prospect] — I have been working with [Founder] on [specific workflow]. We
saw [outcome I can personally support]. [Founder] is speaking with [precise
role or company situation] who currently [problem or alternative]. The first
conversation is [discovery call, evaluation, or pilot discussion], not [nearby
ask that would mislead them].

If that is relevant, I am happy to connect you. No pressure if it is not.

The outcome sentence belongs to the referrer’s experience, not the founder’s most ambitious marketing claim. If the person can support only the quality of the discovery conversation, ask for another discovery conversation:

Hi [Name],

Your account of [workflow] clarified [specific thing learned]. You mentioned
that [precise peer group] often faces [specific situation]. Does one person
come to mind who has dealt with that recently?

I would ask for a [length] conversation about how the work happens today. I am
not asking you to recommend the product, and I will not turn the introduction
into a sales pitch. If someone fits, I can send a short note for you to forward.
If nobody does, that is useful to know too.

Keep the promised first step true. If you ask for research and open with a demo, the referrer bears the reputational cost of your bait and switch.

Follow the Trust Through the Introduction

Once the referrer agrees, send the final note promptly and let them alter or decline it. After the introduction, reply while the shared context is still alive. Move scheduling and follow-up into the new relationship instead of making the referrer chase either side.

If the prospect declines or stays silent, do not ask the referrer to apply pressure. If the conversation happens, thank the referrer and close the loop at the level both parties would reasonably expect: “We spoke and the workflow was relevant, but the timing was not,” is enough. Do not relay confidential discovery details merely to prove that the referral was productive.

Treat a poor match as information, not a debt. Ask yourself whether the target description was too broad, whether the customer valued a different part of the product than you assumed, or whether the network simply does not contain the segment. Revise the request before asking the same person again.

Read the Signal Without Overclaiming It

A referral can show that a customer recognizes the problem elsewhere and is willing to lend trust to the conversation. A cluster of introductions into the same role and situation is useful distribution evidence. Neither proves a large market, product-market fit, or willingness to pay. Referrals are selected through the networks of the people you already know, so they can make one niche look more universal than it is.

Track the trigger for each ask, the target description, whether an introduction occurred, whether the referred person actually had the workflow, and what the first conversation became. The useful question is not “How many referral leads did we get?” It is “Did earned value lead us to more people with the same consequential problem?”

The request is ready when the referrer can decide in a few seconds whether someone fits, forward an accurate note without becoming your salesperson, and decline without having to protect the relationship from your disappointment.