A quote goes cold because no one owns the gap between "quote sent" and "quote accepted". In that gap the customer is still shopping, still comparing, and still wondering whether the business they contacted has forgotten them. Nothing you do on the day you send the quote protects that gap. Only what happens afterwards does.

Why do quotes go cold after you have sent them?

  • Nobody wrote down a follow-up date, so the quote exists and nothing points to it.
  • The person who quoted it has moved on and assumes someone else is chasing.
  • The customer asked for three quotes and is still waiting on the third to compare properly.
  • The customer got the quote, felt embarrassed about the price, and stopped replying.
  • Your quote arrived and sat in an inbox with no message, no subject line and no deadline attached to it.
  • The project was postponed for a reason the salesperson never asked about.
  • Somebody assumed silence meant no, and stopped following up without ever confirming.

The last one is the most expensive mistake, because you paid the full cost of winning the job before you lost it.

How long should you wait before following up?

Not long. Set the schedule before you send the quote, and treat it as a diary entry, not an intention.

WhenWhat you doWhat you are actually testing
Day 0Send the quote with a clear expiry date and a named contactThat they received it
Day 2Short confirmation that the quote arrived and the scope is rightWhether the scope was understood
Day 7Offer something useful, not "any news"Whether they are still comparing
Day 21Ask directly what is holding it up, and offer to helpWhether the price is the problem
Day 45Close the file honestly, or send one final versionWhether they are simply not ready

Days 2, 7, 21 and 45 is a workable rhythm. It is short enough that you never go quiet for a month, and spaced enough that nobody feels chased. Adjust the intervals to your sales cycle, but write them down.

Always put an expiry date in your quote. A quote valid for thirty days gives the customer a reason to decide now, and gives you a legitimate reason to write.

What should a follow-up message actually say?

The rule is simple: every follow-up must add something. A reminder adds nothing, which is why reminders get ignored.

Weak version:

Hi Thabo, just following up on the quote. Any news?

Stronger version:

Hi Thabo, following up on the geyser replacement quote I sent on Tuesday.
Two things you may want to weigh up while you decide:

1. The 30-day validity ends on the 12th, after which I will need to
   recheck the parts price.
2. If the budget is the issue, I can do this in two stages — new
   geyser now, new pipework when you are ready — which brings the
   first invoice down.

If it is not going ahead, no hard feelings, just let me know so I
can release the slot for someone else.

The second one gives the customer three things: a reason to act, an option they may not have considered, and an easy way out. People who are not going to buy will often tell you, and that is a win, not a loss.

What should you never do in a follow-up?

  • Never send the same message twice with a different subject line.
  • Never ask "just checking in" with nothing else attached.
  • Never quote a discount on the fifth message because you feel the pressure. If you discount at all, discount for a stated reason and once only.
  • Never leave a quote with no expiry and then treat the silence as final.
  • Never follow up on a Sunday night out of anxiety. Tuesday morning is fine.

How do you keep track of which quotes need chasing?

If a quote is not visible on a list, it does not exist. The simplest thing that works is a single shared sheet or Kanban board with these columns.

ColumnWhat goes in it
Quote referenceA number a customer can quote back to you
Customer and jobEnough that anyone on the team knows what it is for
Value and marginSo you can see where the money is, not just the volume
Sent dateDrives the follow-up schedule
Next action dateThe date somebody has to do something
StageSent, confirmed, chasing, stalled, won, lost
Lost reasonFree text, filled in when it closes

The lost reason column is the one that changes your business. After a quarter of honest entries you will see whether the loss is price, timing, competitor, or silence. Price is a pricing problem, silence is a follow-up problem, and they need completely different fixes.

If a quote leaves your business and nothing in your business is going to remind you it exists, you have not sent a quote. You have sent a hope.

Should you follow up on WhatsApp, email or by phone?

Match the channel the enquiry came in on. A customer who messaged you on WhatsApp will read a WhatsApp message and ignore a second email about the same thing. If you sent the quote by email, confirm it arrived on WhatsApp if you have a number, and follow up on the email thread where the paperwork lives.

A phone call is justified when the value is high, when you have spoken to them before, or when three written follow-ups have gone unanswered. Log the call and the outcome, because a call that is not written down did not happen.

What do you do when the customer says the price is too high?

Take it as information, not an objection to be broken. Ask what the budget looks like, then offer a version that fits it. A smaller scope, a staged project, a different material, a payment plan, or a later start date all work and cost you nothing to offer.

Then record the gap. If you keep hearing the same number as too high for the same type of work, that is not a sales problem, it is a pricing problem, and no follow-up sequence will fix it.

Where do you start this month?

  1. Pull a list of every quote sent in the last ninety days with no recorded outcome.
  2. Close them out honestly. Mark the won, the lost, the stalled.
  3. Build the board with the columns above, and make it shared.
  4. Add the five follow-up dates to your diary as you send each quote from now on.
  5. Put an expiry date in the quote template.

If you would like a second pair of eyes on your follow-up process, book a free strategy session with Agentcy.