How many stages should a contractor pipeline have?
Most contractors do best with 4 to 6 pipeline stages. More than that and you're spending time updating statuses instead of running jobs. Fewer than that and you lose visibility into where deals actually are. Here's what the stages should be and why.
The standard four-stage pipeline
Start here if you're building from nothing. Lead, estimate, booked, and completed. This works because it mirrors how you actually make money. A lead comes in. You send an estimate. They say yes and you schedule it. You do the work and get paid. Each stage represents a real decision point where you either move forward or don't. A plumber with three crews running can track 30 active jobs across these four buckets and know exactly how many are in the field this week. You don't need anything fancier unless you're losing business because you can't see what's happening.
When you need five or six stages
Add detail when your jobs have real gaps between decisions. If you estimate, then wait a week for customer approval, add an 'estimate pending' stage. If jobs require site surveys or inspections before you can estimate, add a 'survey scheduled' stage. A roofing contractor might use: lead, survey completed, estimate sent, booked, in progress, completed. A general contractor taking on bigger residential projects might separate 'booked' into 'signed' and 'deposit received' because that deposit arriving is when you actually commit crew time. The rule: each additional stage should represent a point where your cash flow or resource planning changes. If it doesn't, don't add it.
Why more than six stages hurts you
Every stage you add is another place where a lead gets stuck. You assign someone to update status and they don't do it consistently. Now your pipeline is fiction. A concrete contractor with eight stages is spending 15 minutes a day moving jobs between 'concrete scheduled', 'concrete in prep', 'concrete in progress', and 'concrete curing'. That's time you could spend on pricing the next job. The overhead of maintaining visibility exceeds the benefit. If your jobs need that level of daily granularity, that's what your job site management and crew schedules are for—not your pipeline. Pipeline stages are for sales and resource decisions at the business level.
Track probability separately from stage
One mistake contractors make is trying to use pipeline stages to show deal confidence. Don't. A lead in the 'estimate sent' stage is 100% in that stage. It doesn't need a 10%, 50%, or 90% probability label next to it. You move stages only when something concrete changes. Instead, track probability as a property of the deal itself if you use CRM software. This keeps your pipeline clean and your forecast honest. You'll know that 40% of 'estimate sent' deals typically close, so five estimates out means two jobs booked. That's more useful than guessing which specific estimate is more likely.
Bottom line
Build with four stages and add one more only if you're losing clarity about cash flow or crew scheduling. Keep it simple—your brain will thank you when you glance at it between jobs.