Estimates and Follow-Up
How to Track Outstanding Estimates Before Opportunities Go Cold
An outstanding estimate needs a next action, a decision date, and a clear reason for remaining open.
Published Updated 2 min read
Stop using age as the only signal
An estimate that is ten days old may be healthy if the customer promised a decision next week. A three-day-old estimate may already be at risk if the work starts tomorrow and a revision is still missing. Track age, but interpret it alongside the customer's timetable and the project's dependencies.
Every open estimate should answer four questions: who owns the next action, what is that action, when is it due, and what is blocking the decision. If any answer is missing, the opportunity is not being managed.
Create practical attention rules
Use reminders based on events. Alert the estimator when a customer decision date passes, when a requested revision has not been sent, or when a proposal has had no activity for a defined period. These rules are more useful than sending the same reminder every seven days regardless of context.
Separate waiting on customer from waiting on your team. The first calls for follow-up; the second calls for internal action. Combining them under pending hides whether the delay is external or self-created.
Close the loop
BlueHarbor Contracting carried dozens of old estimates as open because nobody wanted to mark them lost. The backlog made the pipeline appear larger but provided no reliable forecast. The company introduced inactive as a neutral outcome for projects that lacked a current decision path.
That distinction matters. Inactive does not mean the relationship failed. It means there is no active next step today. If the customer returns, the estimate can be reopened with its history intact. A clean pipeline is more valuable than an impressive but fictional total.
Practical takeaways
- Track decision dates and dependencies alongside estimate age.
- Distinguish customer delays from internal delays.
- Trigger reminders from events, not arbitrary repetition.
- Use inactive status to keep the pipeline honest.
Company names and identifying details in the examples are fictionalized composites based on common commercial quoting and project-delivery situations.
