Audience Segmentation and Lead Scoring for an Executive Education Program
Before this workstream, calling a lead hot ran on instinct: anyone who asked a question during a masterclass got flagged as a hot lead. A seven-segment audience model built against data already on the HubSpot record replaced that guesswork, splitting Alumni Warm, Alumni Cold, Prospects, Clients, Staff, Staff Alumni and Partners into their own lists. A fit, engagement and negative-criteria scoring model was scoped alongside it in an October 2025 workshop, meant to route a qualified attendee to the right BD owner within 48 hours. That build never reached HubSpot: the tracker recorded it Blocked through the following sprints, then reclassified it Not in Scope.
Executive Summary
Context
An executive-education provider's HubSpot instance carried years of contacts: alumni, clients, staff and partners, alongside prospects who had only registered for one event. Business development had no consistent way to read that list once an event ended, so every attendee got the same manual review. And whether a lead counted as hot depended on whoever reviewed the record that day.
What We Built
We defined a seven-segment audience model against data already on the HubSpot record and scoped a fit, engagement and negative-criteria lead-scoring model in a dedicated workshop, meant to route a qualified attendee to the right BD owner by industry vertical and region within 48 hours of an event.
Tech Stack
- HubSpot Lists
- HubSpot Lead Scoring
- HubSpot Workflows
Not a fit if you need a working lead score today: the scoring model here was specified in a workshop, not shipped as a HubSpot property, so nothing scores a record automatically. Also not a fit if your BD team can't treat a segment tag as one input among several, since a Warm or Cold flag still needs a person to act on it.
The Challenge
Before this workstream, a hot lead was whoever the reviewer's instinct flagged. A contact who asked a single question during a masterclass got the same tag as one who requested a follow-up call.
Every attendee record sat in one pool, with alumni, prospects, clients, staff and partners together. So a contact who had attended three masterclasses got the same triage as someone who had never engaged before.
Our Approach
We started by splitting the contact base into seven segments, built against data already on the HubSpot record. That gave business development a starting filter before any scoring logic existed.
We then scoped a fit, engagement and negative-criteria scoring model in an October 2025 workshop. It was meant to pair with the existing Lead Status property and to trigger when an attendee record updated after an event, routing a qualified contact to the correct BD owner within 48 hours.
That build was recorded as Blocked through the following sprints, and the January 2026 update reclassified it Not in Scope. So business development kept working from the seven segments and manual judgement.
Impact
Every contact carries one of seven segment tags
Alumni Warm, Alumni Cold, Prospects, Clients, Staff, Staff Alumni and Partners now sit on the record itself, so business development starts from a defined category instead of an undifferentiated list.
A documented alternative to the single-question hot lead
Whether a contact counts as hot no longer depends only on who reviewed the record. The seven segments give business development a category to start from, even for criteria the scoring model would have added.
A fit, engagement and negative-criteria model is specified, not scoring records
The scoring model stayed at the specification stage and never reached the HubSpot record as a live property, so business development still applies its criteria by eye rather than reading a score.
The BD-routing gate stayed a design
Routing a qualified attendee to the right BD owner within 48 hours was the scoring model's stated job. With the build recorded Blocked and later Not in Scope, that gate is documented but not automated.
Alumni Warm, Alumni Cold, Prospects, Clients, Staff, Staff Alumni and Partners were defined against data points already on the HubSpot contact record, each reaching its own list rather than one combined pool.
An October 2025 workshop specified three inputs for a lead score: fit against the program's target audience, engagement with prior sessions, and negative criteria meant to rule a contact out. None reached a live HubSpot field.
The design would trigger when an attendee record updated after an event. It paired the new criteria with the existing Lead Status property to produce a Warm or Cold read, then routed the contact to a BD owner by vertical and region.
The tracker recorded the scoring build as Blocked through the September-December 2025 sprints. By the January 2026 update it had moved to Not in Scope alongside other Phase-2 items, leaving the seven segments as the only piece in production.
When an attendee record updates after an event, it is placed into one of the HubSpot segment lists built from data already on the record. A scoring path was designed alongside it: fit, engagement and negative criteria, combined with the Lead Status property, would route a qualified contact to a BD owner by vertical and region. The dashed lines mark that path as scoped but never built, so only the segment lists are live.
FAQ
No. The scoring model was specified in an October 2025 workshop, but the tracker recorded the build as Blocked and later reclassified it Not in Scope. The seven-segment audience model is the piece that reached HubSpot lists.
A seven-segment audience model replaced the undifferentiated contact list, giving business development a defined category to start from. The scoring layer that would have ranked leads within those segments was specified but never built, so a manual read still fills that gap.
