If your HVAC company marks estimates as lost without recording why, you are missing one of the easiest sources of insight available to you. This guide covers how to use closed-lost reasons well.
Key takeaway: Requiring a specific reason before marking any estimate closed-lost, price, timing, chose a competitor, financing, or no response, turns your loss data into a source of real insight. Patterns in these reasons tell you whether you have a pricing problem, a follow-up problem, or a positioning problem, far more precisely than a raw close rate ever could.
Why raw close rate is not enough
A close rate tells you what share of estimates converted. It does not tell you why the rest did not, which means it cannot tell you what to fix. Two businesses with the same close rate could have completely different underlying problems, one losing on price, another losing on follow-up consistency.
A useful closed-lost reason set
- Price: the customer chose based on cost
- Timing: not ready to move forward now
- Competitor: chose a different company
- Financing: financing fell through or was not available
- No response: never heard back despite follow-up attempts
Keep the list short enough that staff will actually use it consistently, rather than skipping the field or picking "other" by default.
Making it a required field
If your CRM allows an estimate to be marked closed-lost without a reason, that gap will get used. Requiring the field, even a simple dropdown, is what makes the data reliable enough to act on.
Using the data
Review closed-lost reasons monthly, broken out by job type if you have enough volume. If "price" dominates a specific job type, that is a pricing or value-communication conversation. If "no response" dominates, that points back to follow-up consistency, not price at all.
Risks and limitations
Self-reported reasons are not perfectly precise. A salesperson might default to "price" when the real issue was a weak follow-up or a missed question during the estimate. Treat the data as a strong directional signal, not an infallible one, and combine it with direct conversations when a pattern seems off.
QuickPro's approach
We build closed-lost reason tracking directly into the estimate follow-up systems we implement, so the data collects itself as part of the normal workflow rather than as extra work.
Frequently asked questions
How many reason categories should we track?
Five or fewer tends to work best; more categories reduce consistency without adding much insight.
Should we ask the customer directly why they did not book?
When practical, yes; a brief, low-pressure question can surface more accurate information than staff guessing after the fact.
Related reading
Where to go from here
This ties directly into building a consistent estimate follow-up system.
