The eleven days after you send a quote
Silence isn't a no. A practical way to think about the gap between sending a quote and hearing back β what to check, when to follow up, and what an expiry date really does.
You sent it on a Tuesday. It's now the Saturday after next. Eleven days, and nothing β no reply, no questions, no rejection. Just the quiet.
So you do the thing everyone does. You reread your own quote looking for the mistake. You decide the price was too high. You draft a follow-up, delete it because it sounds desperate, and don't send anything at all.
The eleven days are the most neglected part of the sales process, and they're the part where most of the work already done gets thrown away.
Silence is not an answer
The instinct is to read silence as a polite no. It usually isn't. A customer who has decided against you has an easy, low-cost way to end it β they say no, or they say nothing and mean no, and either way it costs them nothing.
But a customer who is still deciding also says nothing. So does one who never received it. So does one who opened it on a phone in a car park, meant to look properly that evening, and forgot.
From the outside, all four look identical. That's the actual problem: not that customers go quiet, but that you can't tell which kind of quiet you're looking at.
Three reasons a quote goes cold
It's sitting with the wrong person. The person you talked to isn't always the person who decides. It might need a partner, a board, a landlord, or a spouse who wasn't on the site visit and is now reading your quote with no memory of the conversation that produced it. Everything that made sense when you explained it in person has to survive being read cold by a stranger.
The price arrived without its context. In the conversation, the number had reasons attached. In the document, it's a total. If your quote doesn't carry the reasoning β why this material, why this much time, what the alternative would have cost β the customer supplies their own explanation, and it's rarely a flattering one.
They simply forgot. This is the most common and the least dramatic. Your quote is the most important thing in your week and one of forty things in theirs. It went to page two of the inbox on the Wednesday and hasn't been seen since.
Notice that only the first of these is about your price, and none of them is fixed by waiting.
The one thing worth knowing: was it opened?
If you take a single thing from this: opened and not opened are completely different situations that call for completely different responses. Guessing between them is what makes follow-up feel awkward.
Never opened. This isn't a sales problem, it's a delivery problem. Wrong address, spam folder, a personal address for a work decision, a mail client that ate the link. The right response is not a nudge about the price β it's "I want to make sure this actually reached you." That's an easy message to send and an easy one to receive.
Opened once, briefly, on the day. Skimmed. They looked at the total and closed it. They may have real objections they haven't articulated yet.
Opened several times, over several days, possibly by more than one person. This is a live deal. Someone is sharing it internally, working through the numbers, comparing it. This is the moment where a phone call is worth more than at any other point in the process β and it's exactly the moment most people are waiting quietly for the customer to come to them.
The difference between the second and third cases can't be inferred from the outside. It's the reason view tracking exists, and it's more useful than most people expect: not as surveillance, but as timing.
A cadence that isn't nagging
The rule that makes follow-up bearable is simple: every touch carries something new. "Just checking in" carries nothing, which is why it feels like nagging β because it is. Something like this works:
Day 2 β confirm arrival, not interest. Short, no pressure, no mention of the decision. You're solving a delivery problem, and if the quote wasn't opened, you've just recovered a deal you'd otherwise have lost to a spam filter.
Day 5 β answer the question you know they have. You almost always know what it is, because it came up in the conversation. The timeline. Whether the old wiring is included. Whether it can be done in two phases instead of one. Send that, not a reminder. If you can offer a smaller version of the job, this is when to do it.
Day 10 β make it easy to say no. "Should I close this off, or is it still live?" This feels counterproductive and does the opposite. A clear no frees your pipeline and, more often than you'd think, produces the real objection β the one nobody wanted to raise because raising it felt like haggling. Half the deals that come back from the dead come back from this message.
Three touches over two weeks isn't pestering. Sending nothing and then blaming the price is not restraint β it's just a slower way to lose.
What an expiry date actually does
An expiry date isn't a pressure tactic. Its real function is to remove the third option.
Faced with a quote, a customer has three choices: yes, no, or decide later. Decide later is the most comfortable one, and it's available indefinitely. An expiry date removes it β not by forcing a yes, but by forcing the choice to happen at all.
Two conditions make it work. It has to be honest β tied to something real, like how long your supplier will hold that price, how long you can keep the slot in the calendar, or the end of the season. A date with a reason attached is information; a date without one is a sales trick, and customers can tell the difference immediately.
And it has to be enforced. A quote that expires and then quietly stays valid teaches the customer that your deadlines aren't real. Automatic expiry does something for you as well: it keeps your own pipeline honest. Ten open deals is a real number worth working; forty open deals, half of them from spring, is a number you've learned to ignore.
When the answer is "yes, but"
Sometimes the eleven days end with a change instead of a decision. They want it, but with the cheaper flooring, or without the second bathroom, or starting in September.
Handle this as a new version of the document, not as a reply in an email thread. Once the agreed scope lives partly in a signed quote and partly in three messages and a phone call, nobody knows what was agreed β and the person who loses that argument later is usually you. The same goes for changes after acceptance: a change order that gets confirmed is worth more than an invoice line the customer disputes six weeks on.
How Dealight helps
Most of this article is about knowing what's happening. That's the part Dealight is built to give you.
View tracking records when a customer opens a deal, and the team gets a notification when it happens β so you know the difference between never-delivered and read-four-times, and you know it while it's still useful.
Expiry dates are configurable per deal, with reminder notifications before the date and automatic expiry after it, so your pipeline reflects reality without you having to prune it by hand.
Version history means every sent deal is an immutable snapshot. Send a revised version and the old one stays exactly as it was, so "yes, but" doesn't cost you the record of what came before. And change orders are a first-class deal type rather than an email β modifications after acceptance get the same document, the same signature, and the same audit trail as the original.
The follow-up is part of the job
There's a version of this that sounds like sales technique, and it isn't. A customer who's about to spend a significant amount of money with a supplier they don't know well is anxious, whether or not they show it. The follow-up is where that anxiety either gets addressed or gets left to grow.
Answering it well β promptly, with something useful, without pressure β is the first real demonstration of what you'll be like to work with once they've said yes. Most competitors send nothing at all.

Hampus Borgos
Founder of Dealight