I am a little bit confused how to set up a lead as qualified since the same action is repeated across multiple records in Hubspot. HubSpot's default suggestions are:
- SQL as a lifecycle stage
- Qualified to buy as a deal stage
same as
- Connected as a lead status - Appointment scheduled
It seems like that one of them is redundant. I'm debating whether I need to remove SQL as a lifecycle stage completely or keep and just start my Deal pipeline stage from 'Demo completed'>>'Qualified to buy'.
There are many things to consider when making decisions about lifecycle stage management, but it is really important not to conflate lifecycle stages with deal stages, since they are not the same thing. Deal stages represent where you are in your current sales process, while lifecycle stages present where you are in your relationship with the contact (person).
The most important thing to remember is that while lead statuses and deal stages can be changed forward and backward and repeated over and over again, a lifecycle stage should only move forward and does not repeat.
In other words, your contact becomes an SQL when they have been qualified by a salesperson for this first time, and never again.
You might qualify that same contact as the lead for several different deals over their lifetime in your HubSpot database. Some of those qualifications might happen much later in their lifecycle, while they are an customer or evangelist, for example.
I hope this helps explain the difference. If you had access to workflows I might potentially recommend using automation to automatically set the Lifecycle Stage to "SQL" when the deal stage reaches "Qualified to Buy" but that isn't available with Starter.
- Trevor If my post solves your problem, please accept it as a solution.
I work with many clients and each has a different process, but you are correct that in most cases a deal is created at the opportunity stage.
How MQL and SQL are defined varies somewhat from client to client, but here is a rough definition:
MQL: A contact that has been identified by marketing as ready to talk to sales, either because they completed a "Contact Us" or "Demo Request" (aka "Hand Raiser" form, or because they completed a top of funnel form and then interacted with enough content to demonstrate clear interest (evaluated using the HubSpot Score property.)
SQL: A contact who has been initially qualified by a salesperson. In many cases this means that the SDR or Salesperson has made contact by phone or email, received a response, and scheduled a Discovery meeting.
Opportunity: The initial discovery meeting has taken place and the contact has met the qualifying criteria, such as BANT (Budget, Authority, Need, Timing).
At this point, a deal is created. If timing is not right, but the other criteria exist, the contact stays in SQL and is nurtured by the salesperson until the timing is right.
Your qualification criteria may be different of course, but this is the sort of thing I see most often.
- Trevor If my post solves your problem, please accept it as a solution.
There are many things to consider when making decisions about lifecycle stage management, but it is really important not to conflate lifecycle stages with deal stages, since they are not the same thing. Deal stages represent where you are in your current sales process, while lifecycle stages present where you are in your relationship with the contact (person).
The most important thing to remember is that while lead statuses and deal stages can be changed forward and backward and repeated over and over again, a lifecycle stage should only move forward and does not repeat.
In other words, your contact becomes an SQL when they have been qualified by a salesperson for this first time, and never again.
You might qualify that same contact as the lead for several different deals over their lifetime in your HubSpot database. Some of those qualifications might happen much later in their lifecycle, while they are an customer or evangelist, for example.
I hope this helps explain the difference. If you had access to workflows I might potentially recommend using automation to automatically set the Lifecycle Stage to "SQL" when the deal stage reaches "Qualified to Buy" but that isn't available with Starter.
- Trevor If my post solves your problem, please accept it as a solution.
Shouldn't a lead be moved through SQL in order to even start and set Opportunity stages?
What stage would you recommend starting a deal pipeline with? We usually determine if there's an opportunity after a discovery call/intro. However, I'm unsure if I should include this as part of the deal stages, since many leads are disqualified after the first call.
I work with many clients and each has a different process, but you are correct that in most cases a deal is created at the opportunity stage.
How MQL and SQL are defined varies somewhat from client to client, but here is a rough definition:
MQL: A contact that has been identified by marketing as ready to talk to sales, either because they completed a "Contact Us" or "Demo Request" (aka "Hand Raiser" form, or because they completed a top of funnel form and then interacted with enough content to demonstrate clear interest (evaluated using the HubSpot Score property.)
SQL: A contact who has been initially qualified by a salesperson. In many cases this means that the SDR or Salesperson has made contact by phone or email, received a response, and scheduled a Discovery meeting.
Opportunity: The initial discovery meeting has taken place and the contact has met the qualifying criteria, such as BANT (Budget, Authority, Need, Timing).
At this point, a deal is created. If timing is not right, but the other criteria exist, the contact stays in SQL and is nurtured by the salesperson until the timing is right.
Your qualification criteria may be different of course, but this is the sort of thing I see most often.
- Trevor If my post solves your problem, please accept it as a solution.
Our team doesn't have SDRs, so the initial qualification is performed by AE. This is why I am considering performing BANT qualification during the SQL stage when a discovery/demo call happens.
Would these pipeline stages make sense:?
Demo completed Proposal sent Negotiating Contract sent Closed won Closed lost