During a HubSpot training session with BluePoint, the team identified a structural problem: both Lifecycle Stage and Lead Status were in active use, creating redundant data entry and reporting confusion. The agreed resolution was to adopt Lifecycle Stage as the single source of truth for the sales funnel and deprioritize Lead Status.
This article documents the rationale, the agreed stage structure, and the implementation steps taken during and after that session.
BluePoint's HubSpot instance had contacts tracked across two overlapping fields:
Lead Status — being used to track sales progress (e.g., "Proposal Presentation")Lifecycle Stage — a core HubSpot property designed for exactly that purpose, but not consistently populated or visible in the sidebarThis created friction: reps were updating Lead Status without touching Lifecycle Stage, which meant automations and reports built on Lifecycle Stage were firing on incomplete data.
"The lifecycle stage is the way all your automations and stuff are going to fire off of this field or off of this property."
— Mark Hope, training session
The team agreed to:
Lifecycle Stage to the primary contact property — move it to the top of the sidebar panelLead Status — leave it in place temporarily to avoid disrupting existing records, but stop actively using it for new contactsDisqualified as a custom stage to Lifecycle Stage, so contacts who should be excluded from campaigns have a formal status rather than being left in an ambiguous stateThe Disqualified option was added directly to the Lifecycle Stage property during the session and placed at the end of the stage order.
| Stage | Notes |
|---|---|
| Subscriber / Prospect | Rename "Subscriber" to "Prospect" — contacts from lists or events not yet qualified |
| Lead | Actively being worked |
| Marketing Qualified Lead (MQL) | Meets partial BANT criteria |
| Sales Qualified Lead (SQL) | Meets full BANT criteria |
| Opportunity | Proposal has been made |
| Customer | Closed/won |
| Evangelist | Optional — not actively used by BluePoint |
| Disqualified | Custom addition — removes contact from active campaigns |
The BANT framework (Budget, Authority, Need, Timeline) was discussed as the qualifying logic for moving contacts from Lead → MQL → SQL.
Lifecycle Stage property added to the contact sidebar panel via Actions → Customize PropertiesDisqualified option added to the Lifecycle Stage propertyNote: HubSpot allows each user to customize their own sidebar view. Mark's changes may not have propagated to Wade's view automatically. Mike was assigned to verify alignment.
Lifecycle Stage is visible and correctly positioned in Wade's sidebar viewLifecycle Stage valuesLifecycle Stage as a visible column alongside Contact TypeLifecycle Stage answers where is this contact in the sales process?
The separately created [1] answers what kind of contact is this? (Lead, Customer, GPO Partner, Vendor). The two fields are complementary and intended to be used together for segmentation and campaign targeting.
The Disqualified lifecycle stage is a key exclusion trigger for BluePoint's planned drip campaigns. Contacts marked Disqualified should be explicitly excluded from enrollment in both the traditional ATM and reverse ATM drip sequences. See [2] for campaign structure details.