How to make an introduction both people want

A professional introduction asks two people to spend attention on a relationship they did not arrange themselves. Treat that attention as something they can choose to give. Before putting anyone on a shared thread, explain the reason to meet to each person separately and wait for a clear yes from both. This guide uses fictional examples to show how that sequence can work in ordinary professional conversations.

Help two people understand why they might talk, then let them decide. You do not need to guarantee a useful outcome, write a glowing character reference, or remain responsible for every message that follows. You do need enough information to make a specific proposal and enough patience to accept a quiet no. A careful introduction often starts with one more question to the person asking for it.

Clarify what the requester actually needs

Suppose Maya asks to meet Leo, a product researcher you know. Before contacting Leo, ask Maya what she hopes to discuss. “I would like to learn about research” is too broad to tell Leo what accepting means. “I am choosing between two ways to recruit participants for a short study and would value a fifteen-minute perspective” is much easier to evaluate. It identifies a question, a relevant area of experience, and a bounded request.

Also ask what can be shared. Maya may be comfortable naming her company but not discussing an unannounced project. Offer to use a short summary she approves. If she sends a long document, do not forward it automatically. A recipient should not have to read confidential background or a detailed pitch simply to decide whether they want an introduction. Prepare a few sentences that stand on their own.

Check the reason for the match

A familiar title is not enough. Think about why this particular person might be appropriate for this particular question. Perhaps Leo has publicly written about recruiting research participants, or has told you that he enjoys occasional conversations with early-stage teams. Keep the claim within what you actually know. “Leo has worked on participant recruitment” is different from “Leo is the best person in the industry.” The latter asks your confidence to do too much work.

Check for a reason not to proceed as well. The request might overlap with paid consulting, create a conflict, or arrive during an unusually busy period. You can still ask, but the message should make the nature of the request clear. If Maya wants free advice that Leo normally sells, do not disguise it as a casual catch-up. A paid consultation may be the appropriate option, and Leo should be free to suggest one.

Ask each person separately

A note to Leo could read: “Maya is planning a small customer study and is choosing how to recruit participants. She asked whether I could connect you for a fifteen-minute conversation about that choice. I thought of you because of your work on research recruitment. Would you be open to an introduction? No problem if the timing or request does not fit.” This is enough context for an initial decision.

Ask Maya to confirm the same proposed introduction before sharing details. Her original request may already give explicit permission, but verify if the scope or person has changed. For example: “Leo may be open to discussing recruitment choices rather than reviewing the full study. Is that still useful, and may I share your email address with him if he agrees?” Both approvals should refer to the same conversation, not two different versions of the offer.

Let a refusal be complete

If Leo declines, reply with a simple acknowledgment. There is no need to ask him to justify the decision or nominate someone else. You can tell Maya that the introduction will not be possible at this time without passing along personal reasons. If Leo explicitly suggests another person, treat that as a new proposal requiring its own permission. A name mentioned in a private reply is not an automatic invitation to contact them.

Silence is also not agreement. You may choose to send one brief follow-up after a reasonable interval if the relationship makes that appropriate. State that you will leave it there if the timing does not work. Avoid serial reminders or messages that make the recipient responsible for the requester's disappointment. If the opportunity expires, close the loop with Maya and move on. The introduction process should have an end even when no introduction occurs.

Write the shared message after both approvals

Once both people agree, make a new thread with a subject that names the topic, such as “Maya / Leo: research recruitment conversation.” Open with the fact that they have each agreed to connect. Give each person one accurate sentence of context and repeat the agreed reason for the conversation. Include the approximate time request if that was part of the approval. Do not expand a fifteen-minute discussion into an ongoing advisory role.

A sample handoff could read: “Maya and Leo, thank you both for being open to connecting. Maya is planning a small customer study and wants to compare two recruitment approaches. Leo has worked on recruitment for product research. Maya, please send Leo a little context and a couple of possible times for the fifteen-minute conversation we discussed. I'll leave you to arrange the details.” This tells the reader who acts next without making the thread feel ceremonial.

Keep the handoff light

The requester should take the next step promptly and stay within the agreed scope. A short reply can thank both people, offer a few times with a time zone, and ask whether another format would be easier. Avoid attaching a large deck or sending a calendar invitation before a time is agreed. A recipient who accepted an introduction has not necessarily accepted a meeting at the requester's chosen hour.

You can remain copied initially or say that you are stepping out. Do not quietly place someone on blind copy while implying the thread is still private to the original group. If using a familiar convention such as moving the introducer to BCC, state it clearly and let everyone know who remains in the conversation. The simplest option is often to start a direct scheduling exchange after the initial acknowledgment.

Recover when the conversation changes

Sometimes Maya realizes that she needs a detailed review rather than a short discussion. That is a new request. She should describe the additional work and ask whether Leo is interested, including whether it would be a paid engagement. The original introduction should not be treated as open-ended permission to ask for more. If Leo cannot help, Maya can thank him for what he has already offered.

A scheduling delay is a smaller issue but benefits from the same clarity. One practical follow-up might say that the project timeline has shifted and ask whether the conversation still suits. If there is no reply, stop chasing. Do not return to the introducer repeatedly to apply pressure. The introducer made a connection; they did not become a collections desk for unfinished calendar arrangements.

Close the loop without demanding a report

A brief thank-you to the introducer is considerate once the conversation happens. It can say that the meeting took place and that the introduction was appreciated. Keep the content of the discussion private unless both participants are comfortable sharing it. An introducer running a formal program may ask for feedback, but should explain in advance what they will collect and how it will be used.

For your next introduction, keep a small checklist: a specific question, an accurate reason for the match, an agreed time request, permission from both people, and a named next step. If one is missing, resolve it before sending the shared email. These ordinary details do most of the work. A useful introduction is one that both people can understand, accept freely, and leave with clear expectations.