Being Easy to Work With Is Not the Same as Being Good at Your Job

Good client service is often confused with endless accommodation. Building a business taught me that the opposite can be true. Sometimes, the most professional thing you can say to a client is no.

When I started my company, I thought being good at client service meant making things easy for the client.

Answer quickly. Accommodate the request. Move the deadline. Make the exception. Find a way.

There was a certain logic to it. When you are building a young business, every relationship matters. You want people to feel looked after. You want to prove that you can deliver. And when your own name is attached to the company, the line between serving a client and pleasing them can become remarkably thin.

I still believe deeply in service. I believe in answering the phone when something genuinely matters. In solving problems nobody anticipated. In occasionally doing more than what was promised because the circumstances warrant it.

What has changed is my understanding of what good service actually requires.

Sometimes, the most professional thing you can say to a client is no.

I did not learn this through one dramatic incident. I learnt it through dozens of small ones.

A deadline moves by a day. Feedback arrives a week late, but somehow the delivery date does not. Something outside scope is described as a “quick thing”. A meeting runs over. An invoice remains unpaid while the work continues. Another revision is absorbed because having the conversation feels more uncomfortable than simply doing it.

None of these things seems particularly serious in isolation.

That is precisely the problem.

Businesses rarely become chaotic because of one catastrophic decision. Chaos accumulates quietly, through exceptions that individually appear too small to challenge. What took me longer to understand was that an exception almost never costs only the hour you can see.

Move one deadline and another piece of work shifts with it. Receive an approval late and production compresses. Add work without adding time and the pressure has to go somewhere. Usually into margin, quality or people.

Eventually I realised that if I wanted to protect the quality of what we produced, I had to protect the system producing it.

This changed the way I thought about boundaries.

We tend to discuss boundaries as something personal — protecting our time, our energy, our wellbeing. All of that matters. But running a company taught me that boundaries are also infrastructure.

A scope defines what is being built. A deadline establishes when decisions need to happen. An approval process determines who is accountable. Payment terms determine how risk is shared. A defined number of revisions forces a decision to eventually become a decision rather than an indefinitely evolving preference.

None of this is particularly exciting. Clients do not hire an agency because they are inspired by its payment terms.

But the beautiful part of the work — the campaign, the identity, the experience, the idea that eventually reaches the world — depends on an architecture nobody sees.

For a while, talent can compensate for weak architecture.

People work later. They solve things at the last minute. They rescue deadlines. Founders become permanently reachable. Everyone becomes very good at performing small acts of heroism.

It can even feel like commitment.

It is not a particularly good way to build a company.

There is another layer to this that I think founders understand particularly well. In a service business, the person making the commercial decision is often the same person maintaining the relationship.

That makes saying no strangely personal.

You know the client. You may genuinely like them. You want the relationship to continue. You know that saying yes will make the conversation easier.

So you say yes.

I have.

But there is a difference between being collaborative and being compliant.

If someone hires you for your judgment, withholding that judgment because you want to remain agreeable is a peculiar form of service.

There have been times when I have had to tell a client that I disagree with a decision. There have been times when the answer to a request has been no. There have also been times when I have made the exception anyway.

I don't believe good businesses should be rigid.

In fact, I think judgment matters precisely because rules cannot anticipate everything.

There are clients for whom I would move things without hesitation. There are circumstances where doing something outside scope is clearly the right thing to do. There are moments when the human response matters considerably more than whatever is written in an agreement.

The difference, for me, is whether the exception is a decision or a reflex.

I increasingly ask myself: What does saying yes to this actually mean?

Not only today, but next week. For the team. For the work. For the relationship. And, importantly, for what happens the next time the same situation arises.

Because people learn how a business works from what it repeatedly permits.

If deadlines routinely move without consequence, the deadline written in the project plan is largely fictional.

If work routinely begins before payment, the payment terms on the invoice are largely fictional too.

And if every request marked urgent immediately rearranges everybody else's priorities, somebody outside the company is effectively managing its capacity.

This has probably been one of the more uncomfortable parts of becoming a better entrepreneur.

I am naturally interested in relationships. I care about how people experience working with me. I want my companies to be warm, responsive and generous. I don't want process to become an excuse for losing humanity.

But warmth and standards are not opposites.

You can understand someone's circumstances without turning those circumstances into your operating model. You can care about a relationship and still enforce an agreement. You can be generous without becoming endlessly available.

And sometimes you have to accept a little friction now to avoid considerably more friction later.

This becomes more important as a company grows.

The behaviours that help you win your first clients are not necessarily the behaviours that allow you to serve many clients well. What feels intimate at a small scale can become ambiguous at a larger one. Personal goodwill eventually has to become institutional standards.

I used to think that meant becoming less personal.

I now think the opposite.

Clear standards make better relationships possible because neither side has to constantly renegotiate how the relationship works.

The client respects the expertise, time and operating requirements of the company they have hired. The company respects the client's investment, objectives and time. Both sides communicate. Both sides are accountable. And when life inevitably interferes with the plan, there is enough trust to make an exception without turning the exception into the system.

That, to me, is good service.

I still want to be easy to work with. I still want both Bungalow and Tallulah to be known for taking care of people. I still believe there are moments when you throw the process out of the window and simply solve the problem.

But being easy to work with cannot mean having no edges at all.

Building a company has taught me that saying no is not necessarily the opposite of service. Sometimes it is how you protect the work, the people doing it and ultimately, the relationship itself.

I wish I had understood that sooner.