Most pipelines fail on one thinking error: they map what the team does, not what the customer decides. A stage called "proposal sent" tells you nothing about whether the deal is closer to closing. "Proposal reviewed" does.
Step by step
- Phrase stages from the customer sideEach stage describes a state on the customer side, not a task on yours. So: contact made, needs qualified, proposal reviewed, decision pending, won. Five to seven stages are almost always enough.
- Create the pipelineOpen the opportunities area, create a new pipeline and give it a clear name. If you sell different offers, each one gets its own pipeline instead of a single catch-all with twenty stages.
- Define the exit criterionFor every stage it must be clear how you know it is complete. Write it down. Without that criterion, two team members will move the same card to different places.
- Add deal valuesEnter the expected value on every opportunity. Only then does your pipeline become a revenue forecast instead of a card collection.
- Connect automationLink stage changes to workflows: moving to "proposal reviewed" starts a follow-up sequence, moving to "won" starts onboarding.
Tip: Keep a "lost" stage with a reason. After three months you will know exactly why business fails instead of guessing.
Common issues
All cards sit in the same stage. Usually the stage is defined too broadly. Split it up or sharpen the exit criterion.
The pipeline is not maintained. Almost always a sign that it is too complex. Fewer stages, clearer criteria.
What comes next
To fill the pipeline automatically you need a funnel that captures inquiries and a workflow that responds instantly.
Was this article helpful?