# Contractor estimate follow-up pack
Arsalan Zaffar, RevSet Labs | October 2, 2026

Original examples, not measured conversion claims. Use verified placeholders, permitted channels, and your normal sender/opt-out disclosures.

## 1. The estimate went unanswered
Use when: The estimate was delivered, the agreed response date has passed, and there is no open customer question.

Subject: One question about your [project] estimate

Hi [name], I’m reviewing the estimate we sent for [specific work] on [date]. Is there a part of the scope you would like us to explain before you decide? Reply here and [owner] will help with that detail. — [sender], [business]

SMS:
[Business]: regarding your [project] estimate, is there one detail you would like us to explain? Reply here. Reply STOP to unsubscribe.

Team action: Keep the estimate awaiting a decision. A reply creates a task for its owner and stops unanswered-quote reminders.

## 2. The customer cannot find the estimate
Use when: The customer says the attachment or quote link is missing or inaccessible.

Subject: Your [project] estimate — replacement link

Hi [name], here is the estimate again: [current quote link]. This is version [number], dated [date], for [scope summary]. If the link still does not open, tell me which format would be easier and I’ll arrange it. — [sender], [business]

SMS:
[Business]: here is the current [project] estimate you requested: [link]. If it will not open, reply and we will help. Reply STOP to unsubscribe.

Team action: Verify the link points to the right customer and current version. Record the delivery problem rather than labeling the customer uninterested.

## 3. The price is higher than expected
Use when: The customer has raised a budget concern. This is a response to an objection, not another automated reminder.

Subject: Reviewing the scope of your [project]

Hi [name], thanks for telling me the estimate is above what you expected. Which part of the project is essential for you? [Estimator] can review whether a different scope is practical and explain what would change. We’ll confirm any revised scope and price in writing before you decide. — [sender], [business]

SMS:
[Business]: thanks for the budget feedback. Which part of [project] is most important to keep? Our estimator can review the options. Reply STOP to unsubscribe.

Team action: Assign the estimator and pause the sequence. Do not let an agent approve a discount, remove required work, or promise phased work before review.

## 4. The customer wants to change the work
Use when: The original estimate no longer describes the requested job.

Subject: Confirming your changes before we revise the estimate

Hi [name], I have noted your request to [customer-requested change]. Before [estimator] updates the estimate, could you confirm [one missing scope detail]? We’ll send a new version for your review. The existing version does not yet include this change. — [sender], [business]

SMS:
[Business]: we’ve noted [requested change]. Can you confirm [missing detail] so our estimator can review it? Reply STOP to unsubscribe.

Team action: Record revision requested. Keep the old version in history and suppress approval reminders for it. Restart only after the revised estimate is approved internally and sent.

## 5. The project is for later
Use when: The customer explicitly asks to postpone the decision.

Subject: Your preferred timing for [project]

Hi [name], I’ve noted that you are considering [project] for [customer’s stated period]. Would you like us to contact you on [proposed date], or would you prefer to get back in touch yourself? We’ll recheck pricing and availability when you are ready. — [sender], [business]

SMS:
[Business]: for your [project], would a check-in on [date] help, or would you prefer to contact us when ready? Reply STOP to unsubscribe.

Team action: Pause the current sequence. Store an agreed next-contact date if the customer chooses one. A postponed project is not automatically lost.

## 6. The current price needs rechecking
Use when: The actual estimate validity period has ended. Do not manufacture an expiry date.

Subject: Rechecking the estimate for [project]

Hi [name], the pricing validity date shown on estimate [reference] has passed. If you still want to consider the work, [estimator] can check the scope and current pricing before you approve anything. Would you like us to do that? — [sender], [business]

SMS:
[Business]: estimate [reference] has passed its stated validity date. Would you like us to review current pricing for [project]? Reply STOP to unsubscribe.

Team action: Route to review. Do not send a payment request for an expired estimate or imply that the former price remains available.

## 7. Close the unanswered sequence politely
Use when: Your approved follow-up limit is reached, the customer has not replied, and contact is still permitted.

Subject: Pausing our follow-up on [project]

Hi [name], we have not heard back about estimate [reference], so I’m pausing our follow-up. If you decide to revisit the project, reply to this email and we can check the scope, price, and availability then. Thank you for considering [business]. — [sender]

SMS:
[Business]: we are pausing reminders about your [project] estimate. Reply if you would like to revisit it later. Reply STOP to unsubscribe.

Team action: Stop the sequence. Record no response, not “lost on price.” Do not add a further “last reminder” after promising to stop.

## Ten-estimate review
Choose ten consecutive open estimates. For each record:
- Estimate ID, version, sent date, validity date
- Latest customer message and current stage
- Permitted channel / preferred contact date
- Next action and message template, if appropriate
- Owner and due time
- Reminder stop condition
- Verified outcome: reply, revision, approval, scheduled job, payment

Do not treat silence as a price objection. Do not record approval as payment.

## Launch cases
Test: unanswered, missing estimate link, price objection, scope change, postpone, expired estimate, accepted, declined, opt-out, duplicate send job, reply immediately before reminder. Use fictional contacts. Record expected vs observed message, quote version, state, owner, and next task.

## Reporting
Use one estimate-delivery cohort. Count unique estimates, replies, approvals, scheduled jobs, and received payments separately. Note unresolved cases and changes in pricing, service mix, and lead source. Results after follow-up do not establish that follow-up caused them.

https://revsetlabs.com/resources/contractor-estimate-follow-up-templates/