# A SaaS sales process: evidence at each transition

> A sales-process review asks what buyer evidence justifies each stage and how commitments survive the handoff. Review the situation, the decisions and the limits before applying the pattern.

Source: https://saas-marketing.net/examples/saas-sales-process-teardowns/
Topic: SaaS Sales
Type: example
Published: 2026-09-17
Last updated: 2026-09-17
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/examples/saas-sales-process-teardowns/

## Short answer

A sales-process review asks what buyer evidence justifies each stage and how commitments survive the handoff.

## Key takeaways

- Stages should describe meaningful progress in the buying process, not only completed seller activities.
- Do not advance a deal solely because a demo happened if the buyer has not agreed on a next step.
- Separate a visible example or constructed scenario from evidence of causal business results.

---

Use this example alongside the [saas sales guide](/saas-sales/). The purpose is to make a decision inspectable, not to promise that copying an asset will reproduce another company's results.

## The situation

A hypothetical account moves from discovery to evaluation and commercial review.

## Work through the decisions

### Discovery

Confirm the problem and relevant participants.

### Evaluation

Agree on success criteria and inspect product fit.

### Commercial review

Resolve pricing, procurement and implementation responsibilities.

| Review point | Observation or decision |
| --- | --- |
| Discovery | Confirm the problem and relevant participants. |
| Evaluation | Agree on success criteria and inspect product fit. |
| Commercial review | Resolve pricing, procurement and implementation responsibilities. |

## The useful lesson

Stages should describe meaningful progress in the buying process, not only completed seller activities.

Before applying the pattern, write down which part of your customer situation is similar and which part is different. A tactic that helps one segment can create friction for another when buying complexity, product readiness or implementation work changes.

## The limit of the example

Do not advance a deal solely because a demo happened if the buyer has not agreed on a next step.

An example can demonstrate a mechanism or a presentation choice without proving commercial performance. Keep that distinction when sharing it with colleagues. If a numerical result is important to the decision, obtain the original evidence and preserve the population, time period and method used to calculate it.

## Adapt the pattern

1. Choose one relevant customer task and define the outcome you want to improve.
2. Use the [working resource](/templates/saas-sales-playbook-template/) to describe the proposed change and required evidence.
3. Confirm that the product and operating team can deliver the promise in the actual customer path.
4. Review a representative case, record the result and decide whether another test or a wider rollout is justified.

Keep the initial scope bounded. A useful exercise ends with a clearer decision and an owner for the next action, even when the conclusion is that the pattern does not fit your business.

## Related reading

- [Choosing a SaaS sales model by ACV](/guides/saas-sales-models-by-acv/)
- [Self serve sales and when to add humans](/guides/self-serve-saas-sales/)
- [Inside sales for mid market SaaS](/guides/inside-sales-for-saas/)
- [The enterprise SaaS sales process](/guides/enterprise-saas-sales-process/)
- [SaaS selling strategies that move deals](/guides/saas-selling-strategies/)

Browse [more worked examples](/examples/) and the [resource library](/resources/) for adjacent tasks.
{/* expanded-practice-2026-09 */}
## Apply a saas sales process: evidence at each transition in a working review

Separate the observed or constructed situation from the inference you draw from it. Identify the mechanism, the conditions that made it relevant and the circumstances in which it would not transfer. A useful example helps a reader reason about their own case; it does not promise that copying the surface appearance will reproduce the same outcome.

For this topic, involve the sales owner and the buyer’s relevant decision participants and work from discovery notes, stage evidence and the next agreed action. The relevant unit is one qualified opportunity with a current buying process. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

### Evidence to prepare

Use buyer evidence to define progression. A completed seller task, such as a proposal or presentation, is not the same as a buyer commitment. Preserve the customer’s actual question and unresolved dependencies so follow-up can help rather than repeat the pitch.

| Review field | What to record |
| --- | --- |
| Topic | A SaaS sales process: evidence at each transition |
| Decision | The specific action this explanation should help you choose |
| Working evidence | discovery notes, stage evidence and the next agreed action |
| Unit and scope | one qualified opportunity with a current buying process |
| Responsible people | sales owner and the buyer’s relevant decision participants |
| Remaining uncertainty | The missing fact that could change the decision |

### Two situations that can change the interpretation

#### When stages advance on seller activity alone

A completed proposal is a seller output; a confirmed review process is evidence about the buyer's next step.

Use this check: Compare stage criteria with observable buyer commitments and unresolved requirements. A buyer's polite interest is not the same as approval, budget or implementation readiness.

The [focused diagnostic guide](/guides/sales-stage-advances-without-buyer-evidence/) provides the correction process and a working evidence sheet.

#### When a proposal omits implementation ownership

A contract for software access does not automatically resolve data preparation, training or integration responsibilities.

Use this check: List customer and vendor responsibilities, prerequisites, acceptance criteria and support boundaries. Do not create delivery commitments without the responsible team's agreement.

The [focused diagnostic guide](/guides/sales-proposal-has-no-implementation-owner/) provides the correction process and a working evidence sheet.

### Record the decision and the limit

An opportunity with a named technical review and an agreed next meeting is different from one with a favorable comment and no decision path. Both can remain in the CRM, but forecasting and follow-up should reflect the evidence actually available.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the [complete topic collection](/topics/saas-sales/) for related methods and the [category field guides](/industries/) when the product's buying situation or implementation requirements change how the method should be applied.

## Frequently asked questions

### What does this example demonstrate?

Stages should describe meaningful progress in the buying process, not only completed seller activities.

### What should not be inferred from it?

Do not advance a deal solely because a demo happened if the buyer has not agreed on a next step.

### How can I apply the example to my own product?

Identify the matching customer situation, verify the required capability and run a bounded test. Record the differences between your case and the example before adopting the approach.

### Are numerical scenarios measured customer results?

Constructed scenarios and illustrative numbers are labelled as such. Public-site observations describe visible material and do not establish internal budgets, conversion rates or causal revenue outcomes.