← Back to the knowledge base

Knowledge base · Verbindend Zakendoen

Why NO often comes before you ask for a YES

How often have you, as an entrepreneur, thought: my product or service really solves a problem, so why does this customer say NO? Especially if you are convinced of the value you provide, such an answer quickly feels illogical. You have understood the problem well, made a suitable proposal and perhaps even quoted a competitive price. Yet there is no signature.

How often have you, as an entrepreneur, thought: my product or service really solves a problem, so why does this customer say NO? Especially if you are convinced of the value you provide, such an answer quickly feels illogical. You have understood the problem well, made a suitable proposal and perhaps even quoted a competitive price. Yet there is no signature.

Then explanations are quickly found. No budget. Wrong moment. Doesn't suit us anyway. Next prospect. Sometimes that's all true. But after more than twenty-five years on both the purchasing and sales sides of the table, I have come to find one question increasingly interesting: what did this other person actually have to be able to understand, trust and oversee before a YES became possible at all?

A NO does not always say anything about the value of your offer

Understandably, salespeople often look at the proposal. Is the price correct? Is the proposition sharp enough? Have we explained the benefits well? These are relevant questions, but they sometimes start too late. A decision is made during everything that precedes it: the way you listen, what questions you ask, how much space you give, what you do and do not explain and whether someone feels understood enough to take the conversation seriously at all.

I have experienced that often enough myself. Sometimes I could explain exactly why something was a good choice and little happened. In other conversations, movement arose remarkably quickly, even though I had "sold" much less. The difference was rarely in a brilliant script. It was more often the moment when I stopped convincing and started listening better to how the other person came to a decision.

That's where something started for me that later grew into the Connective Code. Not as a technique to hear YES more often, but as a language to better understand why people can react very differently with the same information.

A good conversation does not start with your sales goal

That may sound strange coming from someone who has worked in sales, purchasing and negotiations for years, but I believe that a commercial conversation becomes better as soon as the seller temporarily forgets that something needs to be sold.

Not because turnover is unimportant. Of course, something has to happen eventually. But as soon as my need for a YES becomes greater than my curiosity about the other person, the conversation changes. I will complete more quickly, explain more, pile up arguments or deal with objections that may not be the real objection at all. The customer usually feels this sooner than we think.

For me, an authentic commercial conversation does not mean that you just sit around and talk without preparation. Exactly not. It requires that you are well enough prepared not to have to constantly focus on yourself. You know your offer, limits, price and options. This creates space to hear what is really happening on the other side of the table.

Image accompanying Why NO often comes before you ask for a YES

Four different reasons not to say YES yet

That's where the Connective Code becomes practical. People may not be ready to make a decision for very different reasons. Someone who is looking for Vision wants to understand where a choice leads, how your solution fits into a bigger picture and why this is the right direction in the first place. If you immediately start talking about functionalities, you may already be providing information that was not yet requested.

Someone who needs Trust pays more attention to the relationship. Do you really understand what's going on? Is your intention correct? Will you also do what you promise after the signature? That person may be convinced of the content and still not be able to give a YES because something is missing relationally.

Structure wants to know how it will work. What happens after approval? Who does what? What exactly does it cost? What steps follow? When will we notice results? An inspiring story without a process can raise additional questions for that person. And Action ultimately wants movement: what is the decision, when do we start and what is the next step? Another extensive analysis could actually be counterproductive.

None of those four are better. The problem arises when I confuse my own preference with “good sales”.

Sometimes the best agreement starts with a sincere NO

That is also why I believe less and less in the idea that a good salesperson should be able to overcome every objection. Sometimes NO is exactly the right answer. For the customer and for you.

If someone doesn't have enough budget, has different priorities or simply doesn't fit what you can deliver, you don't have to turn it into a creative psychological obstacle course. An adult commercial conversation can also end with: we shouldn't do this.

That may sound less spectacular than “closer more”, but it often results in better relationships. People remember that you didn't try to get a decision out of them. And if circumstances change later, there's a good chance the conversation can start again from a place of trust rather than recovery work.

For me, a YES is therefore only valuable if the other person really understands what he is saying YES to.

You too should be able to say YES

Therein lies the other half of the story. We talk a lot about customers who have to say YES, but you are also a participant in the agreement. Do you want this customer? Can you deliver what you promise? Does the work match your expertise, values ​​and available capacity? Or are you mainly relieved that turnover is coming in?

I have learned through my years in both purchasing and sales that the best deals rarely arise when one party wins. They arise when both parties see sufficient value to want to take responsibility for what they agree on.

That also requires that you dare to say NO. Against an assignment that does not fit. Under conditions that you will regret later. To a customer who expects something that you do not want or cannot deliver. At a turnover that is attractive on paper, but in practice mainly consumes energy.

Receiving a YES becomes a lot easier when you are not desperately waiting for every YES.

Maybe you don't need as much convincing

That's probably my biggest change in how I look at selling. I no longer have to prove that my solution is great before I know what the other person is really trying to decide on. I prefer to understand what someone needs in order to make a good choice.

Sometimes Vision is missing. Sometimes Trust. Sometimes Structure. Sometimes action simply has to finally be taken. And sometimes everything is clear and the answer remains NO. That is also information.

For me, connecting business does not mean that everyone ultimately says YES. It means that a conversation arises in which both parties are free enough to make a real choice. Without scripts that try to be smarter than the other. Without pulling. Without pressure. And especially without turning a customer into an opponent to be overcome.

Where is your YES now?

Do you notice that customers, colleagues or other discussion partners seem to join in substantively, but that decision-making still remains stuck? Then bring your three most important challenges to an introductory meeting. Together we look at where communication may still lack Vision, Trust, Structure or Action and where people may unintentionally drop out as a result.

Would you first like to discover which language you naturally speak most easily and what that means for the way you sell, listen and negotiate? Then take the Connective Code Quiz.