Three weeks into a new portal audit last year, I asked the ops lead how they were identifying current customers for their CS team. She said "lifecycle stage equals Customer."
Then I pulled the data. Forty percent of their Customer-stage contacts hadn't had a single activity in over a year. Two of them were companies they'd lost to a competitor. One was a prospect who'd filled out a demo form in 2021 and somehow got stamped through a workflow nobody remembered building.
I've had a version of that conversation on nearly every portal I've walked into. Identifying active customers inside HubSpot has been one of those foundational problems that gets rebuilt from scratch on every project.
HubSpot shipped a fix for this last week. It's small, and there are some gotchas to be aware of, but it matters more than the release notes let on.
What the Current Customer Property Is
“Current Customer” is a new system-managed property on contacts, companies, and custom objects that flags whether a record is a current customer.
"System-managed" means HubSpot maintains it. You configure the definition (lifecycle stage equals Customer, or a custom logic rule, or a combination of both) and HubSpot handles keeping it current. New customers get a default definition applied automatically. Existing customers will need to set it up for themselves.
Here's the thing about this property: you could build it yourself in about five seconds. Create a custom checkbox property, write a workflow to stamp it based on lifecycle stage, done. Nothing about the underlying infrastructure is revolutionary.
But that’s not the point.
The Difference Between You Knowing and HubSpot Knowing
There are two different things happening when you identify your customers in HubSpot:
You being able to segment and report on your current customers.
HubSpot recognizing, at a system level, who your current customers are.
Custom properties solve problem one. This property solves problem two. And those are not the same problem.
When HubSpot recognizes something on a system level, that means it’s not just reading a property value, but also understanding the context of that data. And when that context is made available to AI, you unlock a new level of utility. If you ask Breeze about your current customers today, without this property set up, Breeze will do its best to infer…and it will likely get it wrong in ways that are hard to predict and harder to audit. With this property configured, when you ask Breeze about your customers, it will know what you are talking about, because HubSpot is telling the AI that this property = customer.
That distinction is going to matter more as AI is woven deeper into the platform.
Why This Is Harder Than It Sounds
The reason "lifecycle stage equals Customer" has never fully solved this problem is that most companies want more nuance than HubSpot's lifecycle stages offer.
A customer isn't just a customer. There's the customer who just signed and is three weeks into onboarding. The customer who's been on the platform for two years and is fully activated. The customer who went dark six months ago and might be churning. The customer who just expanded into a second product line. Most teams try to express all of that nuance through lifecycle stages — and lifecycle stages were never designed to carry that weight.
The Current Customer property sidesteps this by separating the question "is this person a current customer?" from all the other questions your CS team needs to answer. It's a single, clean signal: yes or no. Your other properties and workflows handle the nuance. This one just tells the platform which side of the line a record is on.
How to Configure It
The setup lives in Settings > Properties, or you can get there through the Service workspace if you're already in that hub.
The default definition uses “lifecycle stage = Customer,” which is fine as a starting point, but most teams will want to tighten it. A few configurations worth considering:
Lifecycle stage + deal closed-won: stamps a contact as a current customer only if they have an associated closed deal, not just a stage update. Catches the contacts who got manually promoted without an actual deal behind it.
Lifecycle stage + active subscription property: useful if you're syncing a billing system into HubSpot and have a property that reflects actual subscription status. This is the cleanest version if the data exists.
Exclude based on a churn flag: if your CS team is already tracking churned customers in a property or pipeline stage, add a negative condition so churned accounts don't stay flagged as current.
Just make sure any additional variables you want to include are reflected in properties on the same object.
Pair the Current Customer property with a companion workflow that logs a timestamp to a "Customer Since" date property when the Current Customer flag turns true. You'll want that date for health scoring and expansion workflows later…and you won't want to rebuild it retroactively once the data starts accumulating.
The Bigger Picture
This property is a small piece of something HubSpot has been building toward for a while. In a recent post, HubSpot CTO Dharmesh Shah and the product team outlined their vision for an open ecosystem designed for the agent era, with full API parity, so every capability is accessible to agents and apps, not just humans. The framing is that HubSpot is building a platform meant to be used by both people and AI, with the same level of access and the same underlying data.
For that to work, HubSpot needs to know things. Clean things. Structured things. Not "customer-ish" things inferred from a lifecycle stage that hasn't been touched in 18 months.
A system property for current customers is one data point. But it's the kind of data point that makes a lot of downstream things possible: customer-aware AI responses, accurate CS workspace views, reliable health scoring, expansion signals that don't fire on churned accounts. The value compounds.
The Catch
As of now, this Current Customer property is only available on Service Hub Professional and above.
That's a meaningful limitation. The problem this property solves, not knowing who your customers are, exists at every tier. It's not a Service Hub problem or a Pro-tier problem. It's a HubSpot problem. Locking the solution behind a $90/month per-seat hub feels like the wrong call.
If HubSpot is serious about making this the foundation for how its AI understands customer context, this needs to be a default property on every hub and every tier. A system property this fundamental shouldn't be gated.
Set it up if you're on Service Hub Pro. Push on HubSpot to make it available everywhere if you're not.
Best,
Ryan
Attribution Unlocked: Recordings Now Available!
4 weeks of live attribution strategy, now on-demand! The full recordings of all sessions of the Attribution Unlocked bootcamp are available inside Hubsessed Academy!
Session 1: Attribution Foundations — choosing the right model for your business and sales cycle
Session 2: Building an Attribution MVP — getting your first working attribution system off the ground in HubSpot
Session 3: Advanced Modeling, UTMs, and AI-powered Reporting — layering on complexity with multi-touch models (even at the Pro tier!)
Session 4: Managing an Attribution Implementation — making attribution stick long-term, defending your methodology, and using the data to drive decisions
If the live format wasn’t for you and you were waiting to upgrade, now is the time!
Hubsessed Academy membership also includes:
Instant access to the full Attribution Mastery Certification course (5 on-demand modules)
Access to every future live bootcamp (and their recordings)
Membership is $79.99/month (or $49.99/mo if you pay annually). If you need help getting your company to cover it, there's a budget approval email template here - just copy and send.
