Set yourself up for long term success with a solid B2B Lifecycle program. Not only does it help you exert control and mastery over your reporting, it provides a framework for having tough discussions between sales & marketing.
It opens up career opportunities – average salary according to glassdoor and others for lifecycle marketing manager is $80-$120K – yeah, you unlock big value for your own career.
This topic is too big for a single post, so here’s what’s in store:
- This episode, episode 1: the what & why of lifecycle
- Episode 2: How to avoid overthinking implementing a lifecycle
- Episode 3: How to design a basic lifecycle that actually works
- Episode 4: Picking the right MQL & scoring model for lifecycle
- Episode 5: No sales people were harmed in the making of lifecycle
Traditionally, a lot of companies refer to leads as if you’re taking their temperature. Hot medium and cold leads.
The system isn’t really based off of metrics and is not an effective way to sort leads for sales. There’s no consideration for a lead’s progression from first visit to conversion then to customer.
In this scenario, marketing and sales often clash because there’s no system in place to create alignment. Sales isn’t tackling leads in the most optimal way. Marketing is generating leads that sales might not care about.
What is lifecycle, JT? How do you define it?
Lifecycle is the journey contacts in your database take to become a customer. It mirrors your typical funnel journey and operates in much the same way. Unlike funnel, lifecycle is a bit more specific to conditions in your database.
Your funnel has basic stages that describe the buyer’s journey: awareness through interest, evaluation, purchase, etc.
They are totally compatible! But lifecycle requires data properties or fields in your marketing automation platform to track.
Everyone gets lost in acronym land. Enterprise teams largely follow the standards from the SiriusDecisions waterfall model. What are the standard stages as you see it, and do you think they have to be customized/adapted for each company?
Let’s run through them quick:
- Lead – Yeah, someone in your database
- MQL – a marketing qualified lead — literally exactly as it sounds — marketing qualifies leads
- SAL – sales accepted lead – leads that sales agrees to work with
- SQL – sales qualified – leads that sales qualifies – common in team where front-line sales reps qualify leads to send to account executives
- Opportunity – it’s got an open opportunity
- Customer – they’ve purchased!
Of course, you can do whatever you want! I’m not your mother!
This is a cross section of the database. To me, this is table stakes for any MAP.
Benefits are huge but can be summed up in two points:
- Mastery over your contact DB
- A common language for sales & marketing
So I’m putting my startup hat on, maybe the ops person on that team is wearing many other hats and doesn’t have time to build all these fields and time stamps and create all this alignment. If you don’t have the cycles, at least start with a master lifecycle lists. Some kind of way to get a sense of what stage people are in your db. Because this is a big project, there’s no getting around that.
Multiple teams agreeing on definitions and standard operating procedures. So like every problem, there’s a systems and tech side, how to implement what’s possible, but there’s the human side, if we build this, will it be used, is this helping people? Do people even want this?
What makes this project so hard?
Lots of stakeholders, the people side is so much harder. Lots of things that need to be agreed upon. Can be sprawling and daunting if your DB is a mess. Needs long term follow up after deployment to be successful.
Traditional sales folks who have a process that works well enough often see this as as theoretical or not as important as revenue driving activities. One thing I’ll say here is that this can never be pitch as a marketing idea, it can never be pitched as a top down initiative. This has to be something that is built through the alignment of sales and marketing. Dual buy-in, common languages.
Why on earth should anyone take on this project?
JT, I know you’ve done this in Marketo and HubSpot for clients and in-house — it’s potentially a huge project… Why on earth should anyone take on this project?
It’s 101 for anyone looking to go deep into marketing operations and opens up a super cool avenue for your career. It will allow you to attain mastery over your database. It opens up career opportunities – average salary according to glassdoor and others for lifecycle marketing manager is $120K – yeah, you unlock big value for your own career.
Set yourself up for long term success with a solid Lifecycle program. Not only does it help you exert control and mastery over your reporting, it provides a framework for…
It is so easy to go down rabbit holes when revamping or deploying a lifecycle model. Be very careful not to overthink your lifecycle by creating too many microstages, or…
It’s hard to even know where to start. Even after you get everyone to agree on a model and stages, you need to figure out how to deploy this thing.…
You need a good MQL model so that marketing leads make it to sales and get followed up. There are a lot of ways to define MQLs and pass them…
Every Mops/CRM needs lifecycle in some form or another to function optimally. You cannot make lifecycle work long term if you don’t partner with sales, not dictate to them, not…
<< Previous episode
Next episode >>
- December 2023
- November 2023
- October 2023
- September 2023
- August 2023
- July 2023
- June 2023
- May 2023
- April 2023
- March 2023
- February 2023
- January 2023
- June 2022
- May 2022
- April 2022
- September 2021
- August 2021
- July 2021
- June 2021
- May 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- November 2020
- October 2020
- September 2020
📫 Never miss an episode or key takeaway 💡
By subscribing to our newsletter we’ll only send you an email when we drop a new episode, usually on Tuesday mornings ☕️ and we’ll give you a summary and key takeaways.
Future-proofing the humans behind the tech