Article · 4 min read
Every warm intro guide fixes the email. The real failure is the notes you didn't take at the first meeting, six months earlier.
The cursor blinks after 'Hi Dana' for a full minute. You met her at a conference in the spring. You know she can open the door to the one investor you actually need. And you have nothing to say. No thread, no detail, no reason the message should exist beyond the favor you want. So you type the line everyone types: 'Would love to reconnect and hear what you've been up to.' It reads fine. It's also the reason the intro won't happen.
Every warm intro guide diagnoses this as a writing problem. Wrong tone, wrong length, wrong order of the ask. Fix the wording and the intro lands. That advice treats a symptom. The email is where the failure surfaces, but it isn't where the failure happened. The ask fails upstream, six months earlier, at the moment you first shook her hand and saved nothing specific enough to write a credible message today. Call it the capture gap. By the time you open a blank draft, the outcome is mostly already decided.
'Would love to reconnect' is not weak writing. It's a receipt for the notes you never took.
The template economy exists because the writing frame is easy to sell. Search 'warm intro email template' and you'll find a thousand fill-in-the-blank structures, each promising the ask will land if you just phrase it right. They don't work for the case that matters, because the reader isn't grading your prose. They're checking one thing in the first two lines: does this person actually remember me, or am I a name on a list they're being asked to spend social capital on. A template can't fake that. Specificity can't be pasted in after the fact. Either you have the detail or you're performing a warmth you didn't earn, and the recipient can tell in about four seconds.
Watch how this plays out where founders trade intros in the open. On r/ycombinator, the recurring warm-intro threads circle the same tension: everyone knows deal flow runs on intro chains, and everyone has been on the receiving end of a reconnect message that clearly forgot the last conversation. A r/ycombinator commenter stated 'Even one warm intro through a mutual connection can be worth more than 50 cold demos.' ([source](https://www.reddit.com/r/ycombinator/comments/1qc6wix/any_advice_for_landing_an_enterprise_customer_b2b/)) The VC practitioners who write about this, on blogs like Both Sides of the Table, landed on the double opt-in intro years ago for exactly this reason: the connector forwards your ask to the target first and lets them say yes before any introduction is made. It's a filter for credibility. And the thing that earns your forwardable note a yes is never the polish. It's whether you gave the connector something concrete enough to vouch for. Google's own People Also Ask surfaces 'How do you give a warm introduction?' right next to the request phrasings, which tells you the connectors are as unsure as the askers.
The double opt-in raises the bar
When the connector forwards your ask for a yes before making any introduction, your note has to stand on its own credibility with a stranger. Vague reconnect language fails that filter every time.
Here's the same ask, two ways. Version one: 'Hi Dana, would love to reconnect and hear what you've been up to. Any chance you could intro me to someone at Ridge Capital?' Polite, correctly structured, and dead on arrival, because nothing in it proves the spring conversation happened. Version two: 'Hi Dana, you mentioned at the SaaStr afterparty that Ridge had just passed on a company for being too early, and that timing was your read on most seed misses. We're at the stage you called the sweet spot now. Would an intro make sense?' Same length. Same ask. The second one is impossible to write unless you captured the detail back in April. The template can't generate that sentence. Only your notes can. That's the whole game, and it's decided months before the draft.
| The reconnect note | The credible reactivation |
|---|---|
| Opens with 'Would love to reconnect' | Opens with the exact thing they said |
| Proves nothing about the first meeting | Proves you were listening |
| Reads as a name working a list | Reads as a real prior relationship |
| Any template can produce it | Only your own notes can produce it |
| Connector hesitates to vouch | Connector forwards it without friction |
If the failure is upstream, the fix is upstream too. Stop optimizing the reconnect email and start treating the first meeting as the moment the future ask is won or lost. That reframes what capture is even for. It isn't admin you do to feel organized. It's the raw material every future intro request gets built from, and its shelf life runs longer than you'd guess, because the ask you can't foresee today is the one that will need the detail most. Six months is the ordinary gap between meeting someone and needing something from them. Whatever you saved in that first conversation is exactly, and only, what you'll have to work with.
This is the problem Met is built around. The failure mode isn't that people don't follow up, it's that by the time they try, the context is gone. Met's Event Mode keeps the room captured while you keep talking: who you met, what they said, the specific thread you'd need to reactivate later, saved in the moment instead of reconstructed from a foggy memory in August. iCloud-only storage means those notes stay yours, not sitting on someone's server. The point was never a better template. It's that when the reconnect moment arrives, you're the sender who obviously remembers, and the ask lands before the second sentence.
The open question is whether the double opt-in intro becomes default etiquette in founder networks the way it already is in venture. If it does, the credibility bar for the forwardable note climbs, and the gap between operators who capture and operators who wing it stops being a soft advantage. It becomes the whole difference in who gets the intro and who gets a polite non-answer.
Met was built for people whose next quarter depends on reconnecting with someone they met once, months ago, and needing the conversation to feel remembered. It captures the specific detail at the moment it's said, so the reconnect message writes itself instead of stalling on a blank draft. No ads, no data sold, iCloud-only.
Field notes on conference networking, follow-up timing, and what we ship next. No spam, no AI hype.
No spam. Unsubscribe anytime. Replies go to support@sailquery.com.