How many times should I follow up with a Sales VP (after networking)?

Wait until the review window you agreed on. If none was set, five business days. Within 24 to 48 hours while they still remember your face or handle. 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 lower the price in the follow-up?

Not as an opening move. Ask what's blocking the decision first. If budget is the issue, trim scope or phase the work. Discounting before you know the objection trains them to wait you out. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

How soon should I follow up after a networking event?

Within two days. After that you're a vague name from a badge. Mention where you met and the topic, send anything you promised, and keep the ask optional. If they wanted a pitch, they would have asked. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Is it okay to send this proposal follow-up 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 proposal follow-up?

Don't promise 'AI that runs itself.' They hear that weekly. Telling them how to sell. They've heard it. Don't dump a calendar link as the first follow-up unless they asked. Those three mistakes show up constantly in SaaS inboxes and they all read as "this was templated."

SaaS · Sales VP · After Networking

Proposal Follow-Up for SaaS Sales VP: After Networking

A proposal follow-up email for a SaaS Sales VP (after networking) is a short message that reopens the thread without making them do extra work. A proposal follow-up email helps a stalled decision move without pretending the document didn't land. In this setting, that means speaking to time-to-value that slips past the first 14 days and quietly becomes churn in

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 proposal follow-up work for a SaaS Sales VP?

Name the decision owner out loud.
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.
Remind them of the exact topic you both lingered on.
Diagnose the stall instead of asking if they 'had a chance to review.'

When should I send this to a SaaS Sales VP?

Wait until the review window you agreed on. If none was set, five business days. Within 24 to 48 hours while they still remember your face or handle. For this combo, treat "1-2 days" 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. They protect quota, forecast credibility, and rep time, so keep the ask at "a 15-minute look at one metric, not a platform tour."

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. Evaluation can close in two weeks for a point tool or drag a quarter when security is involved. Words that work: activation, seats, SSO, sandbox, expansion, churn.

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.
Don't resend the whole deck. Link the one page that matters.
Time it for 1-2 days. Within 24 to 48 hours while they still remember your face or handle.
Don't promise 'AI that runs itself.' They hear that weekly.

What mistakes should I avoid with this after networking note?

Asking 'any thoughts?' after a 12-page proposal invites silence.
Don't dump a calendar link as the first follow-up unless they asked.
Don't promise 'AI that runs itself.' They hear that weekly.
Telling them how to sell. They've heard it.

How does this after networking scenario compare?

Dimension	For this template
Best send window	1-2 days
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 cold email	You have a shared moment. Use it. Writing like a stranger wastes the introduction.
Unlike introduction	You already met. Don't re-introduce your whole bio.

What should I copy and send?

Copy-ready template

Subject

Happy to trim [option] if budget is the blocker

Body

Hi [First Name],

Before this sits in a pile, I can cut [option] or split the rollout.

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. If [competitor path] is still in play, I can send a one-page comparison on [criteria they named].

Remind them of the exact topic you both lingered on.

Which piece is actually blocking a yes or no?

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 "Happy to trim [option] if budget is the blocker" 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.