Short answer: follow up 2–3 business days after sending the proposal, or the day after the date the client gave you. Keep it to two or three sentences, give them one easy next step, and set the next follow-up date before you hit send.The hard part usually isn't the wording. It's the waiting.You send a proposal and the client seemed interested. Then nothing. Three days pass, then five. You don't want to look desperate, so you wait a bit longer, and the deal goes cold on its own.Proposal follow-up combines two separate problems: when should you follow up, and what should you say. The first matters more than most people realize, because a perfect message doesn't help if you forget to send it.

Before you send: set the follow-up now

Don't rely on remembering later. When the proposal goes out, create the next action immediately:

Proposal sent: Tuesday
Next action: Follow up with Maya if there is no reply
Review date: Friday

You can improve your odds further before sending. Ask one question in the covering email: "When would you like to decide by?" The answer gives you a natural reason to follow up.

Use the timeline you agreed

There isn't one perfect schedule for every proposal. Context matters. If the client said "we'll review this Thursday," then Thursday afternoon or Friday morning gives you a natural reason to get in touch. If they gave no timeline, a short follow-up after two or three business days is reasonable.A useful principle:

Follow up based on the expected decision process, not your anxiety about the deal.

A simple follow-up sequence

You don't need a long drip campaign. Three touches are enough for most proposals:

WhenPurposeWhat to do

Day 2–3Check-inAsk if they've had a chance to review it and offer to walk through the scope

Day 7–8Decision questionAsk what's blocking the decision, or whether the timeline has changed

Day 14+Close the loopGive them an easy way to say "not now"

Adjust the timing to the client's own timeline. A client who said "we decide at the end of the month" needs a different rhythm than one who said "send it over."

Your first follow-up should move things forward

Avoid sending only "Just checking in." It gives the recipient no new reason to reply. Make the next step easy instead:

Hi Maya, just checking whether you've had a chance to review the proposal. Happy to walk through the scope together if anything needs clarifying. Would a short call this week be useful?

Or, with something concrete to answer:

Hi Maya, following up on the proposal from Tuesday. The main decision point is whether to include the analytics phase in the initial scope. Once that's confirmed, I can finalize the timeline.

Three tones to choose from

Friendly

Hi Maya, just checking back on the proposal I sent earlier this week. No rush if you're still reviewing it. Happy to answer questions or walk through the scope together.

Direct

Hi Maya, following up on the proposal from Tuesday. Is this still something you'd like to move forward with? I'm happy to clarify anything before you decide.

Decision-oriented

Hi Maya, one quick follow-up on the proposal. Are we still aiming to start this month, or has the timeline changed? Either is fine. I just want to plan capacity correctly on our side.

None of these pressures the client. They make the situation clearer. Reply in the same email thread ("Re: Website redesign proposal") so the proposal is one click away.

What if there is still no reply?

Don't send increasingly anxious versions of the same message every two days. Space your attempts and change their purpose. A later follow-up can ask whether priorities changed:

Hi Maya, I wanted to close the loop on this. Has the project been postponed, or is it still something you're considering? No problem either way. Knowing where things stand helps me plan on my side.

This gives the client permission to say "not now," which is useful information.If you still hear nothing after the third touch, send one last short note and move the deal to a later review date:

Hi Maya, I'll assume the timing isn't right and close this out on my side. If things change, the proposal is still valid until the end of the month, and I'm glad to pick it back up.

Then set a reminder to check in again in a month or two. A quiet proposal is not always a lost one.

Don't confuse silence with rejection

Clients go quiet for many reasons. They may be waiting for internal approval, dealing with another deadline, on vacation, or discussing budget. The project may have lost priority, or it may not. You don't need to guess. Create a reasonable next step and get clarity.

Keep the proposal attached to the relationship

A proposal isn't an isolated event. It sits inside a relationship: discovery call, requirements, proposal, questions, follow-up, decision, active client. The context from those conversations shouldn't disappear when the pipeline stage changes. This matters even more once the prospect becomes a client. The person who needed a proposal follow-up may later owe you an approval, while you owe them a progress update.

The proposal follow-up system

A sustainable workflow has four parts:

Record what happened: proposal sent, and what was discussed.
Decide what happens next: follow up if there is no reply.
Give the next action a date: Friday.
Keep enough context to write the message: what was discussed, what needs deciding, how long you've been waiting.

This removes most of the mental work from following up.

Common questions

Should I follow up by email or phone?

Start with email in the same thread. If the deal is large or time-sensitive, a short call or message on another channel the client already uses is a reasonable second touch.

How many follow-ups are too many?

Around three well-spaced touches is usually enough. After that, close the loop politely and set a later date rather than continuing weekly.

What if the client asks for changes?

Treat that as a new next action: confirm the changes, send the revised version, and set a fresh follow-up date.

How AwiFin handles proposal follow-ups

In AwiFin, a proposal is part of the same relationship that continues after the deal closes. You can record that the proposal was sent and keep the follow-up as the primary next action. If the client doesn't reply, it stays visible in your attention queue. When it's time, AwiFin can prepare the message from the client history. If the proposal becomes an active project, you keep the same record for future updates, approvals and promises.The real question isn't "did I follow up on this proposal?" It's "do I know what needs to happen next with every important client relationship?"

How to Follow Up After Sending a Proposal Without Being Annoying