Why the Client Was Right

I thought I had solved it.

After weeks of research, interviews and workshops, I presented a new direction for the client’s website.

The market gap was clear. The strategy made sense. The design was strong, and the headline reduced a complicated proposition to six memorable words.

It was the sort of presentation that makes you feel like you know what you’re doing.

Then the client looked at the opening page and said:

“I love it, but I don’t think our customers will believe it.”

I explained the thinking. The headline came directly from the research. It gave the business a clearer position and separated it from competitors that were all saying roughly the same thing in slightly different shades of blue.

The client listened.

“It’s a good line,” he said. “I’m just not sure we’ve earned it.”

At the time, I thought he was losing his nerve.

He wasn’t.

He was right.

The line was good. That was the problem

My instinct was to defend the work.

That’s a fairly human reaction when somebody questions something you’ve spent weeks building. I returned to the research, explained the creative choices and showed why the position made sense commercially.

None of that was wrong.

I was simply answering a different question.

I was asking whether the message was strategically strong. The client was asking whether the business could stand behind it.

Those aren’t the same thing.

A few days later, I sat down with the customer-success team. One member of the team summed it up better than any strategy document had.

“That’s where we want to be,” she said. “But it isn’t what every customer experiences today.”

That hadn’t properly surfaced during discovery.

I had spent too much time looking at what the business wanted to become and not enough time looking at what happened once an order entered the building.

That was my mistake.

The website described the company’s ambition as though it were already a reliable part of the customer experience. The strategy was pointing in the right direction, but the business wasn’t ready to make the promise.

More leads would have made things worse

The obvious purpose of the new website was to attract more of the right customers and generate more opportunities.

Under normal circumstances, that sounds like success.

Here, it could have crushed the team.

Customer success was already spending hours chasing production updates. Production was manually dealing with complicated order information. Different teams held different parts of the picture, but nobody had a simple way to see the whole thing.

More leads wouldn’t have fixed any of that. They would have poured more work into a system that was already struggling to keep up.

I could have launched the site, watched the enquiries rise and dusted my hands off.

The website generated more leads. Job done.

Except it wouldn’t have been job done. The marketing numbers might have looked better while the customer experience quietly went to shite behind them.

That isn’t success. It’s moving the failure somewhere less visible.

The client understood that before I did.

I saw the market opportunity.

He saw what would happen on Monday morning.

The website wasn’t the real problem

The client’s first suggestion was to return to the old language.

That would have been safer, but it wouldn’t have solved anything. The existing message was accurate, yet almost indistinguishable from every competitor in the market.

I could have watered down the idea and delivered the sort of website everyone else already had.

I could have walked away.

Or I could try to understand what the business actually needed before the website could do its job.

The conversation changed at that point. The customer-success team stopped talking about the ideal experience and started being honest about the real one.

That honesty was far more useful than another workshop full of Post-it notes.

The visible problem was a website that made a promise the business couldn’t consistently deliver.

The actual problem was the way information moved—or didn’t move—between customer success and production.

A spreadsheet did more than another strategy deck

The breakthrough came over dinner with the CTO and head of IT.

After a few beers, the conversation moved away from positioning and onto why the operational gaps existed.

These were two of the most intelligent people I’d worked with. They understood the systems, the order process and the technical constraints far better than I did.

But they were also close to the problem.

The business appeared to need a complicated new management platform, a major integration project or another expensive bit of software promising to make everything seamless.

It didn’t.

It needed a connector.

Customer success needed to see what was happening in production without spending hours chasing people. Production needed a clearer view of the order information without piecing it together manually.

The answer was a shared spreadsheet supported by a small, vibe-coded Google Apps Script that the IT team built.

Nothing elegant. Nothing polished.

It probably wouldn’t have looked particularly exciting in a transformation strategy deck.

But it worked.

Sometimes we are looking in the wrong place for the right answer

It brought the important information into one place, reduced hours of manual work and gave both teams a shared view of what was happening. More importantly, it freed up some of the capacity the business needed to support the new direction.

It wasn’t pretty but it worked, the simple tool did more to make the website strategy viable than another month spent changing the copy.

*Update: Im now supporting the team in adapting the spreadsheet solution, into something a little more presentable.

The line had to be earned

This is the bit I nearly missed.

The positioning wasn’t wrong. The research wasn’t wrong. The website wasn’t wrong.

The mistake was assuming that communication alone could move the business into the position it wanted to occupy.

A strong message isn’t just a description. It’s a promise.

If the operation behind the website can’t fulfil that promise, better marketing doesn’t fix the gap. It makes the gap bigger and invites more people to fall into it.

That doesn’t mean the client is always right. They aren’t, and pretending otherwise isn’t useful to either side.

It does mean resistance is worth investigating before dismissing it.

Sometimes a client is nervous because an idea is unfamiliar.

Sometimes they’re protecting an old assumption that needs challenging.

And sometimes they can see the operational car crash waiting around the corner while you’re still admiring the homepage.

This time, the client was right.

The business hadn’t earned the line.

The answer wasn’t to make the words smaller.

It was to do the work that made the bigger words true.