Consulting · Sales VP · After Meeting
Referral Request for Consulting Sales VP: After Meeting
The query is practical: what should a referral request email to a Consulting Sales VP say for after a meeting? Start with a direct answer, add one proof point about proposals that stall in procurement and relationships that go quiet between projects, and close with confirm the next date or the open question.
Last updated: 2026-09-02 · Reviewed by: Sales Email Template editors
We write templates the way we wrote emails on quota: short, specific, and easy to forward. When we cite research below, it is because the number changes how a buyer reads your note, not to pad the page.
Sources: HubSpot sales email benchmarks; Gong follow-up research
Why does this referral request work for a Consulting Sales VP?
- Ask for a specific profile, not 'anyone in your network.'
- Speaks to proposals that stall in procurement and relationships that go quiet between projects instead of a generic "value prop."
- Fits how a sales VP actually reads: 70 to 90 words. Lead with the outcome.
- List what you heard, what you promised, and what you need from them, in that order.
- Give them cover to decline.
When should I send this to a Consulting Sales VP?
Ask after you've given them a reason to want to help, not after the first coffee. Same day, within a few hours. Next morning is the backup, not the plan. For this combo, treat "Same day" as the default, then adjust around a small diagnostic can start in a week. a transformation waits on a sponsor. If you're emailing a sales VP, 70 to 90 words. Lead with the outcome.
What this Sales VP actually cares about
A sales VP in Consulting is protecting quota, forecast credibility, and rep time. They think in pipeline, ramp, and forecast risk. If you can't map your email to a number they already report, it feels like a hobby. The hook that earns a look is a stage in the funnel that's leaking, a slow follow-up SLA, or a ramp problem. The ask should stay at this size: a 15-minute look at one metric, not a platform tour. Delete trigger: Telling them how to sell. They've heard it. a stage in the funnel that's leaking, a slow follow-up SLA, or a ramp problem
How Consulting changes the note
Consulting buyers are partners and delivery leads selling expertise while protecting utilization. They've written prettier decks than yours. Compete on diagnosis and next step, not on adjectives. A credible proof point in this vertical sounds like: moved three stalled proposals to signature by isolating the real blocker in one email. Watch the language. Words that land here include SOW, utilization, workstream, sponsor, retainer, change request. A thread that ignores proposals that stall in procurement and relationships that go quiet between projects reads like every other vendor bump. A small diagnostic can start in a week. A transformation waits on a sponsor.
How should I customize this template before I send it?
- Replace the pain line with a boutique firm whose last project ended well and then nobody asked for the next phase.
- Keep the tone crisp and commercial.
- Keep the ask to one person or one tightly defined role.
- Time it for Same day. Same day, within a few hours. Next morning is the backup, not the plan.
- Don't call yourself a thought leader. Let the email be useful instead.
What mistakes should I avoid with this after meeting note?
- Asking 'who do you know?' is lazy and gets no names.
- Don't send a pitch deck they didn't ask for as a 'recap.'
- Don't call yourself a thought leader. Let the email be useful instead.
- Telling them how to sell. They've heard it.
How does this after meeting scenario compare?
| Dimension | For this template |
|---|---|
| Best send window | Same day |
| Ideal length | 70 to 90 words. Lead with the outcome. |
| Primary ask | a 15-minute look at one metric, not a platform tour |
| Industry metric to cite | utilization, proposal win rate, and time to SOW |
| Tone | Crisp and commercial. They can handle a direct ask. |
| Unlike after demo | A meeting might have been intro-only. Don't write a product recap they didn't see. |
| Unlike thank you | Gratitude can live in line one. The rest should be operational. |
What should I copy and send?
Copy-ready template
Subject
Could you intro me to [role] at [Company]?
Body
Hi [First Name], This is an ask. I tried to make it easy to say no. In Consulting, that usually shows up as proposals that stall in procurement and relationships that go quiet between projects. If now is a bad time, don't spend political capital on this. List what you heard, what you promised, and what you need from them, in that order. Comfortable making that intro, or should I find another path? Best, [Your Name] [Your Title] [Your Company]
Questions people ask before they hit send
Decisions, owners, dates, and anything you promised to send. Keep opinions out unless they asked for a recommendation. A forwardable recap does more for the deal than a paragraph about how 'great it was to connect.' Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.
Related templates
Want a custom draft instead? Try the email generator.