Sales and marketing disagreeing about lead quality is not a relationship problem. It is a structural one, and your HubSpot lifecycle stages are almost certainly at the centre of it.
This article walks through how to define lifecycle stages, set qualification rules, and assign ownership so both teams are working from the same revenue model, not two competing versions of it.
Why sales and marketing keep arguing about lead quality (and why your CRM is partly to blame)
The next step for your RevOps strategy
FAQs
Ask most revenue teams where a lead becomes an MQL (a Marketing Qualified Lead, meaning one that meets the criteria to pass from marketing to sales) and you will get a different answer from every person in the room. Marketing says it is when someone downloads a guide. Sales says that has never meant anything. RevOps is not sure what is in the CRM.
That disagreement is not a personality clash. It is a structural problem. When your HubSpot lifecycle stages are undefined or applied inconsistently, the CRM cannot tell either team what is actually happening. Marketing reports on leads generated. Sales reports on pipeline. Neither number connects to the other.
So sales blames marketing for sending over contacts who will never buy. Marketing blames sales for ignoring good leads. Both are probably right, and both are probably wrong. The real issue is that no one agreed on the rules before the contacts started flowing in.
A shared lifecycle model fixes this. Not a workshop, not a values exercise. A structural fix: clear definitions, written into your CRM, with ownership assigned at every stage. That is what this article is about.
The starting point is agreeing on what each stage actually means. HubSpot's default lifecycle stages, Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, and Evangelist, are a framework, not a finished model. Most B2B revenue teams need to define the entry and exit criteria for each stage explicitly, in writing, before they configure anything in the platform.
The MQL definition is where most teams fall apart. Marketing tends to define it behaviourally: a contact who has engaged enough to warrant sales attention. Sales tends to define it by fit: a contact who matches the ideal customer profile. Both perspectives are valid. Neither is sufficient on its own. A workable MQL definition combines a fit threshold (industry, company size, role) with a behavioural threshold (specific actions taken, lead score reached). When both conditions are met, the contact moves. When only one is met, it does not.
The Sales Qualified Lead (SQL) definition matters just as much. An SQL is a contact that sales has reviewed and accepted as worth pursuing. Some teams insert a Sales Accepted Lead (SAL) stage between MQL and SQL to create an explicit handoff moment: marketing passes the lead, sales reviews it, and either accepts it into the pipeline or returns it with a reason. That return loop is critical. Without it, rejected leads disappear and marketing never learns why.
Once definitions are agreed, the next step is encoding them. HubSpot workflows can automate lifecycle stage progression based on contact properties, deal creation, form submissions, and lead score thresholds. Automation removes the manual inconsistency that corrupts most CRM data over time. A contact who hits the MQL criteria moves to MQL automatically. A contact associated with a created deal moves to Opportunity. The CRM reflects reality rather than whoever last touched the record.
One configuration decision that trips up many teams is the relationship between lifecycle stage and lead status. In HubSpot, lifecycle stage tracks where a contact sits in the overall revenue funnel, from first touch to customer. Lead status tracks where a contact sits within the sales process specifically: New, Attempting to Contact, Connected, Open, Unqualified. The two properties work together but serve different purposes. Lifecycle stage is a marketing and RevOps reporting tool. Lead status is a sales workflow tool. Conflating them produces reporting that satisfies neither team.
Ownership is the third pillar. Every stage needs a named owner, not a team, a role. Marketing owns contacts from Subscriber through to MQL. Sales owns contacts from SAL through to Opportunity. RevOps owns the rules themselves: the definitions, the automation logic, and the SLA that governs how quickly sales must act on an MQL before it is returned or escalated. Without an SLA, the handoff is a suggestion. With one, it is a commitment both teams have agreed to.
The question of whether lifecycle stages can move backwards is worth addressing directly. HubSpot's default behaviour prevents lifecycle stages from moving backwards automatically, meaning a contact who reaches SQL will not revert to MQL through a workflow. That is intentional: backward movement corrupts historical reporting. If a contact goes cold or is disqualified, the right response is to update lead status to Unqualified and log a reason, not to reverse the lifecycle stage. If the contact re-engages months later, a deliberate workflow or manual update can move them forward again from a defined re-entry point.
Syncing lifecycle stages across contacts, companies, and deals is another area where configuration choices have downstream consequences. HubSpot associates contacts with companies and deals, but lifecycle stage is a contact-level property by default. For B2B teams selling to accounts rather than individuals, it is worth considering how company-level lifecycle stage should reflect the aggregate status of associated contacts. Some teams use a custom company property to track account stage separately. Others rely on deal stage as the primary account-level signal. Either approach works, but the choice needs to be deliberate and documented.
Revenue reporting is the payoff. When lifecycle stages are defined consistently, applied automatically, and owned clearly, the CRM produces reports that both teams trust. Marketing can show how many MQLs converted to SQLs and at what rate. Sales can show how many SQLs progressed to Opportunity and closed. RevOps can model the full funnel, identify where volume drops, and make a case for where to invest. That is the shared revenue model the argument about lead quality was always really about.
If you are not sure whether your current HubSpot setup supports this kind of reporting, a CRM health audit is usually the fastest way to find out. It surfaces the gaps in your lifecycle configuration before they become gaps in your revenue data. For a broader look at how CRM architecture decisions affect your go-to-market model, the piece on the architecture question every marketing agency and RevOps team faces is worth reading alongside this one.
A lifecycle stage model only works if it is built on definitions that sales and marketing have genuinely agreed to, encoded in the CRM, and governed by clear ownership and SLAs. The configuration is not the hard part. The hard part is getting the definitions right before you build anything. If your team is ready to do that work properly, Velocity can help you design a lifecycle framework that holds up under real commercial pressure, and implement it in HubSpot so it runs without manual intervention. Talk to the team at Velocity Digital.
HubSpot lifecycle stages are a contact property that tracks where a person sits in your revenue funnel, from first touch through to customer and beyond. The default stages are Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, and Evangelist. Each stage can be progressed manually or automatically via HubSpot workflows based on criteria your team defines. The property is designed to give marketing, sales, and RevOps a shared view of funnel progression, but it only delivers that value when the entry and exit criteria for each stage are clearly documented and consistently applied.
Lifecycle stage tracks a contact's overall position in the revenue funnel, from first awareness through to closed customer. Lead status tracks where a contact sits within the active sales process: New, Attempting to Contact, Connected, Open, or Unqualified. Lifecycle stage is primarily a marketing and RevOps reporting tool. Lead status is a sales workflow tool that helps reps manage their day-to-day activity. The two properties complement each other but should not be used interchangeably. Conflating them produces reporting that is difficult to act on for either team.
A workable MQL definition combines a fit threshold with a behavioural threshold. Fit criteria typically include firmographic data such as industry, company size, and job title. Behavioural criteria include specific actions taken, such as content downloads, page visits, or lead score thresholds reached. An SQL is a contact that sales has reviewed and accepted as worth pursuing, often formalised through a Sales Accepted Lead stage that creates an explicit handoff moment. The definitions should be written down, reviewed jointly by sales and marketing, and encoded in HubSpot so that progression is automated rather than left to individual judgement.
HubSpot's default behaviour prevents lifecycle stages from moving backwards automatically through workflows, which protects the integrity of historical reporting. If a contact is disqualified or goes cold, the correct response is to update their lead status to Unqualified and log a reason, rather than reversing the lifecycle stage. If the contact re-engages at a later date, a deliberate workflow or manual update can move them forward again from a defined re-entry point. This approach keeps your funnel data clean and ensures that stage progression reflects genuine commercial movement rather than administrative corrections.
RevOps teams should structure lifecycle stages so that each one maps to a measurable conversion event, not just a vague description of intent. Each stage needs defined entry criteria, a named owner, and an SLA that governs how quickly the owning team must act before escalation. Automation via HubSpot workflows should handle routine progression so that the data reflects reality rather than whoever last touched the record. When this is in place, the CRM can produce funnel reports that show conversion rates at every stage, giving RevOps the data needed to identify where volume drops and where investment will have the most impact.