B2B SaaS Sales Pipeline Template
Built around the two things that actually decide a SaaS deal: whether the product got used, and whether procurement will let it through.
The stages
Each stage states what is true about a deal sitting in it, and the one testable thing that has to happen before it moves. If the exit criterion is not met, the deal does not advance, whatever the rep believes.
Qualified Lead
10% probability3 to 7 daysThe account matches your ICP on size, market and tech stack, and a real named person has responded to you. Nothing about their timing or budget is known yet.
A named contact has described a specific problem in their own words and a discovery call is booked in the calendar with a date, not a promise to find time.
Discovery
20% probability5 to 10 daysYou are on a call establishing what they do today, what it costs them, and who has to say yes. The product has barely been shown.
You have documented the tool or process being replaced, the metric they want to move with a current number attached, and the names and titles of everyone who signs off.
Demo and Solution Fit
35% probability7 to 14 daysThe product has been shown against their actual workflow, not a canned dataset. The champion is engaged and pulling colleagues in.
The prospect has confirmed the demoed workflow matches how their team works, and at least one stakeholder beyond your champion attended a session.
Trial or Pilot
50% probability14 to 30 daysThey are in the product with their own data. This is the stage where deals are really won or lost, and the one most teams fail to instrument.
The pilot has a written success metric, a start and end date, and at least three named users who have logged in more than once in the last seven days.
Business Case and Pricing
65% probability7 to 21 daysThe champion is selling internally. You are supplying the numbers, the plan comparison and the answers to the objections you will never hear directly.
The prospect has confirmed the budget owner by name, a budget range you can work inside, and a target go-live date.
Procurement and Security Review
85% probability10 to 45 daysCommercial terms are broadly agreed and the deal is now in the hands of people who did not attend any of your calls: legal, security, finance.
The security questionnaire is returned, DPA and MSA red-lines are resolved, and the contract sits with the named signer with a date they intend to sign.
Closed Won
100% probabilitySame daySigned. The only thing left is making sure the handover does not undo the momentum the pilot created.
Countersigned contract received, first invoice issued, and a kickoff call booked within ten business days of signature.
Fields worth tracking
Stages tell you where a deal is. These fields tell you whether it is any good. Add them as custom fields on the pipeline, and make the ones that gate a stage required.
The single best predictor of whether a SaaS deal closes. Replacing a paid incumbent means budget already exists. Replacing a spreadsheet means you are also selling the category.
A free text field forces the rep to write down what the pilot has to prove. Pilots without one drift into free usage and quietly expire.
Deals that need one take three to six weeks longer. Without this field your forecast dates are guesses and your quarter looks better than it is.
Lets you separate expansion potential from initial contract value, and stops the team pricing every deal from scratch.
Not the champion. The person whose budget it comes out of. If this field is empty past the demo stage, the deal is not qualified.
Automations worth building
A pipeline that only stores data is a spreadsheet with a nicer view. These are the three workflows that make this pipeline maintain itself.
When a deal moves to Trial or Pilot, auto-create the tasks for day 1 setup, day 7 usage check and day 21 results review, assign them to the AE, and start a check-in sequence to the champion. If the success metric field is empty, block the stage change.
Every stage has a healthy time-in-stage. Run a workflow that flags any deal sitting past that window, drops it into an at-risk view, and notifies the owner and their manager. Discovery deals get 10 days, procurement gets 45.
When the security review field flips to yes, automatically push the expected close date out by 21 days and attach your standard security pack to the record so the rep is not hunting for it.
Common mistakes with this pipeline
The demo is the most expensive thing you do and the easiest to give away. Running it before the economic buyer is named produces a pipeline full of enthusiastic champions with no budget, which is how forecast accuracy dies.
A pilot without a written success metric and an end date is not a sales stage, it is a free account. Deals sit there for months because nobody agreed what a pass looks like, and the champion has nothing to take to their boss.
If probability is editable per deal, it stops meaning anything and your weighted forecast becomes a mood ring. Fix the probability to the stage, and let stage movement be the only way the number changes.