After a networking conversation, send a follow-up that includes one genuinely useful resource, idea, or connection related to what the person mentioned. Do this within two days while the conversation is still easy for both of you to remember.
A generic message such as “It was great meeting you” may be polite, but it gives the other person little to respond to. A relevant follow-up demonstrates that you listened and makes the exchange feel like a professional relationship rather than a one-time request for help.
Choose one useful contribution
Review your notes and identify the most specific topic the person discussed. Then choose one contribution that is easy for you to provide:
- Share an article, event, tool, or public resource that directly relates to their challenge.
- Offer a concise observation from your own experience.
- Introduce them to a contact only if the introduction is genuinely relevant and you have permission from both sides.
- Send a sample, template, or public example that could help with the work they described.
Do not force a contribution. If you cannot offer something relevant, ask one thoughtful follow-up question instead of sending an unrelated link.
Write the message in four parts
- Thank the person for the conversation.
- Mention one detail they shared.
- Provide your single useful contribution.
- End with a low-pressure question or offer to continue the conversation.
Keep the message short enough to read quickly. Your goal is not to summarize your entire background or ask immediately for a job referral. It is to show attention, be helpful, and create a natural reason for another exchange.
Worked example
Suppose you met a product manager at a professional event. She mentioned that her team is trying to improve how customer feedback reaches engineers. You have used a simple feedback-tagging process on a previous project and found a public template that explains a similar approach.
Sample message: “Thanks for speaking with me after the product meetup yesterday. I enjoyed hearing about your effort to make customer feedback easier for the engineering team to use. This public feedback-tagging template may give you a starting point: [link]. On my last project, grouping comments by user goal made weekly reviews much quicker. Would it be useful to compare notes sometime next week?”
This message works because it refers to a real detail, offers one relevant resource, adds a brief personal observation, and suggests continued contact without demanding a favor.
Takeaway: Make every networking follow-up easier to answer by connecting it to one detail from the conversation and one useful contribution.