In this guide
You send a quote, make a note to follow up and get pulled into the next job. A week later, you find the sent email and wonder whether another message would help or just annoy the customer.
A useful quote follow-up email makes the next decision easier. It points to the right version, answers an outstanding question and gives the recipient a straightforward way to proceed, defer or decline.
This guide is for quotes someone requested or agreed to receive. It is not a cold-email sequence. The templates are starting points to adapt to the actual conversation, not messages to send automatically to every contact.
Check the quote before chasing the customer
Open the document and the conversation together. Is the scope clear? Does the price include what the customer asked for? Can they tell what happens if they accept? An unanswered quote can be a document problem, not a follow-up problem.
- Confirm the recipient and check for delivery failures.
- Check that the link works and the quote is still valid.
- Use the latest approved version, with clear inclusions and exclusions.
- Read any replies received through other channels before sending.
- Check whether the customer gave a decision date or asked you to wait.
If a quote has changed, explain what changed. Do not quietly swap a price or deadline underneath an old email. Someone comparing two versions should not have to guess which one applies.
Give each open quote an owner and a next action
Keep a small set of fields that makes the next step obvious. A spreadsheet can be enough to begin with if someone maintains it. A CRM helps when several people share the work or quotes move through approval and revision.
Quote reference and current version: [link] Customer and contact: [record] Sent date: [date] Owner and backup: [names] Status: [awaiting response / question open / revision needed / accepted / declined / deferred] Customer decision date: [date or unknown] Next action and due date: [specific task] Actual expiry date: [if applicable] Last conversation: [factual summary]
HubSpot’s quote-management documentation describes status views and filters for ownership, activity and signing status. Its current CPQ tools have subscription and seat requirements, so check your account before planning around a feature. The underlying requirement is simpler: know which quote is current and who is responsible for it. [1]
Keep quote acceptance separate from payment and delivery. A customer agreeing to proceed does not mean the invoice is paid or the work is complete.
Find the broken handoff in your revenue journey.
Send a first follow-up that is easy to answer
Use the review date you agreed with the customer. If you did not agree one, choose timing that fits the purchase and their working schedule. A small repair and a multi-person software procurement should not inherit the same daily reminder sequence.
Subject: Your quote for [project or service] Hi [name], Following up on the quote I sent on [date] for [scope]. Here is the current version: [link]. Is there anything in the scope, timing or price you would like me to clarify before you decide? If your plans have changed, let me know and I can update the next step on our side. [Name]
Ask one useful question. Avoid attaching a new brochure, asking for a call and offering a discount in the same message. You want to learn what is blocking the decision, not create three more decisions.
A quote view is not acceptance. Activity tracking can be useful context, but it does not tell you what the customer thinks. Avoid opening with “I saw you viewed it” when a straightforward question would do.
Make the next message relevant, not louder
If another contact is justified, add something the buyer needs: a response to an earlier question, a clear scope comparison or an explanation of the approval step. If you have nothing new to add, consider whether the agreed timing calls for another message at all.
Hi [name], You mentioned [specific question or constraint]. To clarify, the quote includes [verified inclusion] and does not include [relevant exclusion]. Would [specific clarification or revised option] help you make the decision, or would it be better to revisit this at a later date? [Name]
Do not invent limited availability or a price increase to create urgency. If a quote genuinely expires, state the actual date and what happens afterwards, such as checking availability or issuing updated pricing. An expiry date is a commercial condition, not a reason to pressure someone.
If the customer raises a price objection, find out whether the issue is budget, scope or timing before changing the offer. Any discount or revised term should have the appropriate approval and appear in the current quote.
Close the follow-up loop without a guilt trip
Set a contact limit with the team before starting. There is no universal number of reminders that is right for every quote. Stop earlier if the recipient declines, asks you not to contact them or gives a later date.
Hi [name], I have not heard back about [quote reference], so I will pause the follow-ups for now. If you would like to revisit it, reply here and we can confirm the scope, availability and current pricing. Thank you, [Name]
Use this only when it accurately describes what you will do. Pause the automation, update the record and do not restart the same sequence through another channel. A requested quote is not blanket permission for unrelated marketing.
Record “no response” separately from “price too high” or “competitor selected.” Silence does not establish the reason a sale did not happen.
Automate reminders, not commercial judgement
Start with internal task reminders before automating customer messages. A due-date alert can help an owner act without risking an outdated quote being sent while a colleague is negotiating new terms.
If you automate sending, check the latest status immediately before each message. A reply, acceptance, decline, delivery failure or active revision should stop or redirect the sequence. Decide who gets the exception and how they know it needs attention.
Trigger: quote awaiting response and follow-up due Before sending: check latest version, recipient, validity and recent replies Pause when: reply, acceptance, decline, revision, delivery failure or request to stop Human owner: [name] Backup: [name] Human approval required: price changes, discounts, terms and delivery promises If status cannot be checked: do not send; create a review task
AI can prepare a reply draft or summarise the conversation for an owner. It should not invent a customer objection, change a price or promise a completion date. Give the reviewer the source conversation and current quote so they can check the draft.
Test at least one reply during a scheduled sequence and one quote revision before enabling automated sending. Also check what happens when the integration fails. A workflow that keeps sending when it cannot read the latest status is not ready.
Review the queue, not just the email count
At a regular team review, look for open quotes without owners, overdue next actions, unanswered questions and revisions waiting for approval. These are specific problems someone can resolve.
For reporting, count one commercial opportunity once even if it has several quote versions. Compare acceptance within a defined group and time window, and keep still-open quotes visible. Otherwise, a batch of recent quotes can make performance look worse before customers have had time to decide.
Track meaningful replies, accepted quotes, time to decision and recorded loss reasons. Do not claim an automated reminder caused every later sale. Use the results to improve the quote and the process, not simply increase message volume.
Choose a handful of current quotes and apply this workflow manually first. Once the fields, ownership and stop rules work for the team, you have a much better brief for CRM configuration or automation.
Quote follow-up works best when the offer is clear, the next contact has a purpose and one person owns the decision. Fix version control and stop rules before automating more messages.