What is different in SaaS sales
A SaaS deal does not end at the signature. It starts there. The contract is small compared to its lifetime value, which means the sales process optimises for fit, not for squeezing the first invoice. That single fact changes how the CRM should be built.
The cycle is short and dense. A mid-market SaaS deal runs two weeks to two months, with a demo, a trial or pilot, a security review and a procurement step compressed into that window. Deals move daily, so stage definitions have to be sharp enough to survive daily movement. Vague stages that work for a slow consulting sale collapse here.
The buyer is usually a small committee. A champion runs the evaluation, a budget holder signs, and at larger customers IT or security gets a veto late in the process. Your pipeline needs to see that veto coming, because it is where most late-stage SaaS deals die.
And there are two motions, not one. New business brings logos in. Expansion and renewal keep the revenue. Teams that model only the first motion end up steering the company on half the picture.
An example SaaS pipeline
This is the new business pipeline we deploy most often for sales-assisted SaaS. Six stages, each tied to a buyer event you can verify.
| Stage | Exit criterion |
|---|---|
| Demo booked | Meeting on the calendar with the actual evaluator. |
| Demo held | Demo done, use case and team size confirmed on the deal. |
| Trial running | Workspace activated and at least one real user active. |
| Proposal sent | Pricing delivered, seats and term written on the deal. |
| Security and legal | Contract or DPA under review by the buyer's team. |
| Verbal agreement | Champion confirmed the yes. Only signatures remain. |
Renewals live in a second pipeline with three or four stages, created automatically ninety days before contract end. The principles behind this split are the same ones covered in our guide to pipeline design. Self-serve signups that never speak to sales stay out of both pipelines entirely and sit in the Leads inbox until a human qualifies them.
The fields and automations that matter
Keep the field list short and financial. MRR as a monetary field, contract term in months, seat count as a number, plan tier as a single option, and contract end date. Those five fields power every report a SaaS founder asks for. Add a churn reason field on the renewal pipeline and a lost reason on new business. Everything else should fight for its place, the test we describe in custom fields that earn their place.
Three automations pay for themselves in the first month. First, deal creation from product signups above a threshold, through the API. Second, the renewal generator: when a deal is won, create the renewal deal in the renewal pipeline with the value and the contract end date copied over. Third, a trial expiry countdown that creates an activity for the owner five days before a trial ends. Teams lose more trials to silence than to competitors.
Common mistakes
The most expensive mistake is reporting one-off deal values instead of recurring revenue. A €12,000 annual deal and a €12,000 one-off implementation look identical in a default setup, and every revenue report built on top is wrong. The MRR field plus a consistent rule for what the deal value holds fixes this on day one.
The second is letting self-serve noise flood the pipeline. Hundreds of free signups pushed in as deals bury the twenty real opportunities and destroy conversion metrics. Qualify in Leads, promote the few.
The third is skipping the security stage. Teams add it after their first big deal spends six silent weeks in legal review while the forecast said it would close. If deals above a certain size always hit procurement, the pipeline should say so.
The fourth is forecasting from gut-feel probabilities. SaaS cycles are short enough that stage conversion data becomes reliable within a quarter. Use it, as described in forecasting you can trust.