Every Customer Negotiation Is an Emotional Battle Disguised as a Rational One

I had a customer trying to cut costs by any means necessary. Five-year relationship, 30+ guards deployed, solid operational track record. Didn’t matter. The customer rep kept pushing: reduce compliance expenses, cut our fee, extend payment terms.

My ops manager spent weeks explaining the numbers. Here’s our margin breakdown. Here’s why compliance costs are non-negotiable. Here’s what happens to service quality if we cut pricing. Standard rational defense.

None of it worked.

Then my ops manager asked a different question: “What’s really going on?”

The customer rep admitted the truth. New manager above him. First meeting, the manager had talked about cost savings. Now he was trying his best to show results before their quarterly review on new initiatives undertaken by everyone in his team.

This wasn’t about our numbers. It was about developing a solid reputation in front his new manager

Once we understood that, we stopped defending our pricing and started solving his problem. We undertook a complete operations and security audit with him. We realised the following:

• Two daytime gates with minimal traffic, which could be closed and traffic redirected.
• One nighttime location handling 10% of the load while three others carried 90%, so we could close and redirect traffic

We could reduce three guards cut - a 10% manpower reduction. We kept our pricing intact, he got his cost savings story for his new manager.

We spent weeks on rational arguments when we should have spent one hour understanding the emotional pressure he was under.

This Pattern Has a Name

Robert Greene calls this the Law of Irrationality in The Laws of Human Nature. His central argument: We are not creatures of logic but of emotion. Beneath our polished, rational surface lie deep impulses that quietly drive our behavior.

Most decisions stem from emotion—our need to win, to fit in, to avoid standing out. We dress them up with logic afterward.

Greene’s framework: when someone resists your rational argument despite clear evidence, you’re not in a logical debate. You’re watching emotional forces at work that neither you nor they fully recognize.

The key insight: If you’re trying to win an emotional argument with a spreadsheet, you’ve already lost.

I’ve tested this framework twice in vastly different contexts. Once in 2015 at Ola during a growth war with Uber. Once in 2024 with a warehouse customer fighting internal politics. The pattern held both times.

First Encounter: Ola, 2015

When I joined Ola’s West India operations, the directive was simple: add as many cabs as possible in 30 days. The growth equation was obvious: More cabs lead to shorter wait times, which result in more bookings.

Except in Mumbai, it wasn’t working.

I could see the problem clearly. Our pricing was 20% higher than Uber’s. Most Mumbai bookings were long-distance trips where price mattered. The fix was obvious: rationalize pricing first, then add cabs.

I presented the data. Trip patterns, competitive pricing analysis, projected booking growth. All the rational arguments.

They were ignored.

This was Greene’s Law in action—I just didn’t recognize it yet.

The company was in a growth war with Uber. The CEO’s directive created an simple dikat: more cabs equals winning. The entire organization aligned around that instruction. My data didn’t matter because it challenged the story everyone was invested in.

I didn’t have the credibility to shift the conversation. So I did what was expected and waited for an opportunity

Two weeks later, Finance flagged a problem. In 2015, Ola and Uber provided smartphones to new drivers (₹5,000 per device). The monthly budget was around 6,000 phones. Suddenly it jumped to 15,000+, a 2.5X increase in a single month.

Finance investigated and discovered the issue: 80% of newly on-boarded cabs were inactive after two weeks. The phones were gone and neither were these cabs available in the platform.

That broke the emotional spell.

The narrative shifted from “more cabs equals growth” to “we’re burning money for growth.” Same data I’d been showing for weeks—different emotional context.

I worked with Marketing to reintroduce the pricing proposal—not as opposition, but as an alternative solution to the growth problem. I presented my city-specific metrics: cabs were up, but bookings per cab weren’t growing at the same pace.

This time, the same data was viewed differently. Pricing was approved within days.

Bookings increased 20% within two weeks. Not because of more cabs, because our pricing was competitive and cabs were available on the road.

What I learned: When your rational argument fails, you’re not in a rational battle. You’re in an emotional one. The data doesn’t change—the emotional context does.

Testing It 2024: The Warehouse Customer

The warehouse customer story from the opening? That’s Greene’s Law playing out again, nineyears later.

My ops manager was making rational arguments for weeks. Compliance costs are mandatory. Our pricing reflects actual costs. Payment terms affect our cash flow.

All true. All ignored.

The emotional reality: The customer rep had a new manager breathing down his neck about cost savings. He needed a win before the next review meeting. Our margin structure was irrelevant to his actual problem.

Once we diagnosed the emotional pressure, we re-framed the solution. Instead of defending our pricing, we asked: “How do we show cost reduction through operational efficiency?”

Security audit. Gate consolidation. Manpower optimization. Same pricing, different story for his manager.

What Greene’s framework predicted: The customer rep wasn’t being irrational by ignoring our numbers. He was being perfectly rational within his emotional constraints—succeeding in a new reporting structure.

What Survived from Greene’s Framework

Greene’s core insight holds: most organizational decisions are emotional first, rationalized second.

What I’ve extracted and apply consistently:

The diagnostic questions:

1. “What’s the real reason?” Not “What’s your concern?” but “What changed for you that’s driving this conversation now?”
2. “What problem are you trying to solve?” Not the surface request (cost reduction), but the actual pressure they’re under (impressing a new manager, hitting a budget target, avoiding scrutiny).
3. “What narrative do they need?” Not what’s financially optimal, but what story helps them survive their internal politics.

The tactical shift:

When rational arguments fail three times in a row, I’m in an emotional battle. Stop presenting data. Start diagnosing pressure.

The re-frame:

Emotional diagnosis → Understand their actual pressure → Re-frame the solution to address that pressure using operational tools.

What I Modified from Greene

Greene writes primarily about interpersonal psychology and historical patterns. I’m applying this to operational negotiations and organizational dynamics.

Where I diverged:

Greene’s focus: Individual emotional patterns and how to recognize them in others.

My application: Organizational emotional narratives and how they override individual rationality.

In the Ola case, no single person was being irrational. But the collective emotional narrative (“more cabs = growth”) created organizational irrationality that persisted until Finance broke the spell with contradictory data.

Greene’s method: Study historical figures and psychological patterns to predict behavior.

My method: Watch for specific signals in real-time negotiations:

• Rational arguments ignored repeatedly
• Long-term relationships suddenly shifting demands
• Decisions that don’t match stated priorities

What Greene doesn’t address: How to diagnose emotional vs. rational battles in the moment, not in retrospect. His framework explains why irrationality persists, but not how fast to recognize it operationally.

I’m still building that diagnostic speed.

What I’m Still Getting Wrong

Despite learning this at Ola and applying it with customers, I still default to rational defense too often.

The warehouse customer story? We wasted weeks before my ops manager asked the right question. If we’d started with “What’s really going on?” we could have solved it in one meeting.

The pattern I’m trying to break: When a long-term customer suddenly changes behavior, my first instinct is still to defend our position with data. I should be diagnosing what shifted in their environment first.

What I haven’t figured out:

Timing: How quickly should I switch from rational to emotional diagnosis? I still burn too much time on data that won’t land.

Boundaries: When does “understanding emotional pressure” cross into manipulation? Some of my managers are uncomfortable with this approach—they see it as “playing politics” rather than operational problem-solving.

Failure modes: Are there situations where emotional diagnosis makes things worse? I haven’t encountered it yet, but I’m watching for it.

Cultural variance: Does this framework work differently across Indian corporate culture vs international clients? My sample size is too small to know.

The Lesson I Keep Relearning

Over the years, this quote is always on the back of my mind:

**_What we learn from history is that we don’t learn from history. - _**German philosopher Georg Wilhelm Friedrich Hegel,

I learned this at Ola in 2015. I’m still learning it with customers in 2025.

The framework works. The challenge is applying it fast enough to avoid wasting weeks on rational arguments that won’t land.

What survived: Emotional battles disguised as rational ones are the default in organizational negotiations.

What I’m testing: Can I compress the diagnostic time from weeks to hours?