Nice work on RevOps.FM, Justin! I am enjoying it and it is always nice to hear your voice!
This episode with Charlie Saunders is very interesting. In order to use a CO like this to track multiple (concurrent) product lifecycles, I think a method is required to represent and interact with duplicate records and statuses in SFDC. Perhaps that was out of the scope of this conversation, but I am interested in your thoughts.
So nice to hear from you Shannon. I hope you and all the pups are doing well :)
So your point is absolutely correct.
If I understand the CS2 solution correctly, there can be multiple lifecycle journeys but only a single active lifecycle at any one time. Each lifecycle record in the custom object is controlled by the standard lead/contact status field (or, in later funnel stages, by the stage of the associated opportunity).
In this model, a new lifecycle begins only after the previous active one reaches a natural conclusion (either with a closed won opp or by going to a terminal status like "Disqualified" or "Recycled".
We did do a project in 2016 back at Perkuto with a requirement for multiple concurrent lifecycles across different product lines.
It introduced a lot more complexity as the sales interface needed to be customized so that the sales reps could interact with each of those lifecycle journeys independently, essentially manipulating the status of the custom object records directly (I believe we used task records in lieu of a custom object in that solution).
Interesting! Good luck :) It was very complex 8 years ago. Hopefully there are simpler ways of achieving it now. Certainly customizing the interface is way easier with Lightning, and many things are possible with Flows that should require less Apex coding.
Nice work on RevOps.FM, Justin! I am enjoying it and it is always nice to hear your voice!
This episode with Charlie Saunders is very interesting. In order to use a CO like this to track multiple (concurrent) product lifecycles, I think a method is required to represent and interact with duplicate records and statuses in SFDC. Perhaps that was out of the scope of this conversation, but I am interested in your thoughts.
So nice to hear from you Shannon. I hope you and all the pups are doing well :)
So your point is absolutely correct.
If I understand the CS2 solution correctly, there can be multiple lifecycle journeys but only a single active lifecycle at any one time. Each lifecycle record in the custom object is controlled by the standard lead/contact status field (or, in later funnel stages, by the stage of the associated opportunity).
In this model, a new lifecycle begins only after the previous active one reaches a natural conclusion (either with a closed won opp or by going to a terminal status like "Disqualified" or "Recycled".
We did do a project in 2016 back at Perkuto with a requirement for multiple concurrent lifecycles across different product lines.
It introduced a lot more complexity as the sales interface needed to be customized so that the sales reps could interact with each of those lifecycle journeys independently, essentially manipulating the status of the custom object records directly (I believe we used task records in lieu of a custom object in that solution).
Yes, exactly! I have studied your TDD on that project. :) A lot of orgs are looking for multi-product lifecycles lately. All the options are complex.
Interesting! Good luck :) It was very complex 8 years ago. Hopefully there are simpler ways of achieving it now. Certainly customizing the interface is way easier with Lightning, and many things are possible with Flows that should require less Apex coding.