Send the Ninety-Word Email: A Field Guide to Asking for the Introduction You Keep Drafting

There's an email in your drafts folder. It's been there for eleven days. It's ninety words long and you've rewritten it six times. It's not to a client or a boss or anyone who could fire you. It's to someone who might know someone.

I have four of these sitting in my own drafts right now. So let's do this together.

The Draft Isn't Stuck Because It's Bad. It's Stuck Because It's Vague.

When I ask people why they didn't send the ask, the answer is never 'I didn't know what to write.' It's 'I didn't want to be annoying.'

Which is understandable and also the wrong problem. Vague asks are annoying. Specific asks are a gift, because they let the other person make a decision in twenty seconds instead of carrying an open-ended obligation around for a week.

Think about the last time someone asked you for a favor and you said yes quickly. I'd bet the message contained: the name of the person, why them specifically, what you were actually going to say to them, and an easy exit. That's it. That's the whole craft.

Five Rules Before You Write a Word

One ask per message. You want an intro. Not an intro plus advice plus a portfolio review. Pick one.

Name the person. 'Would you know anyone in brand marketing?' is a survey. 'Would you be willing to introduce me to Dana Whitfield?' is a request. Requests get answered.

Do the work they'd have to do. Write the forwardable blurb yourself. They should be able to copy, paste, and go back to their day.

Ask for permission, not the favor, in the first touch. People will almost always agree to 'can I send you a short blurb you could forward?' far more readily than to the introduction itself. It gives them an out that doesn't feel like rejection.

Give them a one-sentence out. 'Totally fine if this isn't a fit — I know you're slammed.' Say it plainly. Unspoken exits are what make asks feel heavy.

Three Templates You Can Steal

The templates below are in the ninety-to-one-hundred-fifty-word range on purpose. Longer reads as pressure. Shorter reads as rude.

1. The permission ask (to someone you know reasonably well)

Hi Marcus — quick one. I'm trying to get in front of Dana Whitfield at [Company] about their spring content push, and I know you two worked together. Would it be alright if I sent you a two-line blurb you could forward if it feels right? No pressure at all — and happy to return the favor anytime, including right now if you've got something in your drafts.

Note the ending. The reciprocity isn't a transaction; it's an acknowledgment that you're in the same boat.

2. The referral ask (after a posting or a warm signal)

Hi Priya — I saw the producer role on your team's page and I'm applying this week. Before I do: is there anything about how the team actually works that a job description wouldn't say? And if there's a better way to get my materials in front of the right person, I'd take the tip. My work's at [link] if it's useful context.

This one works because it asks for information first and leverage second. People answer information questions.

3. The second-degree ask (someone you've never met)

Hi Sam — you don't know me, so I'll keep this short. I write [thing] and I've been following your work on [specific project]. I'm not asking you to vouch for me. I'm asking one narrow thing: would you be open to a fifteen-minute call about how [specific team] handles [specific problem]? If yes, I'll send three questions in advance so it's not a wandering conversation. And if no, no hard feelings — genuinely.

'Send three questions in advance' does more heavy lifting than it should. It tells them the call has an end.

The Forwardable Blurb Is the Real Deliverable

Here's the move most people miss. Don't just ask for the intro — hand them the intro.

Something like:

Dana — meet [Name]. She spent three years building the content program at [Company] and is now taking on freelance projects, including a relaunch last quarter that doubled [specific metric]. I told her you're rethinking [Company]'s newsletter and thought you two should talk. I'll let you take it from here.

Two sentences of context, one specific proof point, one reason for the connection. Now the introducer has zero writing to do. They're not composing; they're forwarding. That's the difference between a yes and a polite non-response.

When Nobody Writes Back

At some point you'll send the perfect ninety-word email and hear nothing. Nineteen times out of twenty, that silence has nothing to do with you. It's a person with three deadlines and a kid's soccer game who read your message on their phone at a red light and genuinely meant to reply.

So here's my rule: one follow-up, seven to ten business days later, one sentence long. 'Bumping this in case it got buried — happy to drop it if the timing's off.' Then you close the tab. Not forever, just for this ask.

And when a real no arrives, resist the urge to treat it as a verdict on your work. It's a scheduling answer or a relationship answer or a bandwidth answer. Usually all three. The best thing you can do is reply with something gracious and short, and then — this is the part that compounds — remember them when you're the one with the door.

Send It Today, Actually Today

Open the drafts folder. Pick one. Make it one ask, name the person, attach the blurb, add the out. Ninety words. Then close the laptop and go do something else with your hands.

The introduction you need is almost certainly one honest message away. It's just very rarely the seventh rewrite of it.