Warm Intro Request

The Introducer Is Lending More Than Access

A warm introduction carries someone else’s judgment into the prospect’s inbox. The introducer is deciding whether you have chosen the right person, whether your request is honest, and whether making the connection will burden a relationship they value. A vague request makes them perform all three judgments for you.

Use this script only after you can name the person by role and situation, not merely by possible interest. “Someone in home care” asks a contact to search a market. “An operations lead at a home-care agency who has handled same-day caregiver cancellations” gives them a person to recognize.

The useful answer may still be no. A quick no protects everyone’s time and can reveal that the target is difficult to identify through this channel. Do not make a trusted contact apologize for failing to produce a lead.

Qualify the Request Before Borrowing Trust

Write these five lines before contacting anyone:

• Person: [role and company or operating context]
• Qualifying moment: [recent event or recurring work they should know firsthand]
• Learning question: [the assumption this conversation could change]
• Why this introducer: [the legitimate relationship or context that makes the request reasonable]
• Bounded ask: [one factual reply or a short conversation]

If you cannot complete a line, narrow the inquiry before asking for access. The introducer should not have to translate a product pitch into a research question, decide whether a loose persona counts, or invent a reason the prospect might care.

Do not ask for “one or two people who might be interested.” Interest in an idea is not the qualification. Firsthand experience with the workflow is.

Ask for Recognition, Then Consent

The first request has two small decisions: does a specific person come to mind, and would the introducer be comfortable asking that person whether they want the connection? Separating those decisions protects the prospect from a surprise introduction and lets the introducer decline without negotiating the request.

Hi [name],

Because you [specific connection to the community, company type, or work], I
thought you might know a [specific role] who has recently dealt with [specific
workflow moment]. I am trying to understand [one learning question].

Does one person come to mind? No need to search or make a loose match. If
someone does, would you be comfortable asking whether they are open to a
[time boundary] conversation? I have included a note you can forward below.
It is completely fine if the answer is no.

[name]

Use the “not a sales pitch” reassurance only when it is true. If you already sell a product in this area or may make an offer, say that plainly. You can still promise that this conversation is for understanding the current workflow, then keep that promise.

Give Them a Note That Stands Alone

The consent note should tell the prospect why they were chosen, what you want to learn, how much time you are asking for, and that declining is easy. Write it in your own voice so the introducer can forward it without endorsing claims they did not make.

Hi [prospect name] — I am [founder name]. I am studying how [specific role or
company type] handles [workflow moment], especially [learning question].

[Introducer name] thought you might know this work firsthand. Would you be open
to a [time boundary] conversation about the last time it happened and what you
used? This is [an honest statement of commercial intent]. No problem at all if
the timing or fit is wrong.

[contact detail]

Avoid private context, flattering claims, or assumptions about the prospect’s pain. “You have struggled with scheduling chaos” turns an introduction into an assertion the prospect did not make. “You have owned scheduling operations” states the relevant experience without diagnosing them.

Modeled Request

This fictional request gives Priya enough detail to recognize a fit without asking her to sell Maya’s idea:

Hi Priya,

Because you advise several regional home-care agencies, I thought you might
know an operations lead who has recently handled same-day caregiver
cancellations. I am trying to understand how the agency finds a replacement,
who gets pulled into the decision, and where the recovery process stalls.

Does one person come to mind? No need to search or make a loose match. If
someone does, would you be comfortable asking whether they are open to a
twenty-minute conversation? I have included a note you can forward below. It
is completely fine if the answer is no.

Maya

Forwardable note:

Hi Jordan — I am Maya. I am studying how home-care agencies recover from
same-day caregiver cancellations, especially how they find a replacement and
coordinate the change.

Priya thought you might know this work firsthand. Would you be open to a
twenty-minute conversation about the last cancellation you handled and what
you used? I am researching the workflow and will not pitch a product on the
call. No problem at all if the timing or fit is wrong.

[Maya's contact detail]

The qualifying moment does most of the work. Priya can think of an operator, say that she does not know one, or correct the title without guessing what “interested” means. Jordan can evaluate the request before their time is volunteered or a joint thread appears in their inbox.

Read the Reply as Channel Evidence

An immediate name suggests that the role and workflow are legible in this part of the network. A title correction is useful: revise the target before asking for an introduction. Broad categories or several weak possibilities usually mean the request is still fuzzy. Repeated “I know someone” replies that become courtesy calls suggest borrowed goodwill is carrying a weak qualification.

None of these outcomes proves demand. An introduction establishes reachability and enough trust for a conversation. Evidence about the problem still comes from recent behavior, current alternatives, consequences, authority, and willingness to take a next step.

Track the path from request to consent, conversation, qualification, and next behavior. Do not collapse those stages into an “intro count.” A warm channel is useful when it repeatedly reaches people who recognize the workflow, not when it produces friendly meetings.

After the Introduction, Take Back the Work

Once the prospect agrees, respond promptly, thank the introducer, move scheduling out of their inbox, and conduct the conversation you promised. Do not turn the thread into a product pitch or ask the introducer to chase a reply.

Afterward, close the loop without sharing private interview details: thank the introducer, confirm that you connected, and say whether the fit was useful. That small act lets them calibrate future introductions and shows that you treated their trust as a limited resource.

If the introducer does not reply, follow up once by reducing the work rather than increasing the pressure:

Hi Priya,

One quick follow-up. If no one comes to mind, there is no need to search. I am
also trying to learn which role usually owns same-day shift recovery in the
agencies you know: operations, scheduling, or branch management?

Thanks,
Maya

Then stop. A warm relationship is not permission for indefinite follow-up.

The request is ready when a busy contact can recognize the right person, decide whether to lend the relationship, and forward an honest note without rewriting it. The channel is worth repeating when the resulting conversations are qualified enough to change the next discovery decision.