← All briefs

Brief 01 · Renewals · Nov 2026

Green accounts that still churned

A plain breakdown of one customer success postmortem: what it claims, what is only the author's word, and a check a small team can run.

Source"What my CS team was missing" by Manuel Faust (founder of a company that sells an early warning product, and the article ends with a sign up pitch for it.), The Next Web (contributed article, not TNW reporting), 16 February 2026. Read the original. Full credit at the bottom.

Voiced by AI. A 30 second brief.
Read the captions
  1. Green everywhere. Gone in 90 days.
  2. Both green. NPS 72.
  3. 23 tickets. Closed one by one.
  4. 3 of 5 power users changed profiles.
  5. Champion title, one level down.
  6. A health score shows where an account was.
  7. Tickets, last 90 days.
  8. Who your champion is.
  9. What changed since the last call.
  10. 60 days out, not 6.
  11. A few dozen accounts, a Friday afternoon.
  12. Renewal windows: 30, 60, 90 days.
  13. 7 day trial. No card. cshubb.com
Accounts lost2

enterprise accounts, within the same 90 days

Author's account
Tickets23

at one account over four months, each closed on its own

Author's account
Power users3of 5

changed their profiles in a two week window

Author's account
NPS72

at one of the two accounts, still green

Author's account

The case

The case in one minute

Two enterprise accounts left the author's company within the same 90 days. The author calls it a $2M quarter, without saying whether that means contract value or revenue, or how it split between the two. Both accounts showed green in every internal system, and one had an NPS of 72.

The author says the postmortem found a coverage gap: the warning signs sat in places the team's process did not look. He does not describe it as an execution problem.

What was found

What the two postmortems found

Account one

Engineers filed 23 tickets about API latency across four months.

23 small tickets, each closed on its own. Read together, they showed rising frustration. None became critical.

Account two

Three of five power users updated their profiles in the same two week window.

Updated
Updated
Updated
No change
No change
Champion: Head of→Senior Manager

One of them started posting about a competitor's product.

Author's accountNo documents or data are shown, so treat it as a first person account.

The argument

What a health score and an EBR can and cannot see

  • An executive business review captures what the customer chooses to say in the room.
  • A health score summarizes what the team measures, and it lags behind what is happening on the account.
  • The buyer and the person who renews are often different people, so a happy champion tells you little about the budget holder.
  • The signals live in five or six systems, and nobody's job is to read them together.
Author's opinionPlausible, not proven by the article.

The framework

The three layer signal framework

The author groups the signals into three tiers. The article gives no numeric thresholds for any of them.

1

Support ticket patterns

Ticket speedSentiment trendSame team filing

A steady trickle of resolved tickets from one team can say more than a single critical escalation.

2

People changes

Champion leavingReorganizationsTitle changesNew executives

The person who bought and the person who renews are often not the same.

3

Competitive exposure

Being pitchedCompetitor eventsCompetitor content

Shows interest in alternatives before it reaches a conversation with you.

A note on tier 3

Watching public professional activity is a sensitive practice. If your team does this, check local privacy law and your own policy first. We do not recommend it as a default and CSHUBB does not do it.

Key facts

The facts, with their status

ItemWhat the article statesStatus
Accounts lostTwo enterprise accounts within 90 daysAuthor's account
Value"$2M quarter", unit not definedUnverified
NPS72 at one accountAuthor's account
Tickets at account one23 over four months, all resolved individuallyAuthor's account
Profile changes at account two3 of 5 power users in two weeks, champion title one level lowerAuthor's account
Accuracy claimAbout twice a health score, 300 accounts, 18 monthsUnverified, no method
Manual effortAbout 90 minutes per account per weekAuthor's estimate
Scaling limitA few dozen accounts by hand, automate at about 80 to 150Author's estimate
Author interestFounder of a company that sells the fix, and the article ends with its sign up pitchdisclosed.

The one number we do not repeat

The author says one rate of increase in tickets predicted churn about twice as well as a composite health score. The article does not say whose accounts, how churn or accuracy was measured, what the baseline was, or how many accounts churned. We cannot verify it, so this brief and its video do not use it.

Doing it by hand

The manual approach and its limit

The author describes one unnamed team whose managers logged signals from six sources every Friday, about 90 minutes per account per week. He says the method stops working past a few dozen accounts. The figures and thresholds are his own estimates, with no source.

Our reading: the defensible takeaway is that a hand check is realistic for a small book and unrealistic for a big one.

What it recommends

What the article recommends doing

  • Keep the existing process: EBRs, health scores, stakeholder maps.
  • Add a signal layer on top using the three tiers.
  • Manual teams do a weekly Friday review. Automated teams get an alert when something changes.
  • Match the response to the signal. A sponsor who stopped logging in needs a different move than a competitor's contact appearing in a sandbox.

What the article is also doing

It closes by promoting the author's own product, with a form for a one page executive brief of 10 accounts. Those product claims are not independently verified, and the article promises to show how both churned accounts would have looked in the product but does not. That does not make the case wrong. It means the claims should be tested, not trusted.

Our check

A simple pre renewal check

Built from the parts of the case that need no special tool. Our own, not from the article. Run it for every account renewing in the next 90 days.

Our check
  1. TicketsCount tickets in the last 90 days against the 90 days before. Note whether one team keeps filing.
  2. PeopleConfirm your champion and budget holder are still in role. Note what changed since your last call.
  3. NotesWrite the findings next to the renewal date, with a name and a next step.
  4. TimingDo this at 60 days out, not at 6.
  5. ScaleA few dozen accounts fits a Friday afternoon. Past that, you need one place for it all.

Where CSHUBB fits

What CSHUBB does for this

  • Renewal windows at 30, 60 and 90 days.
  • Configurable health scoring, separate from NPS.
  • Playbooks triggered by health, renewal window, NPS or alerts, with tasks assigned automatically.
  • Integrations with Zendesk, HubSpot, Jira, Gmail, Google Calendar and Microsoft 365, plus any webhook source.
  • 7 day trial, everything unlocked, no card.

Credits

Source and credit

Source and credit

Article
"What my CS team was missing"
Author
Manuel Faust, founder of a company that sells an early warning product, and the article ends with a sign up pitch for it.
Publisher
The Next Web (contributed article, not TNW reporting)
Published
16 February 2026
Read the original
thenextweb.com/news/what-my-cs-team-was-missing
Last checked
15 November 2026

We use the case as a prompt for a useful check. We have no connection to the author. Every claim below is marked as stated in the article, the author's own claim, or our own check. The author's own site lists The Next Web among its customer stories.

We summarize and comment on this article under fair use and link to the source. Check the original for the author's full wording. The numbers are the author's and have not been audited by us. Last checked 15 November 2026.

CSHUBB is a customer success platform for teams who care about data privacy. Know which accounts need you, why, and what to do next.

Contact

hello@cshubb.comDemos and inquiries
founder@cshubb.comFeedback and pricing
support@cshubb.comProduct issues
security@cshubb.comSecurity questions
See the platform in action.4.5 minutes, all modules.
Momentum AIOffline mode11 alertsLocal AI via LM Studio
Watch demo
© 2026 CSHUBB Innovations. Built by a CS professional, for CS professionals.Need hands-on help? CS consulting
SupabaseCloudflareMulti-method authRLS enforced