I am going to describe a client without naming them.
They paid on time. They were not rude. The work was interesting. By most surface measures, it was a successful engagement.
But it was the most exhausting client relationship I have had, and it taught me more about how I work than any good client experience.
Here is what happened and what I learned.
The client had no internal decision-making process. This revealed itself slowly. Feedback from one stakeholder contradicted feedback from another. Approved designs were revisited after implementation. "Final" decisions turned out to be preliminary ones.
None of this was malicious. They were genuinely a disorganized team working through legitimate disagreements about what they wanted.
The problem was that I was absorbing the cost of their disorganization.
Every revisit was my revision cycle. Every changed direction was scope creep I was not charging for. Every contradictory stakeholder was a conversation I was managing instead of them managing internally.
What I should have done differently from the start:
I should have required a single point of contact with final authority. Not a committee. Not "we'll discuss and get back to you." One named person who has the authority to say yes and to whose yes I deliver.
I did ask this question at the discovery stage. The answer was vague. I should have pushed for a specific name and made it a condition of moving forward.
I should have defined what "approved" means in the contract. "Approved deliverables are approved once [point of contact] has provided written confirmation." Not "once the team has had a chance to review."
I should have introduced a change order much earlier. The first revisit of an approved design was the moment to send a short note: "This falls outside our agreed revision scope. I am happy to make this change - let me send a quick change order."
I did not do this because the change felt small and I did not want to create friction with a client who was otherwise pleasant. But the second revisit became easier to accept because I had accepted the first. By the fourth, it was the established pattern.
What actually happened:
The project took 40% longer than scoped and I was paid for the original scope. My effective hourly rate was well below my target. I was tired and slightly resentful by the end despite having done good work.
The client was happy. They left a positive review. They would have hired me again.
I declined.
The lessons:
Decision-making authority must be confirmed before the project starts. Not vague assurance. A specific name.
The first out-of-scope request is the one that sets the pattern. Address it professionally and immediately.
A pleasant client is not the same as a well-functioning client relationship. Both matter.
Some engagements will be more costly than the invoice suggests. Recognize them earlier.
I do not regret the project. The lessons from the difficult client have been more durable than the lessons from the easy ones.
Top comments (0)