Roofing - Lead follow-up - 10 min read
After a Roofing Inspection: Don't Let the Estimate Die on the Desk
The roof has been inspected, but the estimate has not gone out. Keep a pending estimate clear with a known blocker, next action, expected send date, and current status.
The roof has been walked. The homeowner is waiting on a number.
The roof has been walked. Photos are taken. Measurements are in. Maybe you have EagleView, maybe handwritten notes, maybe a few photos sitting in the rep's phone. The homeowner is waiting on a number, but the estimate still has not gone out.
That does not automatically mean somebody dropped the ball. Maybe you are waiting on a supplier price, the rep needs one more measurement, or the scope needs a second look.
The real problem starts when nobody can answer three simple questions: what are we waiting on, who is responsible for the next move, and what happens next? That is how an estimate goes from "we are working on it" to quietly sitting there.
There is a whole stage between the inspection and the quote
Roofing teams usually think about the obvious steps: lead comes in, inspection gets booked, the rep gets on the roof, the estimate gets built, the estimate gets sent, and the homeowner decides.
The messy part is inspection done to estimate not sent yet. At that point, it is not really a fresh lead anymore. But it is not an unsold estimate either, because the homeowner has not received the quote. It is a pending estimate.
There is a big difference between "we are waiting on metal pricing and Mike is calling ABC Supply tomorrow" and "I thought somebody already wrote that one up." The first is waiting. The second is stuck.
The homeowner may be talking to other roofers while you are building the estimate
In a nationwide homeowner survey published by Roofing Contractor in 2026 and sponsored by Owens Corning, 66% of respondents said they would gather three roofing quotes, and another 27% said they would seek multiple quotes. The same survey found that roughly 23% mentioned poor communication, lack of updates, or delays as a problem when working with roofers.
That does not mean every homeowner is racing your estimate against two competitors. It does mean one thing is worth keeping in mind: while your estimate is sitting in production, the homeowner's project may still be moving.
The answer is not "every estimate must go out in 24 hours." That is not realistic for every job. The better question is: can the team see why this one is waiting and when it is supposed to move again?
Waiting on something is normal. Nobody knowing what it is waiting on is not.
A roofing estimate can be sitting for a perfectly good reason. The point is not to make another complicated pipeline. It is to keep the estimate from becoming one of those jobs everybody vaguely remembers but nobody is actually moving.
| What is going on | Is it really stuck? | What should the team know? |
|---|---|---|
| Waiting on shingle or metal pricing | Not necessarily | Who is calling the supplier and when. |
| Need one more measurement | Not necessarily | Who is getting it and by what date. |
| Rep is writing the estimate | Not necessarily | Who is responsible and expected send date. |
| Waiting on a manager review | Not necessarily | Who needs to review it and when. |
| Roof was inspected but nobody is responsible for the estimate | Yes | Assign one person to move it. |
| Nobody knows why it has not gone out | Yes | Find the blocker and set the next step. |
| Promised send date already passed | Yes | Reset the plan. |
| Quote went out but the record still says pending | The record is stale | Update the status. |
First question: what are we waiting on?
After the inspection, write down the actual blocker if there is one. It might be material pricing, a supplement question, another measurement, scope clarification, siding or gutter pricing, a manager review, financing information, something from the homeowner, or nothing - the rep just needs to build the estimate.
That last one matters. Sometimes there is no blocker. The next step is simply: write the estimate. If nobody can say what the estimate is waiting on, you already found the problem.
A pending estimate only needs a few things to stay clear
You do not need 30 fields. For this stage, the team mainly needs a last action, one responsible person, a blocker if there is one, a next action, an expected send date, and a current status.
- Last action: write what actually happened. "Sep 16 - inspection completed. Photos and measurements uploaded" tells the next person what is done; "working on estimate" does not.
- Responsible person: put one name on it, not "sales," "office," or "estimating." That does not mean the person must do every piece; it means everybody knows whose board it is sitting on if it stops moving.
- Blocker: if something is holding the estimate up, say what it is. "Waiting on standing-seam pricing from supplier" is more useful than "pending."
- Next action: write the next real move. "Luis - call ABC Supply Tuesday morning" or "Maya - review measurements Wednesday before 3" can be acted on; "finish estimate soon" cannot.
- Expected send date: write when the homeowner should get the estimate if you know it. A supplier call Thursday and an expected estimate Friday are two different commitments.
What a clean pending-estimate record looks like
Two inspections can happen the same day, yet only one has a clear reason for waiting. That is the difference between a known delay and an estimate that needs attention.
| Field | Known delay | Needs attention |
|---|---|---|
| Last action | Inspection completed Sep 16 | Inspection completed Sep 16 |
| Responsible person | Luis | Maya |
| Blocker | Supplier pricing | None recorded |
| Next action | Call supplier Sep 17 | Draft estimate Sep 17 |
| Expected estimate | Sep 18 | Sep 17 |
| Status | In progress | Needs action |
Busy is not the same as stuck
Roofing gets busy. A rep can spend the morning on a roof, the afternoon meeting an adjuster, then get two emergency leak calls before dinner. That does not mean every estimate needs to be sent immediately.
A controlled delay is a roof inspected, material pricing awaited, a supplier call tomorrow, and an estimate expected Friday. That is not chaos; it is a job with a known blocker. An uncontrolled delay is a roof inspected, estimate never sent, nobody sure who is writing it, and no date or next step. That is where trouble starts.
It is not really about whether the estimate is one day old or four days old. It is about whether there is still a clear path forward.
Give the homeowner a date you can actually hit
If you need more time, tell them. You do not need to give them your whole internal play-by-play. A simple update is enough: "We have the inspection done and I am putting the estimate together. You will have it by Thursday." Or: "I am waiting on one material price before I finish this up. I expect to have it to you Friday."
Do not promise Thursday if you already know Thursday probably is not happening. If the timeline changes, update the homeowner.
A Modernize 2025 homeowner survey covering home-improvement contractors found that, among respondents asked what sales behaviors made them less likely to hire a contractor, 32.6% selected a confusing quote and 25.4% selected lack of communication. That is broader home-services data, not a roofing-only benchmark, so it should not be treated as a measurement of roofing homeowners. It does reinforce one basic contractor lesson: clarity around the quote matters.
A promised send date is not a speed-to-lead KPI
Do not turn this into "every quote out in 24 hours." Some estimates are simple. Others need multiple scopes, specialty material pricing, insurance documentation, decking assumptions, ventilation changes, gutters, siding, financing options, or a manager's sign-off. Those are not the same job.
The operational standard should be simpler: does every inspected request have a responsible person, a known blocker if there is one, and a next date? If yes, the estimate is moving. If not, it needs attention.
Four situations worth flagging
You do not have to flag every estimate that is old. Start with these four situations.
- Inspection done, no responsible person: put one name on it.
- Status says pending, but nobody knows why: find the actual blocker.
- The promised date already passed: set a new next step and update the homeowner if needed.
- The estimate already went out, but the record still says pending: mark the estimate sent and move it into the follow-up stage.
Once the estimate is sent, this stage is over
The second that quote goes out, the workflow changes. Now you are waiting on the homeowner. They may want to talk through the scope, wait on insurance, compare quotes, need financing, want another material option, need time, sign, or go another direction.
That is no longer a pending estimate. It is estimate follow-up. Record "Last action: estimate sent Sep 18" and set the next appropriate action.
Do not confuse a full pipeline with a clear pipeline
A dashboard can say "12 estimates in progress" and still tell you almost nothing. What matters is whether the team can open those 12 and answer who is responsible for each one, what happened last, what is holding it up, what happens next, and when it needs attention again.
That is a more useful check than simply looking at the number of pending estimates.
Where Kaldwick fits
Kaldwick is not estimating software. It does not build roof measurements, price shingles, calculate labor, write a scope, or replace your estimating system.
It keeps the request itself clear while your team is still working it: what happened last, what needs to happen next, when that next action is due, and where the request stands now. If Luis is waiting on supplier pricing or Maya needs to finish the estimate, the request record can show that context. If nobody has taken the next step yet, that is visible too.
If you want to test the process without adding another tool, the Free Roofing Follow-Up Tracker gives each request you add a simple place for last action, next action, and status. For the wider routine, see Roofing Lead Follow-Up: A Clear Process for Small Teams.
Frequently asked questions
How long should a roofing estimate take after the inspection?
There is no single turnaround that fits every roofing job. A simple reroof can be different from a project waiting on specialty material pricing, measurements, insurance information, or an internal review. The better rule is to make sure somebody is responsible for the estimate, the blocker is visible, and there is a real next date.
How do I know if a roofing estimate is actually stuck?
Ask three questions: what are we waiting on, who is responsible for the next move, and when should it move again? If the team cannot answer those, the estimate is operationally stuck.
What should I record after the roof inspection?
At minimum, record that the inspection is complete, who is responsible for the next move, the blocker if there is one, the next action, a next-action or expected-send date, and the current status.
Is waiting on supplier pricing a stuck estimate?
Not necessarily. If somebody is responsible for the supplier call and the team knows when to check again, the estimate is simply waiting on a known blocker.
Should every roofing estimate go out within 24 hours?
Only if your company can genuinely support that promise for the type of work you do. Do not invent a universal turnaround just because it sounds fast. Set a timeline your team can actually keep.
What do I tell the homeowner if the estimate is taking longer?
Keep it simple and factual. For example: "We completed the inspection and I am finishing the estimate. You will have it by Friday." If the date changes, tell them.
What happens after the estimate is sent?
Move the request out of pending estimate. Record the estimate as sent and set the next step based on the homeowner's situation: a follow-up call, a question about scope, an insurance update, or waiting until the homeowner's stated decision date.
Does Kaldwick build roofing estimates?
No. Kaldwick does not write or price the estimate. It keeps the request's context, recorded activity, next action, and current status visible while your team handles the estimating work.