The proposal went out on Thursday. On Monday, the account manager asks whether the client had time to look at it. On Wednesday, another reminder follows. By Friday, the CRM shows three activities and not one new fact about the deal. Very busy. A bit like a treadmill: plenty of distance, same address.
The silence did not necessarily start after the email. The gap may have opened earlier, when the proposal was sent before anyone answered a few simple but uncomfortable questions: who decides inside the client’s company, which criteria matter, which risk is still open, and which event would count as real movement.
1. Where the deal may have broken before the proposal
The proposal left without a route
The manager understood the need, calculated the work, and packaged everything nicely. But the final agreement was only “I will take a look.” Who else looks, when it is discussed, what must be approved, and where it can stop - unknown.
The seller has one process: call, proposal, follow-up, contract. The buyer may have another: marketing checks scope, the owner weighs risk, finance looks for budget, and legal reads the terms. If those processes do not meet before the proposal is sent, the document simply falls between them.
Your contact was left to sell the decision alone
Your contact may genuinely support the idea and still have no right to say the final yes. After the call, they must retell your logic to a manager, accountant, or partner. Without you. In their own words. Between two other meetings.
If they do not know which questions those people will ask, another “have you decided?” email will not help. Find out who needs the explanation and what that person sees as the risk: budget, timing, implementation, responsibility, or an uncertain result.
The proof answers the wrong fear
Phrases such as “high quality,” “turnkey,” and “experienced team” offend nobody. That is the problem: they change nothing.
The client may fear a failed launch rather than the price. You send a case about cheaper leads. They may fear extra work for the team. You show polished design. The proof exists, but it serves your presentation rather than their decision.
2. One silence can mean four different things
From outside, the picture is identical: no reply. Inside the deal, these can be different states. Using the same follow-up for all four works roughly like using one key for every door. These four scenarios are GrandMa’s editorial framework for testing hypotheses, not a validated classification from Microsoft or HubSpot. They can overlap and do not cover every explanation: a missed message or an unexpected absence may also leave you without a reply. Until there is evidence, the reason remains unknown.
A real pause has an event
The decision is alive but tied to something concrete: a budget committee, a new quarter, a manager’s return, or the end of another project. The useful thing here is not more frequent messaging. It is the event after which the conversation can restart.
“Let us return to this in August” is not an event yet. “After the budget meeting on 12 August, finance confirms whether the project enters Q4” already resembles a process.
An internal blocker has a name
The contact has not disappeared. They are stuck between your proposal and someone else’s approval. The blocker may be a finance director, partner, lawyer, or department lead who will have to implement the result.
The useful question is not “what did you decide?” but “which part of the proposal will be hardest to approve internally?” The answer tells you whether the next move is a shorter calculation, a separate conversation, an implementation plan, or an honest admission that your option does not pass.
The priority changed
The project mattered during the first meeting, but then a more urgent problem appeared, the budget changed, or the team lost capacity. Your proposal may not have become worse. It simply stopped being first in the queue.
Check the original reason, not the person’s mood: “During our last call, the September launch mattered. Does that date still hold, or has the priority changed?” A concrete answer can give you a fact instead of another “we are still looking.” If no answer comes, the priority remains unconfirmed.
An actual no sometimes arrives without the word no
The client may have too little reason to move and too little desire to spend time on a rejection. Unpleasant, yes. But a series of polite reminders will not turn no into yes. It only makes the CRM more optimistic than reality.
The useful signal for reviewing an active status is not the number of silent days. It is the lack of any confirmed priority, decision participant, or next event even after a direct and calm question. That supports an internal pause or review under your team’s rules; it does not prove a rejection. Record “no response; reason unknown” unless the client confirms a reason. A confirmed event helps make a pause actionable, but a genuine delay can also have no known end date.
3. Diagnose the silence instead of writing again
Return to the last confirmed fact
Do not begin with new copy. Reconstruct what the client actually agreed to. For example: the problem was acknowledged, the budget was not confirmed, marketing and the owner must review the proposal, and there is no launch date.
Now it is obvious that “did you have time to review it?” diagnoses nothing. You are missing information about the budget, the decision owner, and timing - not merely an answer to an email.
If the last confirmed fact is “interesting, send the deck,” that alone does not show the deal was close. You had permission to send a file.
Test one hypothesis at a time
If priority is unclear: “Is the need to launch by September still current, or has the project moved?”
If your contact cannot decide alone: “Who else evaluates this project, and which question matters most to them?”
If the decision depends on an event: “After which meeting or approval will it be clear whether we continue or pause?”
If there is no signal at all: “It looks as though this is not a priority right now. I will remove it from the active plan. If I am wrong, tell me which event we should return to.”
These are not magic templates. Their job is smaller and more useful: each question targets a specific missing fact. A concrete reply can add evidence; an unanswered question leaves that fact unknown. “Just following up” does not specify what you need to learn. The questions and pause rules here are editorial methods, not documented product behavior or a promise of a reply.
4. What to record in CRM instead of a message diary
Seller activity is not buyer progress
The field “messaged on 25 July” is useful history. It does not explain whether the deal moved closer to a decision. The team needs other fields: last confirmed priority, known blocker, decision participants, next buyer-side event, and pause condition.
There is a concrete product example for part of this structure. Microsoft Learn’s documentation for Dynamics 365 Sales describes Purchase Timeframe, Estimated Budget, an individual-or-committee Purchase Process, identification of decision makers and stakeholders, and an expected decision date. These are ways to record information. An estimated budget is not an approved budget, and completing a field does not independently verify buyer commitment. The priority, blocker, next buyer-side event, and pause-condition fields proposed here are GrandMa’s editorial additions, not a claim that Microsoft supplies or requires this exact schema.
The distinction is simple. “Call on Friday” describes the manager’s work. “After the budget committee, the client confirms whether the project enters Q4; if there is no committee date by 15 August, the deal moves to pause” describes the deal’s state. This is where analytics should count confirmed changes in the buyer’s decision, not the seller’s motions.
A hypothetical worked example, not a client case: on 25 July, a marketing lead says a Q4 launch is still wanted and that finance must review the budget, but gives no meeting date. The account manager records that statement with its date and source; budget approval and the committee date remain unknown. The next question is: “Has the finance review been scheduled, and when can we check its outcome?” Suppose the contact then confirms a 12 August meeting and agrees to a 13 August check-in. That establishes a next event, not budget approval. If no meeting date is confirmed by 15 August, the team applies its chosen pause rule and records “review date unconfirmed.” The dates and threshold illustrate an internal rule, not a benchmark. A reminder sent in the meantime belongs in activity history; any later buyer confirmation is recorded separately.
Automate signals, not hope
When many deals get stuck this way, the problem is no longer one manager’s talent. Check whether your process forces the team to see criteria, participants, and blockers before a deal receives an optimistic status.
With suitable recorded fields and configured rules, automation can help flag missing information or an overdue recorded event. An empty participant field means the CRM lacks that information; it does not prove the buyer has no decision maker. Automation cannot invent priority for the client or turn activity into progress. AI systems and automation help after you define which signals genuinely mean movement and who checks the exceptions.
HubSpot’s documentation provides a specific mechanism: filter-based workflow enrollment can use properties of a record or associated records. The documented workflows require an eligible Professional or Enterprise subscription and Super Admin or Workflows permissions; some features have additional subscription requirements. For company, deal, quote, ticket, subscription, and custom-object workflows, records with no data are excluded by default: explicitly include empty values where the rule needs them. Relative-date filters using “is more than” or “is less than [x] days ago” are checked at the start of the day, so enrollment may be delayed. These filters can identify records for review; an alert still needs a configured workflow action, and neither enrollment nor an alert establishes why a buyer is silent.
5. What to do with the next proposal
Before the next proposal, ask yourself an uncomfortable question: “What exactly must happen inside the client’s company for this document to become a decision rather than an attachment?” If the whole answer is “they will look at it,” the decision route is still missing. Our editorial recommendation is to clarify it before treating the proposal as a step toward closing. If the buyer needs a preliminary estimate or a formal submission first, send what is needed with assumptions and open questions made explicit; do not mistake that submission for confirmed buying commitment.
Agree on at least a minimal route: who reads the document, which question each participant answers, when you compare the result, and which condition means pause. For a more complex deal, add technical review, budget approval, and the contract process. You do not need a corporate quest with twenty-seven steps. You do need to stop pretending that nothing happens between sent and signed.
After silence, do not polish the eleventh follow-up. Name what you do not know about the decision and test it with one question. Honest status does not weaken sales. It only weakens a forecast that calls hope a process.