Published 8 min read
The Consulting Cold Email: Templates That Get Replies
A consulting cold email gets a reply when it does three things in under 100 words: proves you did homework specific to that person, asks for something that takes 15 minutes or less, and gives them an easy way to say yes. Most emails fail on the first one. They open with "I am very interested in consulting" and ask for "any advice," which reads as a mail merge, and a mail merge gets deleted on a phone screen in about four seconds.
I read a version of this email nearly every week of my time at McKinsey, forwarded by whoever received it, usually with a one-line comment attached that was not flattering. So I know what gets forwarded with "worth a call" instead, and it is not about being clever. It is about respecting the reader's time in a way that shows up in the actual words. This article covers the email itself. For the fuller strategy of who to email, when, and how to build a network before you need one, read the full networking guide.
Why most cold emails get ignored
Consultants get a lot of these. A busy staffer on a live project might see three or four a week from students and career changers, on top of client work that runs sixty-plus hours. The email is competing with that inbox, not with your effort. Three patterns kill it immediately.
The subject line is vague. "Networking" or "Quick question" tells the reader nothing and often gets swept into a folder they check monthly.
The body asks for too much, too soon. "Can we set up a call to discuss your career path and the industry" is a 30-minute ask from a stranger. Nobody owes you 30 minutes.
The email is about you. Paragraph one explains your background and your interest in consulting. The reader has to work through your story before finding out what you want, and most stop reading before they get there.
The template that works
Here is the shape, then the reasoning for every line.
Subject: [Mutual connection or shared detail] - quick question about [specific team or project]
Hi [Name],
[One sentence connecting you to them specifically: shared alumni group, a project you read about, a mutual contact who suggested you reach out.]
I am a [year, school] student interested in [practice area, if you know it], and I saw you worked on [specific thing about their background]. I have two quick questions about [specific topic], and I would be grateful for 15 minutes on a call whenever is convenient, or I am happy to take a shorter answer over email if that is easier.
[One line on what makes you a credible use of their time: a relevant project, a shared background, a specific reason this practice area interests you.]
Thank you for considering it. I know your time is limited.
[Your name]
[One line: school, phone number]
Notice what is missing. There is no resume attached, no full life story, no ask for a referral. The ask is small, specific, and gives an out.
Line-by-line reasoning
The subject line names a specific detail, not a category. "Mutual connection at [firm]" or "Fellow [school] grad, quick question about your restructuring work" gets opened because it signals this is not a mass email. A generic subject like "Networking opportunity" gets the same treatment as spam, because functionally it is the same email everyone else is sending.
The opening line does the work of proving you are not a stranger with a form letter. If you found them through a school database, say so. If a mutual contact suggested you reach out, name them in the first line, not buried in paragraph three. Reviewers and staffers give more benefit of the doubt to a warm path than a cold one, and the fastest way to signal a warm path is to name it immediately.
The two-questions framing is the single most important line in the template. It bounds the ask. "Can we talk about consulting" is unbounded and vague, and vague asks get deferred indefinitely. "I have two questions about how the industrials practice staffs junior analysts" is answerable in one paragraph if they choose to reply by email, which most will, because it is faster for them than scheduling a call.
The credibility line matters more for people without a warm connection. If you are cold-emailing based on a shared school or a specific project, one line explaining why their background is relevant to your interest reads as intentional. Skipping this line is what makes an email feel like it was sent to fifty people with the name swapped.
The closing is short on purpose. A long thank-you paragraph reads as filler. One sentence acknowledging their time, then your name and contact information, is what a person who respects busy schedules actually writes.
Follow-up email, if you do not hear back
Silence after one email is normal. People are busy, and your email is not the only thing in their queue. Wait one week, then send a short follow-up rather than a second full pitch.
Hi [Name],
Following up in case this got buried. Still happy to take a shorter answer over email if a call does not work with your schedule this month. No worries either way, and thank you again for considering it.
[Your name]
This works because it removes pressure. "No worries either way" signals you are not going to keep emailing, which paradoxically makes people more likely to respond, because replying costs them nothing in social obligation.
What to do with the reply
If they say yes to a call, come prepared with your two questions ready and one or two follow-ups, and end the call by asking if there is anyone else on their team it would make sense to talk to. That question is how one email turns into three conversations.
If they answer by email instead of scheduling a call, treat that answer as the full conversation. Reply with a thank-you and do not push for a call afterward. Pushing after they chose the lower-effort option reads as ignoring the signal they just gave you.
If they do not reply after the follow-up, move on. A third email crosses from persistent into ignoring a clear signal, and the recruiting world inside a firm is smaller than it looks. This matters more the earlier you start: if you are still years out from applying, the internship timeline guide covers when networking outreach should actually begin relative to your application cycle.
Common mistakes, and the fix
| Mistake | Why it fails | Fix |
|---|---|---|
| Subject line is generic ("Networking", "Quick question") | Reads as mass email, gets filed or ignored | Name a specific shared detail or project in the subject |
| Opening paragraph is about your background | Reader has to work to find the ask | Lead with the connection, then the ask, in the first two sentences |
| Asking for a 30-minute call from a stranger | Too large a favor for a first email | Ask for 15 minutes or offer an email-only option |
| Attaching a resume unprompted | Turns a conversation request into a job pitch | Only attach if asked, or mention it is available if useful |
| Sending a second full pitch after silence | Reads as not respecting the first silence | One short, low-pressure follow-up, then stop |
| No specific questions, just "any advice" | Puts the work of defining the conversation on them | Come with two specific, answerable questions |
The bottom line
A consulting cold email gets a reply when it respects the reader's time more than it showcases your interest: a specific subject line, a fast connection to why you are writing, a bounded ask of 15 minutes or an email answer, and an easy exit if they cannot help. Send the follow-up once, then let it go. Networking earns you a warmer read, but the resume still has to close the deal, so once you have a contact willing to help, make sure the document they see is not working against you: check it against the complete consulting resume guide and the 11 mistakes that get resumes rejected. And if a referral turns into an actual application, how many firms to apply to is the next question worth answering.
Go deeper
Networking is one piece of getting to the interview. If you want the full system for building a network into interviews and interviews into offers, the course covers the whole path, not just the emails.
Get the complete Cut to the Case course →
One payment, lifetime access, 30-day guarantee.
Frequently Asked Questions
What should the subject line of a consulting networking email say?
Name a specific detail, not a category. A shared school, a mutual contact, or a specific project they worked on gets opened because it signals the email is not a mass send. Generic subjects like 'Networking' or 'Quick question' often get filed and ignored.
How long should a consulting cold email be?
Under 100 words. One line connecting you to the reader, one line stating your ask with two specific questions, one line on why you are a relevant use of their time, and a short thank-you. Anything longer asks the reader to do work before they trust you.
Should I ask for a call or offer to take answers over email?
Offer both. Asking only for a call is a bigger favor from a stranger, and some people will answer over email if you give them the option, which is faster for everyone and still gets you the information.
How many times should I follow up if a consultant does not reply?
Once, about a week after the first email, and keep it short and low-pressure. A second full pitch after that reads as ignoring their silence, and the recruiting world inside most firms is small enough that persistence past that point works against you.
Should I attach my resume to a cold networking email?
Not unprompted. Attaching a resume to a first email turns a conversation request into a job pitch, which is a different and larger ask. Mention it is available if it becomes relevant, and let them ask for it.
What questions should I ask in a consulting networking call?
Come with two specific, answerable questions about their practice area, staffing, or path into the firm, not an open-ended 'tell me about consulting.' End the call by asking if there is anyone else on their team worth talking to, which is how one conversation turns into three.