How to follow up on a quote without chasing customers: a service-business playbook
A practical quote follow-up system: three useful messages, clear stop rules and a worked example that separates accepted work from collected cash.
A quote needs a next step, not another “checking in”
When a customer goes quiet after receiving an estimate, the reason is still unknown. The price may be unclear, the timing may have changed, someone else may need to approve it, or the customer may have chosen another provider. A follow-up should help identify the decision instead of assuming the prospect needs more pressure.
The SBA’s marketing guidance connects a sales plan to the customer’s buying steps and recommends comparing marketing costs with revenue. The workflow below is BGA’s proposed operating method, not an SBA-prescribed schedule or a claim that a particular number of messages guarantees sales. It is designed for customers who requested a quote, not a cold prospecting list.
Record six things before sending another message
Keep one quote record with the customer’s requested work, the version and date of the estimate, the person responsible for following up, the promised next contact, the actual response, and the current decision. A shared sheet can handle this for a small team; a CRM is useful when handoffs become difficult. Avoid buying software before deciding who owns the work.
Use specific statuses: sent, clarification needed, decision pending, accepted, declined, or closed without a decision. Track scheduled, completed, invoiced and paid separately. An accepted estimate is not a collected payment. Record the reason a customer gives in their own words rather than guessing that every silence means the price was too high.
Three messages, each with a different job
At delivery, make the estimate easy to locate and explain the next step. Example: “Hi Jordan, your estimate for the office repaint is ready. It covers the rooms and preparation we discussed; the optional storage room is separate. Would you like me to walk through the scope, or would you prefer to review it first? What day works for a follow-up?” Replace every detail with the actual job.
At the agreed follow-up time, resolve uncertainty. Example: “Hi Jordan, what still needs to be clear before you decide: the work included, scheduling, or the price? I can answer by email or talk through the estimate.” If the customer names a decision date, use it. For nonurgent work with no agreed date, a trial reminder after two business days is a starting assumption to test, not an industry benchmark.
For a final closeout, ask permission to stop keeping the work open. Example: “Hi Jordan, is this project still under consideration, postponed, or already handled? If it is postponed, tell me when you would like to reconnect. Otherwise, I’ll close this estimate in our follow-up list.” Closing the record does not change any signed contract, cancel an accepted job or create a new expiration date.
Know when to stop and when to change the conversation
Stop the sequence when a customer declines, asks not to be contacted, or books the work. A complaint, disputed scope or pricing error needs a responsible person, not the next automatic reminder. Use the channel the customer agreed to use and check applicable communication requirements before automating calls, texts or marketing email. A quote request is not blanket permission for every channel or future campaign.
If affordability is the issue, clarify the scope and legitimate options. Explain what a smaller job leaves out, whether a different schedule changes your costs, and which terms genuinely apply. Do not invent a discount, deadline, limited opening or expected result to trigger a response. The FTC’s guidance requires advertising claims to be truthful and evidence-based.
A worked example: track the whole job, not just replies
Illustration only: suppose 20 requested estimates total $40,000, with each job priced at $2,000. Six are accepted, so accepted value is $12,000 and the acceptance rate is 6 ÷ 20 = 30%. If four jobs are completed and paid in full, collected cash is $8,000. The remaining $4,000 of accepted value is not yet collected, assuming no other payments.
Suppose a later set of 20 comparable estimates produces seven acceptances after the team introduces the workflow. That is 35% accepted, five percentage points above the earlier set, and $2,000 more accepted value under these assumptions. It does not prove the messages caused the change. Lead source, job type, season, price and capacity may differ. Compare similar work and watch completion, payment, complaints and staff time before expanding the process.
Run a small seven-day pilot
Day one: select a manageable group of recent, genuinely requested estimates that have no decline or contact restriction. Assign one owner and correct missing scope or pricing information. For the rest of the week, send only the next useful message, honor promised dates and update the record after every response. Do not restart the sequence when the same customer appears twice.
At review, count eligible estimates, messages actually delivered, meaningful replies, accepted work, completed jobs, collected payments and stop requests. Keep delivery failures separate from silence. Ask which question helped a customer decide and which step made the team waste time. Then change one part of the workflow and test again. A useful follow-up system makes the next decision clearer for both sides.