20 years in customer-facing roles have taught me a few things. One of the clearest is that the warning signs of churn almost always show up before the churn itself. Often teams lack the language and the framework to act on those signs in time.

For me, that framework is MEDDIC. Built for sales, it has quietly become one of my most useful customer success tools. 

Here's how my team uses it to spot risk earlier, stay close to the people who decide on renewals, and keep the habit going with help from AI.

Two financial customers, two different outcomes

Two stories from my own team show the difference a shared framework makes. Both involve large financial customers.

The customer we lost

This one had been with us for years. They expanded at every renewal, adopted each new product, and joined our early access and testing programs. Then, about a year ago, they went quiet.

We lost a key person inside the account and never got the momentum back. Eventually, we lost the customer.

If there's an upside, it's that my team documented exactly what went wrong. Product issues played a part, alongside several other factors we could now name clearly. We could see what we might have caught earlier, and we've shared those lessons with sales and leadership so we don't repeat them.

The customers who renewed and expanded

Two other large financial customers, both based in South Africa, renewed and expanded while paying in US dollars. Given the market conditions they were operating in, that was a significant result.

The difference came down to one thing. The team shared a common language and a common way of thinking about each account, and they used it consistently throughout the relationship.

That common language was MEDDIC.

AI Across the Customer Journey ebook

Why CS teams often spot risk too late

When a customer starts showing signs of risk, conversations inside the team can get vague quickly. You hear things like:

  • "They didn't see value."
  • "There were product issues."
  • "The relationship changed."

All of these might be true, but they're hard to act on. In my experience, losing a customer usually comes down to several factors at once.

A couple of patterns tend to sit behind this:

  • We flag risk late. The warning signs were there, but without a clear framework, we didn't know how to troubleshoot what we were seeing.
  • We default to the people who respond. It's easy for CS teams to spend their time with contacts who reply to emails and show up to calls. The relationships that decide a renewal (the economic buyer, the person who signs the contract, the stakeholder with genuine influence) take deliberate effort and a different skill set.

Both patterns are understandable. Neither is sustainable.

How MEDDIC applies to customer success

When I told someone on my team I'd be speaking about MEDDIC publicly, her first response was, "MEDDIC is a sales thing." She's right about its origins, but the variables it covers matter just as much once the contract is signed.

Here's how I look at each component through a CS lens.