All field notes

Roofing - Lead economics - 8 min read

The Real Monthly Cost of a Slow Roofing Estimate

You already know a slow estimate loses roofing jobs. This field note puts a number on it - with your own job value and your own close rate, not an industry statistic - so you can see which leak is worth fixing first.

Put a number on the leak

You already know a slow estimate loses jobs. What you probably have not done is put a number on it - not a scary industry statistic, but your number, from your own board. This field note walks the math with you, using figures you can pull from records you already keep. The point is not to feel bad about the leaks. It is to see them clearly enough to decide which one is worth fixing first.

Why the cost stays invisible

A lost roof does not send you an invoice. That is the whole problem.

When a marketplace charges you per lead, the cost is a line item - you can see it, resent it, and decide about it. When an estimate goes out three days late and the homeowner signs with someone else, nothing lands in your inbox. The job simply never happened. There is no line item for the roof you did not sign, so it never makes it into the math, and a cost you cannot see is a cost you cannot manage.

This field note is about making that invisible cost visible. Not with our numbers - with yours.

The pile you already paid for

Before you buy another lead, look at the requests already on your board. Every one of them is already a cost. A marketplace charged you for it, or an ad brought it in, or a past customer's referral came out of years of work you already did. The request sitting quiet on your board is not free just because no new invoice arrived this week.

That is what makes a slow estimate expensive in a way cost-per-lead never shows. You paid to get the homeowner to raise their hand, and then the delay let them walk. For the broader case that the number to watch is cost per booked job, not cost per lead, see why lead cost is the wrong number. This field note is narrower: it puts a dollar figure on the delay itself.

The four leaks, and how to measure each one

A slow estimate does not lose money in one place. It leaks in four, and each one is measurable from records you already have. Take them one at a time.

Leak one: the request that never got a callback. Some requests never became estimates at all, because no one reached the homeowner in time. Pull last month's requests and mark the ones where the first real contact happened more than a day after the request came in, or never happened. That count is not "bad leads." Some of those were roofs.

Leak two: the estimate that went out too late. Of the requests you did answer, some got an inspection but the written estimate lagged - days on a desk while the homeowner collected other bids. Mark the jobs where the estimate went out more than two or three days after the inspection. Late estimates tend to close at a lower rate than prompt ones, and you can see it in your own signed-versus-sent numbers if you compare the fast estimates to the slow ones.

Leak three: the estimate that went quiet and never got a second look. Estimates sent, then silence, then nothing - no second call, no reason recorded. Count last quarter's sent-but-unsigned estimates that got zero follow-up.

Leak four: the discount you did not need to give. When you are slow and the homeowner is already holding three bids, you negotiate from behind. Some of your margin erosion is not the market - it is the clock. This one is the hardest to measure precisely, so estimate it conservatively or leave it out. The first three leaks are usually enough to make the point.

Run the math: one month, your numbers

If you do one thing from this field note, do this. Here is the arithmetic, and every input is yours - nothing here is an industry average you have to trust.

Start with your average signed job value - the real one, from your last twenty invoices, not the round number you tell people. Then, for one month: count the requests that got no timely first contact (Leak one); count the inspections whose estimate went out late (Leak two) and the sent estimates that got no follow-up (Leak three); apply your own fast-path close rate - the rate at which requests you handle promptly become signed jobs - to those counts; and multiply the result by your average signed job value.

A worked example - replace every figure with your own
InputYour numberExample only
Average signed job value$ ____$12,000
Requests with no timely first contact (month)____6
Inspections with a late estimate (month)____4
Sent estimates with no follow-up (month)____5
Your fast-path close rate____ %30%
Est. jobs lost to delay = (6 + 4 + 5) x 30%____about 4.5
Monthly cost = jobs lost x job value$ ____about $54,000

Read the number honestly

The example number is deliberately not the point - yours will be different, and it is the only one that should change how you run the shop. Even if your real figure is a quarter of the example, it dwarfs almost any tool or subscription you would buy to fix it. That is the useful part: the leak is almost always larger than the fix.

A calculation like this can flatter you if you let it, so two guardrails.

First, not every leaked request was a real roof. Some were price-shoppers, some were out of area, some were never going to sign at any speed. That is exactly why the math uses your fast-path close rate instead of assuming every lost request was money - the close rate already discounts for the ones that were never going to happen.

Second, the goal is not the total. It is the biggest single leak. If most of your number comes from Leak three - estimates that went quiet with no follow-up - then a follow-up routine is your highest-return fix, and a faster estimate turnaround matters less this quarter. The number tells you where to spend attention, not just how to feel.

For the routine that closes Leak three, see our unsold roofing estimates follow-up playbook. For Leaks one and two, see the first five minutes.

The fix is usually visibility, not speed

Run the math and the fix usually names itself: most of the leak is not a slow crew, it is requests and estimates going invisible between steps, where no one can see them to act. You are not buying speed, you are buying visibility - an owner and a next action on every open request, so nothing goes quiet by accident.

When buying more leads is still the right move

None of this means the answer is always to stop buying and start fixing. Say it straight: sometimes more leads is the correct call.

A brand-new shop with an empty board has nothing to fix yet, and buying a few leads to get real homeowner conversations going is a reasonable trade. A shop with genuine open capacity - crews standing around - needs volume now, not a process project. And a real seasonal peak can justify buying while you also tighten the intake.

The point of the math is not that you should never buy another lead. It is that you should know what your current board is leaking before you decide the answer is more of them. Fix the biggest leak, buy when the capacity is real, and do not buy to paper over a follow-up problem that will leak the new leads too.

Where Kaldwick fits

When requests and estimates land in one visible place with an owner and a next action attached, the four leaks get much harder to spring. A Kaldwick quote link keeps each request visible from the moment it arrives, with the owner, last action, and next action in one view - so a late estimate or a quiet follow-up is something you can see and fix, not a cost you find out about at the end of the year.

We are taking 20 founding teams: $0 during the beta, no card. If you want your open requests and estimates visible before they leak, apply here.

The bottom line

The cost of a slow estimate is invisible because a roof you did not sign never sends a bill. Run the math once, with your own job value and your own close rate, and it stops being invisible. Then fix the largest leak first - usually a matter of making requests and estimates visible, not making your crew move faster.

Frequently asked questions

How do I calculate what slow estimates cost my roofing business?

Count, for one month, the requests that got no timely callback, the inspections with a late estimate, and the sent estimates with no follow-up. Multiply the total by your own fast-path close rate, then by your average signed job value. Every input comes from your own records, which is what makes the number defensible.

What is a fast-path close rate?

The rate at which requests you handle promptly turn into signed jobs. Using it instead of assuming every lost request was a sale keeps the estimate honest - it already accounts for the price-shoppers and out-of-area requests that were never going to close.

How late is too late for a roofing estimate?

There is no universal number, but you can find yours: compare the close rate of estimates sent within a day or two of inspection against those sent later. The gap between the two is the cost of the delay, measured on your own jobs.

Which leak should I fix first?

The largest one in your calculation. If most of your number comes from estimates that went quiet, a follow-up routine returns the most; if it comes from requests that got no callback, response visibility does. The math points you at the priority.

Should I just buy more leads instead?

Sometimes - a new shop, real open capacity, or a seasonal peak can justify it. But buying more leads does not fix a board that leaks the ones you already have. Size the leak first, then decide whether the answer is more volume or a tighter intake.