Kaldwick resources
Practical guides and free tools for residential roofing teams that need clearer inquiry handoffs, a visible owner, and a specific next action.
Roofing
An inspection on the calendar is a booking. Whether it becomes a signed roof depends on what happens after: the context, the owner, the next action. Why booked and captured are not the same number.
Read the field noteA referral is the warmest, cheapest lead a roofer gets, which is exactly why it gets the least follow-up. Dropping one costs you twice: the job, and the customer who vouched for you.
Read the field noteYou 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.
Read the field noteA request comes in while you are on a roof. Two competitors call back before you climb down. Here is how to win the first five minutes without promising to answer your phone at midnight.
Read the field noteEvery few years roofing finds a new edge: shared leads, Google LSA, an AI that answers the phone. Each one flattens as competitors buy it too. Here is the part that does not erode.
Read the field noteKeep roofing Requests moving while a homeowner waits on an insurance adjuster by preserving context, ownership, and the next action.
Read the field noteKeep deferred roofing prospects from disappearing by recording why they asked to wait, who owns the follow-up, when to reconnect, and what happens next.
Read the field noteFind where roofing leads stall between request, inspection, estimate, and signed work — and identify the stage that needs attention.
Read the field noteA roofing estimate appointment gets rescheduled, cancelled, or missed. Keep the changed request clear with a recorded last action, next action, status, and one responsible person.
Read the field noteThe 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.
Read the field noteFull board, past the county line, or not your kind of roof? A request you can't take still deserves an answer. How to keep the context, assign responsibility, and close it clean.
Read the field noteRoofing teams buy a CRM and quietly stop using it. Why adoption fails on small teams, and how to make a tool actually stick: process first, then software.
Read the field noteFive requests open, one free hour between tear-offs. A plain, human way to pick who gets the first call - by readiness, not by who arrived last or shouted loudest.
Read the field noteA practical guide to the columns and routine that keep roofing follow-up clear, with a ready-made tracker available for teams that prefer a workbook.
Read the field noteFive roofs down your street from three years ago. A consent-clean way to work that list - maintenance, small repairs, and the work next door - without becoming the roofer whose texts they mute.
Read the field noteThirty estimates went quiet last year. A playbook to pick which ones deserve a second call, give each one an owner - and find out why they went quiet before reaching for a discount.
Read the field noteTwelve requests in two hours after the hail. A practical post-storm intake workflow: preserve what the homeowner said, name an owner, make the next action clear - without claiming damage you have not seen.
Read the field noteFive questions. That's the whole form. A roofing quote-form checklist that captures what the office needs to route the call - without turning the homeowner's request into homework.
Read the field noteWhen four roofers get the same request, one form can mean four phones. Before you buy another shared lead, run the math that actually decides: cost per signed roof, not cost per contact.
Read the field noteNeed a roofing CRM - or will a spreadsheet do? Five questions decide. The minimum fields that keep estimate requests visible, and the honest test for when a CRM earns its place.
Read the field noteSix steps between form submitted and job booked. Most shops collapse them into one - and that is where the request goes quiet.
Read the field noteA roofing lead follow-up process a crew of three can actually keep: one visible list, one owner per request, and a next action with a date - before any software conversation.
Read the field noteA request lands at 9:40 p.m. The office is closed. Five steps that make sure it still has an owner in the morning - no midnight-response promise required.
Read the field noteA Google Local Services Ads contact is not an inspection or a sale. Six fields keep the original request, owner, and next action clear after it reaches a roofing team.
Read the field noteA roofing lead handoff is complete when the estimator can see what the homeowner asked, what the office did, and what the next action is. Use this seven-item checklist.
Read the field noteExisting field notes
These existing notes remain available, but Kaldwick’s current resources focus and new editorial work are roofing-first.
Marketing says the leads are fine. The field says they're junk. The argument repeats because no one can see what actually happened to each lead. Here is how a shared record settles it.
Read the field noteTwo home service companies can pay the same per lead and get completely different results. The number that decides whether the month works is cost per booked job, and the way to move it is not cheaper leads.
Read the field noteThe advisor quoted the changeout, the homeowner said "let me think," and the file went quiet. A simple way to keep an undecided HVAC replacement from turning into a silent lost sale.
Read the field noteThe July board fills by 9 a.m.: no-cools, changeouts, maintenance. A call order that sorts them by readiness before the day decides for you.
Read the field noteA practical plumbing callback-priority system: separate active leaks, drain calls, water-heater work, and out-of-area requests before the day runs itself.
Read the field note