Most sales pipelines are a collection of opinions. One rep calls something a discovery call. Another rep calls the same conversation a proposal. The forecast then averages across both and produces a number nobody trusts.
This post walks through a clean 7 stage pipeline template, what each stage actually means, the exit criteria that move a deal forward, and how to build the same model in Salesforce. The Excel version is free to download at the end.
Why most pipeline templates fail
Pipelines fail in three predictable ways.
First, the stages are vague. "Discovery" can mean anything from a first call to a fully scoped requirements doc. So reps log deals at whatever stage feels good that week.
Second, there are no exit criteria. A deal slides from one stage to the next because the rep moved it, not because anything specific happened. The result is a pipeline that looks healthy and a forecast that misses by 30 percent.
Third, the pipeline lives somewhere reps do not work. A spreadsheet on a shared drive is a snapshot of a moment. By the next forecast call it is already wrong.
A good template fixes the first two problems with discipline. The third problem only gets fixed when the pipeline lives in your CRM. We cover both below.
The 7 stage pipeline at a glance
The template uses seven stages.
- Lead
- Qualified
- Discovery
- Proposal
- Negotiation
- Closed Won
- Closed Lost
For each stage the template captures three things: what is true when a deal enters the stage, what should be true before it exits, and the exit criteria that mark the gate.
This is the part most templates skip. Without the exit gate, stages are decoration.
Stage 1: Lead
What is true. A name, a company, and a reason to believe this account fits your ICP. Maybe a form fill, an inbound demo request, or an outbound reply. No conversation has happened yet.
What should be true before exit. A real person at the account has agreed to a first call and held it. You know their role and a rough version of why they responded.
Exit criteria. First meeting held, contact confirmed as the right starting point, ICP fit revalidated.
Common failure mode. Reps mark inbound leads as Qualified before any conversation. The pipeline inflates. The forecast drifts.
Stage 2: Qualified
What is true. You have had a first call. There is a real problem the buyer has acknowledged. The account is in your ICP for size, vertical, and tech stack.
What should be true before exit. You have confirmed there is some kind of budget or budget process, a rough timeline, and at least one other stakeholder who will be involved. You have a documented pain.
Exit criteria. Pain is documented in the CRM. At least one secondary contact is identified. The buyer has agreed to a discovery session with a defined agenda.
Common failure mode. "Qualified" becomes a parking lot. Deals sit here for 90 days because nobody wants to disqualify them and nobody is doing the work to advance them.
Stage 3: Discovery
What is true. You are running a structured discovery process. Multiple stakeholders are participating. You are mapping the problem, the current state, and the impact of doing nothing.
What should be true before exit. You have a clear picture of the buying committee. You know the metric the buyer is being measured on. You have a champion who will sell internally on your behalf. The economic buyer is identified, even if you have not met them yet.
Exit criteria. Champion confirmed. Economic buyer identified. Use case and success metric agreed in writing or on a recorded call. Decision criteria captured.
Common failure mode. Discovery turns into a feature dump. The rep demos product instead of mapping pain. Deals advance to Proposal without a champion and stall.
Stage 4: Proposal
What is true. A formal proposal or scoped offer has been delivered. The buyer has the document, the price, and the proposed scope. They are reviewing it internally.
What should be true before exit. You have walked the proposal through with the champion and at least one decision maker. You have surfaced the objections that will come up in the negotiation. You know the procurement and legal path.
Exit criteria. Proposal acknowledged. Internal review meeting confirmed. Procurement timeline mapped. Mutual action plan or close plan in place.
Common failure mode. "Sent the proposal" becomes the proxy for stage. The rep loses visibility into who is actually reviewing it. The deal goes dark.
Stage 5: Negotiation
What is true. Pricing, terms, and scope are being actively negotiated. Procurement is involved. Legal redlines are flowing. The buyer wants to do the deal.
What should be true before exit. All commercial terms are agreed. Legal is on a path to signature. The implementation path is defined. The economic buyer has confirmed budget release.
Exit criteria. Final terms accepted. Order form or contract sent for signature. Implementation kickoff date discussed.
Common failure mode. Endless redlines with no signature in sight. Reps discount in advance of asks instead of trading. Deals slip a quarter.
Stage 6: Closed Won
What is true. Contract is signed. Revenue is bookable. Implementation is starting.
What should be true before exit. A clean handoff to customer success or onboarding. The promises made in the sales process are documented. The first 90 day plan exists.
Exit criteria. Contract executed. Handoff meeting completed. Customer success owner assigned.
Common failure mode. The sales rep disappears at signature. Onboarding inherits a vague brief. The customer experience starts on a bad note.
Stage 7: Closed Lost
What is true. The buyer chose a competitor, chose to do nothing, or the deal stalled out. You are not getting it this cycle.
What should be true before exit. You have logged the reason in a structured field, not a free text note. You have a reengagement date if appropriate. The full account history is captured.
Exit criteria. Loss reason logged from a fixed list. Reengagement timing set or marked dead. Lessons logged for the deal review.
Common failure mode. Loss reasons become free text. Nobody can roll up loss data. The same patterns repeat for years.
What the Excel template includes
The downloadable template has four tabs.
Pipeline. One row per opportunity. Columns for account, stage, amount, close date, days in stage, next step, and exit criteria checks.
Stage definitions. A reference tab with the seven stages, the entry conditions, the exit criteria, and the typical conversion rate from each stage to the next.
Velocity. A simple calculator that turns your stage data into a velocity number. Average deal size times win rate divided by sales cycle length.
Forecast. A weighted forecast view. Each stage gets a probability. The sheet rolls up commit, best case, and pipeline coverage.
It is a working template, not a polished BI dashboard. The point is to force the right conversations during the weekly pipeline review.
Building the same pipeline in Salesforce
Spreadsheets are useful for design. They are bad for execution. The same model belongs in your CRM where reps already work.
Here is the rough build.
Stages. Configure the Opportunity object to use the seven stages. Set probabilities per stage. Mark the Closed Won and Closed Lost stages explicitly.
Required fields per stage. Use validation rules or path guidance to require specific fields before a stage moves forward. For example, Champion field required before exiting Discovery. Loss reason picklist required for Closed Lost.
Exit criteria checklist. Use Salesforce Path or a custom checklist component to display the exit criteria for the current stage on the opportunity record. Reps see what is missing before they try to advance the deal.
Stage age. Add a formula field that calculates days in current stage. Use it on the pipeline list view. Anything sitting more than 1.5x its average dwell time is a flag.
Reports. Build three core reports. Pipeline by stage. Stage conversion over time. Aged opportunities by owner.
This is the foundation. Account plans, relationship maps, and mutual action plans layer on top of this foundation. That is where deals are actually advanced.
Pipeline review cadence
The template assumes a weekly pipeline review and a monthly forecast call.
In the weekly review, work the top 10 deals. For each one, ask three questions. Are the exit criteria met for the current stage? What is the next event that moves the deal? What is blocking it?
In the monthly forecast call, work the rollup. Compare commit to coverage. Look at stage distribution. Flag any rep whose pipeline is too top heavy or too bottom heavy.
The template is a tool. The review is where it earns its keep.
Common pitfalls to avoid
A few things to watch for as you roll this out.
Do not change stage definitions mid quarter. You will lose the ability to compare period over period.
Do not let probabilities drift. If a stage shows 60 percent close rate in your historical data, do not let your reps argue it should be 80 because their deal is special.
Do not skip the loss review. Closed Lost is the stage with the most learning per dollar invested. Treat it as a signal source, not a graveyard.
Do not expect a template to fix a discipline problem. The template gives you the structure. The leadership conversation is what makes it stick.
Download the template
Get the free Excel sales pipeline template with all seven stages, exit criteria, velocity calculator, and weighted forecast view. Use it as a starter or as a design doc for your Salesforce build.
Download the sales pipeline template
Related reading
Bring this into Salesforce with CRUSH
A pipeline template is the start. The deals inside it move when account plans, relationship maps, and mutual action plans are tied to the opportunity record.
CRUSH lives natively in Salesforce. Your pipeline, the strategic plan behind every account, and the close plan for every deal sit on the same record reps already work from. No tab switching. No stale spreadsheets.
