The intro went nowhere because context was missing
Warm intros stall when the forwarded blurb transfers a name but not the context an investor needs to say yes.
A friend who knows a partner at a fund you want agrees to make the intro. Good. You send him a quick line: "We're building an AI tool for sales teams, raising a seed round, would love to connect with [partner]." He copies most of it into an email, adds "I think you two should talk," and hits send.
The partner opens it on her phone between two board meetings. She reads "AI tool for sales teams, raising a seed." She has seen forty of those this quarter. There is nothing in the message that tells her why this one is worth an hour, why she specifically, or why now instead of next quarter. So she does the rational thing with an ambiguous request from someone she trusts but who vouches for a lot of founders: she replies "happy to chat, have them grab time" and forgets about it. The intro technically happened. The meeting, if it happens at all, starts from zero. You spend the first ten minutes re-explaining context the intro was supposed to carry.
The intro did not fail because your connector did a bad job. It failed because you handed him a name and asked him to transfer it, when the job was to transfer context. The blurb you wrote was the weakest link, and you wrote it in thirty seconds because you treated getting the intro sent as the finish line. It is the starting line, and the gun went off with the investor still confused about why she is in the race.
Why founders under-write the blurb
Most founders put real effort into the ask ("will you intro me?") and almost none into the artifact the ask produces (the message that actually reaches the investor). The reasoning feels sound: you do not want to over-engineer it, you trust your connector to say nice things, and a long blurb feels presumptuous. So you send a vague one or, worse, no blurb at all and leave your connector to improvise.
Here is what that misses. The forwarded message is the only thing the investor sees before she decides whether you are worth scarce calendar time. Your connector's credibility gets her to open the email. Your blurb is what makes her say yes to a real meeting instead of a brush-off "send me the deck." If the blurb is generic, the warmth of the intro is wasted, because warmth gets you read, not funded. The investor still has to answer "why should I spend an hour on this?" and you have left that question blank.
And there is a second cost. A vague blurb forces your connector to either improvise context he does not have, which can be wrong and embarrassing, or to add nothing, which signals low conviction. Either way you have made him do work he is bad at instead of doing the work you are good at. The person who knows why this matters is you. Write it down.
A warm intro is a context transfer
The mental shift is to stop thinking of an intro as moving a name from your network to the investor's inbox, and start thinking of it as moving a specific, decision-ready context. A complete intro context answers six questions before the investor has to ask any of them.
The six are not interchangeable. Each one closes a specific gap in the investor's head, and a blurb that skips one leaves that gap open for the meeting to fill.
| Element | The question it answers | What happens if you skip it |
|---|---|---|
| Who you are, in one concrete line | "What does this company actually do?" | She pattern-matches you to the nearest generic category and loses interest |
| Why this investor specifically | "Why is this in my inbox and not someone else's?" | She assumes you are spraying intros and discounts the warmth |
| Why now | "Why should I act this week instead of later?" | The request drifts to the bottom of a list with no deadline |
| One piece of proof | "Is there any signal this is real?" | She has nothing to weigh against the forty other AI-for-sales pitches |
| The specific ask | "What exactly am I being asked to do?" | She defaults to the lowest-effort response: 'send the deck' |
| The mutual context | "How do you and my friend actually know each other?" | The connector's vouch feels thin and she trusts it less |
Notice what is not on the list. You are not asking the investor to read a pitch. You are not attaching a twelve-slide deck to a cold-ish first touch. You are giving her exactly enough to make one decision: is this worth a first meeting? Six lines, each doing one job, is enough. The deck comes after she says yes.
The other thing to notice: every one of these six is something you know and your connector does not. "Why this investor specifically" requires you to know that she led the seed in a company two doors down from your problem space. "Why now" requires you to know your own timeline. Proof is your number. This is why outsourcing the blurb to your connector produces mush. He can vouch for you, but he cannot supply the context, because the context lives in your head and your sources.
Teardown: the blurb that went nowhere
Here is the blurb from the top of this piece, and the gaps it leaves open.
"We're building an AI tool for sales teams, raising a seed round, would love to connect with [partner]."
"AI tool for sales teams" is a category, not a company. It tells her nothing she cannot already imagine. "Raising a seed round" is true of half her inbox. "Would love to connect" is not an ask she can act on; connect how, for what, by when? There is no reason she specifically should be the one, no proof anything is working, and no sign of why this week matters. Every one of the six elements is missing. The blurb is a name with a label on it.
Now the rewrite. Same company, same length budget, six jobs done.
Subject: Intro to [Founder] / [Company] - [your connector] suggested I reach out
Hi [Partner],
[Connector] offered to connect us. Quick context so you can decide if it is worth a call.
[Company] turns a sales team's call recordings into the CRM updates the reps never make. We sit inside the rep's existing workflow instead of asking them to log anything. (Who we are.)
I wanted to reach you specifically because you led [Portfolio Company]'s seed, and we are solving the data-capture problem one layer upstream from what they do. (Why you.)
We are opening a [size] seed and lining up first conversations over the next two weeks before the round gets noisy. (Why now.)
Early signal: [N] teams are live, and [specific metric, e.g. "CRM fields filled per rep per week went from 3 to 19 in the first month"]. (Proof.)
The ask is a 30-minute call in the next two weeks. If the timing is off, even a yes/no on whether this is in your wheelhouse would help. (The ask.)
[Connector] and I worked together at [shared context]. (Mutual context.)
Deck and data room ready whenever useful.
[Founder]
The rewrite is longer, but it is not asking for more of her time, it is saving her time, because it answers in sixty seconds the questions she would otherwise spend the first ten minutes of a meeting asking. And critically: she can forward your connector's intro with this pasted underneath, and the context survives the forward intact. Your connector adds one line of warmth on top. He does not have to know your metrics or your timeline, because you supplied them.
Use a labelled placeholder for any number you do not have yet. An honest "[insert real activation metric]" that you fill before sending beats a clean fabricated figure that collapses the first time she asks a follow-up.
The intro packet template
This is the artifact. Fill it once per investor before you ask anyone for the intro, and send it to your connector along with the ask. Your connector's entire job becomes: read it, add a sentence, forward.
INTRO PACKET - [Investor name] @ [Fund] TO MY CONNECTOR: Here is everything you need to make this intro. Add one line of why you rate us, paste the block below, hit send. You do not need to explain what we do. It is all here. ----- FORWARDABLE BLOCK (paste this) ----- WHO WE ARE (1 line, concrete, no category-speak): [Company] does [specific thing] for [specific user], by [specific mechanism]. WHY THIS INVESTOR (1 line, specific to them): Reaching out to you because [thesis fit / portfolio overlap / public POV they wrote]. WHY NOW (1 line): [Round timing / milestone just hit / window before the round gets crowded]. PROOF (1 line, one number or one named design partner): [Strongest real signal. Use a placeholder if you must, fill before sending.] THE ASK (1 line, specific and low-friction): [30-min call by DATE / or a quick yes-no on fit if timing is off]. MUTUAL CONTEXT (1 line): [Connector] and I know each other through [shared history]. CLOSE: Deck and data room ready when useful. ----- END FORWARDABLE BLOCK ----- NOTES FOR ME (do not send): - Personalization source: [where the "why you" line came from] - Is the proof number real? [yes / placeholder] - Sent: [date] Forwarded: [date] Reply: [date]
The rule that makes this work: never send your connector a bare ask. Send the ask and the packet together, every time. You are removing the only step where the intro can break, which is the moment your connector has to manufacture context he does not have.
Where this gets expensive at scale
One intro packet is twenty minutes. The problem is that the "why this investor" line is different for every investor, and it is the line that does the most work and takes the most effort. Doing it well means knowing that this partner led a relevant seed, that she wrote a post last month about the exact problem you solve, that your connector overlapped with her at a previous fund. That research lives across your inbox, your notes, LinkedIn exports, and the partner's public writing. Pulling it together by hand for thirty investors is where founders quietly give up and revert to the generic blurb that goes nowhere.
This is the part of the workflow RoundOS is built to carry. It reads the sources where your round already lives, your email, calendar, meeting notes, LinkedIn exports, and investor lists, and for a given investor it surfaces the specific connection: the warm path to them, the overlap between your connector and the partner, the public thesis that makes the "why you" line true instead of flattering. The packet stays yours to write and approve. What you stop doing is the cross-source digging that makes a personalized intro context take an hour instead of two minutes.
The point is not automation for its own sake. It is that the difference between an intro that lands and one that dies is the specificity of two or three lines, and that specificity comes from context scattered across sources you already have but cannot search fast enough by hand.
Rewrite the last stalled intro.
Pull up the last intro that went quiet and check it against the six elements. Then rewrite it as an intro packet so your connector forwards context, not just a name.