Why Your Clients Keep Ghosting Your Feedback Requests

You sent the deliverable on Friday. You wrote "Let me know what you think — happy to revise!" You attached a Loom. It's now Wednesday. The client hasn't replied, hasn't opened the file, and has ghosted both of your follow-ups.

This is the most common, most demoralising pattern in freelance work, and it has nothing to do with the client being rude or you being a bad freelancer. It has to do with how the human brain handles decisions, and the surprisingly small adjustments that change everything.

The decision-fatigue lens

Behavioural-economics research is consistent on this: humans avoid decisions that feel hard, unstructured, or open-ended. The classic jam study by Iyengar and Lepper.pdf) found that shoppers presented with 24 jam choices were ten times *less* likely to buy than those presented with 6. Too much choice produces paralysis, not better outcomes.

Now consider a typical freelancer feedback request:

"Here's the first draft of the homepage. Let me know what you think!"

The client is being asked to:

• Open the file (1 click)
• Read or watch it (10-30 minutes)
• Form an opinion across 12 different dimensions — copy, layout, typography, photography, vibe, brand alignment, mobile responsiveness, conversion clarity, headline strength, tone, technical implementation, "the boss's wife's reaction"
• Decide which dimensions matter
• Articulate that opinion in writing
• Send the email

That's not feedback. That's a 90-minute task disguised as a question, on a Friday, three weeks into a project they're 60% certain about.

The result is what feels like ghosting. It's actually decision fatigue. The client opens the email, feels the weight of "form a coherent opinion across 12 dimensions," closes the email, and tells themselves they'll come back to it tomorrow. They don't.

Why "any thoughts?" is the worst question in freelance

Open-ended feedback requests fail for the same reason "what do you want for dinner?" fails. The brain's response to a wide-open question is *anything sounds fine; defer*. The brain's response to "Indian or Thai?" is *Thai*.

If you ask "any thoughts?" — your client doesn't know what bucket to think in. So they don't.

If you ask "Does the headline land for you, yes or no?" — they have a binary, they answer in 10 seconds, and you're moving.

This isn't manipulation. It's reducing the cost of giving you the answer you need. Lower cost = faster reply.

The four-step fix

The pattern below has been tested across designers, devs, copywriters, and video editors. It cuts feedback turnaround from 5+ days to under 48 hours in most projects we've seen on Delivvo.

1. Replace "any thoughts?" with three named questions

Instead of "let me know what you think," send three explicit, named questions tied to specific decisions:

• "Does the headline communicate what we agreed on (yes/no)?"
• "Is the colour direction the right vibe for the brand (yes/no/needs adjustment)?"
• "Does the call-to-action read as something you'd actually click (yes/no)?"

Three questions — never four. Binary or ternary answers, never open-ended. The client is now answering a quiz, not writing an essay.

2. Anchor each question to a specific element

Don't ask about "the design." Ask about the headline, the colour palette, the CTA. The more specific the target, the cheaper the answer.

Pro tip: if your tool lets you pin feedback to specific files or page elements (Delivvo's portal, Figma comments, Loom hot-spots), use it. The client doesn't have to *describe* what they're commenting on — they just click and react.

3. Set a deadline that's about your workflow, not theirs

"Take your time, no rush" is well-meaning and catastrophic. Without a deadline, the request defaults to *infinity*, and infinity-priority tasks never get done.

Reframe it as your constraint, not theirs:

"I'm setting up Tuesday's revisions block — could I lock these answers down by Monday EOD? Otherwise I'll keep moving on the parts you've already approved."

You're not pressuring them. You're showing them that *something will happen* on Tuesday whether they reply or not. That's not pressure — that's relief from the open-ended infinity.

4. Default to "approve" if they go silent

This one feels counterintuitive but works. Add to your contract or the email:

"If I don't hear back by Monday EOD, I'll assume the current direction is approved and continue building from there. We can always revise after final review."

Most clients — once they realise silence equals approval — reply. The ones who don't reply genuinely don't have strong opinions, and you've saved a week of back-and-forth.

This works because it inverts the cost. In a normal request, *replying* has a cost (the 90-minute essay). Now *not replying* has a cost (loss of control over the direction). The brain reorders priorities; the email gets answered.

What to do when you've already been ghosted

If you're three days into silence, don't send another "any thoughts?" Reset.

Hi [name],

>

Quick reset on the homepage draft from Friday. I'd love to keep momentum going so I can get you a v2 by Wednesday.

>

Three quick yes/no questions, takes 2 minutes total:

>

1. Does the headline land — yes or no? 2. Is the green-and-cream palette the right vibe — yes or no? 3. Should the CTA stay "Start a project" or change?

>

If I don't hear back by EOD Monday, I'll assume the current direction is approved and keep building. We can always revise after.

>

[Your name]

This works because it acknowledges the silence, removes the cost of replying (just three yes/no answers), and sets the silence-equals-approval default. Most clients reply within hours of receiving this version of the email.

Frequently asked questions

Isn't structured feedback rude or pushy?

The opposite. Open-ended "any thoughts?" puts the burden of structuring the response on the client, on top of them already being busy. Three named yes/no questions are *respectful of their time*. Most clients prefer the structured version once they've experienced it.

What if the client genuinely needs to think about it?

Two things. First, "needs to think about it" is sometimes real but usually a euphemism for *I haven't prioritised this yet*. Second, the silence-equals-approval default doesn't override anything — they can still come back two days later and ask for a change. It just keeps the project moving instead of stalled.

How does this work for ongoing retainer clients?

Even better. With retainers you can set up the structure once — three named questions per deliverable, default deadlines, silence-equals-approval — and apply it across every project. The client gets used to the rhythm; replies arrive faster and faster as the relationship compounds.

Does this work for non-creative work (like dev or strategy)?

Yes. The principle is independent of discipline — humans avoid open-ended decisions universally. Devs can ask "Does this API contract work for your frontend (yes/no)?" instead of "Thoughts on the spec?" Strategy consultants can ask "Should we prioritise option A or option B?" instead of "What's your reaction to the deck?"

The takeaway

Stop interpreting client silence as disrespect. It's almost always decision fatigue, and almost always fixable in four small moves: ask three named yes/no questions, anchor them to specific elements, frame deadlines around *your* workflow, and default to approve on silence. The pattern feels strict the first time you use it. By the third project you'll never ask "any thoughts?" again.

Delivvo's portal lets clients react to specific files with structured feedback per file — approve, request changes, or leave inline comments — instead of writing long emails. File versioning is built in (5 versions per deliverable on Starter, up to 100 on Agency), so the v1 → v2 → v3 trail is preserved and "go back to last week's version" is one click, not a Dropbox dig. Try it free for 7 days.