How many times should I follow up with a Sales VP (replied then went silent)?

Don't follow a cold email the next morning. Give it 4 business days. Give it a week unless they named a date. Then write on that date, not the day after you got impatient. After that, send a breakup note and archive it. A sales VP who wants it will answer a clean close more often than a fifth bump.

Should I mention a mutual connection in a cold email?

Only if the connection would be comfortable with it. Name-dropping someone who barely knows you can backfire. If you do mention them, say exactly how you know them in one clause and move on. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Why do prospects reply once and then disappear?

Often they needed to check with someone, a fire started, or your last ask was bigger than they meant to take on. A good follow-up shrinks the next step and references what they already said so they don't have to reload context.

Is it okay to send this cold email on LinkedIn instead of email?

Yes if this sales VP is actually active there and the thread isn't about long attachments. Keep the LinkedIn version even shorter. Don't paste the full email. One context line and one question is plenty. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

What should I never say in a SaaS cold email?

Don't promise 'AI that runs itself.' They hear that weekly. Telling them how to sell. They've heard it. Don't forward the whole thread with 'friendly bump' and nothing else. Those three mistakes show up constantly in SaaS inboxes and they all read as "this was templated."

SaaS · Sales VP · Replied Then Silent

Cold Email Template for SaaS Sales VP: Replied Then Silent

Use this cold email template when you're emailing a Sales VP in SaaS (replied then went silent). They engaged once, then the thread died. That's usually calendar, a missing internal yes, or a fear of opening a project. Keep the note aligned with Crisp and commercial. They can handle a direct ask.

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 cold email work for a SaaS Sales VP?

Lead with an observed trigger, not a compliment about their About page.
Speaks to time-to-value that slips past the first 14 days and quietly becomes churn instead of a generic "value prop."
Fits how a sales VP actually reads: 70 to 90 words. Lead with the outcome.
Quote their last sentence and answer it. People reply to their own unfinished thought.
Show you understand their bottleneck in their language.

When should I send this to a SaaS Sales VP?

Don't follow a cold email the next morning. Give it 4 business days. Give it a week unless they named a date. Then write on that date, not the day after you got impatient. For this combo, treat "5-7 days, or the date they named" as the default, then adjust around evaluation can close in two weeks for a point tool or drag a quarter when security is involved. 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 SaaS 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. If your note would embarrass them in a team channel, rewrite it.

How SaaS changes the note

SaaS buyers are software teams juggling seat growth, churn, and a stack that's already too loud. They've been burned by tools that demo well and then die in implementation. Lead with integration and time-to-value, not feature lists. A credible proof point in this vertical sounds like: cut onboarding from 19 days to 6 for a 40-person customer success team. Watch the language. Words that land here include activation, seats, SSO, sandbox, expansion, churn. Words that work: activation, seats, SSO, sandbox, expansion, churn. A thread that ignores time-to-value that slips past the first 14 days and quietly becomes churn reads like every other vendor bump.

How should I customize this template before I send it?

Replace the pain line with a B2B SaaS company adding usage-based billing on top of a messy seat model.
Keep the tone crisp and commercial.
Write the subject after the body so it matches the actual hook.
Time it for 5-7 days, or the date they named. Give it a week unless they named a date. Then write on that date, not the day after you got impatient.
Don't promise 'AI that runs itself.' They hear that weekly.

What mistakes should I avoid with this replied then silent note?

Opening with your company story is how cold email dies.
Don't forward the whole thread with 'friendly bump' and nothing else.
Don't promise 'AI that runs itself.' They hear that weekly.
Telling them how to sell. They've heard it.

How does this replied then silent scenario compare?

Dimension	For this template
Best send window	5-7 days, or the date they named
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	net revenue retention, time-to-first-value, and expansion inside existing accounts
Tone	Crisp and commercial. They can handle a direct ask.
Unlike no response	They already spent social energy. Treat them like a conversation, not a lead.
Unlike after proposal	You may not have a document on the table yet. Don't invent a buying process.

What should I copy and send?

Copy-ready template

Subject

SaaS note on time-to-value that slips past the first 14 days

Body

Hi [First Name],

I'll be direct: I help [role peers] cut [pain] without adding another bloated tool.

The version of this that matters for software teams juggling seat growth, churn, and a stack that's already too loud is cut onboarding from 19 days to 6 for a 40-person customer success team. Teams like [peer example] use [Your Product] to cut onboarding from 19 days to 6 for a 40-person customer success team in [timeframe]. The fit depends on whether time-to-value that slips past the first 14 days and quietly becomes churn is actually costing you net revenue retention.

Quote their last sentence and answer it. People reply to their own unfinished thought.

Wrong person? Point me to whoever owns [pain].

Best,
[Your Name]
[Your Title]
[Your Company]

Questions people ask before they hit send

Name the situation and the business object, not your excitement. Something like "SaaS note on time-to-value that slips past the first 14 days" outperforms "Just checking in" because a sales VP can decide from the preview text whether it's worth opening. Keep it under 50 characters when you can.

Related templates

Want a custom draft instead? Try the email generator.