
Sign up to save your podcasts
Or
Okay, you’ve got everyone to agree on a flow chart; you look like a wizard for building it all out, now the easy part, right?
Is it the easy part?
It should be the easy part but what I’ve often seen is that folks deploying lifecycle are doing it for the first time; often they are unsupported except some high level guides from vendors. Once you get it down, it can be highly formulaic.
As a marketer, you’re kind of in between your data team/revops/IT/bizops and sales, your end users. I see the role bridging the gap between was possible on the tech side and balancing what the end user wants, not always sales, sometimes marketing.
But it can be stressful managing these projects. Some companies have massive programs that are triggered off of lifecycle stage changes. So what’s the formula?
First, you need strong stage definitions. Hand-in-hand with this is knowing what constitutes a transition. I think the transition part of lifecycle is often where people get hung up.
Mechanism for transition needs to be a data signal of some sort. Moving from Marketing side of the fence to Sales side needs a clear hand off.
3 typical mechanisms for transitioning records are:
Question - You’ve talked to me quite a bit about the difference between lifecycle stages and contact statuses. This can be super confusing to folks new to automation. What’s the difference and why’s it important?
Lifecycle Stage = Roadmap
Contact Status = Traffic lights
One of the big value points of deploying a solid lifecycle is reporting. What are you doing during set up to make sure your reporting is top-notch post deployment?
How simple is all this really? I mean, once you know your way around lifecycle, it’s actually not that hard to deploy?
In terms of a technical problem, it’s a solved problem. You can mix and match components, and tailor things to your needs. The real challenge will always be getting buy-in:
Thanks for listening! Make sure you check out part 1 and 2 in the previous two episodes and stay tuned for part 4 and 5.
If you absolutely can't wait 7 days for the next episode, we'll give you a super secret link to unpublished episodes if you sign up for new episode notifications here humansofmartech.com.
--
Intro music by Wowa via Unminus
Podcast artwork font by StarJedi Special Edition by Boba Fonts
5
55 ratings
Okay, you’ve got everyone to agree on a flow chart; you look like a wizard for building it all out, now the easy part, right?
Is it the easy part?
It should be the easy part but what I’ve often seen is that folks deploying lifecycle are doing it for the first time; often they are unsupported except some high level guides from vendors. Once you get it down, it can be highly formulaic.
As a marketer, you’re kind of in between your data team/revops/IT/bizops and sales, your end users. I see the role bridging the gap between was possible on the tech side and balancing what the end user wants, not always sales, sometimes marketing.
But it can be stressful managing these projects. Some companies have massive programs that are triggered off of lifecycle stage changes. So what’s the formula?
First, you need strong stage definitions. Hand-in-hand with this is knowing what constitutes a transition. I think the transition part of lifecycle is often where people get hung up.
Mechanism for transition needs to be a data signal of some sort. Moving from Marketing side of the fence to Sales side needs a clear hand off.
3 typical mechanisms for transitioning records are:
Question - You’ve talked to me quite a bit about the difference between lifecycle stages and contact statuses. This can be super confusing to folks new to automation. What’s the difference and why’s it important?
Lifecycle Stage = Roadmap
Contact Status = Traffic lights
One of the big value points of deploying a solid lifecycle is reporting. What are you doing during set up to make sure your reporting is top-notch post deployment?
How simple is all this really? I mean, once you know your way around lifecycle, it’s actually not that hard to deploy?
In terms of a technical problem, it’s a solved problem. You can mix and match components, and tailor things to your needs. The real challenge will always be getting buy-in:
Thanks for listening! Make sure you check out part 1 and 2 in the previous two episodes and stay tuned for part 4 and 5.
If you absolutely can't wait 7 days for the next episode, we'll give you a super secret link to unpublished episodes if you sign up for new episode notifications here humansofmartech.com.
--
Intro music by Wowa via Unminus
Podcast artwork font by StarJedi Special Edition by Boba Fonts
38,560 Listeners
77,717 Listeners
30,723 Listeners
32,081 Listeners
30,252 Listeners
55,980 Listeners
7,009 Listeners
9,503 Listeners
26,938 Listeners
57,326 Listeners
648 Listeners
28,554 Listeners
11 Listeners
1,365 Listeners
19,352 Listeners