Ridiculous client negotiations: 3 real world stories from BearStudio

You know those moments when a client says something so absurd, you can’t help but wonder if they’re living in a completely different reality? Over the years, I’ve had my fair share of these interactions-negotiations so ridiculous they’d be funny if they weren’t so frustrating. From clients who think I should lose money just to work with them, to those who compare apples to oranges and call it logic, I’ve seen it all. So, here’s my top 3 list of the most hilariously bad negotiations I’ve ever had to deal with.

TL;DR

Most client negotiations fail because people focus on price instead of value.
Your job is to bring clarity, push back when needed, and know when to walk away.

#1: Daily rate vs real value

Five years ago, a corporation spent weeks evaluating us, and the tech lead was clear: we were the right fit for the job.

Then procurement stepped in with a different lens: “Your daily rate is higher than this other contractor’s.”

So I asked: “If they bring the same value, why are you here negotiating with us instead of working with them?” Silence.

Typical procurement pattern: comparing a senior backend specialist to a junior frontend dev, ignoring all context, and acting like daily rate means everything. If the cheaper option was actually better, we wouldn’t be in this room.

But then the tech lead reframed it: “Look, procurement is focused on daily rate. What if we increase project scope, give you more sprints, and you lower your rate enough to satisfy their constraints?”

This highlights a key principle: price is not the only variable in a negotiation.

This is what real negotiation looks like: more volume means less uncertainty; in that case, lowering the daily rate becomes acceptable. So we agreed to commit to a longer engagement with guaranteed volume.

In the end, everyone won.
We dropped our daily rate, but the total contract value increased compared to the initial proposal: we got stability and predictability. Procurement got their paper victory. And the tech lead got the right expertise.

#2: The client who shoots itself in the foot

Let me tell you about a client who managed to turn a bad situation into an even worse one: all by their own doing. We were working with them on a project that had been a complete mess for years. It was chaotic, and on the verge of collapse. But we stepped in, fixed it, and got everything back on track.

Then things took a different turn:
One day, we received an email from them saying that, moving forward, we’d need to subscribe to a paid service just to receive our payments. Yes: they wanted us to pay in order to get paid. And, of course, they made it very clear that we absolutely could not increase our rates to offset this new cost. So, essentially, I was expected to lose money just to keep working with them.

And this wasn’t even coming from someone directly involved in the project. It came from an external service with no context on what we had done to save their company’s software. No counteroffer. No discussion. No middle ground. It was a completely one-sided, closed negotiation. Their attitude was basically “Take it or leave it.”

What they didn’t seem to realize (or maybe didn’t care about) was that we were holding their entire project together. If we walked away, the whole thing would fall apart. But they never stopped to ask themselves, “What happens if they say no?” They were so focused on reducing costs that they ignored the consequences of losing us. They didn’t see they were shooting themselves in the foot.

This kind of behavior is a perfect example of an external service coming into the relationship without context, and sometimes just creating problems for their company while “just doing their job”. They think they’re saving money, but in reality, they’re creating more problems for themselves. And as frustrating as it is, sometimes the only reasonable option is to walk away. Because if a client doesn’t value your work, they’re not worth your time.

#3: “He’s a junior, so he should cost less”

Here’s a classic example of how some clients completely miss the point when it comes to evaluating expertise. We were working on a JavaScript project, and the client’s procurement team decided to compare two profiles: a senior Java developer who had never worked with JavaScript, and a junior JavaScript developer who was a specialist in the stack. Their logic? “The junior should cost less, no matter their specialization.”

Why is this logic fundamentally flawed? Because they were comparing inherently different profiles. Sure, the Java developer might be more experienced overall, but when it comes to this specific project, the junior JavaScript developer is far more skilled and efficient. Specialization matters. Procurement teams also tend to ignore soft skills and team dynamics, which are critical to project success.

So, what did I do? I calmly explained the value of having the right person for the right job. I broke down how the junior developer’s expertise in JavaScript would allow them to deliver faster, cleaner, and more reliable results than someone who would need to learn the stack from scratch. I also highlighted how this would save time and money in the long run, even if the junior’s daily rate wasn’t as low as they expected.

The key takeaway: comparing contractors or employees based solely on surface-level metrics like experience or daily rate is a recipe for disaster. Quality, speed, and specialization are what truly save time and money. And if a client can’t see that, they’re setting themselves up for trouble.

Max Verstappen won his first GP at 18, age is not a metric for talent and expertise…

The takeaway

In the world of business, negotiations can often feel like a balancing act between logic and absurdity. As these stories show, focusing solely on surface-level metrics like daily rates, arbitrary costs, or irrelevant comparisons can lead to costly mistakes and missed opportunities. True value lies in expertise, efficiency, and the ability to deliver results that prevent future problems.

As professionals, it’s our job to educate clients on the bigger picture, and stand firm in the value we bring to the table against the illogical arguments. And when faced with clients who refuse to see reason, sometimes the only reasonable move is to walk away (I’m writing an article on how I stopped working for a client, for the sanity of my team). After all, the right clients will understand that quality work is an investment and not an expense.

An update on these stories which happened before AI became widely accessible: Nowadays more and more people rely on AI tools to simplify discussions and interactions. This can lead to arguments being brought into discussions without full context, leading to more illogical negotiations. At the same time, AI is also a powerful way to explore ideas, challenge our reasoning, and brainstorm arguments. But it should never replace critical thinking.

This makes one thing increasingly more important:
The ability to inform your clients, guide the discussion, and challenge their ideas becomes essential. This brings clarity about your value and how it should be used within their projects. That remains our responsibility as professionals.

Because in the end, negotiation isn’t about stacking arguments: it’s about understanding value, context, and knowing where to draw the line; and pushing back when things no longer make sense.