The field that's 100% filled and still breaking your AI

Good Morning {{first_name}}!

It’s Wednesday - and that means it’s time for your Property Playbook - an issue where we dig into the default and custom fields.

Well, we’re sticking with the Lifecycle Stage this week, and we’re adding in a second field: Cumulative Time in Stage.

Why?

It's the one nobody's using, it's the reason your AI is giving you weird recommendations, and fixing it takes about 20 minutes.

Grab your coffee, tea - whatever you drink this time of day (I don’t judge). Open your CRM and let’s fix this together.

Let’s dive in.

Object: Contact

Property: Cumulative Time in [Stage] (e.g., hs_v2_cumulative_time_in_lead, hs_v2_cumulative_time_in_customer)

Group: Contact Lifecycle Stage (contactlcs)

Type: Number (stored in seconds)

HubSpot tracks how long a contact has spent in each lifecycle stage, not just where they are right now.

There's a full set of these fields: one per stage, from Subscriber through Evangelist. They capture cumulative time, meaning if a contact drops back and re-enters a stage, it adds up.

Pretty neat, huh?

Most teams focus entirely on the Lifecycle Stage itself, which has a 100% fill rate and feels complete. This person is a lead, this person is an SQL, and this person is a customer. Complete.

But the cumulative time fields sit at 0% fill on most portals because they're read-only, auto-populated by HubSpot, and don't show up in the default contact view.

Understanding this field allows you to address leads that have been dropped, how long sales takes to move a contact along, and much more.

A contact stuck in Lead for 180+ days is not the same contact as one who got there last Tuesday. The lifecycle stage doesn’t know that time delay, though.

One of them is warming up, and the other one has gone cold, and your automation doesn't know the difference.

When we talk data quality, we often look at things like email addresses bouncing, lacking data inputs, and wrong addresses. But data quality is also across the lack of behavioural data in default fields.

Again, it’s not the AI but rather the foundation in which AI operates.

Retention signal: if a current client (Customer stage) has a growing cumulative time with no logged activity, that's a quiet warning sign worth watching.

Cue “preventative churn automation.”

61% of marketers say this is the biggest marketing shift in decades.

Get the data and trends shaping growth in 2026 with this groundbreaking state of marketing report.

Inside you’ll discover:

Results from over 1,500 marketers centered around results, goals and priorities in the age of AI

Stand out content and growth trends in a world full of noise

How to scale with AI without losing humanity

Where to invest for the best return in 2026

Download your 2026 state of marketing report today.

Get Your Report

Play 1: The Stalled Lead Re-engagement

Build a workflow that checks hs_v2_cumulative_time_in_lead. If a contact has been in the Lead stage for more than 45 days with no deal activity, trigger a re-engagement sequence. Not a "just checking in" email - we know those don’t really work anymore. Everyone is doing them.

Play 2: The MQL Timing Qualifier

Before passing a contact to sales as an MQL, add a filter: cumulative time in Lead must be under 30 days. Contacts who moved quickly through Lead tend to convert better. Contacts sitting at 90+ days need nurturing first, not a call. Make a game plan with sales on how this nurture can work as a one-two punch between marketing and sales.

Play 3: The At-Risk Client Flag (Retention)

For contacts in the Customer stage, create a workflow that fires when cumulative time in Customer exceeds your average client tenure by 20%. Pair it with the last activity date. If both are trending wrong, flag it for a personal outreach before it becomes a churn conversation.

Go to Contacts, click into any contact record, and search "cumulative time" in the property search bar. Confirm the fields are populating. Then head to Workflows and create a contact-based workflow with the trigger "Cumulative time in Lead is greater than [time]."

Add those fields to your contact view or a saved filter so your team can actually see them.

Hack: You can also create segments with this field to make it a quick campaign.

On the docket this month: videos and The Lifecycle Audit Checklist.

Hit reply if you want to share something you’re struggling with because I’d love to help!

TL;DR

Every team I've worked with that said "our automation isn't working" had the same problem: they were automating off stage labels, not stage behaviour. The Lifecycle Stage field tells you where someone is parked. The cumulative time fields tell you how long the car has been sitting there with the engine off. Those are two completely different conversations, and only one of them leads to a pipeline that actually moves.

And behaviour tends to be the one thing that influences conversion, not - “oh, I’ve been a lead for 180 days? Oh shoot, I'd better talk to sales then.”