Your warm intro ask fails because you asked someone else to write it

The ask that dies in someone else's drafts folder

Eleven at night, and the person you asked for an introduction is looking at your message for the second time. They like you. They know the person you want to meet. And they still haven't sent anything, because your message left them with homework: work out why the two of you should talk, decide how hard to vouch, and write the framing paragraph themselves.

That paragraph is the expensive part. It's also the part most people quietly hand to the busiest person in the chain. Nothing rude happened. Your ask just landed as a request for labor instead of a request for a click, and requests for labor sit. A week later it's four screens down the inbox, and you've decided the connection wasn't that warm after all.

The connector tax

Every intro request carries a connector tax: the amount of thinking the person in the middle has to do before they can hit forward. Two lines asking for time with a VP of engineering at a company you admire is a high-tax ask. It reads short and costs a lot.

The forwardable email pays that tax up front. You write the email you want your connector to send, in their outbound voice, complete with the reason the two of you should talk and a clean out for the other side. They forward it with a sentence on top. The ask stops being a favor that needs drafting and becomes a decision that takes eleven seconds.

Here's what the template blogs skip. A forwardable email isn't a writing problem, it's a capture problem. Its entire value sits in one or two specific lines about why this pairing makes sense, and those lines only exist if you wrote them down when the conversation happened.

A connector's yes is cheap. A connector's paragraph is expensive.

Why the template advice keeps missing

Search for a warm intro email example and the top results converge on the same artifact: a fill-in-the-blank paragraph with brackets where the specifics go. Subject line, one-line context, the ask, a thank you. All of it competent. All of it aimed at the wrong bottleneck.

The templates assume your problem is phrasing. It almost never is. By the time you sit down to write, you already can't remember whether the person you met in March said their team was hiring or that they'd just finished hiring, whether the budget conversation was Q3 or next fiscal year, or which of the two people at that booth was the one who actually cared about your category.

So the brackets get filled with the only material you still have, which is generic. "I'd love to connect and learn more about their work." That sentence is why the intro didn't happen. It gives your connector nothing to stand behind, and vouching is a credibility transfer. Nobody spends credibility on a paragraph that could have been about anyone.

What the convention actually says

The forwardable email has a reasonably settled shape, and it didn't come from marketing copy. Roy Bahat of Bloomberg Beta is the most-cited source for the framing: write the email your connector can forward as-is, so their job shrinks to a one-line preface and a send. Roy Bahat's post 'Introductions and the "forward intro email"' was published on LinkedIn Pulse in 2014 ([source](https://www.linkedin.com/pulse/20140916181235-3890229-introductions-and-the-forward-intro-email))

It pairs with the double opt-in convention, now standard practice across investor and founder circles: the connector checks with the other side before making the introduction, and the forwardable email is what they check with. Fred Wilson introduced the double opt-in introduction convention on his blog AVC in a post titled 'The Double Opt-In Introduction' published in 2009 ([source](https://www.startupdaily.net/advice/mick-liubinskas-how-to-get-introductions/))

Both conventions solve the same thing from different ends. One removes the drafting burden, the other removes the social risk. Put together, they turn an open-ended favor into a yes or no question with the evidence attached.

How it plays out, start to finish

Take a composite of a common sequence. Tuesday afternoon at a 3,000-person conference, you spend nine minutes with a security architect who mentions, in passing, that their team is replacing an authentication vendor before the fiscal year closes, and that a former colleague of theirs now runs partnerships at a company in your space. You trade cards. Two more conversations happen before you reach the escalator.

Three weeks later you want the intro to that partnerships lead. Two versions of the ask exist.

The first: "Hey, saw you're connected to Dana at [company]. Any chance you could intro us? Would love to chat." Your connector now has to remember what you do, guess why Dana would care, and write something. That message waits.

The second: a two-line note to your connector, then the draft underneath it, addressed to Dana. Who you are in one sentence. The hook, verbatim from the conversation: their architect is replacing an auth vendor before fiscal close and mentioned Dana by name. The ask, sized correctly, which is twenty minutes, not a partnership. And the out, written in, so Dana can pass without anyone losing face.

Same relationship, same connector, same week. The difference is that version two contains a fact you could only have if you wrote it down on Tuesday.

Your intro hit rate is set before you ask

If the thesis holds, the useful work moves. Every hour spent polishing intro request phrasing is being spent at the wrong end of the timeline, because the raw material for a good forwardable email is either in your notes or it's gone.

We've written before about the 72-hour memory cliff, the window in which the specifics of a conversation stop being retrievable and become an impression. The forwardable email is where that cliff sends the bill. You don't feel the loss on Wednesday. You feel it in September, when a great connector is one click from a great introduction and you can't give them a single line that makes the case.

Which reframes what a contact record is for. Not a list of people you've met. A store of the exact sentences that make future asks easy: what they're buying, what they're stuck on, who they mentioned, what they said they'd do next.

Capture is the part you can actually control

Most contact tools optimize the wrong ninety seconds. They make the scan fast, then leave you with a name, a title, and a company, which is the part you were never going to forget anyway. The forgettable part is the sentence the person said right before they walked off.

Met was built around that sentence. Event Mode is designed for the version of you who's mid-conversation and can't stop to type properly, so cards and context go in while the room is still loud, and everything stays on your own iCloud rather than someone else's server. When the intro request comes up three weeks later, the specific hook is already sitting in the record, in the words the person actually used.

The email your connector will forward is mostly a retrieval job. Do the capture, and the writing takes four minutes.