[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cms-entry-blog-how-to-define-sales-pipeline-stages-en":3},{"message":4,"data":5,"success":42},"OK",{"id":6,"entry_type":7,"locale":8,"slug":9,"title":10,"summary":11,"body":12,"blocks":13,"author_name":14,"published_at":15,"updated_at":15,"data":16,"category":17,"tags":18,"related":19,"alternates":32,"seo":37,"cover":17,"media":41,"preview":40},38,"blog","en","how-to-define-sales-pipeline-stages","How to Define Sales Pipeline Stages: 5 Steps with Exit Criteria","Tie stages to customer behaviour, give each a written exit criterion and correct probabilities with your real win rate. A sample B2B pipeline and checklist.","A sales pipeline is the list of stages a deal goes through from first contact to signature. When stages are not clearly defined, the same deal shows up as \"proposal\" for one rep and \"negotiation\" for another; forecasts miss and managers cannot tell which deals need their help.\n\nThis post explains how to define stages, which **exit criterion** to give each one, and the common mistakes teams make in the first months.\n\n## 1. Tie stages to the customer's behaviour, not the seller's\n\n\"Preparing a quote\" is an internal task; a stage should change when something happens on the customer's side, such as \"The customer confirmed the requirement in writing\" or \"The quote reached the decision maker\". That way two reps put the same deal in the same stage.\n\n## 2. Five to seven stages are enough\n\nFor most B2B teams this structure is a good starting point:\n\n| Stage | Exit criterion (to move to the next one) |\n|---|---|\n| Prospecting | First conversation with the right person held |\n| Qualification | Budget, authority, need and timing confirmed |\n| Needs analysis | Scope agreed in writing |\n| Proposal | Priced quote reached the decision maker |\n| Negotiation | Commercial terms under discussion, objections known |\n| Won \u002F Lost | Order or rejection received in writing |\n\nThe more stages you add, the less reps update them; the fewer you have, the less managers can see.\n\n## 3. Give each stage a probability — but don't trust it blindly\n\nStage probabilities (for example 60% at proposal) are the basis of the forecast. Use them as assumptions for the first three months, then adjust them to your **actual win rate**. Measuring the win rate requires recording the outcome and reason of every closed deal; we cover that in [win\u002Floss reason analysis](\u002Fen\u002Fblog\u002Fwin-loss-reason-analysis).\n\n## 4. Prevent stage skipping with required steps\n\nIf deals move from qualification to proposal without a known budget or decision maker, the pipeline gets inflated. Define one or two **required steps** per stage (e.g. \"Budget and authority confirmed\") and don't allow progress until they are done.\n\n## 5. Make stalled deals visible\n\nA deal that has stayed in a stage twice as long as average is usually already lost. Discussing only those deals in the weekly meeting saves time and keeps the pipeline clean.\n\n## In CRModular\n\nUnder **Settings → Sales Path** (Ayarlar → Satış Yolu) you define guidance text and required steps for every stage; a deal whose required step is not done cannot move to the next stage. Probability is filled in automatically when a stage is selected, and deals can be followed in table, Kanban and calendar views. See the help article [Sales process: stages and reasons](\u002Fen\u002Fhelp\u002Fsales-process-stages-and-reasons) for setup, and the glossary entry [Sales pipeline](\u002Fen\u002Fglossary\u002Fsales-pipeline) for a short definition. The application interface is currently in Turkish.\n\n## Quick checklist\n\n- Are stages tied to customer behaviour?\n- Does every stage have a written exit criterion?\n- Have probabilities been compared with the real win rate?\n- Are deals that sit in a stage for too long discussed every week?",[],"CRModular","2026-10-06T22:11:51.268Z",{},null,[],[20,24,28],{"slug":21,"title":22,"summary":23,"entry_type":7},"dealer-price-list-management","Dealer Price List Management: 5 Rules That Protect Your Margin","Price books by customer group, quantity and discount limits per product, tiered pricing and approved exceptions. A practical guide for distributors and wholesalers.",{"slug":25,"title":26,"summary":27,"entry_type":7},"turning-support-emails-into-cases","Turning Support Emails into Cases: 6 Steps from Shared Inbox to Numbered Tickets","Turn support emails into numbered cases: one address, replies kept in the same case, customer matching, SLAs, rule-based assignment and replying from the case.",{"slug":29,"title":30,"summary":31,"entry_type":7},"win-loss-reason-analysis","Win\u002FLoss Reason Analysis: What Lost Deals Can Teach You","A closed reason list, three required fields on every loss and the same four questions each month. A practical way to separate losses due to price, competitors and missing follow-up.",[33,34],{"locale":8,"slug":9},{"locale":35,"slug":36},"tr","satis-hunisi-asamalari-nasil-tanimlanir",{"title":38,"description":39,"canonical_url":17,"noindex":40,"og_image":17},"How to Define Sales Pipeline Stages (with Examples) | CRModular","Define sales pipeline stages with exit criteria: a sample B2B pipeline table, stage probabilities, required steps and a checklist for stalled deals.",false,{},true]