Proposal & Quote Follow-Up Emails: 15 Templates, Subject Lines & a Day-by-Day Cadence (2026)

Key takeaways:

• Follow up on a schedule you set on day 0, not when you get nervous. A practical default: confirm on day 0, check in on day 2, add value on day 5, ask about timing on day 10, close the loop on day 21 (business days). Compress or stretch it to the buyer's stated decision date.
• Every follow-up needs a reason to exist: a question answered, a new resource, a smaller ask, or a deadline. "Just checking in" is not a reason.
• Subject lines should say what the email is about ("[Company] proposal: 2 questions from your team") rather than sound urgent or cute.
• Ask for one small, specific thing per email. "Is Thursday at 2pm ET or Friday morning better for 15 minutes?" beats "Let me know your thoughts."
• If you use view tracking, be upfront about it and never quote private viewing details back to the buyer ("I saw you spent 4 minutes on page 6").
• Below are 15 copy-paste templates, from the day-0 confirmation to the "we went with someone else" reply.

---

Should you follow up after sending a proposal?

Yes. Silence after a proposal usually means the buyer is busy, waiting on someone else, or unsure what to do next—not that they said no. A follow-up that makes the next step easy is a service to the buyer, not pressure.

The only large public dataset on follow-ups that we could verify is about outreach emails rather than proposals, so treat it as directional: in a 2019 analysis of 12 million outreach emails by Backlinko and Pitchbox, only 8.5% of outreach emails received a response, and a single follow-up message can lead to 65.8% more replies. Sending three or more messages produced the best overall response rate. A proposal is a warmer situation than a cold outreach email—the buyer asked for it—so the case for following up is, if anything, stronger.

What changes after a proposal is who you are waiting on. In Forrester's State of Business Buying 2024, an average of 13 people were involved in a B2B buying decision, and 89% of purchases involved two or more departments. Your contact may like the proposal and still be stuck collecting input from finance, IT, or legal. Many of the templates below are designed to help your contact move the proposal internally, not just to get a reply from them.

---

When to follow up after sending a proposal: a day-by-day cadence

Send a short confirmation the day you deliver the proposal, then follow up about 2, 5, 10, and 21 business days later—unless the buyer gave you a decision date, in which case anchor your follow-ups to that date instead. This is a practical default we recommend, not a research-backed rule; adjust it to your deal size and buying cycle.

A few rules make the cadence work:

1. Agree on the next step before you hit send. The best follow-up is scheduled on the call where you promised the proposal: "I'll send it Tuesday—can we hold 20 minutes Friday to walk through it?" If you have a review meeting booked, most of the cadence becomes unnecessary.
2. Anchor to their date, not yours. If the buyer said "we decide at the end of the month," a day-2 check-in is fine, but your main follow-up belongs a week before that date.
3. Quotes with an expiry date get one extra email. Send a reminder a few business days before the price or availability expires (template #11). Only set an expiry you will actually enforce.
4. Switch channels after two unanswered emails. A short call or a LinkedIn message often reaches someone whose inbox has buried your thread.
5. Stop after the breakup email. Move the contact to a long-term nurture and come back only with a real reason (template #13).

For quick transactional quotes—say, a one-off freelance job or a small reorder—compress the cadence to day 0, 2, 5, and 10. For enterprise proposals that go through procurement, stretch it and lean on a shared mutual action plan so both sides can see what happens next.

---

Subject lines for proposal follow-up emails

The best follow-up subject lines tell the reader exactly what's inside and who it's from, in plain words. Reply in the original thread when you can—"Re: [Company] proposal" keeps the context attached—and write a new subject only when you're adding something new.

Four formulas cover most situations:

• [Company] + document + purpose: "[Company] proposal: next steps"
• Specific question: "Quick question on the [Project] timeline"
• New value: "Cost breakdown your finance team asked about"
• Clear deadline: "Your quote for [Project] is valid until [Date]"

15 subject line examples

These are standalone examples to mix and match by situation—they aren't numbered to match the 15 templates below one-to-one.

1.  [Company] proposal – sent, plus one next step
2.  Re: [Project] proposal – any questions so far?
3.  2 questions your team might have about the [Project] proposal
4.  One-page summary of the [Project] proposal for your team
5.  Case study: similar rollout at a [Industry] company
6.  Re: your question about [Topic]
7.  [Project] quote – broken down by phase
8.  Pricing options for [Project] (3 tiers)
9.  Summary to share with [Stakeholder role]
10. What does your decision process look like for [Project]?
11. Recap and next steps from today's call
12. Your [Project] quote is valid until [Date]
13. Should I close the file on [Project]?
14. Checking back on [Project] – anything changed on your end?
15. Thanks for letting us know – one quick question

Subject lines to skip: "Just following up," "Checking in," "URGENT," "Did you get my email?," "Last chance!!!," and fake reply or forward prefixes ("RE:" on a message that isn't a reply). They either say nothing or erode trust.

---

15 proposal follow-up email templates (copy and paste)

Each template below is short on purpose: one reason for writing, one ask. Replace everything in [brackets], and cut any line that doesn't fit your situation. All times use a single time zone for clarity—name the buyer's time zone when you're scheduling across regions.

1. Proposal sent confirmation (day 0)

Send this with the proposal or right after it. It confirms delivery, highlights what to look at first, and restates the next step you agreed on.

Subject: [Company] proposal – sent, plus one next step

Hi [First name],

As promised, here's the proposal for [Project]: [link]

If you only have five minutes, start with page [X] (scope and timeline)
and page [Y] (investment). Everything else is supporting detail.

A quick recap of what we agreed:
- Goal: [outcome in the buyer's words]
- Proposed start: [Date]
- Next step: walk through it together on [Day, Date] at [Time]

If anything in the proposal doesn't match what you had in mind,
tell me before the call and I'll adjust it.

Best,
[Your name]

2. First check-in (day 2)

The goal is to catch questions early, before they turn into silent objections. Offer a specific, low-effort way to respond.

Subject: Re: [Project] proposal – any questions so far?

Hi [First name],

Checking whether the proposal raised any questions on your side.

In similar projects, the questions that usually come up first are:
1. How the [phase/milestone] works if [common constraint]
2. What we need from your team, and how much of their time
3. How the payment schedule lines up with delivery

Happy to answer any of these by email, or in 15 minutes by phone.
Would [Day] at [Time] or [Day] at [Time] work?

Best,
[Your name]

3. Value-add follow-up (day 5)

Bring something new that helps your contact sell the proposal internally: a relevant case study, a one-page summary, or an answer to a question they haven't asked yet.

Subject: One-page summary of the [Project] proposal for your team

Hi [First name],

Proposals tend to get forwarded, and [N] pages is a lot to ask of
someone who wasn't on our calls. So I put the essentials on one page:
[link]

It covers the problem, the proposed approach, timeline, and cost,
in that order. Feel free to forward it as is or edit it.

If it would help, I can also join a short call with [Stakeholder role]
to answer their questions directly.

Best,
[Your name]

4. Answering an objection

Use this when the buyer raised a concern (price, timing, risk, fit). Restate the concern accurately, answer it with specifics, and offer an option—don't argue. For more on this, see our objection handling guide.

Subject: Re: your question about [Topic]

Hi [First name],

Thanks for flagging the concern about [objection, in their words].
That's a fair point, and I'd rather address it now than have it sit.

Here's how we'd handle it:
- [Specific answer #1 – e.g., phased rollout so you can stop after phase 1]
- [Specific answer #2 – e.g., reference from a customer with the same setup]

If that still doesn't fully solve it, one option is [alternative:
smaller scope / different start date / pilot]. I've outlined what
that would look like here: [link]

Does either approach work for you, or is there something else
behind the concern I should know about?

Best,
[Your name]

5. The buyer viewed the proposal but went quiet

If your proposal tool shows the proposal was opened, don't quote that back to the buyer. Use the signal only to time your email, and write it so it would make sense even if you had no tracking at all.

Subject: Re: [Project] proposal

Hi [First name],

I imagine the proposal is making the rounds on your side,
so I wanted to make that easier rather than ask for an update.

Two things that sometimes help at this stage:
- A 15-minute walkthrough for anyone who wasn't on our earlier calls
- Written answers to the questions your [finance / IT / legal] team
  is likely to ask

Would either be useful? If the timing has changed, just let me know
and I'll adjust.

Best,
[Your name]

What makes this version work: it doesn't say "I saw you opened it three times." It offers help that's relevant whether or not the buyer read the proposal, and gives them an easy exit if priorities changed.

6. Quote follow-up email (after sending an estimate)

For quotes and estimates, the buyer's first questions are usually "what's included?" and "can I change it?" Make both easy to answer.

Subject: [Project] quote – broken down by phase

Hi [First name],

Following up on the quote I sent on [Date] for [Project]: [link]

To make it easier to compare, here's how the $[Total] breaks down:
- [Phase / item 1]: $[Amount]
- [Phase / item 2]: $[Amount]
- [Phase / item 3]: $[Amount]

If you need to fit a specific budget, the easiest items to move to a
later phase are [item] and [item]. That would bring the first phase to
$[Amount].

Want me to send a revised version with that option?

Best,
[Your name]

7. Responding to a pricing question

When the buyer pushes on price, don't discount in your first reply. Clarify what they're comparing against, then offer scope options rather than a lower number for the same work.

Subject: Pricing options for [Project] (3 tiers)

Hi [First name],

Thanks for being direct about the budget. To make sure I respond to
the right thing: is the concern the total amount, the timing of the
payments, or how it compares with another quote?

In the meantime, here are three ways to structure it:

Option A – Full scope as proposed: $[Amount]
Option B – Core scope only ([what's removed]): $[Amount]
Option C – Phased: $[Amount] now, $[Amount] after [milestone]

Each option keeps [the outcome that matters most to them]. Happy to
walk through the trade-offs on a short call.

Best,
[Your name]

8. Follow-up to a multi-stakeholder group

When several people received the proposal, write to the group once with a summary tailored to each role, then follow up individually. Keep your champion in the loop before emailing their colleagues.

Subject: Summary of the [Project] proposal for the review team

Hi all,

[Champion's name] asked me to share a short summary ahead of your review.
The full proposal is here: [link]

What each of you may want to check:
- [Finance lead]: total cost and payment schedule (page [X])
- [IT / Security lead]: integrations and data handling (page [Y])
- [Operations lead]: rollout plan and time required from your team (page [Z])

If it's easier, I can hold a 30-minute Q&A with everyone on
[Date option 1] or [Date option 2]. Questions by email are also welcome.

Best,
[Your name]

Tip: agree with your champion beforehand on who gets this email and when. Going around your contact is the fastest way to lose them.

9. Asking about the decision timeline (day 10)

By day 10, you need to know the process more than you need an answer. Ask about the steps, not "have you decided?"

Subject: What does your decision process look like for [Project]?

Hi [First name],

I don't want to follow up at the wrong moments, so it would help to
understand the next few steps on your side:

1. Who else needs to review the proposal before a decision?
2. Is there a meeting or date when this gets decided?
3. Is anything missing that would make that conversation easier?

If it helps, I can draft a simple timeline we both work from—for
example, questions answered by [Date], internal review by [Date],
decision by [Date].

Best,
[Your name]

A shared timeline like this is the start of a mutual action plan. Our mutual action plan template has copy-paste versions.

10. Follow-up after a meeting or demo (recap)

Send this the same day as the meeting. A recap gives your contact something accurate to forward, and it puts the next step in writing.

Subject: Recap and next steps from today's call

Hi [First name],

Thanks for the time today. Here's what I heard, so we're working from
the same notes:

What you need:
- [Goal / problem #1]
- [Goal / problem #2]

What we agreed:
- [Decision #1 – e.g., start with phase 1 only]
- [Decision #2]

Next steps:
- [Your name]: send the revised proposal by [Date]
- [Buyer name]: confirm [information needed] by [Date]
- Both: review call on [Date] at [Time]

If I missed or misunderstood anything, reply here and I'll correct it.

Best,
[Your name]

11. Nudge before a quote expires

Send this a few business days before the expiry date. State the date, the reason it exists, and what happens after it—without pressure tactics.

Subject: Your [Project] quote is valid until [Date]

Hi [First name],

A quick heads-up: the quote for [Project] is valid until [Date].
After that, [what changes – e.g., the team we reserved for a
[Month] start is released / pricing moves to the [Year] rate card].

If you need more time, that's fine—just tell me and I'll either
extend it where I can or send you an updated quote.

If you're ready to move forward, the next step is [signing the order
form / confirming by email / a kickoff call].

Best,
[Your name]

Only send this if the expiry is real. An invented deadline you later waive teaches buyers to ignore your deadlines.

12. Breakup email (day 21)

The "breakup" email closes the loop politely and gives the buyer permission to say no. Many sellers find it gets a reply precisely because it's easy to answer.

Subject: Should I close the file on [Project]?

Hi [First name],

I haven't heard back on the [Project] proposal, which usually means
the timing isn't right or priorities have shifted. Both are completely
fine.

To keep things tidy on my side, could you reply with a number?

1 – Still interested, just busy (I'll check back in [timeframe])
2 – Not now, try again in [quarter]
3 – We've decided not to move forward

Either way, thanks for considering us.

Best,
[Your name]

13. Re-engagement 60–90 days later

Reopen a stalled proposal only with a new reason: a change on their side (funding, hiring, a new leader), a change on yours (a new capability, a relevant result), or a seasonal trigger.

Subject: Checking back on [Project] – anything changed on your end?

Hi [First name],

When we last spoke in [Month], [Project] was on hold because
[reason they gave].

I'm reaching out because [new reason – e.g., we've since added
[capability] that addresses the [concern] you raised / I saw your
team is hiring for [role], which is often when [problem] resurfaces].

If it's worth revisiting, I can update the proposal to reflect
where you are now—no need to start from scratch. If not, no problem
at all.

Best,
[Your name]

14. After "we went with someone else"

Reply graciously, ask one learning question, and leave the door open. Buyers sometimes revisit a vendor decision later, so it's worth staying on good terms.

Subject: Thanks for letting us know – one quick question

Hi [First name],

Thanks for telling me directly—I appreciate it, and I hope the
project goes well.

If you're open to it, one question would help us improve: what was
the deciding factor? Price, approach, timing, or something else?
A one-line answer is plenty.

If anything changes down the line, I'm easy to reach. I'll leave
you in peace until then.

Best,
[Your name]

15. Agency / freelancer version

For agencies, consultants, and freelancers, the proposal often doubles as a scope-of-work document. Make it easy to say yes to a smaller start.

Subject: [Project] proposal – a smaller way to start

Hi [First name],

Following up on the proposal for [Project] I sent on [Date]: [link]

If committing to the full scope right now is a big step, we could
start with [small first deliverable – e.g., a 2-week discovery sprint /
a homepage redesign / one pilot campaign] for $[Amount]. You'd get
[concrete output] by [Date], and you can decide on the rest afterwards
with real results in hand.

My calendar currently has room for a [Month] start. If that timing
works, I can send a short agreement for the first phase.

Would that be easier to approve on your side?

Best,
[Your name]

---

What to never write in a proposal follow-up email

Avoid lines that guilt, pressure, or reveal surveillance. Each of the examples below is common, and each one makes it harder for the buyer to reply.

---

How to personalize a follow-up in under five minutes

Personalization means referring to something the buyer said or cares about, not inserting their first name. Before each follow-up, take five minutes to pull one detail from your notes.

• Use their words. Quote the goal or problem as they described it on the call ("cut onboarding time for new reps"), not your product language.
• Name the person who needs convincing. "Would a summary for your CFO help?" shows you understand their situation.
• Reference their timeline. "Since your board meets on the 15th…" is more useful than any generic reminder.
• Add one relevant proof point. A short case from their industry or company size beats a generic brochure.
• Match their channel and tone. If they write two-line emails, send two-line emails.

The same Backlinko/Pitchbox outreach study found that personalized subject lines had a 30.5% higher response rate and personalized message bodies a 32.7% higher response rate—again, measured on outreach emails, so use it as a direction rather than a promise for proposals.

For call-based follow-ups, our sales talk script guide covers how to open a follow-up call without sounding scripted.

---

Tracking proposal views ethically

View tracking is useful for timing, but treat it as private context for you, not material for your emails. Be open that you use it, and never quote specific viewing details back to the buyer.

Many proposal and sales-room tools show when a document was opened, by whom, and which pages were read. That data can help you follow up at a good moment—but buyers generally don't expect to be watched page by page, and some tools (Terasu included) don't display a notice to viewers, so disclosure is up to you. A few ground rules:

1. Disclose it. Add a line to your proposal email or sharing page, e.g., "We use analytics on shared documents so we know when materials have been received and which sections to cover in follow-up." Mention it in your privacy policy as well.
2. Use signals for timing and content, not for commentary. If the pricing section got the most attention, lead your next email with pricing options—without saying why.
3. Don't read too much into it. An open can be a forward, a preview pane, or a security scanner. A lack of opens can mean the buyer printed it or read it in a meeting.
4. Respect a "no." If a buyer asks you to stop tracking or to send a plain PDF, do it.
5. Check your legal obligations. Rules on tracking and consent vary by country and state. If you sell into the EU or other regulated markets, check with your legal or privacy team.

---

Following up on proposals in Terasu

Terasu is a workspace where the proposal, supporting documents, and next steps live together in one shared Room with the buyer, instead of scattered across email attachments. Three things help with follow-ups specifically:

• One link for everything. You share a Room with the proposal, case studies, and a mutual action plan, so each follow-up can point to the same place instead of re-attaching files.
• View notifications. When a customer opens a shared document, you can get notified via Slack, Terasu, or email, and see who viewed what with page-level engagement. Use it to time your follow-up—within the ethics above.
• AI-drafted follow-ups, human-approved sending. Terasu's AI Agent can draft customer follow-up messages, but anything customer-facing waits for a user to approve it before it's sent.

There's a free plan (up to 3 Rooms and 2 users) and a 14-day free trial of paid plans.

---

Frequently asked questions

---

Conclusion

A good proposal follow-up is planned on day 0, adds something new every time, and makes the next step easy. Pick the cadence that fits your deal, copy the templates that match your situation, and personalize each one with a single detail from your notes.

If your proposals keep stalling, the fix often starts earlier: a clearer proposal and a shared plan. See how to write a sales proposal and the proposal template collection for the document itself.