Project
← Back to ProjectsLead Signal System
This project is a working HubSpot lead signal system designed to separate Engagement, Intent, and Priority into stable, cross-team signals. The system is implemented as real CRM properties and active lists, with automation architecture designed but constrained by the free HubSpot tier. The goal is not maximum expressiveness, but decision clarity: enabling routing, prioritization, and reporting without semantic drift.
Evidence
Representative contact example
A single contact is shown as a representative example to demonstrate how the system attaches interpretable signals (Engagement, Intent, Priority) to a real CRM record. Click any image to enlarge.
What I built
System components
Core properties
Engagement, Intent, and Priority implemented as first-class CRM fields. Designed as primitives with stable meaning across teams.
Segmentation proof
Active lists that separate high engagement from high intent and assign priority without conflating behavior with readiness.
Automation intent
Automation architecture defined around list membership and signal changes, with execution intentionally limited by free-tier constraints.
Context
Implementation constraints
This system was designed and documented on the free HubSpot tier. The Automation architecture section describes list- and signal-based pathways that would be fully executable on Pro/Enterprise (workflows, enrollment triggers, property-based branching). Guardrails in the design—single source for property definitions, no ad-hoc score overrides—keep signals interpretable and prevent score drift regardless of tier.