Goal:
HubSpot users should be able to be restricted when moving deals between stages. Let’s say you have a Sales Pipeline with stages like “Qualified Prospect”, “1st Meeting”, “2nd Meeting”, “Proposal Given”. You shouldn’t be able to move a deal from Qualified prospect to 2nd meeting as there must have been a 1st meeting between.
Why is this good?
As HubSpot’s deal funnel analytics works the same way it would be more accurate and this way sales people would be incentivized to update their own deals more frequently. JIRA has a similar option although it’s for a different purpose, it would fit how HubSpot’s pipelines work.
How to create this option?
Admin users will want every kind of restrictions, not just the one where you can only put a deal to the next or previous deal stage. As a user experience on where to add this to HubSpot I would suggest adding this option to the Deal Settings page (where you are able to edit deals and create automation for them).
I would change the “Delete” button to “Actions” and add this functionality as a possible action to choose which deal stage the deal can move to from its current deal stage.
To add to this, I’d like to see a way of restricting permission from moving deals between certain stages all together. Some of the portals I work with run mostly off of APIs/workflows, so the deal stage changes through setting a deal property to the correct criteria (rather than click and dragging).
I agree that this would be a very helpful feature.
Often there are different job junctions involved further in the pipeline, and clients have requested for only users part of the Finance team to be able to move a deal to closed-won for instance, once they see the amount reflect in the financials.
Agreed, good feature. I’d also like to reststric backwards movement through the pipeline. For example, if you have a “Demo Completed” and a “Proposal Sent” stage, once the deal has been moved to “Proposal Sent”, it would not be able to move back to “Demo Completed” without admin privledges.
It’s definitely a must have when you have API-driven pipelines to guarantee data synchronization.
That would be great to have limitations on property changes for each pipeline.
e.g. : for my transactionnal pipeline, I don’t want my Reps to be able to change the deal properties (included the stages) but they are able to log calls, …
e.g.2 : for my prospecting pipeline, my Reps are free to create all the opportunities they want