Salesforce Opportunity Stage Flow: Exit Criteria Guide

The idea behind this project is to make it clear to reps which fields need to be filled out as exit criteria for certain opportunity stages. This helps reduce time spent in the CRM and, in many cases, replaces some validation rules making the process easier to manage. This also helps leadership ensure that all necessary data is captured at each stage. Less validation rules = less complex and prescriptive process = better data hygiene.

1. Introduction to the Project

• Description: The project consists of building a screen flow that’s triggered by a button on the opportunity page. Depending on the opportunity’s stage, the flow will display different screens. Each screen will show the fields required as the exit criteria for that specific stage.
  
• Problems that this solves:
  - Bad Data Hygiene
  - Uncertainty of the fields the rep needs to fill before moving to the next stage
  - Hard to find fields to fill
  
• Definition of success: Our goal is to reach a stage where sales reps are fully trained and aligned on the exit criteria for each stage of the process. At that point, we will be consistently tracking and improving KPIs such as data quality, CRM adoption, and efficiency. Ultimately reducing the time spent in the system and driving stronger operational performance. The reps should feel like Salesforce is a tool that works for them and helps them know what to focus on next rather than just another data entry chore.

2. When to Implement?

Examples

Client states that may trigger the project (pain points): 

• Low rep engagement and reluctance to spend time in the CRM.
• Inconsistent understanding of exit criteria across opportunity stages.
• Excessive validation rules creating friction within the system.
• Lack of clarity around which fields must be completed at each stage.
• Limited understanding of the purpose and meaning of specific fields.
• Sales reps are not consistently completing the required fields.

When is the right time to implement this project (prerequisites): 

• Team alignment on exit criteria for each stage.
• Shared understanding of the meaning of every required field.
• Clear definition of which specific opportunity data points should be tracked and reported.
• Clarity around the overall data structure.

3. KPIs

CRM Adoption
If the project is well implemented and sales reps are properly trained, there is significant potential for stronger CRM adoption. This results in higher data quality and ensures that reps are more aligned with the meaning of each stage.

Stage / Forecast Accuracy
With greater confidence that opportunities are placed in the correct stages, it becomes easier to analyze sales cycle length, identify stalled opportunities, and ultimately improve forecast accuracy.

Number of Coaching Opportunities Identified
With improved data quality in our opportunities, we can identify patterns and uncover what top-performing reps are doing differently. This enables us to provide targeted coaching and upskill the entire team, driving overall performance improvements.

4. Client Roles Involved

‍Sales Ops
This role would be involved because, if any errors come up, this person can usually fix them as long as they’re not too complex. On top of that, they play a key role in training and supporting the reps throughout this process transition.

Sales Leadership
Sales leadership needs to be involved because their perspective helps make several decisions easier to reach. In addition, we need their input to understand what information needs to be reported.

Sales Reps (BDRs, SDRs, etc…)
These roles are especially central to this project. It’s important to note that the key KPIs here are CRM adoption, number of coaching opportunities identified, and reduced time spent on the CRM. On top of that, the reps will be using this project on a daily basis.

5. Tools

Salesforce
The project will primarily leverage Salesforce Flows, with some custom fields being developed as well. However, the core of the initiative will be centered around a Screen Flow.

Lucid Chart/Miro
Tools like Miro or Lucidchart can be highly valuable in this project, particularly for aligning processes across the team, as well as supporting other strategic initiatives.

6. Questions before Implementation

Need to Know Before Starting the Project

• What is the main goal behind this project? Is it data quality, sales process compliance, or something else?
• How standardized is your sales process across different opp types, teams, regions, or verticals/industries?
• For each opportunity stage, what are the exit criteria that a rep must complete before moving forward?
• Are there any fields that must be filled at specific stages — or are they just recommended?
• Should we block the stage from being changed if certain fields are missing? Or just display a warning?
• Are there any differences in required fields based on record type, product, industry, or region?
• Do reps currently struggle to know what to fill out during the sales process?
• Have your sales reps already used screen flows before? Are they comfortable with guided flows?
• Do you have any dashboards or reports today that rely on the accuracy of these fields?
• Do managers regularly review data completeness or pipeline stage hygiene?
• Do you want this flow to run only in Lightning, or should it also be mobile-friendly?
• Are there any automations or validation rules today that might conflict with this flow?
• Who will be our main point of contact for developing the UX/UI? (Sales Rep Champion)
• Which fields are critical in current opp reporting?

‍

7. Additional Details and Context

• Always review validation rules before building the flow.
• Ensure there are no upcoming changes planned for the opportunity stages. If there are, discuss rolling this out along-side those stage changes.
• You need to make sure reps are fully aligned on what each stage represents and which questions should be asked at each step of the sales process.
• We need to make sure we highlight that this is a project requiring rep training, and it’s usually best to have that planned out before the project even begins.

‍

8. Step by Step

Simple step by step summary:

1. Discovery

A. Map validation rules
B. Get all of the questions in Section 6 answered
C. Align with the client on the definitions, exit criteria, and required fields for each stage

2. Build it

A. With all the mapping done the building shouldn't be that hard

3. Test it

A. We need to test it with our Sales Rep Champion with real life experiences.
B. Do a video and train reps
C. Make sure to have reports for us to track if the flow is getting used properly

9. Possible Problems

Problem 1

Record ID: the problem is that if you write the variable in the wrong way the Id doesn't get stored on this variable and then it won't update the opportunity. If this problem happens you will see in the debug if the variable got set with the Id of the opportunity or if its null
Solution: the solution is always to have the recordId variable with this nomenclature: recordId (lowercase ‘r’, capital ‘I’)

Problem 2

Validation Rules can cause a lot of problems so please map out everything.
Solution: Planning very well can solve this. Study and map their validation rules and what they are doing and match with the process that they will do in the flow.

Problem 3

If Reps are not well trained on this project it can feel as micromanagement or more work for them to do
Solution: We need to usually convince reps that we are doing this to save them time and not to give them more work to do.

10. Summary

List of possible next steps:
- Data quality dashboard for opp stage
- Reports to identify coaching opportunities
- Stalled opportunities notifications

• Recurring or follow-up tasks generated:
  Quarterly/yearly feedback sessions, exit criteria optimizations, data audits.

When should you revisit this? Probably you should revisit this in 3 ~ 6 months and make sure that reps adopted it and that it’s being used right.