How to follow up after an introduction

After an introduction, reply to the actual reason you were connected, thank the person who introduced you and propose one useful next step. Keep scheduling simple, respect a decline and send a short update once something happens. The goal is a worthwhile conversation, not keeping an email thread alive.

An introduction can arrive with enthusiasm and still leave both people wondering what to do next. “Great to connect” is friendly, but it does not tell the other person whether you want advice, a potential collaboration or a specific answer. A useful follow-up makes the purpose easy to understand and the next decision easy to make.

What should your first reply say?

Read the introduction before writing. Notice what the connector said about each person and why they thought a conversation could help. Respond to that context instead of pasting a general biography. If the introduction describes a different purpose from the one you expected, clarify it gently before making a larger request.

A simple structure is a thank-you, one sentence of relevant context and one proposed next step. You do not need to retell your entire career. If your project matters to the request, describe the part that connects to the other person's experience. Make it possible for them to understand the ask without opening several attachments.

Here is an original example for a hypothetical founder: “Thanks for connecting us, Maya. Jordan, we're trying to understand why new customers get stuck between setup and their first useful result. Maya mentioned your experience with onboarding. Would you be open to a short conversation about how you approached that handoff?”

The example names a problem and gives the other person room to decide. It does not turn a friendly introduction into a request to become an adviser, join a company or provide an unpaid project. Save those larger possibilities for a conversation in which both people have enough information to consider them.

Who should stay on the email thread?

Acknowledge the connector and make the transition clear. An introduction guide hosted by UC San Diego recommends taking responsibility for the reply, sparing the introducer routine scheduling messages and later closing the loop. Apply that advice to the actual conversation rather than removing someone who still has a working role in it.

If the connector's part is finished, you might write: “Thanks, Maya. I'll take it from here so you don't get all the scheduling replies.” If you move someone to BCC, say so in the message and check the recipient fields before sending. If the connector is participating in the meeting or coordinating a shared project, keep them included as appropriate.

Do not copy extra colleagues merely because the subject might eventually involve them. Start with the people who agreed to the introduction. Before forwarding sensitive material or bringing someone else into the exchange, check that doing so fits what the participants agreed to share. A shared contact is not blanket permission to circulate the conversation.

How do you suggest a meeting without creating more work?

Offer a limited choice and state your time zone. If the other person has already offered a scheduling method, use it. Otherwise, suggest a couple of possible windows or ask what works for them. Avoid sending a calendar invitation before you have agreed on the time and purpose.

For example: “I can do Tuesday between 10 and 11 a.m. Eastern or Thursday after 2 p.m. Eastern. Would either work? If email is easier, the main question is how you decided who owned the handoff.” These are illustrative options, not recommended universal meeting times. The useful part is making both the format and the decision clear.

Provide a brief agenda once the conversation is agreed. Mention the question you hope to answer and any material the other person offered to review. Keep preparation proportionate to the meeting. Asking someone to read a full presentation before a first conversation can create a burden that the introduction never implied.

What if nobody replies?

First check the basics: did you reply to the correct people, is your request clear and did you acknowledge any availability they already mentioned? Silence can have many explanations. Do not interpret it as interest, rejection or permission to try every available contact channel.

If the exchange has gone quiet and there is no stated deadline, a short reminder after several business days can be reasonable. That interval is an editorial suggestion, not a researched response-rate formula. If someone gave a different timeline, follow it. Include the context again so they do not have to reconstruct the original thread.

An original reminder could say: “Following up on Maya's introduction about customer onboarding. If a short conversation would be useful, I'm happy to work around your schedule. If the timing isn't right, no problem.” It is enough to make the request visible again. You do not need to manufacture urgency or suggest the connector expects a reply.

If there is still no response, stop chasing unless the person invited a later check-in or you have a genuinely relevant new reason to reconnect. Do not recruit the connector to apply pressure. If there is a real deadline, describe it accurately and arrange an alternative plan rather than treating the introduction as an obligation.

How should you follow up after the conversation?

Send a short note tied to what was actually discussed. Name one useful point, state any action you agreed to take and confirm any next step that belongs to the other person. If no further step was agreed, a specific thank-you is enough. Do not invent a continuing relationship because the conversation was pleasant.

For a hypothetical operations discussion: “Your point about checking who owns each handoff was useful. I'll map our current onboarding process before changing tools. You offered to look at a one-page summary, so I'll send that next week.” This note records a real commitment. It does not ask the recipient to supervise work they never volunteered to review.

If the conversation revealed a possible role, describe the next discussion honestly. Someone helping you think through a process is not automatically a candidate. Our guide to finding an operator for your startup explains how to turn a vague need into a role brief before proposing responsibility.

What should you tell the person who introduced you?

Close the loop without sharing the other person's private information. A useful update can be as simple as: “Thanks again for connecting us. We spoke, and I now have a clearer way to approach the onboarding problem. I'm going to test it with the team.” You can report a useful outcome without exaggerating it into a partnership or endorsement.

If the fit was wrong, be equally straightforward: “We spoke and realized we're focused on different stages of the problem. I appreciated the introduction.” That feedback can help the connector understand your needs. Avoid blaming them for an outcome neither of you could know before the conversation.

If you want another introduction, make a separate request with its own reason. Our guide to requesting a warm introduction covers that earlier stage. This article begins after the connection has been made; a completed meeting is not a standing invitation to ask the connector for more access.

What if you want to decline or change the purpose?

A direct, considerate reply is better than accepting a meeting you do not want. You might say: “Thank you for thinking of me. I don't have the relevant experience for this question, so I won't be useful on a call.” Offer an alternative only if you genuinely want to and can do so without volunteering someone else's time.

Sometimes the introduction is relevant but the original request has grown. Restate what you can offer: “I can answer the question about our onboarding process by email, but I can't review the full operating plan.” That keeps the relationship honest. A clear boundary is compatible with a thoughtful introduction.

If you are making the introduction yourself, our guide to asking both people before connecting them covers the consent and context that belong before this stage. Follow-up works best when both people already understand why they are in the conversation.

AME learns what you are building and what you need next, then makes purposeful introductions one at a time. You can apply for AME 1000. Whatever route brings you together, treat the first reply as the start of a conversation and leave both people free to decide what comes next.