Proposal Follow-Up Timing: Run Your Own Study Instead of Copying a Benchmark

Follow-up timing advice circulates as though it were settled. Follow up within a day. Make five attempts. Tuesday morning performs best. Whatever the specific claim, it originated in a particular market with a particular buying process, and it was often calculated on data with the same confounder described below. None of that makes it worthless. It makes it a hypothesis.

The good news is that this is one of the few sales questions a small business can genuinely answer for itself, because the data required is minimal and the analysis is arithmetic rather than statistics. What follows is a method rather than an answer, and the absence of an answer here is deliberate.

Export every proposal from the last twelve to eighteen months with the date sent, the date of first follow-up contact, deal value, segment and outcome. Bucket by days to first follow-up. Calculate three numbers per bucket: win rate, median days to decision and average number of contacts before the outcome.

The table is deliberately empty. Filling it with invented numbers would be exactly the error this article argues against. What you are looking for is direction and consistency: does win rate decline monotonically as delay increases, or is there a plateau? Does the pattern hold within each deal size band, or does it reverse in one of them? A reversal in a segment is often the most useful thing the analysis produces.

Here is the trap. Reps follow up fastest on the deals they believe in most, which are also the deals most likely to close for entirely separate reasons. So the fast bucket is contaminated with better opportunities, and the observed advantage of speed is partly an artefact of selection rather than an effect of timing.

Two ways to reduce it. Segment on quality indicators you recorded at proposal stage, such as whether budget was confirmed and whether the decision maker attended the meeting, then compare timing buckets within a single quality band. Or run a genuine test: for a defined period, assign the follow-up interval by rule rather than by judgement, for example alternating between a same day and a three day first follow-up across all incoming proposals of a similar type. Assignment by rule is what makes the comparison meaningful.

Write the interpretation rule before you look. Something like: we will change our standard cadence only if one bucket shows a difference of at least a defined margin, across at least a defined number of proposals, and the direction is consistent in both deal size bands. Committing to that in advance is what prevents the very human process of finding the cut points that produce an interesting story.

Expect the answer to be less dramatic than the advice you were about to copy. In most small businesses the honest finding is that anything from same day to about three days performs similarly, that delays beyond a week hurt, and that what the follow-up says matters more than exactly when it arrives within the reasonable range. That is a genuinely useful result, because it redirects effort from cadence engineering to message quality.

Set a standard, write it into the process as an automatic task at proposal stage, and then spend your attention on content. Build two or three follow-up types that add something: an answer to a question raised in the meeting, a document that helps internal approval, a reference from a comparable buyer. Measure response rate by type. That is a second study, and in my experience it produces a larger improvement than any timing change.

Practically, this analysis only works if proposal sent and first follow-up are both timestamped in one place. HelloGrowthCRM records proposal stage entry and every subsequent call, message and email against the deal, so the export required for this kind of study is a filter rather than a reconstruction project.

Related reading on follow-up and pipeline measurement: sales automation, lead management software, CRM for small business, features, calling from the CRM, and use cases.