The design rule: stages should change what happens next
- Use meaningful customer states, not staff activity
- Keep sales and fulfillment separate when they serve different jobs
- Use opportunity status for Open, Won, Lost, or Abandoned outcomes
- Give every stage an owner and a next action
- Automate only from stages the team can maintain reliably
A useful pipeline is usually simpler than the first version people imagine. Create a stage only when being in that stage changes how the team should treat the opportunity, what information matters, or what automation should happen next. Do not create a new stage for every phone call, voicemail, email, task, or internal note. Those are activities. The stage should describe the opportunity’s current business state.
Pipeline stage and opportunity status are not the same thing
| Concept | What it should answer | Example |
|---|---|---|
| Pipeline | Which business process does this opportunity belong to? | Sales, Fulfillment, Past Customer Nurture |
| Stage | Where is it inside that process? | New Lead, Estimate Sent, Scheduled |
| Status | What is the overall outcome state? | Open, Won, Lost, Abandoned |
| Activity | What did a user or automation do? | Called, sent email, left voicemail, added note |
Keeping those concepts separate makes reporting and automation easier to reason about.
What the Carmil Car Audio pipeline shows
Clear, meaningful stages made it possible to trigger estimate follow-up and review requests directly from stage changes, instead of relying on someone remembering to send a message. Read the case study →