Why 'Not A Priority Right Now' Keeps Killing My Deals

'Not a priority right now' is a discovery failure, not a timing problem — 6 meanings, 4 plays, 8 scripts, 30-60-90 nurture plan.

TL;DR

"Not a priority right now" is almost never about timing. It is usually a discovery failure — no compelling event, no priority owner in the room, or no modelled cost of inaction.
The phrase has 6 real meanings. Diagnose which one is in play before you reply. The label is useless; the cause is everything.
It shows up in 4 deal stages — cold reply, post-discovery, post-demo, and late-stage. The right response changes at each one.
Run one of 4 plays: re-discover, multi-thread, reframe cost of inaction, or nurture and disqualify. Pick the play before you write the email.
Follow up with a 30-60-90 trigger-based nurture plan — not weekly "just checking in" noise. Past 90 days with no trigger, close the deal.

Snippet answer

"Not a priority right now" is a stall that usually hides one of six real problems: no compelling event, the wrong priority owner was in the room, the cost of inaction was never quantified, a bigger fire started, the buyer was never interested, or a competitor was already chosen. Diagnose which meaning is in play with one question, then run one of four response plays — re-discover, multi-thread, reframe cost of inaction, or nurture and disqualify. The phrase itself is a label; the cause decides the play.

'Not a priority right now' is a discovery failure, not a timing problem

Most reps hear "not a priority right now" and reach for a timing script. Three days later they send "just checking in." A week after that, "circling back." By day 30 the deal is a ghost. The rep blames the buyer's quarter — and closes-lost a winnable deal.

The problem is the diagnosis. "Not a priority right now" is almost never about timing. It is a label the buyer puts on a problem they already have — and that problem is usually something the rep failed to surface in discovery. No compelling event got named. The priority owner was never in the room. The cost of doing nothing was never modelled. The champion was never told what to say to the budget holder.

A good rep does not respond to "not a priority right now." They respond to the real cause underneath it. The rest of this post is how to find that cause in one reply, pick a play, and move the deal — or disqualify it and keep your forecast honest.

One scenario, familiar to any AE: you ran a clean discovery call. The pain was confirmed. The next day, the recap email comes back with "this is interesting but not a priority right now — let's revisit in Q4." The rep's instinct is to argue with the Q4. The better move is to ask which of six things is actually happening. One of those six — the missing priority owner — can be fixed in 72 hours. The other five split cleanly into plays or disqualification. Either way, the "Q4" is noise.

What 'not a priority right now' actually means — 6 real translations

The phrase hides six different problems. Labelling your pipeline by the phrase tells you nothing — labelling by the real translation tells you exactly what to do next. Read each one and ask which one actually fits the last deal that stalled on you.

1

"I have no compelling event."

The buyer sees the pain but nothing forces action this quarter. No regulator, no renewal, no board meeting, no missed number. Without a forcing function, every vendor conversation dies on the calendar.
2

"You were talking to the wrong person."

The champion liked the demo but was never the priority owner. The real budget holder has not been in the room. Your deal was a side project for the champion — not an urgent project for the company.
3

"I do not believe the cost of inaction yet."

You quantified features but never quantified the cost of the status quo. The buyer cannot make the case internally because no one can model what doing nothing costs through the end of the year.
4

"A bigger fire started."

A layoff, a platform migration, a security incident, a product failure, a board change. The deal was real — and then the room caught on fire. This is the most recoverable version of the objection.
5

"I never wanted it — I was being polite."

The champion never had intent. They took the demo to be helpful, to keep optionality, or because a peer asked them to. This one is disqualification, not re-engagement.
6

"I am buying your competitor and sparing you the call."

The deal is decided, the vendor is chosen, and "not a priority right now" is the kindest way to end the conversation. Happens more than reps admit.

A practical test: before you draft your reply, write the number — 1 through 6 — at the top of your draft. If you cannot pick a number, you do not have enough information to respond yet. Send a one-line diagnostic question instead. The reps who do this catch roughly a third of their lost deals before they actually die, because the diagnosis forces them to solve the right problem instead of the default "send a friendly nudge" non-response.

Rep note: translations 2 (wrong priority owner) and 4 (bigger fire) are the most recoverable. Translation 1 (no compelling event) is the most common — and the most fixable if you ask one question early enough. Translations 5 (never wanted it) and 6 (buying a competitor) are disqualification signals, not save attempts. The rep's win rate goes up the moment they learn to accept disqualification fast rather than fight for month three.

The 4 deal stages where it shows up — and why the response changes

The same phrase means different things at different deal stages. A "not a priority right now" from a cold prospect on day one is a different problem than the same phrase after a verbal commit in week six. The rep who uses one template for every stage burns the pipeline at both ends.

01

Pre-discovery (cold reply)

A cold prospect replies "not a priority right now" to your first sequence email. This is usually a polite no, sometimes a priority-owner problem. Response: do not argue. Log the reply, set a 90-day trigger-based reminder, move on. Fighting a cold prospect on the objection is how cold sequences get unsubscribed.

The reply is a signal that you reached an inbox — not a buying conversation.
02

Post-discovery call

You had the discovery call, the pain was confirmed, and the buyer replied "not a priority right now" when you sent the recap. This is the highest-leverage stage — you have enough context to diagnose which of the 6 real translations is in play. Run the 4-play framework here before you accept the stall.

Deals revived at this stage have the best close rates of any save motion.
03

Post-demo / mid-deal

Demo went well. Two internal follow-ups happened. Then "not a priority right now" lands in your inbox. Almost always a priority-owner problem: your champion liked the demo, the budget holder never saw it. Multi-thread immediately — skipping this step is how demos turn into ghosts.

One executive reply in 72 hours saves 3 of 10 stalled demo deals.
04

Late-stage (verbal commit, then stall)

You heard "we are going with you" — then silence — then "not a priority right now." This is a fire drill or a competitor. Ask, do not guess. The direct message — "is a bigger fire happening, or are you going another direction?" — saves or closes the deal inside a week.

Half of late-stage stalls are fire drills that return in 30–45 days if you stay calm.

The most expensive version is stage 3 — post-demo — because reps tend to over-invest time before the demo and under-invest effort after. A clean discovery, a good demo, and a polite stall is not a dead deal; it is a multi-threading failure. Send one tailored note to the priority owner within 72 hours. If no reply, disqualify — do not send five follow-ups that train the buyer to ignore your name.

The compelling event test: why features never beat urgency

A compelling event is a dated, external forcing function that makes the buyer act this quarter instead of next. Renewal dates, regulatory deadlines, board reporting cycles, missed quota numbers, platform migrations, new executive hires, upcoming audits, headcount plans. Pain without a compelling event is a problem the buyer can live with. Pain with a compelling event is a deal.

The MEDDPICC "I" — Identify Pain — is in practice Identify Compelling Event. If you cannot name the event on paper, with a date, in the buyer's words, the deal will stall. Every time. No feature demo, no ROI model, no social proof will beat the absence of a forcing function, because the buyer has no reason to prioritize you over the 40 other "nice to have" projects stacked in their Asana.

The test is brutally simple. After "not a priority right now," send one question: "Before I step back — is there a date this quarter when [pain] gets meaningfully worse or cheaper to fix?" If the answer is a real date — a renewal, a board meeting, a regulator filing — you have your event. Anchor the deal to it. Rewrite the recap. Send a second recap to the executive who owns that date.

If the answer is a non-date — "not really, just ongoing" — you have a problem, not a deal. The rep's move is to either surface a different event the buyer has not thought about (end-of-year hiring freeze, upcoming board, public commitment), or accept the disqualification. Reps who learn to read "not really" as a signal to disqualify fast end quarters stronger than reps who keep pushing.

A short mini-FAQ the best reps answer out loud before every deal forecast: (a) What is the compelling event? (b) What is the date? (c) Who owns the date internally? (d) Does that person know about us yet? If any of those four answers is missing, the deal is not forecastable at better than 20% — regardless of how good the demo went.

The 4-play response framework: pick the play before you reply

Once you have diagnosed which of the 6 translations is in play, pick a play. Do not write the email first — pick the play first. The email falls out of the play. Writing first is how reps end up sending a four-paragraph cost-of-inaction essay to a buyer whose real problem was a missing priority owner.

01

Re-discover No compelling event

Ask one question that surfaces a forcing function: renewal date, board reporting, regulatory deadline, headcount plan, missed number. If nothing surfaces, the deal is an information exchange — not a sales process.
02

Multi-thread Wrong priority owner

Get a second buyer in the room — the budget holder, the executive sponsor, the user who feels the pain daily. Send one tailored note per persona, not a forwarded thread. Single-threaded deals are how "not a priority" becomes "ghosted."
03

Reframe cost of inaction Buyer undervalues the pain

Model the cost of the status quo in their language — missed quota, runaway AWS bill, churn points, rep ramp time. The buyer cannot sell this internally without the math. You provide the math.
04

Nurture + disqualify Real timing block or polite no

Agree to step back, set a trigger-based follow-up, and stop manually chasing. Use the 30-60-90 plan below. If 90 days pass with no trigger, close the deal as lost — keep the forecast honest.

A simple decision tree from the 6 translations to the 4 plays: translation 1 (no event) → play 1 (re-discover). Translation 2 (wrong owner) → play 2 (multi-thread). Translation 3 (undervalued pain) → play 3 (reframe cost of inaction). Translations 4, 5, 6 (bigger fire, polite no, competitor) → play 4 (nurture + disqualify). Half the deals that used to close-lost at "not a priority" reopen once reps use this mapping instead of reaching for a generic objection-handling script.

Related reading: the sales objection handling framework covers the full stack of objections a rep hears, and the discovery call framework is how you surface the compelling event early enough that this objection never lands in the first place.

34%

Stalled deals revivable

Deals marked "not a priority" that recover inside 90 days with compelling-event diagnosis.

3of 10

Demo deals saved by multi-threading

Reaching one executive inside 72 hours rescues ~30% of post-demo stalls.

90days

Nurture ceiling

Past 90 days with no trigger, the deal is pipeline theatre. Close it.

Real meanings behind the phrase

Diagnose which one is in play before you reply. Label ≠ cause.

8 scripts that actually work (by scenario)

Eight scripts. Each one maps to a specific scenario — not a generic template. Adjust the bracketed variables to your deal and keep the length. Short replies do more work than long ones here; the buyer already thinks the deal is not urgent, and a six-paragraph email confirms that instinct.

1 Email · after discovery

When the buyer replies "not right now" after a discovery call

Totally fair — I heard on the call that [specific pain] is real but not on this quarter's board agenda. Before I step back, one question: if that [pain] compounded for two more quarters, what would it cost you? If the number is small, we should not be talking. If it is big, I think we should keep going — I have an idea for how to frame this to [CFO / exec name] that is less "new vendor" and more "cheapest way to stop the bleed."
2 Email · after demo

When the demo went well but the follow-up reads "not a priority"

Got it — the demo clearly was not urgent enough to beat what else is on your plate. Quick question: was the issue (a) the pain is real but smaller than I thought, (b) the priority owner is actually someone else, or (c) there is a bigger fire I should know about? If it is (b) or (c), I can help. If it is (a), I would rather disqualify than keep nudging.
3 LinkedIn DM

When the prospect went dark and you caught a priority-owner signal

Saw [Priority Owner] just [triggered event — funding, hire, post]. That usually shifts the [pain] conversation from "nice to have" into "this quarter." Worth 20 minutes to re-open the thread we had in [month]? If not, I will step back.
4 Email · multi-thread

Breaking single-thread when champion says "not a priority"

Thanks for the honesty — sounds like this is not the right quarter on your side. Quick ask: mind if I send a short note to [budget holder name] directly? I want to make sure they have seen the [specific metric] before it shows up in a board review. Happy to CC you so nothing is done behind your back.
5 Email · compelling event

When a forcing function already exists but was not named

One thing I want to double-check before I stop reaching out: your [renewal / reporting deadline / regulator / quota cycle] lands on [date]. Is the plan to absorb the [pain] through that, or do you want to see what the last-90-day version of this looks like? If it is the first, I will get out of the way.
6 Email · cost of inaction

When the buyer will not champion the deal internally

Totally understand internal prioritization is hard. To make this easier to defend internally, I built a 5-line cost-of-inaction model for your case: [number 1] on [metric], [number 2] on [metric], [number 3] on [metric]. If any of these are off, tell me and I will fix them. If they are close, that is the email that gets this back on the priority list.
7 Call · objection live

When the buyer says it on a discovery call out loud

"Fair — and I hear that a lot on the third call. Can I ask: is the pain real but later, or is the pain real but the wrong person is in the room? Because those two lead to very different next steps. If it is the first, I will send a trigger-based note every quarter. If it is the second, I would love 10 minutes with [priority owner]."
8 Email · graceful exit

When it is time to disqualify and keep the door open

Understood — I will stop pushing. One thing I will do: if [trigger event — funding, hire, renewal, new exec] happens on your side, I will reach out once with a specific angle. If none of those happen, we can both go quiet without it being weird. Appreciate the straight answer.

A quick note on length: the longest script here is 110 words. Most are under 80. The buyer already thinks the deal is not important; a 300-word email confirms it. The win is asking one specific question the buyer has to answer — not showing them how much you have been thinking about their business.

The 30-60-90 nurture plan — follow up without pestering

Once you have played your play and the deal still did not move, accept the stall and switch modes. Nurture is not "send a newsletter every month." Nurture is a small set of trigger-based touches on a clock. The goal is to be first in the inbox the day the buyer's priority changes — not to wear them down with frequency.

When	Action	Why
Day 0	Send the graceful-exit script	Resets the relationship from chasing to professional. The buyer's guard drops.
Day 14	One trigger-based message — only if a signal fires	A new hire, a funding round, a layoff, a LinkedIn post mentioning the pain. No signal, no send.
Day 30	Share one piece of value, not a pitch	A benchmark, a short post, a peer quote. No meeting request. Builds permission without pressure.
Day 60	Re-test the compelling event	A short email: "last time we spoke [pain] was not urgent — has the [trigger] happened yet?" One line. One question.
Day 90	Decision: re-engage, disqualify, or hand off	If a trigger fired, re-engage with a specific angle. If nothing changed, close-lost with the door open. Dead-air nurture past 90 days is pipeline theatre.

The hardest discipline is silence on day 21, day 35, day 47. A rep who can stay quiet between triggers looks more credible than a rep who emails every Tuesday. Silence tells the buyer the deal is priced fairly and the rep is not desperate. Noise does the opposite. Past day 90, move the deal to close-lost with the door open and stop manually monitoring — a proper sales workflow watches the triggers for you.

When to disqualify: the 3-signal test

Not every stalled deal is a save. Some are disqualifications wearing a polite mask. The 3-signal test tells you when to stop working the deal and move your hours to a live opportunity. All three signals have to be present — with any two, keep running the plays; with all three, close the deal and nurture on triggers only.

1

No compelling event surfaces after two asks

You have asked twice for a forcing function — renewal, regulator, reporting deadline, quota cycle — and nothing real has come back. The pain exists, but without a forcing function, it will live under the desk for another year. Disqualify, nurture on triggers only.
2

The priority owner refuses to come into the room

You asked to multi-thread once. Your champion said "let me handle it." You asked again. Same answer. The priority owner is not coming. The deal is either dead or will die in procurement — either way, selling harder will not fix it.
3

The buyer will not model cost of inaction with you

You offered the 5-line cost-of-inaction model. The buyer would not engage with the numbers — not "the numbers are wrong," but "we do not need to do this." That is a signal that the pain is smaller than the demo conversation implied.

Disqualification is not failure. It is the cheapest way to protect this quarter's hours. Every hour spent chasing a dead deal is an hour not spent on a live one, and the cost of that trade compounds across a territory of 30-80 accounts. The reps who hit quota most consistently are also the reps who kill their own deals fastest.

6 mistakes reps make after hearing 'not a priority'

Six patterns show up in almost every post-mortem on a lost "not a priority" deal. Each one is cheap to fix once you have seen it named. None of them is a tooling problem — they are all habits.

1

Sending "just checking in" on repeat

Every "just checking in" email confirms the buyer's instinct that the deal is not important. Replace it with a trigger-based note or silence. Silence beats noise.
2

Arguing with the objection instead of diagnosing it

The rep who says "well, the real cost of inaction is..." before the buyer has raised it is pushing, not selling. Diagnose which of the 6 translations is in play first. Then respond to that specific one, not the label.
3

Accepting the objection at face value and giving up

Half of "not a priority right now" replies are solvable — a missing priority owner, a missed compelling event, a silent fire drill. Accepting all of them at face value means you close-lost a third of winnable deals.
4

Single-threading through the stall

If the only person who replied "not a priority" is the champion, you have one data point from one node. Get an executive reply in the next 72 hours before you close the deal — or leave it open.
5

Hiding the stall from your manager

Reps who leave stalled deals in the forecast for two quarters make the forecast lie. The mature move: reclassify the deal, name the reason, set the trigger. Managers trust reps who kill their own deals.
6

Forecasting the deal for the next quarter anyway

Every "not a priority right now" that stays in forecast at "best case" is a small lie that compounds. Move it to "pipeline" or "close-lost — open door" and keep the forecast clean. Your next quarter depends on an honest starting point.

The meta-mistake underneath all six: treating the phrase as a signal from the buyer, instead of a diagnosis about your discovery. "Not a priority right now" tells you what the buyer is saying. It does not tell you why. The rep's job is the why.

How Gangly surfaces the real priority before you send the reply

Gangly runs the full sales workflow as one connected sequence — signal detection, outreach, call prep, live coaching, post-call notes, and CRM sync. For the "not a priority right now" problem specifically, three parts of the product remove the manual work of the diagnosis-and-play loop:

Signal Detection — watches the stalled account for compelling-event triggers (funding, exec hire, public post about the pain, job posting). The rep does not manually check — the signal arrives in the daily feed the moment it fires.
Call Prep Engine — surfaces the likely compelling event and priority owner before the discovery call so the rep asks the right question the first time. Most "not a priority" replies trace back to a discovery where the compelling event was never named.
Live Call Coach — when the buyer says "not a priority" live on the call, the coach surfaces the right reframe in real time, not after. The rep gets a prompt to ask "which of these three is actually happening?" instead of taking the phrase at face value.

The rep still runs the deal. Gangly handles the signal-watching, the priority-owner lookup, and the reframe prompt — so "not a priority right now" stops landing in the first place, and the ones that do land get the right play inside 24 hours instead of the default "just checking in" spiral.

Related reading: the price objection playbook covers the other most common mid-deal stall, and the multi-threading guide is the direct fix for the "wrong priority owner" translation.

Run the play

Stop losing deals to a four-word objection.

14-day free trial. Connect HubSpot or Salesforce in 3 minutes. No credit card.

Start free trial Book a demo

Frequently asked questions

What does 'not a priority right now' actually mean in B2B sales? +

'Not a priority right now' is rarely a literal timing statement. It usually means one of six things: the buyer has no compelling event, you were talking to the wrong priority owner, the cost of inaction was never quantified, a bigger fire started, the buyer was never interested, or they are buying a competitor and being polite. Diagnosing which meaning is in play is the first step — the label itself is almost useless. Respond to the real cause, not the phrase.

How should I respond when a prospect says 'not a priority right now'? +

Do not argue or over-explain. Send one short reply that does two jobs: acknowledge the stall and ask one diagnostic question. The simplest version is: 'Totally fair — quick question: is the pain real but smaller than I thought, is the priority owner actually someone else, or is there a bigger fire I should know about?' The buyer's answer tells you which of four plays to run next: re-discover, multi-thread, reframe cost of inaction, or nurture and disqualify.

Is 'not a priority right now' a polite no? +

Sometimes — but not always. Roughly a third of stalled deals that get labelled this way are recoverable inside 90 days if the rep runs a proper diagnosis. The tell that it is a polite no is two things in a row: no compelling event surfaces after a direct ask, and the priority owner refuses to come into the room. When both are true, it is a polite no — disqualify and move on. When one of them breaks, the deal is still alive.

How do I create urgency without being pushy? +

Urgency is not created — it is surfaced. Every B2B buyer already has forcing functions: renewal dates, regulatory deadlines, board reporting cycles, missed quota, upcoming audits, headcount plans. The rep's job is to find the one that matters and anchor the deal to it. Pushy reps manufacture urgency with fake deadlines and countdown emails; effective reps ask one question that surfaces the forcing function the buyer already lives with.

How do I follow up after 'not a priority right now' without pestering? +

Use a 30-60-90 nurture plan, not a weekly chase. Day 0: send a graceful-exit note. Day 14: one message only if a buying signal fires — a funding round, a new hire on the buying committee, a public post about the pain. Day 30: share one piece of value (a benchmark, a peer quote) with no meeting request. Day 60: re-test the compelling event with one short question. Day 90: decide — re-engage, disqualify, or hand off. Any nurture past 90 days with no trigger is pipeline theatre.

Should I disqualify a deal after hearing 'not a priority right now'? +

Only if three signals show up together: no compelling event surfaces after two asks, the priority owner refuses to come into the room, and the buyer will not model cost of inaction with you. With all three, the deal is cooked — disqualify, keep the door open on triggers, and move your effort to a live opportunity. With any one of the three, the deal is still worth running one diagnostic play on. Keeping dead deals in the forecast is how reps miss quarters.

What is a compelling event in sales? +

A compelling event is a dated, external forcing function that makes the buyer act this quarter instead of next. The common ones: a renewal date, a regulatory deadline, a board reporting cycle, a missed quota, a platform migration, a public commitment. The 'I' in MEDDPICC stands for Identify Pain, but in practice it is identify the compelling event — pain without an event is a problem; pain with an event is a deal. If you cannot name the event on paper, the deal will stall.