Start with a simple set of stages: Lead, Qualified, Proposal, Negotiation, Won or Lost. Then pick one revenue stream and write one pass/fail criterion for every stage. That single exercise gives you faster follow-up, because everyone knows what "next" means, and clearer forecasting, because a deal sits in a stage only when it has earned it.
TL;DR:
- Give every stage an entry rule, one exit proof, minimal required fields, a completed activity, and one named owner; advance deals only when evidence exists.
- Use Lead, Qualified, Proposal, Negotiation, and Won or Lost for a team; solo operators can use three stages, while complex commercial sales may need more.
- Start with example close weights of 10% at Qualification, 60% at Proposal, 80% at Verbal Commitment, and 100% at Won; revise them using monthly results.
- After lead conversion, confirm one opportunity owner, a dated next activity, and converted status; use deduplication rules to prevent duplicate records.
- Build separate stage views for each record type, assign new leads automatically, and create tasks or reminders when deals enter stages or stall.
Table of Contents
- What pipeline stages are and why clear stage design matters
- How to map stages with entry and exit criteria
- Practical stage names and example stage sets
- Measuring stages: probabilities, forecasting, and hygiene metrics
- Implementing stages in your CRM, step by step
- Handoff and ops: what changes when a lead converts
- Quick checklist and copy-ready criteria templates
- Why scoped, security-first automation gets used
- How we can help you design and automate your pipeline stages
- FAQ
- Sources
What pipeline stages are and why clear stage design matters
A lead is an early-stage prospect. An opportunity is a qualified deal. In Salesforce terminology and common CRM practice, converting a lead typically creates account, contact, and opportunity records and transfers key fields and ownership so the sales team can work the deal.
Clear stages matter because they turn a vague pile of inquiries into a process you can manage:
- Consistent qualification: every lead is judged by the same rules, not by whoever answered the phone.
- Fewer missed follow-ups: each stage implies a next action and an owner.
- Cleaner forecasting: you can see how many deals sit at each point and how long they stay there.
- Easier handoffs: an owner-led shop and a larger team both know who holds the deal.
This guide assumes the sales you run are estimates, scheduled services, and quotes, where a person asks for a price and you decide whether and how to pursue it.
How to map stages with entry and exit criteria
Every stage needs a gate: the evidence, document, or completed activity required to move forward. Use this template for each one:
- Entry rule: what must already be true when a deal arrives (for example, a phone number and a described problem).
- Exit rule: the one proof that lets it advance (a booked estimate, a sent quote, a spoken yes).
- Required fields: keep them minimal: contact name, phone or email, service type, estimated value, owner, next activity date.
- Required activity: log at least one completed action, such as a call or visit, before changing the stage.
- Owner: one named person, never "the team."
Here is a short example for a roof repair. The lead is "Lead" until someone confirms the address and the leak. It becomes "Qualified" once an onsite estimate is booked. It moves to "Proposal" only when the written quote is sent with a value attached.
Pro Tip: If you cannot say what proof moves a deal forward, the stage is a label, not a stage. Rewrite it or cut it.
Practical stage names and example stage sets
Pick the smallest set that still shows you where deals stall.
- Short set (solo owner, small team): Lead → Quote sent → Won/Lost. Fast and hard to misuse.
- Team set (office plus field crew): Lead → Qualified → Proposal → Negotiation → Won/Lost. Our default recommendation.
- Enterprise set (multiple estimators or commercial work): Lead → Qualified → Site visit → Proposal → Internal review → Verbal commitment → Won/Lost.
The trade-off is simple. Fewer stages give clarity and speed. More stages give granularity when several people touch one deal.
A home-services example maps like this: lead → onsite estimate → proposal → scheduled → closed. It mirrors how the job actually happens, so crews and office staff read it without training.
Measuring stages: probabilities, forecasting, and hygiene metrics
Assign each stage a close probability so your open pipeline becomes a forecast. Salesforce's own guidance suggests planning every opportunity stage with a close probability, for example Qualification 10%, Proposal/Review 60%, Verbal commitment 80%, Closed won 100%, while keeping the stage count low.
Use that mapping as a model, then replace the percentages with your own history. A deal at the Proposal stage contributes its value multiplied by the example probability to a weighted forecast.
Four hygiene metrics keep the pipeline honest:
- Lead response time
- Conversion rate per stage
- Average stage age
- Activity completion rate
For deeper forecasting ideas, this pipeline analytics playbook pairs well with the weights above. Review probabilities monthly, comparing each stage's weight to what actually closed.
Implementing stages in your CRM, step by step
- Create the stage picklist values using your chosen set.
- Add a probability percentage to each stage.
- Reorder stages so they run left to right in the order work happens.
- Create a sales process or filtered view for each record type, so estimates and recurring services each see only their own stages.
- Add automations: assignment on new leads, a follow-up task when a deal enters a stage, and a reminder when a deal sits too long.
For assignment, our post on round-robin lead assignment walks through testing the rules before you trust them.
Pro Tip: Auto-name opportunities with the customer and service type, such as "Garcia: water heater replacement." Reports become readable without opening a record.
Handoff and ops: what changes when a lead converts
At conversion, the CRM creates account, contact, and opportunity records. Check three things every time:
- Owner: the opportunity has one named owner, and it is the person who will do the next step.
- Next activity: a dated task exists, not just a note.
- Converted status: the original lead is marked converted so it never appears in two lists.
Set an ownership rule, such as the estimator who booked the visit keeps the deal, and a follow-up service level, such as prompt first contact. A 15-minute response target for lead capture is a stricter option for inbound calls and web forms.
The most common failure is duplicate records. Prevent it with dedupe rules and a required next-activity field. Our guide to setting quality rules before you merge covers this.
Quick checklist and copy-ready criteria templates
- Pick one revenue stream.
- Choose a stage set.
- Write criteria for each stage.
- Set probabilities.
- Build it in your CRM.
- Test with 10 leads.
Three pass/fail templates to paste in:
- Qualification: pass if the caller has a described problem, a service address, and a budget or timeline. Fail otherwise.
- Proposal sent: pass if a written quote with a total price went to the decision maker.
- Verbal commitment: pass if the customer said yes and named a start window.
Run the setup, then review conversion rates and stage ages and adjust.
Pro Tip: Enrich thin records before testing. Our lead data enrichment test shows what a clean match looks like.
Why scoped, security-first automation gets used
Here is our opinion: stage rules fail because people route around them, not because the design was wrong. Automations get adopted when a build is scoped in writing, owned by one accountable technical lead, and easy to roll back if it misfires. Documentation and least-privilege access mean the automation touches only the data it needs. Those are checkable claims about how we work, and they are why teams trust enforced stages instead of resenting them.
— Felix
How we can help you design and automate your pipeline stages
We build the stage system with you, then wire it into your daily work. Equinox Strategies offers:
- Lead generation
- AI voice and messaging agents
- Done-for-you automations
- The operating system underneath
- Custom software from client briefs
The outcome you should expect is faster lead response, consistent qualification, and fewer missed follow-ups, because every stage has an owner and a next step. Current pricing details are on our website. The next step is a scoping call: tell us your revenue stream and your current stages, and we will map criteria, probabilities, and automations at Equinox-strategies.
FAQ
How many stages should a service business pipeline have?
The right number of stages depends on how the business works and how many people handle each deal. Fewer stages keep the process clear, and Salesforce's guidance on opportunity stages recommends minimizing the stage count. Add more only when several people touch the same deal.
What is the difference between a lead and an opportunity?
A lead is an early-stage prospect you have not yet qualified. An opportunity is a qualified deal worth working, and converting a lead creates the account, contact, and opportunity records.
How do I choose pipeline stage names?
Use plain verbs and nouns your crew already says, such as "Estimate booked" or "Quote sent." Keep one name per stage across every report and record type.
What should I do with stalled leads?
Flag deals that exceed your average stage age and trigger a follow-up task or automated reminder. If there is still no response after a set number of attempts, move the deal to Lost with a reason, so you can re-engage it later.