You leave a networking event feeling good. You met someone interesting, had a real conversation, and exchanged cards or LinkedIn profiles. Then a few days pass, and you finally send a message that starts: "It was great meeting you at the event last week. I'd love to stay connected."
No reply.
The problem isn't the wording. It's that enough time passed for the context to fade, and the message that followed gave the other person no real reason to respond. A networking follow-up fails because most people treat it as a formality rather than as a continuation of the conversation they already had.
This is about fixing that, not with a better template, but with a clearer sense of what a follow-up is actually supposed to do, and why timing and specificity matter more than tone.
Most people design their follow-up around their own need to reconnect, not around the other person's experience of the original conversation. The result reads like a reminder that you exist rather than a reason to respond. Generic politeness isn't the same thing as connection, and a low reply rate on networking follow-ups is almost always a content problem, not a volume problem.
A networking follow-up isn't a thank-you note. It's a second chapter in a conversation. The strongest ones reference something specific: a problem the other person mentioned, an idea that came up, something they recommended. That specificity signals that you were actually present. Strip it out, and you remove the very thing that made the original conversation worth having in the first place.
Consider what it's like to receive "It was great connecting with you" from someone's inbox. There's no reason to respond beyond social obligation, and social obligation is a weak motivator for anyone busy. The more generic the message, the more it reads like it could have been sent to anyone, and the reader knows it.
This matters more than it might seem because Mark Granovetter's 1973 research on the strength of weak ties found that loose connections (people met once or twice) often lead to the most valuable introductions and opportunities.
But weak ties are also fragile. They fade fast without reinforcement. A specific, timely follow-up is what converts a weak tie into one that's actually maintained. It doesn't need to be long. It needs to be real.
The single biggest factor in whether a follow-up gets a reply isn't how it's written. It's when it's sent. Details decay faster than most people expect, and timing controls how the message lands.
Follow up within 24 hours of meeting someone, and the conversation is still in working memory for both of you. The details feel fresh, the recognition is immediate, and that recognition creates the kind of warmth that makes a reply more likely. Wait even 48 to 72 hours, and that starts to erode.
By day four, many people need real effort to remember who you were and what you talked about, and responding to something you barely remember takes more energy than just ignoring it.
This isn't about memory quality so much as attention. People encounter dozens of interactions a day. The ones reinforced early stay vivid; the ones that aren't blur into a vague category of "event I went to."
The real obstacle usually isn't writing the email. It's having something worth writing. Walk away from a conversation with no notes, and all you're left with is an impression, not a fact, and impressions make poor follow-up material.
Take sixty seconds after a meaningful conversation to note one specific thing: what someone's working on, what they mentioned, what you said you'd send them. A note in your phone is enough. That one detail is what separates a follow-up that feels personal from one that reads like it was generated afterward.
A networking follow-up doesn't need to be sophisticated. It needs to be clear, specific, and low-friction to answer. A strong one references a specific moment from the conversation, offers something of value or clarity, and makes it easy for the other person to respond without having to figure out what you actually want.
Most effective follow-ups share a similar shape: a specific anchor pulled from the real conversation, a clear reason for writing beyond courtesy, something of value (a resource, an idea, an introduction), and a low-friction ask, or no ask at all. Not every email needs all four. But when one falls flat, it's usually missing at least two.
Sounding transactional almost always comes from leading with what you want. If the first meaningful sentence is about your goals or your business, the email reads like a pitch before the reader's even finished it.
Lead instead with what you noticed about them: "You mentioned you were trying to hire for a role in a market with no local talent pool, and that stuck with me" reframes the whole message as continuation rather than request.
Subject lines do more work than most people give them credit for. If the subject doesn't get the email opened, the body never gets read. A subject line feels personal when it contains something that could only apply to that specific person and that specific conversation: a shared reference, a topic, anything that signals the message is meant for them and no one else.
"The podcast you mentioned at the panel last Tuesday" works because it can't be mistaken for mass outreach. "Following up" or "Great to meet you" could have been sent to anyone, and reads that way. The key is specificity over cleverness: the reader needs to see one detail that jogs their memory, not a manufactured curiosity gap.
Templates are useful as a starting structure, not a finished message. Swap in names and event details without changing anything else, and the result reads exactly like what it is, which is part of why it gets ignored. Use the structure as scaffolding, but the actual content needs to come from the conversation that actually happened.
A few short examples of what this looks like in practice:
A short note after a brief but meaningful conversation, kept under 100 words:
Subject: From the [event name] panel, re: [specific topic]
[Name], good to connect on [day]. Your point about [specific thing they said] stuck with me after the session. I've been thinking about [related observation or question]. Would love to hear how that's been playing out on your end if you're open to a quick exchange. No pressure either way.
A follow-up built around a genuinely relevant resource, not a pretext to reach out:
Subject: Article that connects to what you mentioned about [topic]
[Name], I came across this piece today and thought of what you described about [their challenge]. [One sentence on why it's relevant.] Might be worth a read. Happy to swap notes if anything in it resonates.
A message suggesting a low-pressure next step, when there was clear mutual interest but nothing concrete was arranged:
Subject: [Their name], picking up where we left off
Good to meet you at [event]. The conversation about [topic] felt worth continuing. If you're open to it, I'd be happy to grab twenty minutes sometime in the next few weeks — no agenda, just continuing the thread.
The phrase "no agenda" is doing real work in that last one. It signals you aren't building toward a pitch.
A well-written follow-up is worthless if it bounces. If the only address you have is a personal one from a business card, or you're guessing at a company's email format from a LinkedIn profile, it's worth confirming the address is active before sending anything.
This matters most when reaching out to someone at a company where you're not yet known, a hard bounce to an unfamiliar company domain can affect how your future emails get filtered.
Email lookup and verification tools can help close the gap between a name and a working address, but they're a confirmation step, not a prospecting shortcut. The relationship is already warm from the event itself; the goal is just to make sure a genuine message actually reaches the person, not to hunt someone down.
Whatever tool does that work should stay invisible to the reader; the tone of the outreach should match the warmth of the original conversation, with nothing about how the email address was found showing up anywhere in the message.
Within 24 hours is ideal. The conversation is still vivid for both of you, so your reference points land naturally. Waiting beyond 48 to 72 hours starts to erode the familiarity that makes a message feel warm rather than obligatory.
Lead with what you noticed or remembered about them, not what you need. Opening by reflecting something they said positions the message as a continuation rather than a request; and if there's an ask at all, it comes after you've shown you were actually listening.
Shorter than most people assume. One specific detail beats three generic paragraphs. Reference one thing from the conversation, offer one relevant observation or resource, and ask one easy question, or none at all.
One built from an actual detail in the conversation rather than a clever hook. Something like "Re: the expansion challenge you mentioned" works because it's specific to that person; it jogs memory instead of manufacturing urgency.
Wait five to seven days, then send one brief, low-pressure note. Don't apologize for following up, just resurface the original context in a sentence, add something new if you have it, and make it easy to answer with a yes or no. If there's still nothing, let it rest.
None of this is really about wording. It's about timing and specificity, and both of those depend on capturing a detail before it disappears, which is exactly the part most people skip, because it takes discipline to do in the moment rather than days later when the memory's already gone soft.
This is the specific gap Goodword is built to close. It captures the context of a conversation as it happens, so when you sit down to write the follow-up, you're not starting from a blank page trying to remember what someone said. Instead, you have the one detail that makes the message land.
Start your free trial and see how much easier the follow-up gets when the context is already waiting for you.
.svg)
.png)