"This Is a Nice-to-Have Right Now" — Losing to Other Priorities, Not Other Vendors

The loss you never see coming

Ask a rep why a deal died and you will usually hear a competitor's name. Ask the buyer and you will hear about a data migration.

I have sat in a lot of pipeline reviews, at big companies and at the four businesses I built myself, and the pattern holds. The deals that go to a bake-off are loud. You know you are in one. There are security questionnaires and reference calls and a procurement person who wants your SOC 2 report. Those deals feel like work, and when you lose them you know exactly why.

The deals that quietly die are the ones where you were never really compared to anything. You were compared to a Salesforce instance nobody trusts, a Workday rollout that slipped two quarters, and a headcount plan that got frozen in November. You lost to a queue.

And the way the buyer tells you this is almost always the same sentence: "This is a nice-to-have right now."

That sentence gets treated as an objection to handle. It is not an objection. It is a ranking. And you cannot argue your way up a ranking you have not seen.

What "nice-to-have" actually means

When someone says nice-to-have, they are not saying your product is useless. They are usually saying the opposite. Useless things get a flat no. Nice-to-have means it registered, it made sense, and it landed somewhere below the line.

The line is real. It is drawn by a finite number of things: the projects that already have a budget code, the projects that already have a named owner, and the projects the CEO mentioned on the last all-hands. Everything above the line has already consumed political capital. Somebody stood up and said they would deliver it. That person's bonus is attached.

You are asking to be inserted into that list. Not compared against a competitor. Inserted. And the buyer knows something you do not, which is what is already on the list and how much pain each item is causing.

This is why the standard response fails so badly. The standard response is to restate value. "I understand, but let me just reiterate that we would save your team ten hours a week." You have now told a person who ranked three things above you that they ranked wrong, based on information you do not have. Even if you are correct, you have made them defend the list instead of showing it to you.

Almost every rep I have watched do this loses the thread within two exchanges. The buyer gets polite. Politeness is the sound of a deal ending.

Arguing value is the wrong move because value was never the problem

Here is the mental model I use. Every buyer has a stack. The stack is ordered by a mix of pain, politics and inertia, and the ordering is mostly invisible from the outside.

When you pitch, you are handing them a card and asking them to slot it into the stack. They slot it. It lands fourth. They tell you it landed fourth by saying nice-to-have.

There are only two useful moves at that moment, and neither of them is arguing.

The first is to see the stack. You cannot move a card you cannot see the position of. If the three things above you are a compliance deadline, a platform migration and an open req they cannot fill, those are three very different situations, and two of them are actually good news for you.

The second is to change what card you are. Not the product — the card. A new line item competes with everything. A component of something already funded competes with nothing. More on that shortly.

Both moves start with questions, and the questions are not clever. They are just specific.

The question set for surfacing the priority stack

When I hear nice-to-have, I stop selling entirely. Full stop, mid-sentence if I have to. Then I say some version of this:

"That is fair, and honestly it is useful to know now rather than in March. Can I ask what is ahead of it? Not to argue — I genuinely want to know whether this is a this-quarter conversation or a next-year one, because I would rather stop bothering you than keep chasing something that was never going to move."

That framing matters. You are giving them permission to deprioritise you, which is the only condition under which most people will tell you the truth. If they think the information will be used against them, you get a vague answer about "a lot of competing initiatives."

Then you work through the stack. These are the questions, roughly in order:

"What are the two or three things that are ahead of this?" Ask for two or three specifically. Asking "what else is going on" gets you a shrug. Asking for a number gets you a list.

"Which of those has a hard date on it?" This separates deadlines from ambitions. A compliance deadline in Q2 is immovable and will consume attention until it passes. A "we want to improve onboarding" project has no date and will slip forever, which means it is not actually above you — it is just louder.

"Who owns each one?" You are looking for whether the same person owns your project and the thing beating it. If your champion owns both, you have a resourcing conflict and you probably lose. If a different team owns the thing ahead, you may be competing for budget but not for your champion's calendar, and that is a much easier fight.

"What happens to the business if that project slips a quarter?" Ask it about the thing beating you, not about your own deal. The answer tells you how real it is. "Nothing much, it just gets embarrassing" is a very different answer to "we cannot close the books."

"Is the thing ahead of us going to make this problem better or worse?" This is the question that opens the reframe. Migrations, re-platforms and reorgs almost always make the problem you sell into worse before they make it better. If they are moving CRM instances, their reps' pipeline hygiene is about to get ugly. If they are freezing hiring, every existing rep's productivity just became the only lever they have.

"When that project lands, what is the next thing that comes off the shelf?" You are asking whether you are on the shelf at all. Some people will say "honestly, probably not this." That is a gift.

None of this is new — it is discovery, done later than it should have been. If you are hearing nice-to-have often, the real fix is upstream, and the 25-minute discovery diagnostic I use for SaaS buyers exists mostly to surface the priority stack on the first call instead of the fourth. The version for selling into VPs, SDR managers and CROs leans even harder on it, because sales leaders run more concurrent initiatives than almost anyone and they are the most likely to genuinely want your product and genuinely not have room for it.

The reframe: stop asking for a new line item

Once you can see the stack, you have a decision to make about what you are.

A new line item is the hardest thing to sell. It requires someone to make a fresh case, find fresh money, and take fresh responsibility. In most companies that is a quarterly cycle at best, and in a lot of companies it means waiting for annual planning.

A component of a funded project is a completely different purchase. The money exists. The owner exists. The justification has already been written and approved by people above your champion. All you are doing is changing how a slice of an approved budget gets spent.

So the move is to find the thing above you in the stack and attach.

The attachment has to be honest. You are not claiming to be a migration tool if you are not one. You are identifying the part of their funded project where your product removes risk, effort or delay. Concretely:

If the project ahead of you is a CRM migration, your pitch is no longer "we improve rep productivity." It is "during a migration, your reps will be working out of two systems and their activity data will be a mess for a quarter. Here is what we do about that specific window." You are now a migration risk-mitigation cost, not a productivity nice-to-have.

If the thing ahead is a hiring freeze, you are not selling growth, you are selling capacity from the headcount they already have. The freeze is not your enemy. The freeze is your budget. Somebody just took money out of the payroll column and it has to do something.

If the thing ahead is a compliance or regulatory deadline, and you touch that surface at all, you attach to it and you inherit its urgency. I have found this especially true when selling into regulated industries, where the deadline is externally imposed and non-negotiable. The financial services discovery playbook is built around that, because with wealth management buyers the compliance calendar frequently is the priority stack, and everything else queues behind it.

If the thing ahead is a reorg, be careful. Reorgs move the buyer. Attaching to a reorg means attaching to a person who may not have the same job in eight weeks.

The script for the attachment is short:

"Given the migration is the priority, I do not think this should be a separate project. I think the honest framing is that it is part of the migration budget, because the risk it removes shows up during the migration, not after it. Would it be worth me putting together a version of this scoped just to that window, so you can look at it as a migration cost rather than a new spend?"

The buyer either engages with that or they do not. If they engage, you have moved from a new line item to a funded one, and the deal cycle just got shorter. If they do not engage, you have learned something important, which brings us to the harder decision.

Fight now, or set a real trigger

After you have seen the stack and tried the attachment, you have to make a call. I use three tests.

Is there a date on the thing beating me? If yes, and the date is within about a quarter, waiting is rational. The blocker will resolve itself and you can come back into an empty slot. If there is no date, waiting is not a strategy, it is hope. Undated projects do not finish. They get replaced by other undated projects.

Does my champion still want this? Not "do they think it is interesting." Do they want it. The test is whether they will spend any capital at all — take a fifteen-minute internal meeting, forward an email to their boss, add a line to a planning doc. If they will not spend fifteen minutes, they will not spend fifty thousand dollars, now or in six months.

Is the problem getting worse on its own? Some problems compound. Data debt, tech debt, ramp time on a growing team. If the problem compounds, time is on your side and a trigger-based follow-up is genuinely worth setting. If the problem is flat, it will still be a nice-to-have next year, and you should qualify out.

If all three point the wrong way, say so out loud. "Based on what you have described, I do not think this is a this-year conversation, and I would rather be straight with you than keep putting invites in your calendar. Can I check back when X happens?"

Buyers remember the reps who let them go. It is a small industry.

What a real trigger looks like

Here is where most follow-ups die. The rep says "great, I will circle back in Q3," sets a task, and in Q3 sends an email that says "just checking in as promised!" Nothing has changed except the date, so the answer is the same.

A date is not a trigger. A trigger is a named event with an owner.

Bad: "I will follow up in six months."

Good: "You said the Salesforce cutover is the gate. Can we agree that when the cutover is signed off — not started, signed off — that is when this comes back on the table? And is it you who signs that off, or Priya?"

Now you have three things you did not have before. You have an event both of you named. You have an owner. And you have a reason to make contact that is about their world rather than your pipeline.

Other triggers that actually work: the new VP starts. The board approves next year's plan. The renewal with the incumbent vendor comes up. The audit closes. The freeze lifts. Headcount reopens. The pilot with the other team finishes.

Write the trigger down in the buyer's own words and send it back to them in the recap email, because the recap is where the trigger becomes a commitment rather than a comment. "To make sure I have this right: not now, revisit when the cutover is signed off, which you expect around the end of Q2 and which you own. I will not chase you before then." If they correct you, brilliant — the correction is more discovery. If they confirm it, you have a re-entry point that does not require you to invent a reason to call.

Then build the mechanism to actually catch the trigger. Job change alerts on your champion and their boss. Funding announcements. Earnings calls if they are public. A calendar reminder is the weakest option because it fires on your schedule, not theirs, but it beats nothing.

Spotting the polite exit

Sometimes nice-to-have is not a ranking. It is a no, wearing a coat.

The tells are consistent. The stack is vague — they will not name the projects ahead of you, or the names change between calls. There is no owner for anything, including your project. They will not put a trigger in writing, or they agree to one enthusiastically and then decline to name who owns it. They keep the relationship warm but will not spend a single unit of internal effort. And when you offer the attachment reframe — the version scoped to the funded project, the smaller thing, the pilot — they do not engage with the substance, they just repeat the timing.

That last one is the strongest signal. A real priority conflict is a timing problem, so a smaller, cheaper, faster version of the offer changes the maths and the buyer will at least think about it. A polite no is a want problem, and shrinking the offer changes nothing, so they hand back the same sentence in different words.

When I see that pattern I ask directly, and I make it easy to say yes to: "I might be reading this wrong, but it feels like the timing is not the real issue. Is this something you would want if it were free and instant? Totally fine if the answer is no — it just changes what I do next."

Some people will take the exit. Good. You get the slot back in your pipeline and you stop lying to your forecast. Others will tell you the real objection, which is usually about trust, internal politics, or a previous vendor who burned them. Both outcomes beat a stage-four deal that has not moved since August.

This matters more when you are selling into partner-led firms and other consensus-heavy organisations, where nobody says no directly and everything sounds like a maybe. The professional services discovery playbook goes deeper on reading those rooms, because the politeness is structural rather than personal.

The part that is actually hard

None of this is complicated to understand. It is hard to do live, when a buyer you have spent five weeks on says the words and your stomach drops and every instinct you have says defend the value.

That instinct is trained in. Untraining it takes reps, and you do not want to do those reps on real deals. If you want to get better at this specific moment, I would take the question set above, have someone throw "this is a nice-to-have right now" at you cold, and practise stopping mid-pitch and asking what is ahead of you without a trace of defensiveness in your voice. That is the whole skill. We built DrillCall so you can run that drill against an AI buyer who pushes back the way real ones do, as many times as you need, before it costs you a deal.

But the tool matters less than the shift in framing. Stop treating nice-to-have as a verdict on your product. Treat it as an invitation to see the list. Most reps never ask what is on it, which is why most reps lose to a data migration and record it in the CRM as "lost to competitor: none."