What to Do When a Client Won't Approve Your Design (or Goes Silent)
A client who won't sign off, or stops replying, leaves your project stuck and unpaid. Why it happens and how to get a decision without nagging or burning the relationship.
The work is done. You sent it for final approval a week ago. Since then: nothing. No "approved," no changes, no reply. The project is at 99%, your final payment is tied to sign-off, and you're stuck, unable to invoice and unable to move on, waiting on one word from someone who's gone quiet.
A stalled approval is one of the most expensive states a project can sit in, because everything is finished except the part that lets you get paid. The good news is that most non-approvals aren't rejection. They're friction, ambiguity, or fear, and each of those has a fix.
Why clients don't approve
Before you chase, it helps to know what you're actually dealing with. A client who won't sign off is usually in one of four situations:
- They don't know they're being asked to decide. You said "let me know if this works." They read it as optional. No clear ask, no clear answer.
- They're not the decision-maker. The person you're talking to needs someone else to bless it, and that handoff has stalled somewhere you can't see.
- Approving feels risky. Saying "approved" feels final and a little scary, like signing something. So they avoid it, vaguely, indefinitely.
- They're genuinely busy and it's not urgent to them. It's the most important thing in your week and item nine in theirs.
Notice that none of these is "the work is bad." If the work were the problem, you'd usually hear about it. Silence is almost always a process gap, not a verdict.
How to get the decision
1. Make approving a clear, single action
"Let me know your thoughts" is not an approval request. Replace it with an unmistakable one: "This is final. Can you reply 'approved' so I can lock it and send the last invoice?" One action, obvious, binary. You'd be surprised how often the holdup was simply that the client never realized a decision was being requested.
2. Lower the stakes of saying yes
If approval feels like signing a contract, make it feel like confirming an obvious fact instead. Remind them what they're approving and how bounded it is: "This approves the homepage as it is now. Anything new after this is just a separate future task, so you're not locking yourself out of changes later." People say yes more easily when yes isn't a trapdoor.
3. Find the real approver
If you suspect your contact can't actually decide, ask directly and helpfully: "Is there anyone else who needs to see this before we call it final? Happy to send it to them directly." You're not going over their head. You're unblocking a handoff they may be stuck on too.
4. Set a deadline with a default
The single most effective tool against silence is a stated default: "If I don't hear back by Friday, I'll treat the current version as approved and proceed to final delivery." This is fair, it's clear, and it converts an open-ended wait into a decision the client has to actively make. Put this in your contract up front and it's never a surprise.
5. Keep the follow-up warm and short
When you nudge, keep it light and assume the best: "Hi! Just bumping this. Whenever you get a sec, a quick 'approved' is all I need to wrap things up." No guilt, no passive aggression. The client isn't your adversary. They're busy.
How to never be here again
Most stalled approvals are preventable, and the prevention is structural, not a matter of chasing harder. Two habits remove almost all of it:
Agree the approval mechanism up front. In your proposal, state how sign-off works and what happens if the client goes quiet (the deadline-and-default rule). When the client has already agreed to the structure, the closing conversation is just you following the plan.
Make the approval moment a real, low-friction step, not a vague message. This is the root cause behind most of this. When approval is an explicit, easy action tied to a specific version, clients take it, and you end up with a dated record instead of a hope. That's the entire idea behind how to get a client to formally sign off, and it's why a stalled "looks good" is so much rarer when the sign-off step is built into the workflow.
How Lyba makes approval the easy path
Lyba turns sign-off from a vague email request into a single, obvious action. After the client reviews your live Framer site and the feedback is resolved, approval is its own deliberate step: one clear action on a specific version, not a sentence buried in a thread. When they approve, Lyba records who signed off, what version, and when, as a dated receipt in your dashboard.
Because the ask is unambiguous and tied to a frozen version, clients are far less likely to drift into silence, there's a clear thing to say yes to. And because the approval is its own step rather than an inference from a comment, you're never again in the position of wondering whether "looks good" counted.
FAQ
What do I do if a client won't approve my design? Make the approval a single, clear, binary action ("reply 'approved' so I can lock it"), lower the perceived stakes, confirm you're asking the real decision-maker, and set a deadline with a default. Most non-approvals are friction or ambiguity, not rejection.
My client stopped responding after I sent the final design. What now? Send one short, warm nudge with an explicit ask and a deadline-and-default: "If I don't hear back by Friday, I'll treat this as approved and proceed." This is fair and converts silence into a decision, especially if you set the rule in your contract up front.
Can I treat silence as approval? You can if you agreed that rule in advance. State in your proposal that work is considered approved if the client doesn't respond by a set deadline. Without a prior agreement, assuming approval from silence is risky.
How do I stop projects stalling at the approval stage? Build a clear, low-friction sign-off step into your process and agree the mechanism up front. Stalls happen when approval is a vague message; they mostly disappear when it's an explicit action on a specific version. Here's the full process.
Stop sitting at 99%
A finished project you can't invoice is the worst place to be stuck. The fix is rarely chasing harder. It's making the decision easy to give and impossible to misread.
See how Lyba makes client sign-off a one-action step on your live Framer site, or start a free 14-day trial.