What should you do when a client gives you total creative freedom?

Run structured discovery anyway, especially because they did not ask for it. Build what you think is best is never literal. It means there is a picture in their head they cannot articulate and are hoping you will guess. Your job is to extract it before the build, not discover it at the review.

Why is an open brief a risk rather than a gift?

Because the expectation still exists, it is just unstated. It might be a competitor's product, a workflow they saw at a conference, or opinions the CEO has not shared yet. None of that is dishonesty. It is simply invisible until something concrete contradicts it.

Who loses when there are no agreed criteria?

Both sides. The agency does three times the work for the original price, and the client feels they overpaid for something that should have been simpler. There is no version where one party comes out ahead, which is worth saying out loud when you propose the discovery work.

How do you sell discovery to a client who does not want it?

Frame it as protecting their money rather than as your process. A client who declines a requirements phase is not refusing paperwork, they are choosing to find out what they wanted during the review instead of before the build. Put the choice in those terms and most agree.

The Client Said 'Build What You Think Is Best.' It Was a Trap.

Q: What does the revision spiral look like?

Contradictory feedback, because the client is reacting emotionally rather than evaluating against agreed criteria. Can we make it simpler but also add more features. Then new feedback on parts they approved earlier, scope growing while the timeline does not, and an awkward budget conversation.

The dream brief

The email from the client read: “We trust you guys. Just build what you think is best. You’re the experts.”

If you’ve worked in an agency, your pulse just went up. Maybe from excitement, maybe from dread, depending on how many times you’ve been through this.

On the surface, it’s the perfect client. No micromanagement. No 47-page requirements doc. Total creative freedom. The team gets energized. The designers go bold. The developers build something genuinely clever.

Six weeks later, the client sees the first demo. Their face says everything.

“That’s… not what we had in mind.”

What went wrong

Nothing went wrong with the build. The team did excellent work. The problem started before a single line of code was written.

When a client says “build what you think is best,” they don’t mean it literally. They mean: “I have a picture in my head, but I can’t articulate it, and I’m hoping you’ll just guess correctly.”

They’re not being dishonest. They genuinely believe they’re giving you freedom. But there’s always an expectation hiding underneath. Maybe they want it to look like a competitor’s product. Maybe they’re imagining a specific workflow they saw at a conference. Maybe their CEO has opinions they haven’t shared yet.

If you don’t dig those expectations out early, you’ll discover them at the worst possible moment: during the review.

The revision spiral

Here’s how the next two months typically go.

The client gives feedback. It’s contradictory because they’re reacting emotionally, not evaluating against agreed criteria. “Can we make it simpler but also add more features?” The team revises. The client is happier with some parts, but now has new feedback on things they approved before. Scope changes, but the timeline doesn’t. The budget conversation gets awkward.

By the end, the agency has done three times the work for the original price, and the client feels like they overpaid for something that should have been simpler. Nobody’s happy.

All because nobody wrote down what “best” meant before starting.

The fix: structured discovery, even when they don’t want it

I’ve seen agencies handle this well, and the approach is always the same. When a client offers total freedom, the agency politely refuses it.

Not the project. The ambiguity.

Here’s what that looks like in practice.

Ask the questions they haven’t thought about

Before any design work starts, run a structured discovery session. Even a short one, 60 to 90 minutes, changes everything. Cover these:

Who is this for? Not “our users.” Specific people. What are they trying to do? What frustrates them about the current solution?
What does success look like? If this project goes perfectly, what’s different in 6 months? More signups? Fewer support tickets? A specific conversion rate?
What should this NOT be? This question surfaces hidden constraints faster than anything. “We don’t want it to feel like Salesforce” tells you more than 20 pages of requirements.
Who else has opinions? Find out if there’s a CEO, board member, or department head whose preferences will show up at the review. Get those people into the room early.

Document it in their words

Write up what you heard, using their language, not yours. Send it back within 24 hours. Ask them to confirm or correct it.

This document becomes your insurance policy. When the feedback starts shifting later, you can point to it and say: “Here’s what we agreed on. Do you want to change direction? That’s fine, but let’s update the plan and talk about what that means for timeline and budget.”

Show work early and often

Don’t wait six weeks for a big reveal. Show rough work in week one. Ugly wireframes. Basic flows. The earlier they see something, the earlier they can react. Early reactions are cheap to act on. Late reactions are expensive.

The relationship angle

Some agency people push back on this. “If we make the client go through all this upfront work, they’ll think we’re difficult. They chose us because we’re easy to work with.”

I understand the instinct. But here’s what actually damages client relationships: delivering something they didn’t want and then telling them it’ll cost more to fix.

Clients remember agencies that nailed it on the first try. They don’t remember the kickoff meeting being thorough. They remember the result feeling like exactly what they needed.

Structured discovery isn’t overhead. It’s how you earn “they just get us” status.

The one thing to take away

When a client gives you total freedom, treat it as a yellow flag. Not a red one. Just a signal that the real requirements are hiding and it’s your job to find them.

Ask the questions. Write down the answers. Get sign-off. Then go build something great.

The freedom to build well starts with the discipline to define clearly.