Your client has not responded to the proposal: check before you follow up

You sent the proposal three days ago. Silence. At this point, most teams reach for the calendar: a reminder after two days, another after a week, and a third before the end of the month. A calendar is easy to implement, which is why it is so popular, but it answers only the question ‘when?’ The question ‘what should I write?’ remains unanswered—and that is what determines whether a reminder makes sense at all.

Why cadence alone fails

A cadence treats every recipient the same. Someone who has returned to your website three times since receiving the proposal and ended every visit on the pricing page gets exactly the same message as someone who has never returned after receiving it. These are two entirely different sales situations, yet a process based solely on the send date cannot tell them apart.

It is also worth dismantling a statistic that circulates in Polish sales guides: that a decision is made only after a certain number of contacts. Nobody quoting it provides the study, sample size, or even a definition of ‘contact.’ Without those details, you can neither verify it nor apply it to your own sales process. Building a cadence on that basis means the number of reminders comes from someone else's anecdote rather than your customers' behavior.

Client A should receive a message about the terms and implementation process, because that is exactly what they were looking for. Client B should receive a brief question asking whether the matter is still relevant, with a clear invitation to say no. Sending them identical messages wastes an opportunity with the first and gives the second yet another message unrelated to anything they have done.

In some industries, what matters is not the speed of the follow-up but the speed of the first response, because the client is contacting several companies at once. We explore this using real estate inquiries as an example. What to put in that first response, before any proposal exists, is covered in our guide to replying to a sales enquiry.

What you can check before following up—and what you cannot

Before writing, check four places. They all concern activity on your own website—a caveat we will return to shortly, because it matters more than it may seem.

• Return visitsWhether the same person started new sessions after you sent the proposal and how those visits were spread over time.
• Pages viewedThe pricing, implementation, case studies, and contact pages mean something different from an incidental visit to the blog.
• Questions asked in chatA conversation before the proposal often reveals a genuine concern that did not appear in the formal inquiry.
• Previous contact historyA callback request, a ticket with a reference number, or a conversation from a month ago changes the tone of the follow-up.

Meetlead brings all four together in one view. The customer journey shows one person's successive sessions, including the traffic source, landing and exit pages, visited URLs, device, active time, and events. Each session also links to any conversation, callback request, or ticket created at the time. We explain how such a history is built—and where the limits of its reliability lie—in our guide to the customer journey on a website.

• Whether the client opened the proposal email—this happens outside your website, so Meetlead cannot see it.
• What they do on competitors' websites, in search engines, or in internal conversations at their company.
• Their behavior on other websites owned by the same company—the history covers only the active website.
• The traffic channel for sessions without a recorded source—these are explicitly marked as uncovered, and you must not invent an origin for them.
• Who exactly was using the device if several people at the client's company share it.

This list is just as important as the previous one. A follow-up based on assumptions sounds worse than a general reminder, because the client will notice that you have attributed an intention to them that they never had. If there have been no visits since the proposal was sent, the only honest conclusion is that you do not know what happened to it.

A specific person's behavior on a website is personal data, even if you do not know their name. Using it in sales communication is subject to the same rules as the rest of the contact: you need a lawful basis, disclosure in the privacy policy, and a limited retention period. We break down the obligations concerning chat and website data in our article on live chat and the GDPR. This material is not a substitute for individual legal advice.

Four situations and four different messages

The table below is not a collection of templates to copy. Instead, it shows how a quick look at visit history can turn a vague check-in into a concrete proposal.

↔ Scroll the table sideways to see all columns.

Two rows deserve comment. In the penultimate case, the worst thing you can do is remind the client about a document that no longer fits their situation. In the final case, switching channels can be more effective than another message—with one proviso: the client should request a phone conversation rather than be surprised by one. We explain how to set up such a request in our article on website callbacks.

Where reminding becomes pressure

There is no universal number of messages after which contact becomes intrusive. There are, however, several conditions you can check against your own process and agree on as a team once, rather than deciding them separately for every opportunity.

• Every new follow-up adds something: information, an option, or an answer to a concern. Repeating the same request adds nothing.
• The intervals between messages grow rather than shrink. Shorter intervals signal pressure, not engagement.
• The client has an easy way to say ‘no’ and knows that doing so will close the matter.
• An explicit refusal ends the sequence immediately, even if the plan still contains two more steps.
• Channels do not multiply. Sending the same message by email, text, and instant messenger is the same message three times—not three attempts.
• What you know about website behavior stays on your side and changes the subject of the message; it does not become the message itself.

The final point is the easiest place to stumble. Saying ‘I can see that you viewed our pricing three times yesterday’ turns relevance into someone looking over the client's shoulder and ends the conversation faster than silence would. Used discreetly, the same knowledge leads to a message about billing options—without a word about how you know that this is the issue. The mechanism is identical to the one used at first contact, which we cover in our article on qualifying leads on your website.

In longer buying processes, the boundary shifts further because several people make the decision together. We explore this in our guide to B2B customer communication.

How to close the matter when there is no response

A sequence with no planned ending costs more than a lost contract: it takes up a salesperson's time and leaves an impression of the company that is hard to reverse. Decide how it ends before frustration sets in. How to set that end point in a conversation the customer started on Instagram is covered in our guide to Instagram DM sales follow-up.

1. Define the final message in advance.Before sending the first reminder, decide which attempt will be the last. Otherwise, the sequence ends only when someone loses the will to continue.
2. Say explicitly that you are closing the matter.A brief ‘we are closing the matter on our side; the proposal remains valid until the end of the month’ works better than another unanswered question.
3. Leave a way back.Provide one specific way to get in touch later, with no deadline and no obligation on the client's part.
4. Record the reason if you know it.Silence is not a reason. If a conversation or website behavior suggests a hypothesis, label it clearly as a hypothesis.
5. Set one return signal.If this person returns to the website in three months, you want to know before you begin writing a new proposal from scratch.

In practice, the final step is the most valuable. A client who returns after several months usually comes back with the same matter and does not want to explain it again. A contact history attached to one profile does all the work here: it shows the conversation from six months ago, the proposal sent at the time, and where the discussion stopped.

When the client does say ‘yes,’ an equally easy-to-waste moment begins. We outline the first few days in our article on the first days of a client relationship.

What to record to make the next follow-up easier

Your follow-up process improves only if every closed opportunity leaves a record that can be compared with others. A few fields in a note are enough, provided they remain consistent every time.

• The date the proposal was sent and its scope—without these, you cannot later determine whether the client returned to the relevant material.
• What happened on the website after sending: the number of returns and the pages where the client spent time.
• The content of every follow-up and one sentence explaining why you sent it.
• The response as a separate value, not a comment: reply, silence, or refusal.
• The outcome and closing date, including cases that ended without a decision.

After a few dozen such records, patterns emerge that no guide can give you: which types of opportunity turn silence into an ending, which merely delay the decision, and which reminders genuinely removed an obstacle. This is the only cadence worth implementing—your own, calculated from your own opportunities. It takes longer to build than a ready-made list from a guide, but it is the only one you can defend to your team.

The most useful figure you can extract from these records is the typical interval between the first visit and the inquiry. We explain how to calculate it in our article on time to customer decision.