Skip to main content

LinkedIn Message to VP of Sales Template: 7 That Land

These templates are for founders and SDRs writing to VP Sales and CRO buyers. The principle behind every one of them: name a pain the sales leader personally owns this quarter, such as pipeline coverage, quota attainment, or rep productivity, and ask for nothing bigger than a reply. Below is each LinkedIn message to VP of Sales template we'd stand behind, from the 300-character connection note through the final follow-up, with notes on when to use each.

Why sales leaders ignore almost everything

A VP of Sales knows how outbound works because they run it. They have written your template, or coached a rep through it, so they can spot "Hi {first_name}, I came across your profile" from the notification preview and archive it without opening.

Three things set a message apart for this persona.

First, specificity they can verify. "Your team is growing" is noise. "You have six open AE roles" is a fact they recognise, and it tells them you looked.

Second, a pain framed the way they would frame it. Sales leaders talk in coverage, attainment, ramp time, and forecast accuracy. Vague words like "growth" or "efficiency" sound like a vendor.

Third, an ask that costs them nothing. A yes/no question or "want me to send it over?" gets answered. "Do you have 15 minutes Thursday?" gets ignored, because a calendar slot is the scarcest thing they own.

Connection notes: the first 300 characters

LinkedIn cuts connection notes off at 300 characters, and merge tags expand. Draft to roughly 250 so a long company name doesn't break the note. If you're unsure whether to add a note at all, connection request with or without a note covers that trade-off. For VP-level prospects, the answer is almost always to include one.

1. The hiring-wave note (quota attainment)

{first_name}, saw {company} has {open_roles} AE roles open. The quarter after a hiring push is usually where attainment dips, because ramping reps eat manager time. That's the problem I work on. Worth connecting?

This works because open roles are public, verifiable, and directly tied to the number they'll be judged on. Only use it when the job posts are real and recent. Check the careers page first.

2. The new-number note (pipeline coverage)

{first_name}, congrats on the {funding_round}. New capital usually means a bigger target for sales next year, and pipeline coverage tends to lag the target by a quarter. Would like to connect and compare notes on how {company} is building pipeline.

Funding, a new market, or a new product launch all mean a raised quota. The note shows you understand the downstream consequence. That is a stronger signal than the congratulations.

3. The content note

{first_name}, your post on {topic} stuck with me, especially the point about {specific_point}. Plenty of sales leaders think it, few say it publicly. Would be good to connect.

The note has no pain and no pitch, and that's on purpose. Sales leaders who post are fishing for exactly this kind of signal that someone read the post. Save it for prospects who post at least monthly. The longer play is in outreach openers referencing their content.

First messages after they accept

Accepting a request is not interest. It costs them one click. Your first message still has to earn the reply, so keep it short and diagnostic. Each LinkedIn message to VP of Sales template in this section asks a question before it offers anything. For more variations, see first message after LinkedIn connection templates.

4. The non-selling-time question (team productivity)

Thanks for connecting, {first_name}. One question, no pitch attached: how much of an AE's week at {company} goes to work that isn't selling? CRM updates, list building, chasing internal approvals. I ask because {your_company} exists to give that time back, and I'd rather know if it's a non-issue for your team before saying more.

Every VP has an opinion on this, so it's easy to answer. The "before saying more" line tells them a pitch is coming only if they want one, which lowers their guard.

5. The slipped-deal question (forecast accuracy)

{first_name}, quick one. When deals slip at {company}, is it usually late in the cycle, legal and procurement, or early, no real champion? We built {product} around the early version of that problem. If your forecast breaks somewhere else, I'll leave it there.

A forced-choice question beats an open one with busy readers. They can answer with "early" and you have a conversation. The exit line is what sets this apart: offering to stop is rare in cold outreach, and senior buyers notice.

Follow-ups and the CRO variant

A CRO carries a board-level number. That makes their pain wider than a VP's, and your offer should be wider too: a teardown, a benchmark you can actually share, a short write-up. Meeting requests can wait.

6. The board-pressure message (CRO)

{first_name}, most boards are asking CROs for the same thing this year: more revenue per rep, not more reps. If that's on your plate at {company}, I put together a short teardown of how {similar_company} restructured territory and pipeline ownership to get there. Want me to send it over?

"Want me to send it over?" is about the lowest-friction CTA there is, because a yes commits them to nothing but reading. Make sure the teardown exists before you send this, and make it good. It becomes your pitch.

7. The closing-the-loop follow-up

{first_name}, closing the loop on my note about {pain_topic}. If the timing's wrong, a one-word "later" is genuinely useful, and I'll check back next quarter.

Send this once, 5-7 days after the last message, and then stop. Asking for a one-word reply turns silence into a small decision they can make in two seconds. More variations live in LinkedIn breakup message templates.

Which template for which situation

Scenario Template Goal
Company has several open AE roles 1. Hiring-wave note Connect on a quota attainment pain
Recent funding or expansion 2. New-number note Connect on a pipeline coverage pain
Prospect posts regularly 3. Content note Connect with zero pitch pressure
Accepted, no context yet 4. Non-selling-time question Get a reply about rep productivity
Accepted, you sell into deal execution 5. Slipped-deal question Get a one-word diagnostic answer
Persona is CRO, not VP 6. Board-pressure message Get a "yes, send it"
No reply after the first message 7. Closing-the-loop Turn silence into a decision

A typical sequence pairs one connection note (1, 2, or 3) with one first message (4, 5, or 6) and the follow-up (7). Three touches is enough for this persona. A fourth reads as persistence from someone who isn't listening.

Running the sequence without burning the account

Sending these by hand works if you're writing to ten sales leaders a month. Past that, the follow-up timing slips, and a late follow-up is a worse follow-up.

In Ampliflow, the sequence above maps onto the drag-and-drop workflow builder. Send template 1 as the connection request. Add an If/Else branch on acceptance, a delay, then template 4. Add another delay, then template 7. Auto-pause on reply matters here: when a VP answers "early" to template 5, the sequence stops, so they never get a canned follow-up on top of a real conversation. The replies land in the unified inbox.

To build the list, import from LinkedIn search or Sales Navigator, filtered by title and headcount. Then A/B test template 1 against template 2 on the same segment and let the funnel analytics show which pain draws more acceptances from your market.

The safety side is where the architecture earns its keep. Campaigns run in the cloud via the Unipile API, not in your browser, so you can close the laptop. Connecting the account takes one click with the Chrome extension. Actions follow human-like daily limits with randomised timing jitter, only inside the working hours you configure. Real-time account safety scoring with anomaly detection flags unusual patterns before LinkedIn does.

The limits themselves: 25 connection requests per account per day on every paid plan. Messages run 25 a day on Standard, 50 on Pro, and 80 on Team. A list of 300 VPs takes a couple of working weeks to reach. For a senior persona, that pace is a feature. You get time to read replies and adjust the copy mid-campaign.

Where Ampliflow fits, and where it doesn't

If you only need a handful of messages a week, cheaper tools are cheaper. Octopus CRM starts at $9.99/mo, Dux-Soup at $14.99/mo, and Linked Helper at $15/mo, all below Ampliflow Standard's regular $39/mo. Ampliflow's case is cloud execution and safety scoring, not the lowest sticker price.

Against the tools that also sell automated sequences, the gap runs the other way. Pro is $39/mo for founding members, against $79/mo for Dripify or HeyReach and $99/mo for Expandi. Next to Dripify, that saves $40 a month, or $480 a year. Founding prices apply to the first 100 paying customers and stay locked for life, and every plan starts with a 7-day free trial. Full details are on the pricing page.

Our recommendation: write the copy by hand first. Send templates 1, 4, and 7 manually to twenty prospects and see which pain gets answers. Then automate only the version that worked.

Frequently asked questions

Lead with one specific pain they own this quarter, such as pipeline coverage, ramping reps, or forecast slippage, and tie it to something visible about their company. End with a question they can answer in one line. Leave out your product name, any meeting request, and any calendar link.
LinkedIn caps connection notes at 300 characters, and your merge tags count toward that once they expand. Draft around 220-260 characters so a long company name or job title still fits. One observation and one question is enough.
No. A CRO sees pitches all day and can spot the shape of one from the preview line. Ask a diagnostic question or offer something useful, and pitch only after they reply and confirm the problem exists for them.
On Ampliflow, every paid plan allows 25 connection requests per LinkedIn account per day. Messages are capped at 25 a day on Standard, 50 on Pro, and 80 on Team. For a senior persona like VP Sales, the connection request limit is the real constraint, and that is fine, because a tight list beats a big one.