A sales pipeline is useful when every open opportunity has an owner, a current stage, a next action, and a reason it can move forward. The system below is deliberately small: it gives a 5-to-50-person team enough structure to see work without turning the CRM into a second spreadsheet.
Outcome and scope
The goal is not to add every possible field. The goal is to make the next decision visible: qualify, schedule, propose, negotiate, win, or close. Use the workflow for new-business opportunities and keep post-sale delivery in the system that owns delivery.
Workflow map
- New: capture the source, contact, company, and reason for contact.
- Qualified: confirm the problem, fit, timing, and decision process.
- Discovery complete: record the agreed need and next meeting.
- Proposal: attach the scope, value, amount, and decision date.
- Negotiation: record the open issue and the person who can resolve it.
- Won or closed: record the outcome and a short reason.
Map stages to decisions, not optimistic percentages. A stage should answer what evidence is required before the opportunity advances.
Setup steps
- Write the stage definitions in plain language and assign one owner for each open deal.
- Create only fields that affect qualification, forecasting, handoff, or review.
- Set a required next-action date for every open opportunity.
- Define one place for activity notes and one place for the commercial decision.
- Run a weekly cleanup for stale, duplicated, or ownerless opportunities.
The Pipedrive guide to sales pipeline stages is a useful product-specific reference; adapt the labels to the team rather than copying a stage list without an owner.
Example fields or pipeline table
| Field | Example | Review question |
|---|---|---|
| Owner | Person accountable for the next action | Is ownership unambiguous? |
| Problem | One sentence describing the customer’s issue | Can another teammate understand the need? |
| Next action | Send scope draft by Friday | Is the action concrete and dated? |
| Decision date | 2026-09-15 | Is the date based on a customer event? |
| Close reason | Won, no decision, budget, or fit | Can the team learn from the outcome? |
Failure modes
- Too many stages hide the fact that nobody knows the next decision.
- Probability values become a substitute for evidence.
- Activities are logged but no owner or due date is recorded.
- Closed-lost reasons are free text and cannot be reviewed.
- The pipeline is cleaned only at the end of the month.
Metrics to review
Review a small set of operational measures each week: open opportunities without a next action, stage aging, new opportunities by source, conversion between adjacent stages, time to first response, and closed-lost reasons. These measures describe process health; they do not guarantee revenue.
FAQ
How many stages should a small team use?
Use the fewest stages that represent different decisions. If two stages require the same evidence and action, combine them.
Should every opportunity have a probability?
Only if the team has a defined method for setting and reviewing it. A probability number without evidence can create false precision.
When should a deal be closed?
Close it when the agreed decision window ends or the customer explicitly ends the process. Keep the reason so the team can distinguish timing from fit.
Leave a Reply