BluepointATM — Lifecycle Stage Strategy
Overview
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.
The Problem: Dual-Field Confusion
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 sidebar
This 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 Decision: Lifecycle Stage as Single Source of Truth
The team agreed to:
- Elevate
Lifecycle Stageto the primary contact property — move it to the top of the sidebar panel - Deprioritize
Lead Status— leave it in place temporarily to avoid disrupting existing records, but stop actively using it for new contacts - Add
Disqualifiedas a custom stage toLifecycle Stage, so contacts who should be excluded from campaigns have a formal status rather than being left in an ambiguous state
The Disqualified option was added directly to the Lifecycle Stage property during the session and placed at the end of the stage order.
Agreed Stage Structure
| 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.
Implementation Steps
During the Session
Lifecycle Stageproperty added to the contact sidebar panel via Actions → Customize PropertiesDisqualifiedoption added to theLifecycle Stageproperty- Change applied globally (affects all contact records, not just the one being edited)
Note: 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.
Post-Session (Assigned to Mike Stebbins)
- Verify that
Lifecycle Stageis visible and correctly positioned in Wade's sidebar view - Begin updating existing contacts with appropriate
Lifecycle Stagevalues - Update the Active Leads list view to include
Lifecycle Stageas a visible column alongsideContact Type
Relationship to Contact Type Property
Lifecycle 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.
Relationship to Drip Campaigns
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.
Related
- [3]
- [1]
- [4]
- [2]