How to handle: "We just implemented a new system last year. Can't change again."
Acknowledge change fatigue, then explore satisfaction with recent implementation so the conversation moves from "we just implemented a new system" to the business outcome they actually care about.
Score your response
What this objection really means
Loss aversion. Switching feels riskier than staying put, even when the current setup is leaking time and money. For "we just implemented a new system" specifically, the underlying job is to acknowledge change fatigue before you say anything else — that one move usually reveals whether this is a genuine blocker or a reflex response.
The framework
Validate → Surface the hidden cost → Compare to the unrealised upside → Lower the switching risk.
Three sample responses
"That's a fair point, and I hear it a lot. Before I respond, can I ask — when you say "we just implemented a new system", what's the specific concern behind it? I want to make sure I address the real thing, not the version I assume you mean."
"Totally understand. Most of our customers raised exactly that before they saw the numbers. The way we'd normally approach it is to explore satisfaction with recent implementation — and then discuss sunk cost fallacy. Would it be useful if we walked that through against your own situation?"
"Let's park the status-quo question for a second. If nothing changes in the next 12 months, what does that cost you — in revenue, time, or risk? Because loss aversion. switching feels riskier than staying put, even when the current setup is leaking time and money."
What a strong response covers
- Acknowledge change fatigue
- Explore satisfaction with recent implementation
- Discuss sunk cost fallacy
- Focus on future-proofing, not past decisions
Common mistakes
- Skipping the "acknowledge change fatigue" step — reps who jump straight to a rebuttal here lose the prospect's trust before the real response even lands.
- Attacking the current solution — it makes the buyer defend the past decision they own.
- Selling features the incumbent lacks instead of quantifying the cost of staying put.
- Talking before fully understanding what the objection actually means to them.
- Defending instead of diagnosing — turning a question into a debate.
Want to rehearse this one out loud? Run a roleplay where the AI buyer will say "we just implemented a new system" verbatim and score your verbal response.
Handling "We just implemented a new system" by role
The right response changes depending on who is answering. Pick the role-specific playbook below:
- For SDRs — the first 30 seconds — cold outreach, opener replies, and booking the discovery meeting.
- For BDRs — outbound pipeline into named enterprise accounts — multi-threaded outreach across a defined territory.
- For AEs — the full sales cycle from discovery to close — the person with the number on their back.
- For sales managers — coaching reps and forecasting the team's number — objections show up in deal reviews, not on the phone.
- For CSMs — retention, expansion, and renewal — objections here threaten revenue you have already earned.
- For account managers — expansion within existing accounts — new logos in the enterprise are yours, but so is protecting the base.
- For sales engineers — technical validation — demos, proofs of concept, and answering the objections the AE cannot.
- For founders — the first N deals — you are the product, the pitch, and the objection handler until you can hire an AE.
Every objection on this site is one the LemCoach AI buyer actually uses inside our practice scenarios. The rubric on the right is the same one we use to score live roleplays — so the advice here matches the coaching you'd get from the product.
Frequently Asked Questions
Hear "We just implemented a new system" out loud — then answer it
The AI buyer says this objection verbatim and scores your spoken reply. 37 more objections waiting after this one.
No credit card required · 7-day free trial · Cancel anytime