Unclear Client: The Root of Project Frustration
When a client says the work isn't what they expected, the problem started in the first conversation. Start with why.
You finish building a website, but the client says it isn’t what they expected.
You spend days making changes, only to realize you’re solving the wrong problem.
Now, you’re dealing with unexpected changes, wasted time, and difficult conversations. The client is disappointed, and you’re frustrated because you delivered what you understood was required.
When a client approaches you, they usually have something specific in mind.
“I need a website.”
“I want to build an app.”
“I need a logo for my business.”
As freelancers, we naturally start asking questions about requirements, features, design, and functionality.
But we often miss the most important question:
Why does the client want this in the first place?
A client who wants a website might be trying to attract more customers, establish credibility, or reduce repetitive enquiries. Each objective requires a different approach.
If you focus only on what the client wants to build, you might deliver exactly what was requested without addressing the problem they wanted to solve.
That’s where the disconnect begins.
Start With WHY, Not Requirements.
Share your experience on the feedback page. I read every message and reply by email, and I’d love to learn from other freelancers.