How do you set up a sales pipeline for a contractor?
Stages that match the real job: estimate, decision, scheduling. Not a generic pipeline copied from B2B software sales that does not reflect how contracting works.
The short answer
- A generic pipeline built for software or B2B sales, with stages like 'discovery' and 'proposal', does not map well onto contracting work. That moves closer to lead, estimate, decision, and scheduled or completed.
- Insurance work, common in roofing and storm restoration, needs its own stages around adjuster meetings and claim approval. A cash job never touches those. Forcing both through one pipeline creates stages that fit neither.
- The pipeline should not end at 'won' in a narrow sense. A won deal needs to trigger what happens next: scheduling the work. That is either a final stage in the same pipeline or an explicit handoff to an operational system.
- Stage count should match real, distinct points in the process. Too many stages leaves reps unsure which one applies. Too few loses the visibility the pipeline exists to provide.
Why a copied B2B pipeline does not fit contracting work
Most CRM defaults ship with a pipeline built around a B2B software sales motion: lead, qualified, discovery, proposal, negotiation, closed. That structure assumes a sales process most contracting work does not follow. A homeowner requesting a roof estimate is not going through a discovery call and a negotiation phase in the software-sales sense. They get an inspection, receive an estimate, decide, and then, if they say yes, get scheduled for the work. Forcing that real sequence into stages named for a different kind of sale creates a pipeline that has stages but does not reflect what is happening.
The fix is building stages around the actual steps a job goes through in your trade. Typically something like new lead, inspection or estimate scheduled, estimate delivered, decision pending, won and scheduled, and completed. For businesses that do insurance work, extra stages around adjuster meetings and claim approval reflect a genuinely different process from a cash job. That may warrant a separate pipeline or a branch within one, rather than forcing both into identical stages.
Generic B2B pipeline vs. a contractor pipeline
| Generic B2B stage | What it assumes | Contractor equivalent |
|---|---|---|
| Discovery | A discovery call uncovering needs | Initial contact, often a same-call estimate request |
| Proposal | A formal written proposal document | An estimate, often delivered on-site or same-day |
| Negotiation | Back-and-forth on terms and pricing | Homeowner decision, sometimes comparing other quotes |
| Closed won | Contract signed | Job scheduled, work begins |
What to actually build
Map your trade's real process, from first contact through completed job. Name stages after what is happening at each point, not generic sales terms. If insurance work is a meaningful share of your business, decide whether it needs its own pipeline or branch rather than forcing it through the same stages as cash work.
Disclosure: SalesCrew is our product. Pipeline stages are fully configurable per instance today. That is what makes building a trade-specific pipeline, rather than living with a generic default, something you set up directly rather than work around.
A pipeline copied from B2B software sales rarely fits contracting work
Questions
- Should insurance work have a different pipeline than cash jobs?
- Often yes. Insurance work, common in roofing and storm restoration, adds stages around adjuster meetings and claim approval that a straightforward cash job does not have. A single pipeline trying to cover both can end up with stages that fit neither.
- How many stages is too many for a contractor pipeline?
- There is no fixed number. A pipeline with so many stages that reps are unsure which one to move a job to defeats the purpose. Each stage should represent a real, distinct point in the process.
- Does scheduling belong in the sales pipeline or a separate system?
- It depends on how integrated sales and operations are for the business. At minimum, a won deal should trigger scheduling. That can be a final stage in the same pipeline, or a handoff to a separate operational system.