The Essence
The Interest object (2-54301725) is a custom object that captures intent recognition and engagement patterns. It replaces the deprecated Signal/Lead object with a purpose-built architecture for tracking genuine relationship progression.
Interests recognize patterns of authentic human engagement. They don't "score" people, don't "qualify" them, don't push them through predetermined stages. Interests observe. They accumulate context. They help you understand when someone is genuinely ready for deeper engagement -- and they do so without reducing human beings to numbers waiting to be "converted."
Unlike the native Lead object (which carries decades of industrial-age "lead management" thinking), the Interest custom object was designed from the ground up for the Value-First framework. Breaking free from extraction thinking is the first step toward building a Customer Value Platform.
"The Interest object captures intent recognition -- the meaningful moments when people demonstrate genuine curiosity, readiness, or engagement. The philosophy behind how you use it determines whether your platform enables authentic relationships or optimized extraction."
Unified View Contribution
Customer View
Primary contributor. Interests capture the engagement patterns that reveal what people care about, how they're exploring, and when they might be ready for deeper conversation. Without Interest intelligence, Contacts are just names -- you know who people are but not what they're interested in or how they're progressing.
Business Context
Primary contributor. Aggregated Interest data reveals which content resonates, which channels work, which problems your audience cares about. Interest intelligence informs strategic decisions about positioning, content investment, and market focus.
Revenue View
Supporting contributor. Interests provide attribution context -- understanding which engagement patterns preceded commercial relationships helps forecast and improve revenue generation approaches.
Team Enablement
Supporting contributor. Interest ownership and routing enable appropriate team response. When interests indicate readiness, the right people can engage at the right time.
Sarah's Story
Sarah Chen's first Interest was created when she clicked through from a LinkedIn post to read an article about manufacturing data challenges. She didn't fill out a form. She didn't request a demo. She just read something that resonated.
That initial Interest captured the source (LinkedIn), the content (Data Trap article), and the timestamp. It associated to the Contact record that was created from her previous newsletter signup. The Interest sat quietly, representing a single data point of genuine curiosity.
Over the following weeks, Sarah generated more Interests. She downloaded the Data Trap Assessment -- an Interest with higher engagement depth. She watched two episodes of the Manufacturing Transformation show -- Interests tracking content consumption patterns. She returned to the website and explored the HubSpot CVP service page -- an Interest indicating she was connecting her problem to potential solutions.
None of these Interests triggered aggressive outreach. No one called Sarah because she'd accumulated enough "points." Instead, the Interests accumulated into a pattern: someone in manufacturing, engaging with Data Trap content, exploring implementation services. The pattern suggested she was in active research mode -- the Researcher stage of her Value Path.
When Sarah registered for Office Hours and submitted a pre-session question about her specific ERP integration challenges, that Interest was different. This wasn't passive consumption; this was a hand raise. The Interest moved to "Engaged" status, indicating readiness for human conversation. Not because she'd crossed an arbitrary threshold, but because her behavior demonstrated genuine readiness.
The Office Hours host reviewed her Interest history before the session -- not as a "lead score" but as context. They understood what she'd been exploring, what problems she was wrestling with, what content had resonated. The conversation started from understanding, not qualification.
When Sarah's engagement eventually led to a Deal, the Interest didn't disappear or get "converted." It stayed active, now associated to the Deal for attribution tracking. The Interest continues to accumulate engagement data -- because Sarah's relationship with Value-First didn't end when she became a customer.
What It Holds
Source and Origin
Engagement Pattern
Intent Indicators
Readiness Context
Pipeline Position
What It Connects To
Primary Associations
Every Interest must associate to a Contact. Interests without Contact association are just events; Interests with Contact association become relationship context.
Organizational context for B2B interests. Understanding that three people from the same company are generating similar Interests changes interpretation.
Content that triggered or relates to the Interest. Which articles, episodes, assessments, or resources did this Interest involve?
When Interests contribute to commercial opportunities, the association maintains attribution and context. Interests persist -- they don't "convert."
Interest Association Labels
The first Interest that created this engagement thread
Links Interest to specific content (Listing)
Connects Interest to Deal when engagement contributed
Links Interest to Appointment when happened during session
Why Association Labels Matter
The "Source Interest" label preserves original attribution -- where this relationship began. "Triggered By" connects Interests to content, enabling content performance analysis. "Led To" maintains Deal attribution without losing the Interest record. This is context preservation, not conversion tracking.
Common Patterns
The Accumulation Pattern
The Multiple Pipeline Pattern
The Readiness Recognition Pattern
The Attribution Without Conversion Pattern
The Prospecting Reframe Pattern
Value-First vs. Industrial-Age
| ✗ Traditional Thinking | ✓ Value-First Thinking |
|---|---|
| "Lead generation" -- Capture people into funnel | Interest recognition -- Observe authentic engagement patterns |
| "Lead scoring" -- Assign points to predict readiness | Pattern recognition -- Understand context and behavior |
| "Lead nurturing" -- Drip sequences until qualified | Relationship development -- Support journey when helpful |
| "Lead qualification" -- Gate access to sales | Readiness recognition -- Respond when genuinely ready |
| "Lead conversion" -- Record disappears when won | Interest persistence -- Context maintained throughout relationship |
| "MQL/SQL" -- Internal process stages | Value Path stages -- Human experience stages |
| "Lead status" -- Single linear progression | Multiple pipelines -- Parallel engagement paths |
| "Cost per lead" -- Volume economics | Relationship quality -- Depth economics |
Why This Shift Matters
When you treat early engagement as "lead management," every system decision reinforces extraction thinking. You optimize for volume over quality. You automate sequences that feel like processing. You score people into segments that determine how much attention they deserve.
When you treat early engagement as "interest recognition," everything changes. You observe patterns instead of assigning scores. You respond to readiness instead of triggering sequences. You maintain context instead of converting records. The infrastructure supports genuine relationship development.
In Practice
Implementation details and configuration
Key Properties
Key Properties
| Property | Type | Purpose |
|---|---|---|
interest_source | Text | Where engagement originated |
interest_type | Enumeration | Category of interest |
interest_action | Text | What action was taken |
interest_timestamp | DateTime | When the interest was recorded |
engagement_score | Number | Engagement scoring value |
signal_strength_score | Number | Composite of frequency, depth, recency, breadth (0-200) |
signal_progression_velocity | Number | How quickly interest is strengthening |
signal_readiness_context | Text | AI-generated readiness narrative |
signal_trap_recognition | Enumeration | Which complexity traps identified in this engagement |
signal_source_pattern | Multi-checkbox | Media, Community, Assessment, Direct, Referral |
Interest Recognition Pipeline
Pipeline ID: 871995235 | Object Type: 2-54301725
New Interest
Person identified, basic engagement detected
Form submission, content download, newsletter signup
Multiple content pieces consumed in same topic area
Portal Experience
In the My Value Path Portal, Interest data appears as transparent engagement history:
My Activity
- "You downloaded the Data Trap Assessment on [date]"
- "You attended Office Hours on [date]"
- "You explored the CVP Implementation page on [date]"
"Sarah can see every Interest we've tracked. This isn't surveillance hidden behind a CRM wall -- it's shared context. She can understand why we might reach out, what we think she's interested in, and correct our understanding if we're wrong."