---
title: "CS playbook: when a customer evaluates a competitor | Letterdrop"
description: "When a customer is evaluating a competitor: check account health, then defend the renewal or introduce your product to a team you do not serve yet."
url: https://letterdrop.com/enablement/cs
updated: 2026-11-19
---

# Customer success: a customer is in an evaluation

**Read this first**

When one of your customers gets flagged, your agent sends you a task: **who was flagged, which team they're on, how far along the evaluation looks, the renewal date and your last real conversation.** CS benefits from this signal even though sales and marketing run the program.

Check the account's health, then decide which play it is: **defend the renewal**, or **introduce your product to a team you don't serve yet.**

**The one rule**

**Never mention the competitor, and never hint that you know.** This is a customer who trusts you. "We noticed you've been talking to \[competitor\]" turns a relationship into a surveillance problem, and you'll never get an honest answer out of them again.

Use it to decide who to call this week. Never say it out loud.

## Step 1: check account health

Ten minutes of homework changes what you say. Look at:

-   **Usage trends.** Flat or declining, and since when?
-   **Who’s still logging in.** Did your champion stop?
-   **Last meaningful conversation.** Not a support ticket. A real one.
-   **Time since the last QBR**, and whether anything you promised in it actually happened.
-   **Open tickets**, especially anything that’s been dragging.
-   **Renewal date.** How much runway do you have?

The task covers the Letterdrop side: who, which team, which competitor, how far along, the renewal date and your last conversation. **Add the health data only you have:** usage, logins, tickets, and how the last QBR went.

## Step 2: decide which play it is

The signal on its own doesn’t tell you how worried to be. The signal plus account health does.

| What you’re seeing | What it means | What to do |
| --- | --- | --- |
| **Quiet or declining usage** + competitor activity | Genuine churn risk. They’re shopping because something isn’t working. | Treat as a save. Move this week, and loop your manager in now rather than later. |
| **Healthy usage** + competitor activity | Probably diligence, a board ask, or procurement doing its job. Still worth a touch. | Normal check-in. Don’t panic, don’t ignore it. |
| **Champion recently left or changed roles** + competitor activity | The relationship is being rebuilt by someone with no loyalty to you. | Get in front of the new person fast. Assume nothing carries over. |
| **The flagged person is on a team you don’t serve** | Another team is buying something you could solve. Not a churn risk, an opening. | [Introduce your product](#introduce) before they pick someone else. |

## Step 3: defend the renewal with a check-in

Book it like a normal touchpoint, because that’s what it needs to look like.

**Booking it**

> "Hey \[Name\], it's been a while since we properly caught up. Free for 20 minutes this week or next?
> 
> Want to hear how \[the thing they're using you for\] is actually going, and make sure you're getting what you need out of it."

_No agenda doc, no "urgent". Anything that looks like an escalation makes them close ranks._

Once you’re in the room, **your job is to make it safe for them to complain.** Most customers won’t volunteer dissatisfaction to the person who’d be embarrassed by it. You have to ask for it directly and mean it.

**The question that actually works**

> "Straight question: is this doing what you hoped it would?
> 
> If anything isn't working the way you want, I'd genuinely rather hear it now so we can fix it head-on. I'd much rather have the awkward conversation than find out at renewal."

_Then be quiet. The pause is uncomfortable and that's what makes it work. Don't fill it._

If you get “yeah, all good” and you don’t believe it, go more specific. Vague questions get vague answers.

**If they're being polite**

> "What's the one thing you'd change about it if you could?
> 
> And if \[their leadership\] asked you today whether this was worth renewing, what would you say?"

_The second question is the one that gets the real answer. It lets them tell you someone else's doubts instead of owning them._

## If they bring up the competitor themselves

Fine. They raised it, not you. Don’t get defensive and don’t confirm you knew.

**Say this**

> "Makes sense to look around, honestly. What's got your attention about them?
> 
> Good to know. Where we'd normally hold up better is \[where you win\]. But more useful to me is what's making you look in the first place."

_Get them off the competitor and back onto the gap. The gap is the thing you can actually fix._

## Step 4: if something is wrong, it’s a save motion now

Don’t sit on it. The moment real dissatisfaction surfaces:

1.  **Say it back to them** so they know you heard it. “So the real issue is \[X\], and it’s been going on since \[when\].”
2.  **Escalate internally the same day.** Your manager, and whoever owns the fix.
3.  **Come back with a plan and a date**, not an apology. Customers forgive problems. They don’t forgive drift.
4.  **Put leadership on it** if the account or the relationship warrants it. An exec showing up matters more than another discount.
5.  **Set the follow-up before you leave the call.** An unscheduled fix plan is a fix plan that dies.

| Don't | Do |
| --- | --- |
| Mention the competitor or the signal | Ask open questions and listen |
| Lead with a discount | Fix the actual problem first |
| Make it feel like an escalation | Book it as a normal catch-up |
| Accept "all good" when you don't buy it | Ask the renewal question |
| Wait for the renewal to raise it | Move this week |

## The other play: introduce your product to a new team

Sometimes the flagged person isn’t on the team that uses you. They’re in another department, region or business unit, evaluating a vendor for a problem you also solve. **That’s the cheapest new business you’ll find:** you already have the logo, a champion and a security review behind you.

**Is the contact worth introducing?** Yes, when all three are true:

-   **Their job matches who you sell to,** or they report to someone who does.
-   **Their team isn’t covered** by your current contract.
-   **What they seem to be evaluating is something you solve.** The task says which competitor, so you can tell.

If it’s a yes, bring in the account manager or AE who owns expansion, and **go through your champion**, not around them.

**Ask your champion**

> "Quick one: is anyone on \[other team\] dealing with \[the problem\]? We've helped a couple of teams like theirs, and since you're already set up with us it could be an easy win for them. Happy to put something short together you could forward."

**The note your champion forwards**

> "Hi \[Name\], \[champion\] mentioned your team might be looking at \[the problem\]. \[Your company\] is already in use on \[champion's team\] for \[what they use it for\], so security and procurement are done. If it's useful, happy to show you how they set it up. No pressure either way."

_Mention what's already in place. Not having to run another security review is a real reason to talk to you first._

Related: [How the signal gets worked](https://letterdrop.com/enablement/agents)
