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.
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.
Frequently Asked Questions
- What does "We just implemented a new system last year. Can't change again." really mean?
- Loss aversion. Switching feels riskier than staying put, even when the current setup is leaking time and money. In this specific case, the signal you're looking for is whether you've done step one: acknowledge change fatigue. If that's missing, the objection will keep resurfacing.
- What's the best framework for handling this objection?
- Use the Status Quo framework: Validate → Surface the hidden cost → Compare to the unrealised upside → Lower the switching risk. For "we just implemented a new system" specifically, the move that matters most is to explore satisfaction with recent implementation before you discuss sunk cost fallacy.
- Should I respond immediately or ask a question first?
- Ask first. A useful opener here is: "When you say 'we just implemented a new system', what's the specific thing driving that?" — it earns you the right to respond and prevents you from solving the wrong version of the objection.
- What's the single most common mistake reps make here?
- Attacking the current solution — it makes the buyer defend the past decision they own. Specifically on "we just implemented a new system", reps tend to skip "acknowledge change fatigue" — which is the one move that turns the objection from a wall into a conversation.
- How should I follow up if the call ends with "we just implemented a new system"?
- Send a short recap that mirrors their exact language, references one piece of proof (case study, benchmark, or customer quote), and proposes one specific, low-commitment next step with a date attached.
- Can I practice this objection with an AI buyer?
- Yes — LemCoach scenarios let you run a live roleplay where the AI prospect uses "We just implemented a new system last year. Can't change again." verbatim, then scores your response against the key points: Acknowledge change fatigue; Explore satisfaction with recent implementation; Discuss sunk cost fallacy.