Contractors often invest significant time getting to the estimate stage: answering the enquiry, visiting the property, measuring, pricing materials and preparing the proposal.
Then the estimate gets sent and the process becomes:
“Let me know what you think.”
That leaves too much value sitting in the customer’s inbox.
A better approach is to define a follow-up sequence that combines automation with human judgement.
First: confirm the estimate was received
The first follow-up does not need to sell anything.
Shortly after sending the estimate, confirm delivery:
Hi [Name], we just sent the estimate for [project/service]. Let me know if you have any trouble opening it or if there are any questions I can clarify.
This solves a simple problem: sometimes the proposal was missed, filtered or sent to the wrong address.
Day 1–2: create a human follow-up task
For meaningful projects, a phone call is often more useful than another automated message.
The goal is to understand:
- Did they review the proposal?
- Is anything unclear?
- Are they comparing options?
- Has timing changed?
- Is there an objection you can actually address?
Record the outcome in the CRM rather than keeping it in somebody’s memory.
Day 3–5: useful check-in
If there is no decision, a short message can reopen the conversation.
Hi [Name], just checking whether any questions came up while reviewing the estimate for [project]. Happy to clarify scope, timing or next steps.
Avoid fake urgency unless there is a real deadline.
Day 7–10: ask about timing
At this point, the important question may be whether the project is still active.
Hi [Name], I wanted to check where things stand with the [project]. Are you still planning to move forward soon, or would a later follow-up be more useful?
This gives the prospect an easy way to tell you “not now” instead of simply ghosting.
After that: choose a real status
Do not leave the opportunity in “Proposal Sent” forever.
Move it based on what you know:
- Active decision — continue appropriate follow-up.
- Not now — place into long-term nurture with a future date.
- Lost — record the reason.
- Won — begin onboarding/handoff.
- No response — use a final attempt and then move it out of the active pipeline.
A clean contractor CRM pipeline makes this much easier.
High-ticket projects need more human follow-up
A $20,000 remodeling proposal should not receive the exact same automation as a small maintenance quote.
As project value and complexity increase, use automation mainly to:
- remind the salesperson;
- schedule tasks;
- confirm messages;
- keep the opportunity visible;
- support rather than replace personal communication.
Common estimate follow-up mistakes
Following up with no context
“Just following up” repeatedly gives the customer no new reason to respond.
Ask a useful question or reference the actual project.
Discounting too quickly
Silence does not automatically mean price is the objection.
The customer may be busy, waiting on another decision-maker, changing scope or planning timing.
Understand the obstacle before changing the price.
Leaving the next action undefined
If the salesperson says “I’ll check back sometime next week,” create the task while the conversation is fresh.
Automating after the customer has replied
Workflows should stop or change once the customer is actively speaking with somebody. Nothing feels less personal than receiving an automated “Still interested?” text while already discussing the project with the estimator.
Build the sequence into the CRM stage
A useful setup is:
Opportunity enters Proposal Sent → confirmation message → task scheduled → follow-up logic → branch based on response → Won/Lost/Nurture
That makes follow-up part of the operating process rather than an optional habit.
What about old unsold estimates?
Those are a separate reactivation opportunity.
If you have a database of proposals from six months or two years ago, segment them by service, timing and outcome before contacting them.
My guide to contractor database reactivation explains that process.
A simple sequence to start with
For a normal non-emergency project:
- Same day: estimate delivery confirmation.
- Day 1–2: manual call task.
- Day 4: SMS/email check-in.
- Day 7–10: timing/decision check.
- Day 14+: move to long-term nurture, close lost with reason, or schedule a future follow-up date.
Adjust the cadence to the service, project value and normal buying cycle.
The objective is not to chase the customer forever. It is to make sure a valuable opportunity never disappears simply because nobody remembered the next action.