The happy with current vendor objection is the most honest one you will hear, and the one reps most reliably ruin. The prospect says 'we're happy with our current vendor,' and the rep reaches for the comparison slide. Now the prospect is defending a decision they made, in front of a stranger who is implying it was wrong, and nobody has ever switched vendors to win that argument. Every incumbent has a gap the customer has learned to live with: the report someone rebuilds in a spreadsheet every Monday, the integration that needs a monthly cleanup, the feature request that has been 'on the roadmap' for two years. Happy customers know exactly where those gaps are, and they will tell you if you ask about their week instead of your competitor. The script below does that. The openers give you three ways in, and the smokescreen test tells you when 'happy' means 'not talking to vendors.'
What "We're happy with our current vendor" is really telling you
Under 'we're happy with our current vendor' there are usually two things. The first is switching cost: the prospect knows the tool's flaws in detail, and has decided that re-training thirty reps and migrating two years of data is worse than living with them, which is often correct. The second is political safety: someone senior picked the vendor, the relationship is warm, and replacing it means a conversation nobody wants to start. The mistake reps make is attacking the incumbent, directly or through a comparison chart. Every criticism becomes a criticism of the buyer's judgment, and they will defend a tool they privately complain about. The work is to skip the vendor entirely and ask about the workarounds: the spreadsheet, the manual step, the thing they stopped asking for. Those are the gaps the prospect already knows about and has never been asked to price.
Happy with current vendor objection script: five beats, spoken
Do not name the competitor at any point in this script, even if you know exactly who it is. The moment you do, the call becomes a debate you cannot win.
ACKNOWLEDGE: Good, and I mean that. Most of the teams I talk to are not unhappy with what they have, and I am not going to try to convince you that you are.
CLARIFY: Can I ask a different question, then? When you think about the week for your reps, what is the thing they do around the tool rather than in it? The export, the spreadsheet, the manual step somebody owns?
REFRAME: Every tool people are happy with has one or two of those, and they stop being visible after a year because they turn into somebody's job. I am less interested in replacing what you have than in whether one of those workarounds is costing you more than you have priced.
PROOF: Harlow Logistics were happy with their setup and said so on the first call. The thing they mentioned in passing was a Monday morning report their ops lead rebuilt by hand, about three hours a week. We did not replace their platform. We took that one workflow, and a year later they expanded because their reps asked for it.
ASK: Would it be worth twenty minutes with the person who owns your workarounds, to find out what those actually cost you per month? If the answer is 'not much,' I will tell you so.Direct: 'Glad to hear it. What does your team still do in a spreadsheet, though? That is usually where the interesting conversation is.'
Curious: 'What would your current vendor have to stop doing for you to reconsider? I ask because the answer tells me whether I should be calling at all.'
Dry: 'Most of my customers said the same thing about their last vendor. Happy and well-served are different things, and only one of them shows up in the renewal conversation.'The test: ask 'When does your current agreement come up for renewal, and who runs that review?' A real satisfied customer knows both and answers easily, because they have thought about it. A smokescreen does not know or does not care, which means they are not evaluating anything and 'happy' is a way of saying 'not now.'
If it is not real, stop selling: 'Understood. I will check back a quarter before your renewal, if that is useful, and otherwise leave you alone.' Note the renewal month and do exactly that.Ask about the workaround, never about the vendor; the spreadsheet somebody rebuilds every Monday is the only sales pitch this prospect will hear.
Rewrite the script for your product and this account
The script asks about workarounds in general. It is far more effective when CLARIFY names the specific gap that customers of this particular incumbent tend to live with, and you know or can infer who the incumbent is. Paste that with the prompt below and let Claude tailor the questions without ever naming the competitor on the call.
I am handling 'we're happy with our current vendor' from {{prospect title}} at {{company}} ({{company URL}}). My product: {{one-line description}}. Their incumbent, if known: {{vendor}}. Gaps that customers of that vendor commonly work around, as far as I know: {{list, or 'unknown'}}.
Rewrite the five-beat script below so CLARIFY asks about the two or three workarounds most likely at {{company}} given their incumbent and their team size ({{team size}}), phrased as questions about their week and never naming the vendor. REFRAME should stay on the cost of the workaround rather than on switching. PROOF should use: {{customer who was happy with an incumbent, the workaround you replaced, what happened after}}. ASK should propose a scoped first workflow rather than a replacement. Under 200 words, spoken. Then list the three signals from their website or job posts that suggest which workaround is real. Mark inferences.
SCRIPT:
{{paste the script above}}Handle any objection with Claude
- Objection handling script prompt →The copy-paste prompt that drafts a response to any objection in your voice, with the proof point pulled from your own wins.
- Competitive battlecard skill →For the competitor-shaped objections: a rep-ready battlecard built from live competitor intel.
- Discovery call prep skill →Most objections are discovery you skipped. The skill preps the questions that surface them before the pitch.
Frequently asked questions
How do you handle the happy with current vendor objection?
Agree with them and change the subject from the vendor to the workarounds. Ask what their reps do around the tool rather than in it: the weekly export, the spreadsheet somebody rebuilds, the manual step that became a job. Every incumbent has two or three of these, and happy customers stop seeing them after a year. Price the workaround with them, and propose taking that one workflow rather than replacing the platform. Reps who pull up a comparison chart force the prospect to defend a decision they made, and nobody switches vendors to lose an argument.
Should you ever criticize the incumbent vendor?
No, and especially not when you are sure you are right. The prospect chose the vendor, or works for someone who did, and criticism of the tool lands as criticism of that judgment. Let them raise any flaws themselves; they usually will once the conversation is about their week rather than your product. If they ask you directly how you compare, answer the specific question narrowly and return to their workflow. Your job is to make one gap visible and price it, and the incumbent's name does not need to come up for that.
When is the right time to approach a happy customer of a competitor?
About a quarter before their renewal, and only if you have something specific about a gap they live with. The renewal window is when the buyer is forced to look at the invoice and the roadmap together, and a scoped alternative for one painful workflow reads as an option rather than an attack. Approaching at random with a comparison deck gets you filed under vendor noise. Ask the renewal month on the first call, log it, and come back with the workaround priced; that is the version of persistence that gets a reply.