There's a mistake I made repeatedly in my first year of enterprise sales. I would get excited about a deal, build a great relationship with my champion, put together a compelling business case — and then watch the whole thing stall at the top.
The problem was never the champion. The problem was that I hadn't connected their priority to what the person holding the budget actually cared about.
The short version
Your champion cares about their initiative. The budget-holder only cares about revenue, risk, and cost. Connect the two or the deal dies at the top.
Use this tomorrow
Ask: "How does your priority tie into what your CEO is focused on this year?" If they can't answer clearly, you have more qualifying to do.
Translate everything into C-suite language: revenue growth, risk reduction, cost optimisation. Not features — financial outcomes.
I was working a mid-market deal — a software company, around 300 employees, growing fast. My champion was the VP of Operations. She was sharp, motivated, and genuinely wanted to buy. The business case was solid. The product fit was real.
We got to the commercial stage and I thought we were close. Then her CEO got involved. One call, a few questions, and the deal went cold.
The CEO's feedback came back through my champion a week later: "He doesn't see why this is a priority right now."
I asked her to walk me through what she'd said in that conversation. It became clear immediately what had happened. She had presented the initiative in operational terms — efficiency gains, process improvements, team productivity. All true. All compelling to her.
But the CEO was in the middle of a fundraising round. His entire focus was on growth metrics, burn rate, and investor narrative. Operational efficiency, as she'd framed it, wasn't on his radar.
We hadn't lost the deal on merit. We'd lost it because no one had translated the value into his language.
At Gartner I was introduced to a framework for what we called a mission critical priority — and it changed how I qualify deals entirely.
A priority is truly mission critical when it meets four criteria:
- It ties directly to the corporate objective — revenue growth, risk reduction, or cost optimisation
- It has an associated challenge the prospect is actively struggling to solve
- It is time-bound — there's a deadline or consequence attached
- It is owned or visible at the C-suite level
If a prospect's priority doesn't meet all four, you're in "nice to have" territory. And nice to have doesn't close.
I now ask this question in every qualification conversation, usually after I've understood the prospect's main priority:
If they can answer that clearly — you're in business. If they can't, you have more qualifying to do. And you need to be honest with them about why: if this initiative can't be connected to what the ultimate decision maker cares about, the deal will stall when it reaches them.
The second thing I'd do differently is translate everything into C-suite language earlier. Not "this system improves data quality" but "this reduces the risk of a compliance failure that could cost you €2M." Not "this streamlines your IT process" but "this frees up 20% of your IT budget to reinvest in growth."
That translation is difficult. But it is the job.
You can have the best solution, the best relationship, and the best business case — and still lose the deal because the CEO doesn't see themselves in the problem.
Your job isn't just to understand your prospect's world. It's to connect that world to the person holding the pen.
If the budget-holder doesn't care, you don't have a deal.
Has this ever cost you a deal? I'd genuinely like to hear — hit reply and tell me.