i more or less am looking for feedback (since i have the WF built) but am still struggling a bit with the flow.
I have several WF, actually, that make this work but 2 main WF that i use for the new deal pipeline. ( i went from a simple 3 stage to a more complex one).
1-contact based that works off the lead status of the contact when they are in SQL stage (to progress lead status off of activity)
then
2-deal based WF journey that uses the above lead status to move the deal stages forward.
not sure if i created more work for myself so wanted to see how others progressed their deal stage journey. I thought using the contact lead status in SQL was one approach.
Happy to help here – for that I would need a bit more context.
Am I understanding your workflows correctly that you want to automatically update the lead status based on contact activity (wf1) and the deal stage of the lead status (wf2)? Could you elaborate why?
In most sales processes, the deal stage is updated manually by sales reps. It's not something that is automatically updated based on activity, as deal stage progression not only relies on activity but also checking against certain fit criteria (e.g. confirming BANT or MEDDICC).
In other words, there (typically) shouldn't be any scenario where the SQL stage overlaps with any deal stage.
The lead status (regardless of whether you're using the old contact property or the lead object) would be a sub-stage of the SQL stage only.
If your sales process is different to usual sales processes, could you elaborate on that and why activity alone would push records forward?
In general, using the contact lead status to move the deal stage forward is one approach, yes, but it would definitely be an unusual one and not quite according to HubSpot best practices.
Hope this helps!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Happy to help here – for that I would need a bit more context.
Am I understanding your workflows correctly that you want to automatically update the lead status based on contact activity (wf1) and the deal stage of the lead status (wf2)? Could you elaborate why?
In most sales processes, the deal stage is updated manually by sales reps. It's not something that is automatically updated based on activity, as deal stage progression not only relies on activity but also checking against certain fit criteria (e.g. confirming BANT or MEDDICC).
In other words, there (typically) shouldn't be any scenario where the SQL stage overlaps with any deal stage.
The lead status (regardless of whether you're using the old contact property or the lead object) would be a sub-stage of the SQL stage only.
If your sales process is different to usual sales processes, could you elaborate on that and why activity alone would push records forward?
In general, using the contact lead status to move the deal stage forward is one approach, yes, but it would definitely be an unusual one and not quite according to HubSpot best practices.
Hope this helps!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
thanks Karsten - that article from @@@frankstein is very helpful. I;ve read all i can and fully understand the process..and to your point, i cannot rely on my sales team to flag things which is why i wanted to automate the entire process...so my thought process is that i could use the contacts activity thru lead status to move the deal stages. it mostly works..with a few hiccups!
I was curious how it works - and you said mostly the sales rep moves the stages manually (which we cannot rely on that). If there is a better approach than using the contact lead status i am open to hearing that!! but i do need to automate the sale process.
thanks for the response. well, yes and no. i have other WF to push things along too that i found i need (like re-enollment, reset lead status to give it a push, etc = have gotten quite clever TBH) but have been looking on all the boards for what others have done. we only have 1 sales pipeline with 8 stages plus approval. getting it to flow was complex, which led me to believe there had to be another way - hence seeing what others have done. thanks for that article -