Resources

Solo sales workflows

Proposal follow-up sequence (templates + timing for solo B2B sales)

A proposal follow-up sequence: what to send, when to send it, and templates that help solo B2B sellers move deals forward.

Apr 7, 20269 min read

Why proposals stall (and what to do about it)

Proposals do not usually stall because the buyer forgot you exist. They stall because the next step is unclear, the decision is shared, or the buyer is not ready to say no.

A good follow-up sequence does two things: it makes the next step easy, and it gives the buyer a graceful way to close the loop.

Timing: a simple 4-touch proposal follow-up schedule

Use this as a baseline. If the deal is urgent, compress it. If it is enterprise or committee-driven, expand it.

  1. 1
    Touch 1 (2 business days later): quick nudge + one question.
  2. 2
    Touch 2 (5 business days later): restate outcome + propose a call slot.
  3. 3
    Touch 3 (10 business days later): surface objections + offer options.
  4. 4
    Touch 4 (14-21 days later): close the loop ("should I archive this?").

Your goal is not to send more emails. Your goal is to reach clarity: yes, no, or not now with a date.

Copy-paste templates (4 touches)

Touch 1: Quick nudge

Subject: Re: proposal

Hi {{first_name}} - quick check-in on the proposal I sent on {{date}}.

Is the next step a quick call to walk through it, or do you want me to adjust anything before you decide?

Thanks,
{{your_name}}

Touch 2: Outcome + call option

Subject: Re: proposal

Hi {{first_name}} - wanted to make this easy.

If the goal is {{outcome}}, the proposal is a good fit. If it is not the right timing, totally fair.

If helpful, I can walk through it in 10 minutes. Does {{option_1}} or {{option_2}} work?

Best,
{{your_name}}

Touch 3: Objections + options

Subject: Re: proposal

Hi {{first_name}} - checking in again.

Most decisions at this stage come down to one of these:
1) scope is not quite right
2) timing/budget
3) internal alignment

Which one is the blocker (if any)? I can adjust the proposal or suggest a smaller first step.

Thanks,
{{your_name}}

Touch 4: Last touch (close the loop)

Subject: Re: proposal

Hi {{first_name}} - last note from me on this.

Should I close this out for now, or is there a better date to circle back?

Either way is fine - I just do not want it to hang in limbo.

Best,
{{your_name}}

How to use email tracking without over-trusting it

Tracking can be a useful signal, but it is not a truth machine. Some recipients block images or use privacy tools that make opens unreliable.

  • Use tracking as a hint for timing, not as proof of intent.
  • If a buyer clicks, follow up with a clear next-step question (do not mention tracking).
  • If tracking is quiet, follow your schedule anyway. The sequence is the system.

Common mistakes

  • Following up with "Any updates?" without an easy next step.
  • Writing long emails that re-sell the entire proposal every time.
  • No close-the-loop email, so the deal stays mentally open forever.
  • Not saving the sequence, so every proposal follow-up is improvised.

Weekly review: keep proposal follow-ups from slipping

In your weekly CRM review, every proposal should have one of two things: a follow-up date, or a decision date.

If you cannot name the decision trigger, your next step is to ask for it in one sentence.

Want this workflow inside Gmail?

Donna CRM runs inside Gmail as a Chrome extension. Use these workflows with real contact context, pipeline stages, and follow-up tasks - without leaving your inbox.

FAQs

Common questions about following up after sending a proposal.

How many follow-ups is too many?
If every email is adding pressure, it is too many. If each email makes a decision easier (clarifies next step, offers options, or closes the loop), 3-5 touches over a few weeks is normal in B2B.
Should I follow up by email or call?
Default to email if the buyer started the relationship over email. Offer a short call as an option when complexity is high or the deal is stalling.
What if they keep saying "next week"?
Ask for a specific date and the decision trigger. For example: "What needs to happen internally before you can decide, and when should we reconnect?"

Related reading

Keep exploring: these pages go deeper on the feature set and the core Gmail CRM workflow.