Buyers Are From Mars, Sellers Are From Venus

updated March 2026

Ask any senior leadership team why their customers buy from them, and you’ll get something fluent and rehearsed. A distinctive capability, some aspect of how they work. Yes, it will sound credible, but it will often have zero bearing on what customers would say if asked the same question independently. John Gray’s Men Are from Mars, Women Are from Venus sold 50 million copies on the premise that two people sharing a life can still be operating from entirely different internal maps of reality. The same dynamic runs through almost every company’s relationship with its customers, yet gets considerably less attention.

This has been documented in enough different ways that at some point we need to stop trying to defend such actions. Bain & Company surveyed 362 businesses and found that 80% believed they were delivering a superior customer experience. When Bain surveyed customers, just 8% of them agreed. That data is from 2005, and the intervening two decades produced an entire industry of customer experience platforms and satisfaction tracking programs, but gap doesn’t appear to have narrowed.

The story companies tell themselves

When a business develops a theory about why it wins, that theory gets converted into organizational work almost immediately. The sales team gets trained around it. Which customer stories get amplified in case studies, and which get quietly set aside, gets shaped by it. Product priorities and messaging bend toward it. Over time, the evidence for the theory becomes increasingly circular, because the inputs confirming it were selected by the people who already believed it.

The customers featured in marketing materials are the ones whose experience matched the over-arching narrative in the first place. Win-loss analysis gets filtered through assumptions built from the same story. A new competitor enters the market and the explanation for lost deals gets updated to incorporate them, without anyone asking whether the losses were actually happening for some other reason altogether. What we end up with is an internally coherent picture of our market position that has less contact with how buyers outside the building actually experience the business.

Why is that a big deal? Because strategy built on misreading why customers buy invariably optimizes in the wrong direction. The product roadmap prioritizes the features the internal story says matter, rather than what new and existing users want. Websites lead with whatever the leadership team has decided differentiates the company, rather than the problem we’re solving. Sales training reinforces the version of the pitch that confirmed the theory the last time someone wrote it down, rather than something more helpful and consultative. All of it internally coherent, and aimed at a buyer who exists in our internal narrative.

What buyers are actually weighing

Behavioral science has been consistent on the gap between the reasons people give for decisions and the reasons that actually produced them. Buyers rationalize their choices retrospectively, and they do it convincingly, including to themselves. Ask a procurement lead why their organization selected a particular vendor, and the answer will be coherent, logical and rational. It will cover capability, pricing, references, and 101 other things you can enter into a spreadsheet or supplier matrix. But while those things were considered, they were not the decisive factor.

In B2B purchasing contexts, the thing sitting underneath most evaluation processes is professional exposure. The person making or approving the decision is aware that if this goes wrong, it’s their butt that’s on the line. That rude awakening shapes how they interpret every interaction with a prospective vendor. A response that takes two days instead of two hours registers as a signal, as does pricing information that requires a conversation to access, or a salesperson who appears more interested in delivering a prepared narrative than in understanding the actual situation. Buyers are running a risk calculation, and most of the inputs feeding it are invisible to the provider being evaluated. Trust, in that context, is less about what the vendor claims and more about whether the experience of dealing with them ‘feels’ safe.

The reason this is worth sitting with is that buyers typically measure and optimize for the stated criteria, while the actual evaluation is happening across dimensions that aren’t being tracked. A vendor can score well on every explicit criterion and still lose the deal, because somewhere in the process the buyer quietly decided that choosing them felt risky in a way they couldn’t fully articulate. What customers believe they’re buying and what businesses believe they’re selling tend to occupy different territories.

The feedback problem

Customer feedback, in the way most organizations collect it, is largely a method for confirming what the business already thinks they know. Questions get written by people who have a preconception about the answers, and results get discussed in reviews attended by the same people who approved the strategy the feedback is supposedly evaluating. When a score comes back lower than expected, the conversation tends toward operational adjustments rather than toward whether the underlying model is correct.

Supposing a customer scores onboarding a 6 out of 10 and adds a note that it felt confusing in places. That response will be logged, and may even generate a support ticket. Any subsequent discussion will almost certainly center on what can be tweaked in the onboarding flow to move the score towards an 8 or higher. But what won’t happen is a conversation with that customer about what specifically they felt confusing, partly because the answer has a reasonable probability of implicating something larger than simply what’s been defined as “the onboarding process”. If anyone was allows to dig a but deeper, they find an assumption the product team has been making for years that buyers don’t share. Since those are much harder and deeper conversations to have, the feedback mechanism processes the signal without transmitting the information it actually contained. We continue to live inside our own bubble, bathing in the false reassurance that what we’re doing is fine and dandy.

There’s a version of customer listening that functions as organizational inoculation against actually having to change. Businesses with the largest gaps between self-perception and customer perception aren’t short of research or data. What’s missing is a sincere appetite for what any research might actually reveal.

The conversations most companies avoid

The most diagnostic conversations a business can have are typically with buyers who nearly chose someone else, or with customers who left. These conversations get avoided at an organizational level that often looks like busyness, but functions more like self-protection. They have a credible probability of producing information that disturbs the internal consensus, and organizations, like people, are not naturally drawn toward that.

A customer who churned and is now willing to speak candidly is not a PR problem to be managed. They’re a more accurate signal about the actual customer experience than any collection of post-purchase satisfaction scores from customers who are still invested in the relationship going well. The churn conversation might surface a product limitation that the company knows about internally but hasn’t prioritized fixing, or reveal that the sales process created expectations the delivery couldn’t meet. A competitor might have won on something other than the dimension the company assumed was the battleground. All of that is worth knowing, which makes it all the more crazy that so few businesses actively pursue it.

Building ongoing customer relationships that can hold these conversations requires something beyond a structured feedback program. It requires a genuine organizational tolerance for uncertainty about why things are going well, and a willingness to treat the answer to that question as something that needs to be actively tested rather than assumed. That’s a harder thing to build than a survey tool, and it’s less visible on a quarterly dashboard, which is probably a reasonable explanation for why it remains so rare.

The Bain figure tends to get cited in articles about customer experience as a way of illustrating the scale of the problem. But the real headline is the structural reason why the gap persists across industries and over decades, despite the significant investment organizations make trying to close it. Businesses are not failing to listen to customers because they don’t value insight, but because the systems built to capture that insight were designed by the same internal consensus they would need to challenge in order for any of it to be useful.

Most businesses already have some awareness that the version of events they carry internally and the version their customers would tell aren’t quite identical. That awareness tends to stay comfortably vague rather than being tested against anything specific, which is probably how it prefers to stay.