How to Track Roofing Leads Without Another CRM

Do you even need a CRM for this?

When a roofing owner says they need better lead tracking, the first question is not "which software." It is whether the current system makes open requests visible. On a busy day, can anyone in the shop tell which of last week's requests still needs a call?

A request can go quiet without anyone being careless. Sometimes the next step just stopped being visible.

So before shopping for software, ask a smaller question: what would "tracking" actually have to do for your team, and is a tool you already have enough to do it?

Honest answer: it depends. The wrong call is expensive either way. A CRM you buy and never keep current is worse than a spreadsheet you actually update. But a spreadsheet that works for one person can turn into gaps when several people try to keep it current at once, and those gaps creep in without anyone noticing.

So the decision is not really "CRM or spreadsheet." It is whether your team can consistently see who owns each request and what needs to happen next. There is a quick way to test that below.

What tracking actually has to capture

Strip it down and a follow-up system needs a handful of things per request:

Everything else - estimating, production, invoicing - is a different job. If you are only trying to stop leads from slipping between the request and the first real conversation, those fields are the whole game.

• Homeowner / opportunity: who it is and what they asked for.
• Received: when it came in.
• Owner: one name responsible for the next step - not "the office."
• Last action: call, text, voicemail, or nothing yet.
• Next action and status: what happens next, on what date, and where it stands (Needs Action, In Progress, Booked, or Not Booked).

CRM or spreadsheet? Run this check

Before you spend a dollar, run your open requests through five questions. For any request still in play, can your team answer:

If the answer is consistently yes, your current system may be enough - spreadsheet, shared inbox, or the CRM you already pay for. If it is no, fix the workflow before adding software. A new tool will not, by itself, create clear ownership or a next action.

• Who owns the next step?
• What happened last?
• What needs to happen next?
• When is that next action due?
• Can everyone who touches the request see the same answer?

When a shared inbox is enough, and when it isn't

For a one- or two-person shop, a shared email inbox can genuinely be the system. Requests land, you see them, you call them.

It becomes unreliable the moment more than one person touches the same request. An unread email looks the same as a handled one. Someone replies from their phone and the office never sees it. Two people each assume the other called. Nobody is technically at fault - and the lead still goes cold.

The failure is not laziness. It is that an inbox has no place to record who owns a request or what needs to happen next. It fails the last question in the check above, structurally.

When a spreadsheet is enough

A spreadsheet with one owner per request, a last action, and a next action can outperform a CRM nobody keeps current. That is not a knock on software - it is how adoption works. A tool your team quietly stops updating stops being true, and a system that is not true is worse than none.

A sheet is fast, already familiar, and nobody needs training to open it. Software has to earn the complexity it adds. If a sheet answers the five questions above, it has earned its place - and a platform has not yet.

The honest limit: a basic spreadsheet does not create automatic reminders or enforce consistent updates. It depends entirely on people keeping it up to date. If keeping it current is already the hard part, more columns will not fix that.

When your existing CRM is already the answer

If you already pay for JobNimbus, Roofr, AccuLynx, or something similar, the first move is not to add another tool. It is to check whether the one you pay for already does this and just is not set up to show it.

A CRM is often a great filing cabinet and a weaker sales board. The data is all in there, but "which requests still need a call today" is not always the first view people see, so they fall back to memory. Depending on how it is configured, a saved view, an owner field, and a clear next action may already be enough. Find that out before you buy anything new. Often the tool was fine, and the process on top of it was the missing piece.

The part no tool fixes for you

Here is the through-line. The tool is only ever as good as the process, and the process is only as good as whether your team actually keeps it current. Tool, then process, then adoption. Adoption is usually where these systems break down.

That is why the answer to "which software should I buy" is so often "none yet." Software will not fix a follow-up habit. Get the habit working first: one owner and one next action per request, kept current every day, on whatever you already have. If you want a plain starting point for that habit, our simple follow-up process for small roofing teams lays it out step by step. Once the habit holds, change the tool only if it is genuinely in the way.

So, do you need a CRM?

Run your own requests through the five questions. If your team can answer them quickly and consistently, your current setup is probably enough - CRM or spreadsheet. If it cannot, that is the workflow to fix first. Start with the smallest thing that makes it visible: one owner and one next action per request, in one place everyone checks.

If a spreadsheet is where you would start, we put together a free roofing follow-up tracker that uses those same fields and statuses: Free Roofing Follow-Up Tracker. It uses eight columns: homeowner, received, project, owner, last action, next action, status, and notes. It is not a CRM and it is not an estimating tool; it is a clear place to see what still needs action. And if older quotes keep going quiet, our follow-up playbook for unsold roofing estimates covers how to decide which ones are worth revisiting.

Where Kaldwick fits

Kaldwick gives a roofing team a shareable quote link and a Needs Action work list for incoming requests. The team can initiate a call, text, or email action from that list and record a booking outcome separately. Its role is to make the next work visible at the inquiry handoff.

It does not replace a full roofing CRM, estimating system, dispatch process, or the human judgment behind a relevant follow-up.

If your current system already answers the five questions above, honestly, keep it. That is not a small-print disclaimer. It is the point.

Frequently asked questions