Handling "This isn't a priority for us" as AEs
Explore current priorities and why, then discuss cost of delay and opportunity loss so the conversation moves from "this isn't a priority for us" to the business outcome they actually care about.
Why this hits harder for AEs
For an AE, an objection late in cycle is a signal that discovery missed something — the real move is often to go back one step, not forward.
The tactical move
Reopen discovery with a mutual action plan review. Frame the objection as a shared problem to solve on the way to a decision, not a wall to climb.
The common trap
Discounting or product-answering an objection that is really about internal politics or authority.
What the objection really means
Either the pain isn't sharp enough yet, or you haven't tied the solution to a deadline that already exists in their world. For "this isn't a priority for us" specifically, the underlying job is to explore current priorities and why 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 "This isn't a priority for us right now." really mean?
- Either the pain isn't sharp enough yet, or you haven't tied the solution to a deadline that already exists in their world. In this specific case, the signal you're looking for is whether you've done step one: explore current priorities and why. If that's missing, the objection will keep resurfacing.
- What's the best framework for handling this objection?
- Use the Timing & Urgency framework: Confirm interest → Quantify the cost of waiting → Anchor to an existing deadline → Lock a concrete next step. For "this isn't a priority for us" specifically, the move that matters most is to discuss cost of delay and opportunity loss before you ask what would make it a priority.
- Should I respond immediately or ask a question first?
- Ask first. A useful opener here is: "When you say 'this isn't a priority for us', 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?
- Accepting 'follow up in Q3' without a concrete trigger — Q3 will arrive with new excuses. Specifically on "this isn't a priority for us", reps tend to skip "explore current priorities and why" — 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 "this isn't a priority for us"?
- 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 "This isn't a priority for us right now." verbatim, then scores your response against the key points: Explore current priorities and why; Discuss cost of delay and opportunity loss; Ask what would make it a priority.