A pipeline should answer three questions: what has happened, who owns the opportunity, and what needs to happen next. Start with those questions before adding custom fields and automations.
Use stages that represent real events
A practical starting point is new inquiry, contacted, qualified, appointment booked, estimate sent, and won or lost. Adapt the stages to your sales process. A plumbing dispatch team may need fewer stages than a remodeling company.
Write the rule for moving each stage
Decide what evidence moves an opportunity forward. An appointment is booked when the time is confirmed, not when a scheduling link was sent. An estimate is sent when the customer actually received the proposal.
Require an owner and a next action
Assign each active opportunity to a person and record the next action with a due date. When ownership changes, transfer the context as well as the record. A stage name alone cannot tell a colleague what to do.
Automate the routine work
Create tasks when estimates go out, reminders before appointments, and alerts for unassigned leads. Add one workflow at a time and test replies, cancellations, and duplicate inquiries. Leave judgment calls with the team.
Connect source data carefully
Record where the inquiry came from when that information is available. Distinguish a captured campaign source from a source reported by the customer. Keep unknowns visible instead of assigning credit without evidence.
Review what gets stuck
Look for stages where opportunities have no action, incomplete details, or repeated delays. Ask the people doing the work why those records stall. Simplifying a handoff may be more useful than adding another reminder.
A quick review
- Stages reflect observable events.
- Every active opportunity has an owner.
- Next actions have due dates.
- Won, lost, and opt-out states stop follow-up.
- Unknown attribution stays marked as unknown.
See how we approach CRM and sales automation and lead response.