You sent the estimate. Then nothing. It's tempting to read silence as a no and move on—but a customer who went quiet is often just busy, still comparing a couple of options, or sitting on a question they haven't gotten around to asking. A short, well-timed follow-up recovers a meaningful share of those jobs. The businesses that do this well aren't more aggressive—they just have a system instead of leaving it to whenever they happen to remember.
When to follow up
Response speed matters on the way in—research on web-generated leads has shown that contact within the first hour dramatically outperforms even a one-hour delay—and that same pattern of urgency fading over time applies after you've sent an estimate too. A reasonable rhythm: a light check-in around 48 hours after sending if the estimate hasn't been viewed, a second message a few days after that if it has been viewed but not answered, and a final, low-pressure close-out after one to two weeks of silence.
Five templates
- The simple check-in (sent soon after, low pressure): "Hi [name], just wanted to make sure the estimate for [project] made it through okay. Happy to answer any questions."
- The clarifying-question opener (once they've viewed it but haven't responded): "Hi [name], I saw you had a chance to look over the estimate—wanted to check if anything about the scope or pricing needs more explanation."
- The availability nudge (honest, schedule-based—not fake urgency): "We're currently scheduling into [month]. If you're still planning to move forward, let me know and I can hold a spot for you."
- The value reminder (restates what's included, without resending the whole document): "Just following up on the estimate for [project]—it includes [1–2 key details, like materials or timeline]. Let me know if you'd like to move ahead or have questions."
- The polite close-out (final check before marking it inactive): "No worries if the timing isn't right on this one. If you'd like, I can leave the estimate open for another two weeks—otherwise I'll check back down the road."
What to avoid
Skip fake urgency ("price goes up tomorrow!") unless it's genuinely true—customers can tell, and it costs you more trust than it gains you a response. Don't send more than one follow-up in the same week; it reads as pressure rather than service. And leave room for a real no—a customer who declines isn't a failure, and a follow-up sequence that respects a decline is more likely to get a callback next time they need the work done.
This is the exact gap ClientForth's follow-up feature is built to close: on Growth and Pro, it prepares an editable follow-up like these after a delay you choose, you review and send it (or let an enabled rule send it automatically), and the sequence stops the moment the customer responds, accepts, or declines—so the system does the remembering, and you stay in control of what actually gets sent.