How to Tell a Client Their Idea is Bad Without Losing the Contract

Get 33% off forever

When I first started consulting, I thought being technically correct was all that mattered.

If a client brought me an idea that violated basic logic, I told them so to their face.

I laid out the engineering flaws.

I pointed out the bad math.

I thought I was doing them a favor by saving their time.

I was dead wrong.

During my second year of solo consulting, a founder in downtown Seattle hired me to build a custom customer portal.

Three weeks in, he wanted to scrap our simple, working database and replace it with an unproven custom tool he read about on LinkedIn.

I looked at him on Zoom and said:

“That makes no sense. It will cost three times as much and crash your checkout flow.”

Technically, I was right. Emotionally, I was an amateur.

He felt insulted.

Instead of hearing my technical warning, he heard that I thought he was stupid.

Two days later, he paused the project and fired me.

I lost the contract because I lacked the basic tact to deliver bad news without bruising a client’s pride.

Here is the fundamental rule of client work:

Nobody likes being told their baby is ugly.

When a business owner comes up with a project idea, they tie their identity to it.

They spent hours thinking about it.

They pitched it to their partners. By the time it reaches your desk, they are emotionally invested in the outcome.

If you handle this poorly, you fall into one of two traps:

1. The Order-Taker Trap:
   You smile, nod, and build their terrible idea anyway. Six months later, the system breaks or fails to generate revenue. The client forgets they asked for it and blames you for the failure.

2. The “Brutally Honest” Trap:
   You tell them directly that the idea will fail. You prove your point, but you create defensive friction. They feel alienated, label you “difficult,” and find someone else to build the wrong thing.

When you push back on a bad idea, follow these three rules:

1. Separate Intent from Implementation:
   A client’s idea might be terrible, but their goal is almost always valid. They want to cut labor costs, save time, or acquire leads. Agree with the goal 100% before you question the method.

2. Trade Opinions for Quantifiable Risk:
   Never say “I think this will fail.” Say “If we build it this way, we introduce three specific failure points: API latency costs, maintenance overhead, and a six-week delay on launch.”

3. Offer the Bridge, Not a Wall:
   Never bring a problem to a client without bringing two solutions. Give them the clear choice between the high-risk path they requested and a streamlined path that achieves their goal faster.

Run these three prompts through Claude, ChatGPT, or your local model whenever you need to handle difficult client pushback.

Use this when you are angry, frustrated, or tired, and need to turn an unfiltered technical critique into a professional executive response.

Get 33% off forever