Why this works
A cold connection request asks the reader to make a judgement with no information. A shared name gives them a shortcut: someone they already trust has vouched for you, or at least tolerated you long enough to be connected.
Our test put numbers on it. Ten weeks, 7,340 prospects, one variable changed. Naming a shared colleague lifted replies from 27.0 to 35.1 percent and meetings from 3.5 to 5.1 percent. The effect concentrated where the named person held the same function as the prospect, which makes sense: a VP of Sales cares what another VP of Sales thinks and is largely indifferent to your relationship with someone in finance.
The lift is not magic. It buys you the first read. Everything after that is still your job.
Template 1: the shared employer
Hi {first name}, I worked with {mutual name} at {shared company} for three years, saw you two are connected. I do {one line, what you do} now. Connecting on the strength of that rather than anything else.
Template 2: the same-function reference
Hi {first name}, {mutual name} at {their company} runs the same kind of team you do and mentioned {specific topic} is on your list too. Thought it was worth being connected.
Template 3: the honest weak tie
Hi {first name}, we are both connected to {mutual name}, though I will be honest and say I know her through {specific context} rather than well. The reason I am reaching out is {one specific reason}. Happy to be a contact either way.
Template 4: the warm introduction follow-through
Hi {first name}, {mutual name} said she would mention me to you. Connecting so the thread has somewhere to go. Short version: {one sentence}. No rush on my side.
Template 5: the customer reference
Hi {first name}, we work with {mutual name} at {company}, which is how we ended up connected. She uses us for {specific thing}. If that is a live problem at {their company} I would be glad to talk, and if it is not, ignore this entirely.
How to ask for the introduction properly
Most people ask badly. They send “would you mind introducing me to X” and put the entire cost of the request on the person doing the favour, who now has to write the introduction themselves and decide how strongly to word it.
Do it this way instead. Send the mutual contact a short note saying who you want to reach and why, then write the forwardable paragraph for them: two or three sentences, in their voice, that they can paste with no edits. Give them an easy out, in writing, so declining costs nothing. People say yes far more often when saying no is comfortable.
If they decline or go quiet for a week, use template 3 and name the connection factually. That is not a betrayal, it is a public fact on both your profiles.
When naming someone backfires
Three ways this goes wrong. You inflate the relationship and the prospect checks. You name someone the prospect dislikes, which happens more than you would think inside the same industry. Or you name a customer without asking, and your customer finds out from the prospect rather than from you.
The first two are recoverable. The third costs you a reference customer, which is worth more than the meeting you were chasing.
Finding the shared names at scale
The manual version of this is fine for twenty prospects and impossible for two thousand. Prospectio checks second-degree overlap for every prospect on a list and pulls the shared name into the message variable, so the reference is specific to each person rather than a generic “we have connections in common”. The mechanics are in personalising outreach at scale, and the full test data sits in the outbound benchmarks.