Why quotes die: a follow-up schedule that works

A quote rarely dies in a meeting where the customer says no. It dies quietly: the PDF lands in an inbox, the customer means to discuss it with a partner, the week gets busy, and three weeks later nobody remembers which version was the latest. Your sales pipeline still shows it as “sent”, which is the most optimistic word in sales.

This post is about the part between sending and deciding. It gives a follow-up schedule, message templates for each step and rules for when to let a quote go.

Four reasons quotes go quiet

1. The customer has a question they have not asked. Something in the scope, the payment terms or the timeline is unclear, and asking feels like effort.
2. The decision needs someone else. A partner, a finance manager, a spouse. Your quote has to make the case without you in the room.
3. There is no reason to decide now. No expiry date, no start date, no consequence of waiting.
4. Nobody on your side owns the follow-up. The quote was sent, the task was considered done, and the next step lives in someone’s memory.

Only the fourth one is fully in your control, and it is the one that fixes the other three. A follow-up is how you surface the unasked question, equip the absent decision maker and create a reason to decide.

Build the quote so it can be followed up

Follow-up starts before sending. A quote that is easy to act on needs:

• A clear scope with line items the customer can recognise.
• Payment terms: due date, installments if any, currency. Under TTK Article 1530, in transactions between businesses where no payment date is agreed, the debtor is in default 30 days after receiving the invoice; writing your own term in the quote avoids relying on that default and also shortens collection later.
• A validity date, typically one to two weeks for services.
• One next step: “accept online”, “reply with your start date”, not five options.
• A link, not only an attachment, so you can see when it was opened and the customer can accept without printing anything.

Our quote template lists the sections a quote needs. In the quotes module, each quote has a shareable link, an expiry date with reminders, a change history, and a customer acceptance step that can lead straight to a contract and e-signature.

The follow-up schedule

Here is a schedule for a quote valid for 14 days. Adjust the days to your own validity period; keep the structure.

Day	Action	Purpose
0	Send the quote link with a two-line summary	Make the next step obvious
1	Check whether it was opened; if not, resend by another channel	Rule out delivery problems
3	Short message offering to answer questions	Surface the unasked question
7	Send something useful: an example, a timeline, an answer to a common objection	Equip the other decision maker
12	Remind of the expiry date and what changes after it	Create a reason to decide
14	Last message: expiry today, ask for a yes, no or later	Get a clear answer
15+	Close with a reason, or move to a later follow-up date	Keep the pipeline honest

Two rules make it work:

• Each step has an owner and a date in the system, not in someone’s head. If the schedule depends on memory, it fails in the busiest week.
• Stop the schedule as soon as the customer answers. A follow-up that arrives after a reply looks careless.

Message templates

Keep them short. Each message should have one purpose.

Day 0, sending

Hello Ayşe, here is the quote for the website maintenance package we discussed: [link]. In short: 12 months of support, 4 content updates per month, 3 installments. You can accept directly from the link. It is valid until 14 October.

Day 3, questions

Hello Ayşe, did anything in the quote need clarifying? The most common question is what counts as a content update; I am happy to go through it in five minutes.

Day 7, something useful

Hello Ayşe, in case it helps the conversation with your partner, here is how the first month would run: week 1 setup, week 2 first update, then monthly. Happy to adjust the start date.

Day 12, expiry

Hello Ayşe, a reminder that the quote is valid until 14 October. After that date the prices will need to be updated to the current exchange rate. Should I hold the start date for November?

Day 14, last message

Hello Ayşe, the quote expires today. Is it a yes, a no, or a “later”? Any answer helps me plan, and a “later” with a date is perfectly fine.

Notice what they avoid: “just checking in”, apologies for writing, and pressure that is not real. The deadline in the day 12 message is real because the quote actually expires.

A worked example

A small agency (example figures) sends 20 quotes in a month. Without a schedule, the pattern looks like this at the end of the month: 5 accepted, 3 declined, 12 still “sent”. Those 12 are not a pipeline, they are a question mark.

With the schedule, the same 20 quotes end the month with a status each: accepted, declined with a reason, postponed to a date, or expired with no answer. The accepted count may or may not change, but three things do:

• The team knows which quotes to stop spending time on.
• Declines with reasons show whether price, scope or timing is the problem.
• Postponed quotes get a new follow-up date instead of disappearing.

That visibility is the point. A pipeline where every quote has a real status lets you forecast; a pipeline full of “sent” does not.

When to let a quote go

Close the quote when the validity date passes with no answer, and record why. Useful reasons:

• Lost on price
• Chose another supplier
• Postponed (with a date)
• No longer needed
• No answer

If the customer returns later, create a new quote with current prices and a new validity date. Reopening an old quote brings back old exchange rates and old assumptions.

After the yes

Acceptance is not the end. When a quote is accepted, the scope, installments and payment terms should flow into the sale and the invoice without retyping, otherwise the collection problems start on day one. We cover the other end of the cycle in how to calculate and shorten DSO. For sales teams, the solution page for sales teams shows how leads, quotes and sales connect in one record.

Checklist

• Every quote has a validity date and clear payment terms.
• Quotes are sent as a link, so opening and acceptance are visible.
• Each quote has an owner responsible for follow-up.
• Follow-up steps are scheduled as tasks with dates, not remembered.
• Each message has one purpose and adds something new.
• The schedule stops as soon as the customer replies.
• Expired quotes are closed with a reason.
• Decline reasons are reviewed monthly.
• Accepted quotes flow into the sale and invoice without retyping.

The short version

Quotes die of silence, not of rejection. Give every quote an expiry date, an owner and a schedule of short, useful messages, and close the ones that run out. The result is fewer forgotten deals and a pipeline you can actually read.