Make delivery part of the workflow
Estimate follow-up begins when the estimate is delivered. Confirm that the customer received it, knows what is included, understands important exclusions, and has a clear way to ask questions. A document marked “sent” does not prove that it arrived or made sense.
Record the delivery channel and time. If the project requires multiple decision-makers, ask how they prefer to review it. Schedule the next contact while the conversation is still active instead of relying on someone to remember later.
Separate open estimates by reality
Not every unsigned estimate is the same. Some customers are actively comparing options, some are waiting on timing or financing, some postponed the project, and some chose another contractor. One generic sequence cannot respond intelligently to all of them.
Use a small set of statuses the team will maintain. “Open” alone is not enough. The record should show why the decision is pending, the next contact date, and who owns it.
- Decision pending with a known date
- Questions or scope clarification needed
- Financing, insurance, or scheduling dependency
- Postponed with a future review date
- Lost with a useful reason where known
- No response after the agreed follow-up attempts
Make each contact useful
A useful follow-up reduces friction. It might answer a scope question, clarify scheduling, explain an option, provide requested documentation, or make it easy to postpone or decline. Repeating “Have you decided?” does not create new value.
Reference the actual project and prior conversation. Keep messages short and give the customer a clear response path. When the next step needs judgment—such as revising scope, discussing price, or addressing concern—route it to a person rather than stretching an automated sequence.
Set timing from the job context
The right timing depends on urgency, project type, customer preference, season, outside dependencies, and the date discussed during the estimate. A repair needed immediately should not enter the same cadence as a discretionary project planned for a later season.
Ask when the customer expects to decide and record that answer. Follow up around the agreed timeline. If there is no stated date, use a modest initial sequence and then move the estimate to a longer-term review rather than contacting indefinitely.
Use automation as a safety net
Automation is good at creating reminders, sending approved confirmations, surfacing overdue estimates, and stopping messages when a status changes. It should support the estimator or office team—not conceal the absence of ownership.
Build stop conditions for booked, lost, postponed, unqualified, duplicate, and do-not-contact records. Protect consent and channel preferences. Test updates carefully so a booked customer does not continue receiving sales messages.
Review outcomes, not message counts
A healthy report shows delivered estimates, open estimates by age, next actions due, contact outcomes, revised scopes, booked work, postponed projects, lost reasons, and records with no resolution. The purpose is to find stalled decisions and process gaps.
Compare booked work with gross margin and capacity, not revenue alone. If many estimates remain unresolved, sample the records and determine whether the issue is delivery, slow answers, unclear scope, schedule fit, pricing, lead quality, or missing disposition.
- Percentage of estimates with a scheduled next action
- Age of open estimates by project type
- Contact and response outcomes
- Booked, lost, postponed, and unresolved counts
- Common questions and loss reasons worth fixing upstream