A stage name alone does not change what reps do. The CRM has to ask for the evidence.
Why a name is not enough
Rename “Proposal” to “Solution validated” and nothing happens. A rep can still drag the deal to that stage with nothing behind it. In Name your stages for what the buyer did, each stage has a buyer exit and a record that proves it. This post is about the next step: making the CRM ask for that record. The rule behind it is in No proof, no move.
Build order
Build in this order:
- Fields first. The evidence has to exist as a field or a record before any stage can ask for it.
- Stages second. Each stage asks for the fields that prove its exit.
- Automations last. Stall alerts and tasks only make sense once the stages are real.
Then test with three dummy deals before go-live. Move one without the evidence and see whether the CRM stops you. Move one with the evidence. Then bring one in a side door, such as an import or a workflow, and see what happens. Redwater Integration, my fictional drone maker, might require a “Budget confirmed” field before a deal can enter its proposal stage. The third dummy deal tells you whether that rule holds when the deal does not come through the front door.
What each CRM says
I checked these on November 5, 2026, against each vendor’s own help pages. The dates are the dates the pages show. Menus and plans change, so confirm in your own account. I am not affiliated with any of these vendors.
HubSpot. On a pipeline stage you can set up conditional stage logic, which shows properties when users manually create a record in a stage or move it there. You tick Required, and HubSpot says users cannot create or update the record until they set a value for it. That page says it was last updated September 29, 2026. It names no plan for this feature, so check your plan.
HubSpot’s separate page on pipeline rules, last updated September 9, 2026, says deal approval cannot be bypassed, but all other pipeline rules can be bypassed by Super Admins or users with Edit property settings permissions, by records created or edited by workflows, and by records created or edited by the API. It also says deal approval needs a Sales Hub Enterprise subscription. That page is about pipeline rules, and the Required behavior above is described for manual changes. HubSpot does not say in so many words that conditional Required properties can be bypassed, so test yours.
For stall alerts, HubSpot’s page on stage calculated properties, last updated July 15, 2026, says to trigger on “Date entered current stage” or “Time in current stage.” It says records currently in a stage will not enroll in workflows based on “Cumulative time” or “Latest time in” for that stage.
Salesforce. Salesforce’s page on creating a Path says each step can show up to five key fields and up to 1,000 characters of guidance, “to help users focus.” It describes them as a focus aid and does not say they enforce anything. Its page on path considerations says you can’t use the page layout to require different fields in different steps, but you can set up validation rules based on a path step. It also says validation messages appear as page-level messages, even if you set them to show near the fields. Neither page shows a revision date. Check your edition before you build.
Pipedrive. Pipedrive’s page on required fields, last updated November 4, 2026, says users won’t be able to move a deal to a new pipeline stage until they fill in the missing required field. It also says the feature won’t stop deals from progressing if the fields are updated by import, bulk editing, the API, automations or third-party integrations. It says the feature is only available on Premium and higher plans, and that only global admin users with account settings access can set it up. Plan names change, so check yours. The page also points to “important fields” for drawing attention to a field without making it mandatory.
The catch
Rules can be bypassed. HubSpot and Pipedrive both say so for some kinds of update, as above. A CRM rule makes the right thing easier. It does not make it certain. So keep the weekly inspection. For every open deal, ask four questions:
- What buyer action moved this deal into its current stage, and where is it recorded?
- Is it past the max-days trigger? If yes, what is the next buyer action and its date?
- Which buyer roles are still missing on the deal?
- Does the close date match a date the buyer agreed to, or one the rep hopes for?
If a field cannot be made required in your CRM, put it in this weekly check instead.
The free stage definition one-pager (opens in a new tab) is the short version of the stage idea. The Sales Process Blueprint has the build sheet, the stress test and the weekly inspection page.
I’m Seth Levanen. I find the AI shortcuts that keep the quality and drop the busywork. Email me if you want to talk about it.