Best practice for deal post-sales status

[jons47]

Hello -

We have a SaaS business and we use HS to track deals from early stage until close. Once a deal is closed, there is an implementation process to get a new customer live with our product. We'd like to track how each deal is progressing in the implementation process in our CRM so we can understand areas where deals are getting stuck.

We thought having a second pipeline for integration, with the various integration milestones would be an elegant solution, but since the same deal can't be in two pipelines (a sales pipeline and an integration pipeline) this solution gets messy and overcomplicates our data. 

Wondering if it's best to create a cusom field with the various implementation steps. If we did that, is there a good way to create a pipleline style report that would show where deals our in our process?

Thanks in advance for your advice.

Thanks in advance for your advice. 

[webdew · Accepted solution]

Hi @jons47 ,

Yes, we cannot have one single deals in two pipelines so I will advise you to go fror your idea to create various properties for all the steps and update them according to the satges. While creating the deal pipeline and the stages, you can make those properties *Required: https://prnt.sc/1vtdk4s
https://www.loom.com/share/c53b75e424014cacb92b7da363fe172f

So when you will move the deal onto the next stage, it won't move untill and unless that property is updates. These properties will pop-up on the deal pipleine like this: https://www.loom.com/share/7f0555500b1c445c9aea8ebf42042072

Hope this helps!

If we were able to answer your query, kindly help the community by marking it as a solution.

Thanks and Regards.

[natsumimori]

Thank you @HubDoPete and @webdew for the insights! 

[HubDoPete · Accepted solution]

I agree with @webdew 

Add additional "won" stages to the pipeline, with properties seat as exit criteria for each stage.

Deal based workflows will allow you to set timers per stage, to take action if customers are getting stuck too long in a stage.

cheers

Pete

[webdew · Accepted solution]

Hi @jons47 ,

Yes, we cannot have one single deals in two pipelines so I will advise you to go fror your idea to create various properties for all the steps and update them according to the satges. While creating the deal pipeline and the stages, you can make those properties *Required: https://prnt.sc/1vtdk4s
https://www.loom.com/share/c53b75e424014cacb92b7da363fe172f

So when you will move the deal onto the next stage, it won't move untill and unless that property is updates. These properties will pop-up on the deal pipleine like this: https://www.loom.com/share/7f0555500b1c445c9aea8ebf42042072

Hope this helps!

If we were able to answer your query, kindly help the community by marking it as a solution.

Thanks and Regards.

[natsumimori]

Thanks for your post @jons47 !

@HubDoPete I'm wondering if you could weigh in here, would you mind sharing your thoughts for Jons?