How to Follow Up on Unanswered Proposals

You sent a proposal. It's been four days. Nothing. The silence starts doing work your imagination is happy to fill in: they hated it, they went with someone else, they decided not to do the project at all. Most of the time none of that is true. Most of the time the proposal is sitting in a tab the client meant to get back to, or it's stuck one step above them in an approval chain they didn't mention, or it simply got buried under forty other emails the day it arrived.

A good follow-up doesn't try to force an answer out of someone. It just makes it easier for them to give you one.

Why silence usually isn't a no

Before you write anything, it's worth separating what silence actually means from what it feels like it means. A few of the most common reasons a proposal goes unanswered have nothing to do with your pricing or your work:

• They got busy. Reading a proposal carefully, thinking about scope, and writing back takes focused attention, which is exactly what a lot of people don't have in the middle of a normal week.
• Someone else has to sign off. Even a "solo" decision-maker sometimes needs a partner, a manager, or a budget holder to glance at it first, and that step isn't visible to you.
• It got buried. Email is where things go to disappear. A proposal competing with a full inbox doesn't need a rejection to go unanswered, it just needs to not be the most urgent thing that day.
• They're still comparing options. If you're not the only proposal they requested, they may be waiting to have all of them in hand before replying to any of them.

None of this means you should assume every silent client is secretly interested and just needs enough nudges. It means a single unanswered email, a few days in, is not evidence of anything, so the right first move is a short, low-pressure check-in, not a retreat or a guilt trip.

A follow-up cadence that doesn't wear out its welcome

There's no universal rule for timing, but a cadence that works for most freelance proposals looks like this:

First follow-up: a few days after sending

Not the next morning: give it a few business days. The message should be short and should reference something specific from the proposal, not a generic "just checking in." Specificity signals that you're following up because you actually care about this project, not because you're running a mass check-in across every open proposal:

"Hi [Name]: wanted to check in on the proposal I sent Tuesday. Happy to walk through the timeline section if it's useful, or adjust anything before you decide. Let me know what would help."

That does two things a vague check-in doesn't: it names a specific part of the document (so it's clear you're not sending a copy-pasted nudge), and it gives the client an easy, low-commitment way to respond, ask a question, request a change, instead of forcing an up-or-down decision right now.

Second follow-up: about a week after that

If the first message didn't get a reply, give it another week before following up again. This one can offer something slightly more concrete: a willingness to adjust scope, answer a specific question you suspect they might have, or clarify pricing.

"Hi [Name]: following up once more on the proposal. If the scope or budget isn't quite right, I'm glad to revise it. If now isn't the right time, that's completely fine too, just let me know either way so I can plan accordingly."

That last line matters. Giving the client permission to say "not now" or "no" actually makes a "yes" more likely, because it removes the awkwardness of having to reject you that's sometimes the real reason behind a non-reply.

After that: treat it as a no, and stop

If two follow-ups haven't produced a reply, further messages almost always do more harm than good. At that point, continued follow-up stops reading as helpful and starts reading as pressure, which is a bad impression to leave with someone who might come back to you for a different project six months from now. Two considerate follow-ups is a reasonable, professional effort. A third, fourth, or fifth is not persistence, it's a different signal entirely, and not a good one.

What makes a follow-up message actually work

The common mistake is re-sending the pitch: repeating the value proposition, restating why you're a good fit, re-explaining the scope. If the client hasn't read the first version carefully, a longer second version isn't more persuasive, it's more to skip past. The messages that actually get replies tend to share three traits:

• They're short. A few sentences, not a few paragraphs. If it takes more than thirty seconds to read, it's competing with everything else in their inbox and losing.
• They're specific. Referencing an actual detail from the proposal (the timeline, a line item, a particular deliverable) signals you're following up on this proposal, not running a template across everyone who hasn't replied.
• They're easy to respond to. A message that can be answered with a one-line reply, "yes, let's start," "can you adjust X," or "not right now", gets answered more often than one that implicitly demands a full decision.

Avoid anything that reads as pressure: countdown language, implying the offer expires, or any version of "just wanted to bump this to the top of your inbox" sent more than twice. None of that changes a client's underlying decision, it just changes how they feel about you while they make it.

When not to follow up at all

If your proposal stated an explicit decision deadline, "this scope and pricing are valid through [date]", and that date has passed without a reply, you don't need a follow-up message at all. The deadline already did that job. At that point, the honest move is either to let it lapse silently or to send a brief note that the terms have expired and you're happy to send an updated proposal if they're still interested, not to chase an answer to an offer that, by your own stated terms, no longer stands. A proposal with a clear deadline gives both sides a clean, low-awkwardness way to let it go, which is one good reason to put a decision window in the document in the first place.

Closing the loop when a client goes fully silent

After a reasonable follow-up cadence with no response at all, the last useful message isn't another nudge, it's a clean close:

"Hi [Name]: I haven't heard back, so I wanted to check: should I keep this proposal open, or would it be better if I closed it out for now? Either is completely fine, and I'm glad to revisit it down the line if the timing changes."

This does something a third or fourth follow-up can't: it turns an ambiguous silence into a clear outcome, one way or the other. Some clients will reply to exactly this message after ignoring the first two, simply because it's easier to answer a direct either/or question than an open-ended check-in. Others still won't reply, and that's fine. At that point you've made a genuine, professional effort, the ball is unambiguously in their court, and you can move on to other work without resentment or a lingering sense that you should have followed up "just one more time."

If you're tracking proposals inside VEYQO, you can see at a glance which ones are sitting unopened versus opened-but-unsigned: worth checking before you write a follow-up, since "they haven't opened it yet" and "they've read it three times and gone quiet" call for slightly different messages.