Why the Client Who Can't Explain What They Don't Want Is the Most Expensive Client You'll Ever Work With
The vague brief isn’t the problem. Every project has one.
What kills you is the client who doesn’t know what they want — and doesn’t know that they don’t know. The one who approves the direction enthusiastically, disappears for a week, comes back with “I’m not sure this is right,” and can’t tell you what right looks like.
You’ve spent five hours. They’ve spent ten minutes looking at it. Neither of you can locate the gap.
The cost is never just time
The obvious tax is revision cycles. You estimate three rounds, you get nine. The brief that was “clear” keeps expanding. Requirements that didn’t exist in week one appear in week four, presented as things that were always obviously needed.
But that’s not the real cost.
The real cost is what it does to your confidence in your own work. When someone can’t explain what they don’t like, you stop trusting your own instincts and start guessing theirs. You make changes you don’t believe in, hoping one lands. You start designing for approval instead of designing for the problem.
That’s when the work goes bad. Not because of bad feedback — because of feedback-shaped noise.
Why some clients can’t explain it
It’s not that they’re unreasonable. Most of the time, they genuinely haven’t done the upstream work.
They came to you with an output they wanted — a logo, a site, a campaign — before they finished figuring out what the output was supposed to communicate. They outsourced the artifact because the decision felt like something a designer solves, not something a founder has to resolve first.
So when the work lands in front of them, they’re not evaluating the execution. They’re doing the positioning work they skipped — in real time, at your expense, using your comps as a thinking surface.
That’s expensive for you. But it’s expensive for them too. They just don’t know it yet.
What to do with this
Two things that actually help:
-
Front-load the uncomfortable questions. Not “what do you want this to look like” — that gets answered at the wrong level. Ask: who is this for, and what do they need to believe after they see it? What does failure look like for this project? What have you already tried, and why didn’t it work? The client who freezes on these questions in week one is the client who would have frozen on your deliverable in week three.
-
Name the constraint, not just the direction. Instead of presenting three concepts, present one direction with explicit constraints attached. “This is designed to feel authoritative without being cold, for a buyer who’s seen every SaaS brand. If that’s not the brief, tell me what’s different.” Now they have something to push against. Push-back is useful. Silence isn’t.
The vague client isn’t a bad client. They’re an unprepared one. The project brief is the last place they should be figuring that out.
The most expensive client you’ll ever work with isn’t the demanding one. It’s the one who doesn’t yet know what they’re asking for.