The leak

An estimate can remain in a “sent” stage while the useful context lives in an estimator’s memory. The office sees a date but not the customer’s question. A follow-up reminder fires, and the next person sends a generic check-in because the actual reason for the conversation is missing.

The missing information might concern scope, access, timing or something else. Do not guess that price is the problem or that silence means the customer chose another provider. Treat an unresolved record as a question to investigate, not a confirmed commercial outcome.

Why it matters

A clear next action lets someone continue the conversation without reconstructing it. It also helps the owner see whether estimates are waiting on the customer, an answer from the team or a capacity decision. Those situations need different responses.

For Ontario service businesses, the decision window depends on the work. An urgent repair, planned equipment replacement and larger renovation should not automatically receive the same day-one, day-three and day-seven messages. Follow-up should match the customer’s context and the business’s ability to deliver.

How to fix it

1. Choose one open estimate. Read the actual conversation and identify what is known. If nobody has confirmed the customer’s decision window or concern, record that uncertainty rather than creating a confident story.
2. Name the outstanding question. Replace “check in” with the reason for contact. It might be clarifying scope, checking access or answering a question about availability. Use the customer’s question where possible.
3. Assign the person who can act. If the office cannot answer a technical scope question, the task needs an appropriate owner. Keep the answer and any required internal work connected to the estimate record.
4. Agree useful timing. Use the customer’s decision window and contact preferences. Where no date is agreed, make clarifying timing the next action. A weekly office review does not mean every customer should receive a weekly message.
5. Record progress separately from activity. A sent follow-up is an activity. An answered question and an agreed next step are progress. A confirmed booking or decline is an outcome. Keep those fields distinct.
6. Review coverage and capacity. Check whether the team can fulfil the work and whether a promise about availability is still accurate. More persistent follow-up does not resolve a delivery constraint.

What to track

Choose a defined group of estimates and a consistent review period. Separate urgent and planned work where their decision windows differ. Review both known outcomes and the completeness of the records; otherwise a cleaner report can be mistaken for better sales performance.

• Open estimates with a recorded question, owner and next date.
• Actions due and completed within the defined review period.
• Confirmed bookings and declines, separately from unresolved decisions.
• Confirmed reasons for declining, without inferring them from silence.
• Time to a known decision, with unresolved estimates reported separately.
• Capacity or fit concerns that affect whether the work should be pursued.

Define denominators explicitly. For example, on-time follow-up completion is completed due actions divided by actions due in the period, using a documented rule for rescheduled tasks. That is not a quote-to-booking rate. If you report booking rates, identify the estimate cohort and show how many outcomes remain unknown.

Need help finding the follow-up gaps?

A Revenue Leak Audit examines one workflow using available evidence and prioritises practical corrections. It is paid, scoped work, with implementation scoped separately. The inquiry form starts a conversation; it does not automatically book an appointment or purchase an audit.