Should a sales VP follow-up mention the sandbox?

Yes if that is a plausible reason they went quiet. Plenty of SaaS evaluations die because legal never opened the trial workspace. Offer a one-page on seats and activation instead of another tour. Don't claim your sandbox is live if it isn't. They will check with RevOps.

Is LinkedIn better than email for a silent SaaS sales VP?

Only if they actually post there and your email didn't bounce. Keep the LinkedIn note to two sentences and don't paste the pitch. A short should I send the seat map or drop this is enough. If they wanted a long thread, they would have hit reply.

What should I never put in a follow-up to a SaaS sales VP?

Don't invent customer logos. Don't describe the product as magic. Don't ask them to pick your brain. Don't attach a 19-page deck. Don't imply their current stack is amateur. You can name a class of leak without dunking on the tools they already own.

Should I send a third follow-up if the sales VP stays silent?

Send a breakup, not a third pitch. Ask if you should archive it until SKO or quarter planning. A surprising number of VPs reply because it costs them one word: yes or later. If they still don't answer, stop. Your reputation in that sales org matters more than this logo.

How commercial does the follow-up itself need to be?

Commercial enough to name a forecast leak, not so salesy it belongs in a webinar. One defensible metric is plenty: unused seats, ramp miss, or CS queue depth. Save the deck for after they invite you in. Curiosity isn't a pipeline presentation.

Last updated 2026-09-02 · Reviewed by Sales Email Template editors

SaaS · Sales VP · No Response

Follow-Up Email Template for a SaaS Sales VP After No Response

A follow-up to a SaaS sales VP who never replied is a forecast note, not a second origin story. Silence usually means SKO ate the week, a sandbox never launched, or your first email sounded like a methodology pitch. Name one seat leak. Offer a hold. Stop before you become another vendor in the mute list.

Copy-ready template

Subject

Unused seats at [Company Name], or file this?

Body

Hi [First Name],

I'll skip the methodology speech. Last week I flagged how [Your Product] cuts the unused-seat stall that shows up in [Company Name]'s forecast reviews. Quiet at VP often means a sandbox legal hasn't opened or CS is still sitting on activation numbers.

If I send a 1-page map of dark seats versus AE headcount, would you glance? If this isn't a this-quarter item, reply hold and I'll stop.

[Your Name]
[Your Title]

Why this follow-up works

The subject is a forecast metric they already own, not a category pitch.
You treat silence as sandbox or CS queue, which is how this desk stalls.
The ask is a page, not a 30-minute vision call.
Hold language makes a no cheaper than ghosting through another SKO.
No feature list, so it doesn't look like sequence step two.

When should I send this to a SaaS Sales VP?

Wait 4 business days after the first note. Do not bump the next morning. If they posted SKO, a quarter close, or a board week, your second email is noise they will remember at vendor review. After the second silence, send a close-the-file note that asks whether to archive until the next SKO. Three touches is the cap unless they named a freeze. Tuesday and Wednesday after 10:00 local beats Monday at 07:30 and Friday at 16:00. If RevOps parked new vendors until after a billing cutover, believe it and leave a reopen date. Weekly drips through a close week get your domain a filter.

What this Sales VP actually cares about

A SaaS sales VP reads on a phone between a deal review and a CRO ping. The first two lines have to name a number they already report. Origin-story mail gets filtered. They will spend eight seconds deciding if you will waste a pipeline meeting. Show that you understand seats, ramp, or CS handoff, then stop. Do not CC the CRO to apply heat. That move ends trust even if it books a slot. Do not paste a 14-row feature matrix. Their credibility with AEs is the real product. Protect it. Then stop. A hold is a gift in this seat. They can forward a 70-word note. They cannot forward a sermon.

How SaaS changes the note

SaaS sales VPs live inside unused seats and a CS queue that never quite matches the forecast they just promised. Seat growth looks fine until activation is a cliff and finance asks harder questions in the same pipeline review. Your follow-up has to sound like you have sat in that room, not like you watched a sales kickoff keynote. Time-to-first-value, dark seats, and who still owns onboarding after the AE leaves are the language. If you cannot name a forecast leak in one sentence, wait until you can. Quiet after a first email often means they forwarded you to RevOps or CS and did not want to babysit the thread. Write as if that already happened. Tools that demoed well and died in week three trained this inbox to flinch. A useful bump names the metric that will show up again at the next QBR and the date that already owns the calendar. Vague enablement talk is background noise. Ramp and logo churn survive a skeptical buyer.

Customization tips

Put their real seat count or ramp number in the note if you have a public signal.
Swap seats for sandbox or CS queue if that is the leak you can prove.
Don't attach a deck. Link the page after they reply.
Send Tuesday or Wednesday after 10:00 in their city, never Monday forecast morning.
If a RevOps lead already talked to you, name them in line two.

Common mistakes

Opening with a circling-back line and the same paragraph as email one.
Promising AI that runs the whole sales org. They hear that weekly.
Sending a 30-minute Calendly as the entire follow-up.
Citing you noticed they viewed the site like a camera in the ceiling.

How this scenario compares

Dimension	For this template
Best send window	4 business days after email one, never forecast morning
Ideal length	Under 75 words, one question
Primary ask	Permission to send a 1-page seat map
Unlike a CEO follow-up	Talk seats and ramp, not board NRR
Unlike a clicked-no-reply note	You have zero signal, so don't invent a click

Questions people ask before they hit send

Four business days is the default. Give it a full week if you emailed during SKO, a quarter close, or a board week they posted about. Faster follow-ups read as anxiety. VPs already have a queue. Land once more with a smaller ask, not a restack of email one.

Related templates

Want a custom draft instead? Try the email generator. Word count on this page: 1150.