Should I lower the price in the follow-up?

Not as an opening move. Ask what's blocking. If budget is the issue, trim scope or phase the work. Discounting before you know the objection trains them to wait you out. Procurement also has to explain the number. Don't make that harder with a random cut.

What if security is the only stall?

Send the packet in their format. Ask which control is unanswered. Offer a call with your security owner, not a sales recap. Don't tell them the questionnaire is optional. That's how you get a no from people whose job is to say no to that sentence.

Can I email the business champion and procurement together?

If that's the process they set. Blind CC'ing a VP to hurry a PO can freeze you. Ask the champion how they want status handled. Then do that. Procurement replies to completeness, not personality, and they remember theater. Follow the path they set even when it feels slow.

How do I follow up if they already have a competing tool?

Ask which criteria are still open. Offer a one-page comparison on the criteria they named, not the ones you wish they had. Don't dunk on the incumbent. They chose it once. Help them decide, don't insult last year's decision. A dunk on the incumbent is a dunk on the person who signed it.

What should I never say in a SaaS procurement follow-up?

Don't promise the tool runs itself. Don't invent logos. Don't treat security as a hoop. Don't bury price if they asked for commercial clarity. And don't send a sixth bump that is identical to the first. Change the question or close the file.

SaaS · Procurement Officer · After Proposal

Proposal Follow-Up Email for a SaaS Procurement Officer

A SaaS proposal follow-up to procurement isolates the stuck layer: security, MSA, price, or a missing owner. 'Any thoughts on the proposal?' invites silence. They've been burned by tools that demo well and die in implementation. Lead with the questionnaire and the paper, not the feature list. Completeness is how you unstick a yes that the business owner already wanted.

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

Copy-ready template

Subject

[Company] proposal: security pack or MSA still open?

Body

Hello [First Name],

I sent option [A/B] on [date] with the security pack and MSA redline in [their format]. Checking whether the file is waiting on infosec, legal paper, commercial terms, or a business owner who hasn't signed internally.

I can split implementation into [core] now and [SSO / sandbox] later if that's the cleaner PO. Tell me which document to relabel and I'll send it today.

[Your Name]

Why this proposal follow-up works

You diagnose instead of nagging.
You speak procurement's language: packs, redlines, PO.
A phased start gives budget a non-binary path.
The subject is searchable in a vendor inbox.
No AI slogans, which this buyer hears weekly.

When should I send this to a SaaS Procurement Officer?

On the review date you set. If you didn't set one, five business days, longer if they said security takes three weeks. Don't bump during their quarter close unless they asked. After a complete packet, one status note, then a clean close.

What this Procurement Officer actually cares about

Procurement reads for terms, risk, and process. Charm without paperwork is a delay. Formal enough, never oily. Include commercial facts early. A renewal, a duplicate vendor, or a missing document that blocks a PO is the hook. Ask for the next document or a date, not a relationship meeting. Don't try to go around them to the business owner in a way that's obvious.

How SaaS changes the note

SaaS evaluation can close in two weeks for a point tool or drag a quarter when security is involved. Activation, seats, SSO, sandbox, expansion, and churn are the words. They've been burned. Time-to-value and integration beat feature lists. Don't promise AI that runs itself. A failed implementation or a questionnaire stall is a real trigger. Your follow-up should make the file easier, not louder.

Customization tips

Use their exact product names from the proposal.
Don't resend the whole deck. Link the one page that matters.
If they use a vendor portal, reference the ticket ID.
Ask for redline format now if legal is involved.
Set a decision date in the original proposal so this email has a hook.

Common mistakes

Asking 'any thoughts?' after a 12-page proposal.
Dropping price in the first bump.
CC'ing the champion to pressure procurement.
Claiming SOC 2 you don't have.

How this scenario compares

Dimension	For this template
Best send window	Agreed review date, or 5 business days
Ideal length	Under 100 words plus a clarifying question
Primary ask	Which layer is stuck
Unlike a CTO follow-up	Paper and policy first, architecture second.
Unlike legal procurement	Security questionnaires and MSA, not conflicts letters.

Questions people ask before they hit send

On the date you both named. If you didn't name one, five business days is fair, longer if they warned you about security review. Enterprise legal can take longer. Ask what their path looks like instead of guessing. Guessing looks like you don't buy software for a living.

Related templates

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