Contractor CRM Pipeline Stages
A CRM pipeline is a series of stages that describe where a job stands — and a contractor's pipeline is only as useful as the stages are honest. The stages should describe the customer's position in the journey, not the team's to-do list. Here is a practical pipeline, what each stage means, what moves a record forward, and the mistakes that make most contractor pipelines useless by month three.
A pipeline describes the customer, not the team.
The most common reason a contractor's CRM pipeline stops working is that the stages describe the contractor's actions instead of the customer's position. A stage called "Called" tells you the team picked up the phone. It doesn't tell you whether the customer is waiting for an estimate, comparing quotes, or has gone quiet. A useful pipeline is a map of the customer's journey — and the stage name should answer the question "where is this job, from the customer's side?"
The pipeline below is a starting point for a service business — HVAC, plumbing, electrical, roofing, and the broader trades. It is not the only honest pipeline, and a business with a longer sales cycle or a different workflow may need different stages. What matters is that each stage has a clear definition, a clear move, and no overlap with the one before it.
The stages, what they mean, what moves them.
New
Enquiry landed
The form submission, the call, the referral that just arrived. The record exists. Nothing has been qualified, contacted or promised yet — it simply arrived.
When someone acknowledges the enquiry and decides it's worth a response.
Contacted
First response sent
The acknowledgement, the callback, the text. The customer knows the business received the enquiry. The conversation has started, even if it hasn't gone anywhere yet.
When the customer replies, or when the team schedules the next concrete step.
Qualified
Scope understood
Someone has confirmed the job is real, the territory is right, the work fits what the business does, and the customer is reachable. The enquiry has become a possible job.
When the job is worth an estimate, a visit, or a proposal — and the customer has agreed to one.
Estimate / Visit
Assessment scheduled or done
The site visit, the walkthrough, the assessment that turns a possible job into a quoted one. For larger work, this is where the real scope gets settled.
When the estimate is sent, the proposal is written, the quote is in the customer's hands.
Quoted
Proposal sent
The written estimate or proposal is with the customer. The job is now their decision — to accept, to negotiate, to wait, or to choose another contractor.
When the quote is accepted, declined, or needs a revision.
Won / Booked
Job on the schedule
The customer said yes. The deposit is paid, the crew is assigned, the job is on the calendar. The enquiry has become revenue.
When the work is scheduled — and the record moves to fulfillment, not sales.
Lost / Nurture
Not now, or not this job
The quote was declined, the timing was wrong, or the job didn't fit. A lost record isn't a deletion — it's a follow-up later, a referral source, or a learning about what the market wanted that you didn't offer.
When the timing changes, the need returns, or the record is closed honestly.
The mistakes that make a CRM useless by month three.
A stage called 'Called' tells you what the team did, not where the customer is. Stages should describe the customer's position in the journey — the action the record is waiting for.
A pipeline with twelve stages is a pipeline nobody updates. Five to seven honest stages cover most contractor journeys. More than that and the team stops moving records because the stage names stopped meaning anything.
If 'Qualified' means whatever the person updating it thinks it means, the pipeline stops reporting anything useful. Each stage needs a definition: what makes a record belong there, and what moves it forward.
A lost quote is a future opportunity, a referral source, and data about what the market wanted. Delete it and you lose all three. Keep lost records and revisit them on a sensible cadence.
A pipeline that earns its keep.
A useful contractor pipeline answers three questions at a glance: how much work is coming in, where it's stalling, and what needs a response today. It does that because each stage describes the customer's position, each stage has a clear definition, and each record is owned by a person who knows what moves it. The pipeline is not a status symbol — it is a map of the work the business is actually trying to win.
The standard BGE build includes one pipeline, up to two intake forms, one calendar and up to three core automations. Multi-location routing, field-service dispatch and API integrations are quoted separately — because they are a different scope of work.
Want a pipeline that maps the work?
Tell us the jobs you sell and where they stall. We'll set up the stages, the routing and the automations — so the pipeline describes the customer and the team knows what to move next.