CRM and Job Management
Pipeline Management for roofing contractors
Everything in a pipeline was true when somebody put it there. Nothing marks the day it stopped being true.
A list that still describes reality
Items moved at the moment the thing that moves them happens, rather than in a sweep before a meeting. A pipeline maintained in batches is accurate twice a month and misleading the rest of the time.
Age on the face of every open item. Not available on request — visible, so that the oldest things are obvious to anybody glancing at the list rather than to whoever thinks to sort by date.
And a close reason worth reading, taken from what the customer said. The reason is the only part of a dead opportunity that has any value left in it, and it is the part most often skipped.
Nothing announces that a claim has expired
An entry in a pipeline is a small prediction. It says this is real, this is progressing, somebody is going to decide. When it was made it was probably right — people do not generally invent opportunities — and the difficulty is that it carries no expiry and emits no signal when it stops being accurate.
In roofing the decay is faster than most trades and less visible. A homeowner who was going to decide after the holidays used somebody else in March. A storm job that looked certain settled differently. A commercial enquiry is still technically alive and has not been touched since spring. None of those produce an event at your end. They simply become less true while continuing to look identical on the list.
The damage lands in two places, and the second is worse. The obvious one is the forecast, which becomes a number nobody acts on because everybody privately discounts it. The quieter one is attention: real opportunities sit among dead ones and receive the same treatment, because nothing on the list distinguishes them. A pipeline nobody trusts stops being used to decide anything, and then it is just data entry.
Which is why the remedy is about time rather than about judgement. Nobody has to guess which items are dead if age is visible and movement is recorded when it happens — the list sorts itself, and the conversation that follows is about a handful of things rather than all of them.
What makes a stage mean anything
A stage is only useful if crossing into it required something to happen. Where a stage means "somebody felt more optimistic", it carries no information and the pipeline becomes a mood ring with a currency total attached.
The test we work to is whether a stage change has an event behind it that somebody outside the company would recognise: a site visit happened, a document went out, a decision-maker said something specific. Those are checkable. Optimism is not, and a stage built on it drifts upward under pressure, which is exactly when a forecast most needs to be honest.
The second test is whether movement is ever backwards. A pipeline where nothing ever regresses is not a pipeline where nothing goes wrong — it is one where going wrong is not being recorded. Items that quietly stall at their high-water mark and are eventually deleted tell you far less than items that were moved back when the reason for the optimism disappeared.
None of this requires a view about which opportunities are worth pursuing. That judgement is yours and depends on things a record cannot hold — what you want the business to be doing, who you want to work for. This desk makes sure the picture you are deciding from is a description of what has actually happened rather than an accumulation of what once seemed likely.
Where the department keeps its promises
This desk sits inside CRM and Job Management, and the department boundary — including how customer information is held and where administering it stops — is set out there rather than repeated here. What is particular to this page is that it deals only with the passage of time over records that already exist; nothing here concerns how the system was built or who may contact anybody.
What owners ask about the forecast
Our pipeline number is always wrong. Why?
Because it is a sum of claims made at different times and never re-examined. Each item was plausible on the day somebody entered it, and most of them quietly stopped being plausible without anybody moving them. The number is not lying about the present so much as reporting an accumulation of pasts.
What does this desk actually do?
Makes movement visible and makes staleness cost something. Items get moved when the thing that moves them happens, age is on the face of every open item rather than hidden in a report nobody runs, and anything that has sat too long gets asked about. It is maintenance rather than analysis.
Do you chase our prospects?
No. Contacting people is a separate function with its own rules, and it belongs to a different department here. This desk works on the record: what state each opportunity is genuinely in and how long it has been there. Who gets called, and how, stays with you and with the desk that does that work.
Why record why something was lost?
Because it is the only part of a pipeline that pays you back later, and it is the field most often left blank. A close reason captured from what the customer actually said — rather than picked from a menu at month end — is the difference between knowing you lose on price and knowing you lose to one competitor on a particular kind of job.
How long should something sit before somebody looks at it?
That is yours to set and the setting matters less than having one. What matters is that the threshold exists, that crossing it is visible without anybody running anything, and that crossing it triggers a question rather than a shrug. A pipeline with no ageing rule accumulates indefinitely, because nothing ever forces the conversation.
Would it not be easier to just clear it out periodically?
Clearing it out is the symptom. A pipeline that needs a purge is one where staleness was invisible until it became embarrassing, and the purge destroys the history that would have explained what happened. Moving things as they change costs less in total and leaves a record you can learn from.
Nothing published governs a stage name
No published authority sits behind this page. Naming that plainly is more useful to a reader than attaching a rule that governs a neighbouring subject and hoping the distinction goes unnoticed. How a company tracks its own opportunities is not regulated. What IS regulated is how prospects are CONTACTED, and that axis belongs to customer-support/speed-to-lead-response, which argues it from the telemarketing scope rules. Citing those here would be axis collision.
What it is held to instead: A pipeline stage reflects something that actually happened, not something somebody hopes will.
Where the regulated part of this subject lives: customer-support/speed-to-lead-response.
Sort your open items by the date they last moved
Whatever sits at the bottom of that list has been telling you something for a while, and the total at the top has been counting it.