I spent much of my career believing persistence was one of the most important qualities to being one of the best salespeople. If a customer had concerns, you worked through them. If the timing was not right, you stayed in touch. If someone did not immediately understand the value of what you were offering, you found another way to explain it.

I still believe persistence matters, but my understanding of it has changed. After years of working in commercial sales, enterprise technology, security software, startups, and go-to-market roles, I have become much more comfortable asking a question that would have bothered me earlier in my career. Should we actually be trying to win this deal?

Sometimes, the answer is no. That can be difficult to accept when you work in sales. You have a target to hit, a pipeline to review, and a company expecting growth. You may have already invested weeks or months in an opportunity. Walking away can feel like admitting that all of that time was wasted.

The longer I have worked in this field, however, the more I have seen what happens after a bad sale. Getting the signature isn’t always the same as winning.

A Customer Can Say Yes for the Wrong Reasons

Salespeople spend a lot of time thinking about why customers say no. I think it is equally important to think about why they say yes.

When I am looking at an opportunity, I want to know whether the customer understands what the product actually does. I want to understand whether there is a real problem we can solve and whether the customer has the people and resources required to implement the solution. I also want to know whether their expectations are realistic.

Those questions matter because enthusiasm during a sales process can hide problems that become obvious later. A customer may be genuinely excited about a new technology without fully understanding what it will take to make it useful inside the organization.

I have worked around complex technology for most of my career. These products are rarely purchased, switched on, and forgotten about. There may be integrations to complete, employees to train, security requirements to address, internal approvals to obtain, and existing workflows to change. Several parts of the organization may need to cooperate before the customer receives the value everyone discussed during the sales process.

If those conditions aren’t there, I can keep selling. I can keep explaining features and benefits, answering objections, and trying to move the opportunity forward. I might even get the deal across the finish line. The question I have learned to ask is what happens next.

That question matters more to me now than it did earlier in my career.

Winning the Deal Is Not the End of the Story

One advantage of spending a long time around technology companies is seeing what happens after the sales process ends. You learn that a bad fit does not disappear when the contract gets signed.

Someone has to implement what was sold. Someone has to support the customer when problems come up. The customer has to convince employees to use the new system, and eventually someone will ask whether the technology actually delivered what everyone expected.

This is where a sale that looked great on a spreadsheet can become expensive. The customer may have expected a capability the product was never designed to provide. Implementation may require resources they do not have. The product may technically solve the problem but fit poorly with the customer’s existing systems or processes.

The sales team may have recorded a win, but other people are left dealing with the consequences. Over time, I have become much more aware of that responsibility. A salesperson is not doing the company a favor by creating a customer relationship that begins with unrealistic expectations.

There Is a Difference Between an Objection and a Bad Fit

This is where the decision gets complicated, because I don’t think salespeople should walk away whenever a customer raises an objection.

Customers are supposed to have questions. They should challenge assumptions and ask about price, implementation, security, integration, risk, and expected results. In enterprise technology, I would probably be more concerned if nobody asked difficult questions.

The challenge is understanding what those objections really mean.

If a customer says the price is too high, for example, the real problem may not be the price. Perhaps we have not demonstrated enough value. Maybe another project has become a higher priority and is competing for the same budget. It is also possible the customer simply doesn’t have a problem significant enough to justify the investment.

Those situations may sound similar during a sales conversation, but they require very different responses. That is why I try not to treat every objection as something that needs to be defeated. Sometimes an objection is useful information.

During my career, I’ve had conversations where I wondered why I was working so hard to convince someone they had a particular problem. If I have to spend most of the conversation persuading someone that the problem exists, I have to consider whether it’s important enough to them to justify buying the solution.

I think that is a healthy question for a salesperson to ask.

Saying No Is Harder When You Need the Sale

It is easy to talk about walking away from bad business when the pipeline is full. The decision becomes much harder when the company needs the revenue.

I don’t pretend businesses operate in a perfect environment where salespeople can casually turn down opportunities. Startups need customers. Sales teams have quotas. Leaders have employees, investors, forecasts, and expenses to think about. I have worked with startups for more than a decade, so I understand how real that pressure can become.

Sometimes, taking on an imperfect customer makes sense. A young company may need to stretch a little. The team may make accommodations, learn from the implementation, improve the product, and become better because of the experience. I do not think every difficult deal is automatically a bad deal.

I try to distinguish between an imperfect fit and a fundamentally bad fit.

If winning the business requires promising something the company cannot reliably deliver, ignoring obvious implementation problems, or letting a customer leave the sales process with expectations unlikely to be met, the revenue can come with a much higher cost later.

That cost might show up as additional support requirements, frustrated customers, stressed employees, or damage to the company’s reputation. A deal that looked valuable when it closed can become far less attractive once you include those costs.

I Have Become More Comfortable With a Good No

Earlier in my career, I probably viewed the word “no” too simply. A yes felt like success, while a no felt like failure.

I do not see it that way anymore.

A good no can save both sides significant time and frustration. It can also build trust. There is something valuable about being willing to tell a prospective customer that your product is not the right answer for a particular situation instead of trying to force every conversation toward a contract.

That does not necessarily mean the relationship is over. Circumstances change. Products improve. Budgets change. Companies grow, and problems that were not priorities can become important later.

A customer who is not a good fit today might be a very good fit two years from now. If that happens, I would rather have the next conversation begin with credibility than with memories of a product that was oversold the first time around.

Good Salespeople Still Have to Sell

None of this means I have stopped believing in persuasion. Good salespeople should be able to explain value. They should challenge assumptions when appropriate and help customers look at problems from a different perspective. They should be able to explain why changing an existing process or adopting a new technology may be worthwhile.

If every customer immediately understood why they needed every new technology, companies would not need experienced salespeople in the first place.

However, I believe there is a difference between helping someone recognize value and trying to manufacture a fit that is not there. Experience has made that distinction easier for me to recognize.

These days, I am less interested in simply asking whether we can close a particular opportunity. I want to understand what happens if we do. I want to know whether the customer will actually use what they are buying, whether we can deliver what they expect, and whether the problem is important enough to justify the investment. I also want to know whether we are creating a relationship that both sides will still feel good about after the excitement of the sale is gone.

There will always be some uncertainty in those decisions. I have been around long enough to know that you cannot predict exactly how every customer relationship will develop. Sometimes a difficult sale turns into an excellent partnership, while an opportunity that looks perfect on paper becomes much more complicated than expected.

The goal is not to eliminate that uncertainty. It is to recognize the warning signs and be willing to act on them.

If the answers keep pointing in the wrong direction, sometimes the best sales decision is to stop selling. You may lose a deal today, but you may also avoid creating a much more expensive problem tomorrow.