Customer Churn

The Scary Six: Executive Change

By
Steve Hazelton
January 26, 2024
5 min read

At the end of last year, I shared a regular expression (regex) that identifies "contract requests." That's a scary signal for people who like to keep customers.

Today, I want to discuss the scariest of the Scary Six, "Executive Change."

At my last company, Newton, this signal had the highest correlation to churn and initially resulted in a loss about 50% of the time (for many of Sturdy's customers, this is also true).

So what is it? Let's say you sell accounting services, and this happens:

"Hi, I am the new CFO, and I would like a quick rundown of your capabilities."

The response is often,

"So nice to meet you! LMK when you have 30 minutes for a quick call!"

(By the way, usage will be high during this time, and their Health Score will be green.)

On to the regex…

The first two are specific to HR services/tech, so replace "hr" with "e-commerce," "accounting," "logistics," or whatever business you're in.

Here's what they do:

1. The first detects when someone says, "Hey, we have a new VP of HR coming on board soon."
2. The second, "I will be taking over the Admin role for this account."
3. The third, "Hey, I wanted to let you know that I will be leaving at the end of January."

Remember that they return a fair number of false positives (FPs). FPs are not included in the churn rate calculation.

The frequency of "Executive Change" varies depending on the industry and segment. In the SMB cohort, it occurs in about .1% to .2% of customer conversations. In huge enterprises, around .04%.

Interestingly, this signal is much more common in the HR space, firing at .3% per conversation.

There is also a lot of variation in the severity. Still, the correlation to cancellation is the 2nd highest of any signal we currently detect at Sturdy ("I want to cancel" being the highest, obviously). For SMB customers, the churn rate for this signal, if untreated, will approach 70%. It will be lower for enterprise customers.

Another critical point is that this is a leading indicator. It often occurs long before the cancellation event.

Why is this signal such a strong indicator? At the beginning of the post, we showed a sample trigger-sequence that ended something like, "Let's do a quick demo!"


What's wrong here? I think it is because one or all of the following is happening:

1. The value of your service can't be communicated in a "quick demo."
2. The new contact has undoubtedly used and trusts a competing solution.
3. The person conducting the demo has not been trained to sell your product, overcome objections, and destroy your competition's product.

This is a perfect recipe for failure. Here's a scenario...

Acme Corp sells HR Software on M2M and yearly contracts; it receives:

10k emails and tickets per month (items).
10k items equals to about 2k conversations (1 convo = ~ 4.4 items)
.3% detection per conversation = 6 Exec Changes
Two false-positive (30% FP rate)
50% churn x 4 = 2 losses

If untreated, Acme loses two customers to this signal per month.

The good news is that, in my experience, treatment will save about one of these customers each month. How?

1. Train everyone who touches customers, billing, CS, and marketing to identify the signal.

2. Immediately send the signal to your sales AND marketing teams.
Someone should attempt to discover the product the new contact used at their former company.

3. A salesperson must schedule a demo as soon as possible. (At Newton, our KPI was to conduct the demo within ten days). The seller should come armed with useful information, like usage data candidates hired (e.g.), and be prepared to sell against the new contact's previous solution.

4. In parallel, the marketing team checks LinkedIn to see if the previous contact has landed a new job. If not, someone should reach out and see if they need help in their job search (after all, you sell to companies that hire these people). If the person has landed somewhere, send them a note, a gift basket, or whatever you think is appropriate.

5. Send the previous contact to the Sales team as an SQL.

(Shameless plug: Sturdy has AI-language models that find 1, automatically route 2, and can tell you if 3 and 4 happened.)

The result of this process is a successful "double-dip". You may save a customer and gain a lead for your sales team. Ironically, if your competition is not tracking the Executive Change signal, your chance of closing that deal is very high.

Similar articles

View all
Integrations

Product Update! Sturdy now integrates with Jira

Joel Passen
March 10, 2025
5 min read

We’re making it easier than ever to turn customer feedback into action while saving businesses hundreds of thousands of dollars per year. With Sturdy’s new Jira Connect, any AI-powered Signal in Sturdy can be automatically logged in Jira—helping teams capture, prioritize, and resolve issues faster than ever.

Sturdy for Jira is a Game Changer

Every team needs to know more about their customers. 

Turn customer feedback into valuable Jira content automatically. Sturdy’s AI accurately detects feature requests, bug reports, and other critical product feedback. Customizable agents then deliver this context-rich intelligence to a configurable staging area in Jira with all relevant user and account details, such as segment, ARR, and more. The content is objectively summarized automatically. From there, assigning it to an epic, task, sprint, or release is just one click.

Productivity Gains that Move the Needle

Businesses are unknowingly spending hundreds of thousands of dollars per year on something as simple as manually logging Jira issues. A single customer-facing rep wastes nearly 87 hours annually on repetitive data entry—scaling up to a staggering $354,200 per year for a team of 100 reps. By integrating Sturdy’s AI-driven automation, businesses can reclaim thousands of hours, improve productivity, and reinvest those savings into growth and innovation—all while ensuring more accurate, real-time data flows into Jira effortlessly.

Align product teams with customer reality.

By centralizing AI-powered insights in Jira, Sturdy ensures that product and engineering teams get a complete, objective picture of what’s working, what’s broken, and what needs to be built—without relying on anecdotal feedback. Customer-reported issues appear in Jira moments after they happen, ensuring your product and engineering teams stay ahead of emerging trends and critical bugs—without the lag of traditional reporting.

Effortless setup, immediate impact.

Sturdy’s turnkey integration takes minutes to configure. Once connected, your team gains instant access to context-rich, structured feedback—helping you make faster, data-driven decisions that improve customer satisfaction.

Want to get started? Click the 'Schedule Demo' button at the top of the page.

Integrations

Product Update! Sturdy Now Analyzes Customer Slack Channels

Joel Passen
March 3, 2025
5 min read

We’re making it easier than ever for teams to tap into the power of customer conversations. With this integration, Sturdy’s AI-driven insights—trained to spot key behaviors and trends unique to your business—are now right where your team works. That means more proactive decisions, better collaboration, and a serious productivity boost.

Here’s how Sturdy works with Slack.

  • Get the right insights, right in Slack. Sturdy delivers AI-powered Signals where your team already works, flagging risks, expansion opportunities, and other key moments in real-time. No more digging through conversations—just actionable insights when you need them.

  • Stay on top of every conversation. If your team works asynchronously in Slack channels, it’s easy for important feedback to get lost. Sturdy keeps you ahead by surfacing critical insights before they slip through the cracks.

  • Act fast, not after the fact. Whether it’s a service risk, a feature request, or a potential upsell, Sturdy helps teams spot and respond to what matters—without disrupting their workflow.

Seamless sync with your tools. Sturdy doesn’t just stop at Slack. Insights discovered in customer Slack channels automatically flow into Jira, CSPs, CRMs, and other systems, ensuring the right teams get the right info—without extra work.

Customer Intelligence

He doesn’t talk much, but when he does, you’d better listen.

Steve Hazelton
February 27, 2025
5 min read

He doesn’t talk much, but when he does, you’d better listen.

Quote from C-3PO, Star Wars: A New Hope

A few days ago, I spoke to a business leader, and they asked, "How would Sturdy work for customers who never contact us?"

"Do you know who those customers are?"

"No idea."

"Would you like to?"

“Dark Customers.” It is almost impossible to source this list. Your customer might be dark to five silos, and bright in just one. 

(By the way, there is a little-known filter in the Accounts page of Sturdy that lets you sort by “Last Inbound.”  Check it out. You can see the last time any customer sent you an inbound message.)

Let’s be fair. In a recurring-revenue business, a lack of inbound contact isn’t necessarily bad. Sometimes your customers don’t feel the need to chat with you, but they like you just the same. 

But, here’s the cool thought. What should happen when a Dark Customer suddenly reaches out? 

For example, Acme Corp sends an email to your CS team for the first time in 18 months. What needs to happen next?

I would want to know. So, we’re working on that. Naming such a signal is a bit tricky, if you have ideas, let us know.

How many customers will you have to lose before you try Sturdy?

Schedule Demo
A blue and gray logo with a black background
A number of different types of labels on a white backgroundA white background with a red line and a white background with a red line andA sign that says executive change and contact request
A white background with a red line and a blue lineA number of different types of logos on a white backgroundA pie chart with the percentage of customer confusion and unhappy
A number of graphs on a white background