Most practices have had a project like this. The client seemed reasonable, the brief manageable and the fee, though not spectacular, was fine. Most importantly, there was space in the practice workload, so the practice said yes.
In the end, nobody was quite sure what had gone wrong.
The work was delivered. The building, or the drawings, or the planning application, did what it was supposed to do. But the client was still a bit dissatisfied, and the practice was exhausted in a way that was difficult to justify. Somehow, no one quite knew why.
This kind of project is worth examining, because it doesn’t come from nowhere.
There is more than one version of the client who was never going to be happy, but they tend to have something in common. At some point in the relationship, often earlier than the practice wants to admit, the client stops treating the architect's expertise as something to be appreciated and relied on. At that point, the client starts treating the architect as something to be managed, questioned, or overridden. Professional recommendations become suggestions the client ignores. Previously authorised decisions become arguments and negotiations. And when things go wrong, as happens on every project, the architect is the easiest place to put the blame.
The first version is the client taken on when the pipeline was thin. The signals were there early: a comment about a previous architect that was noted and set aside, a fee negotiation that felt slightly off, a sense that the client's idea of what they were buying did not quite match what the practice was selling. These things were visible, but they were set aside because the timing was awkward and the fee was needed and it seemed easier to hope it would work out in the end.
The second client starts more promisingly. They seem genuinely enthusiastic. The brief initially seems to be a good match, and the early meetings, while they might not have gone quite as smoothly as you could have wished, were just fine. The real disrespect emerged later, when the project met reality. Perhaps the project came up against planning constraints, or the client started getting twitchy about the budget they had described as unlimited. Maybe the gap between their vision and their understanding of the practical steps needed to achieve it had started to become apparent. Either way, the client needed somewhere to put their frustration, and the architect was closest.
The third version is perhaps the hardest to spot in advance. This client never really wanted an architect. They wanted someone to produce drawings that reflected their own decisions. The professional expertise was an inconvenience rather than a resource, and the relationship was difficult from the start in ways that were easy to mistake for normal client anxiety.
What all three have in common, beyond the disrespect, is the effect on the people who had to work on them.
A team that has spent months being second-guessed by a client who does not value what they do does not simply reset when the project ends. The damage is cumulative and quiet. It is not one bad day. It is the slow erosion of the trust that the work is worthwhile, that their judgment is sound, that their effort is going somewhere meaningful. The people most affected are often the ones who came into the profession caring most about the work. The gap between what they believed the job would be and what this client is making it feel like is widest for the people with the most investment in doing it well.
That is the cost that rarely appears in any post-project review. The commercial damage of a difficult client is at least visible: the write-offs, the time lost, the fee that did not justify the hours. The effect on morale is harder to see and slower to recover from.
The client who was never going to be happy costs the practice more than just one difficult project. Professional self-confidence, trust in the worth of your work and simple professional satisfaction are less tangible and far harder to replace.