How to Ask a Client for Feedback (and Actually Get Usable Answers)

You send the work and ask "let me know what you think." Two days later you get back: "Love it! Just feels a bit off, maybe make it pop more?" Now you have a round of revisions and no idea what to actually change.

Vague feedback is almost always a symptom of a vague request. Clients aren't withholding the specifics. They genuinely don't know what you need, because "what do you think?" is an open door into a room with no furniture. The fix isn't a better client. It's a better question.

This is how to ask for feedback so the answers come back specific, located, and actually usable.

Why "what do you think?" fails

"What do you think?" asks the client to do three hard jobs at once: notice what's wrong, diagnose why, and prescribe a fix. Most clients can do the first and stall on the other two, so you get a feeling ("off," "not quite there") with no direction attached.

It also invites the client to react to everything at once, which is how you end up with a single message touching ten unrelated things, half of them contradictory. The request shaped the mess.

Good feedback requests do the opposite. They narrow what you're asking about, give the client a structure to react inside, and make it easy to be specific. You're not interrogating the client. You're removing the work that was stopping them from being clear.

How to ask a client for feedback

1. Ask about one thing at a time

Instead of "what do you think of the site?", ask about a specific decision: "Does the homepage headline say the right thing to your customer?" A narrow question gets a sharp answer. A broad one gets a mood. You can ask several narrow questions; just don't fold them into one vague one.

2. Tell the client what kind of feedback you want now

Feedback has stages, and asking for the wrong stage wastes a round. Early on you want direction ("is this the right direction?"), not polish ("is this the right shade of blue?"). Say which you're after: "This is a first direction. I'm looking for whether the structure and tone feel right, not the fine details yet." It saves the client from sweating commas while the layout is still in question.

3. Make it easy to be specific

The biggest single upgrade is letting the client point at the exact thing instead of describing it. "The bit at the top feels cramped" is a guess you have to decode. The same comment pinned to the actual element is an instruction. Ask for located feedback, on the work itself, not in prose.

4. Give a deadline and a default

"Let me know whenever" produces feedback whenever, which is to say slowly and in drips. Try: "Could you send all your feedback by Thursday? If I don't hear back, I'll take it as approved and move to the next stage." A deadline with a stated default turns an open-ended ask into a decision the client has to make.

5. Ask for it in one place, in one pass

Request feedback as a single consolidated review, not a running stream: "Go through the whole thing, add your comments, then send it back." Batching turns ten interruptions into one reviewable list and lets the client catch their own contradictions before they reach you.

Scripts you can copy

For a first direction:

"Here's the first direction for the homepage. At this stage I'm looking for whether the overall structure and tone feel right for your audience, rather than fine details. Could you go through it and add any comments directly on the page, then send it back by Thursday?"

For a near-final review:

"This is the near-final version with everything from the last round applied. Could you do one careful pass and flag anything that needs to change? If it all looks right, a quick 'approved' is perfect, and I'll lock it."

Notice what both do: they name the stage, ask for located comments, set a deadline, and make the next step obvious. That's the whole technique.

Where the feedback request ends

Asking well gets you clean feedback. But feedback is only half the loop. At some point the comments need to stop and a decision needs to start, which is a different request entirely: not "what do you think?" but "do you approve this?" Confusing the two is how projects stay open forever. That's worth understanding on its own: feedback ends a conversation, approval ends a liability.

How Lyba makes feedback specific by default

Lyba removes the main reason feedback comes back vague: it lets the client point instead of describe. You send one review link, the client opens your live Framer site with no login, and they pin comments directly on the exact spot they mean. Each pin records whether they were on mobile, tablet, or desktop, so a comment about spacing is never ambiguous about which layout it's on.

Because the comments live on the work and batch into a single review, you get one consolidated, located list instead of a drip of prose across email and chat. And when the feedback is done, approval is a separate, explicit step, so the request to comment and the request to sign off never blur together.

FAQ

How do I get specific feedback from a client instead of vague comments? Ask narrow questions about one thing at a time, tell the client which stage of feedback you want (direction vs detail), and let them point at the exact element rather than describe it. Vague answers usually trace back to a vague, broad request.

How do I ask a client for feedback by email? Name what you're sharing, state the kind of feedback you want, ask for it all in one pass on the work itself, and set a deadline with a default ("approved if I don't hear back by Thursday"). See the copyable scripts above.

How do I stop clients sending feedback in five different places? Ask for it in one place as a single consolidated review, and when stray feedback arrives elsewhere, politely ask the client to add it there so nothing gets lost. One located channel beats five scattered ones.

What's the difference between asking for feedback and asking for approval? Feedback is a request for reactions and changes. Approval is a request for a decision that the work is done. Keep them as separate asks, or "looks good" starts standing in for sign-off and the project never formally closes.

Ask better, decode less

If you spend the hour after every send translating "make it pop" into actual changes, the request is the thing to fix, not the client.

See how Lyba turns client feedback into pinned, located comments on your live Framer site, or start a free 14-day trial.