How to Follow Up on a Client Proposal Without Being Pushy

To follow up on a client proposal without being pushy, refer to the specific project, make the next decision easy and respect the review timeline you agreed on. Each message should help the client respond, rather than simply repeat that you are waiting.

This guide is for freelancers, independent consultants and small B2B service businesses following up after a genuine project conversation. It includes three email examples and a simple way to track the next action without relying on memory.

Agree on the next step when you send the proposal

A proposal is easier to follow up when both people know what happens next. Before sending it, ask who will review it, whether anyone else needs to approve it, and when the client expects to make a decision.

Your covering message can include a sentence such as:

I have attached the proposal for [project]. You mentioned reviewing it with [team/person] this week. Would it be helpful if I checked in on [agreed date] to answer questions and confirm the next step?

Make the proposal itself easy to identify: use a clear project name and version, explain the intended outcome, and state the scope and fee. If the client cannot tell what they are deciding on, a reminder alone will not fix the problem.

When should you follow up on a proposal?

Use the client's agreed review date first. A proposal sent yesterday does not need an urgent reminder if the client said their team would review it next week.

If no review date was agreed, choose a reasonable first check-in based on the conversation, project complexity and working days involved. For example, you might send a short check-in after three business days, then leave more time before the next message. That is an illustrative workflow, not a universal schedule or a promise of better response rates.

  • A review date was agreed: follow up at the agreed time, allowing for any stated delay.
  • The client needs an internal decision: ask about that decision date instead of sending repeated reminders before it.
  • The client gives a new date: update your next action and wait until then.
  • The client declines or asks you to stop: close the opportunity and stop the sequence.

A genuine proposal expiry or scheduling constraint can be relevant. Mention it only if it is real and was communicated clearly; do not invent a deadline to force a reply.

Write each message around one useful question

A concise proposal follow-up usually needs four parts:

  1. Context: identify the project and proposal date.
  2. Relevance: refer to a real objective, question or review step from the conversation.
  3. One request: ask for a decision, clarification or revised timeline.
  4. An easy response: give the client a straightforward way to move forward, defer or decline.

Continue the existing email thread when it helps preserve context. If the client normally communicates through another agreed channel, use that channel thoughtfully. Avoid sending the same reminder by email, direct message and phone on the same day.

Three proposal follow-up email examples

These examples were written for this guide. Personalize them using the actual conversation; do not add promises, project details or availability you cannot support.

1. First check-in: confirm the review step

Subject: Re: [Project name] proposal

Hi [Name],

I am following up on the [project] proposal I sent on [date]. You mentioned [specific objective or review step]. Is [agreed decision date] still a suitable time to review the next step?

If a point in the scope or pricing needs clarification, let me know which part and I will address it.

Best,
[Your name]

If you never discussed a decision date, replace that question with: “When would be a useful time for me to check back after you have reviewed it?” Do not imply a commitment the client did not make.

2. Second message: resolve a specific question

Subject: Re: [Project name] proposal

Hi [Name],

One detail from our conversation may be useful while you review the proposal: [brief clarification of an actual question or requirement].

Would you prefer to proceed with [proposed scope], discuss an adjustment, or revisit the project at a later date?

Best,
[Your name]

Use this message when you have something relevant to clarify. If you do not, ask a short status question instead of inventing an insight or sending unsolicited extra work.

3. Final check-in: close the loop without pressure

Subject: Re: [Project name] proposal

Hi [Name],

I have not heard back about the [project] proposal, so I will pause follow-ups after this message.

If the project is still active, please let me know the next step or a suitable date to reconnect. If plans have changed, that is fine too.

Best,
[Your name]

Use a closing message after a limited number of appropriate attempts, taking the client's circumstances into account. It is a stopping point, not a threat. Do not restart the same sequence a few days later without a relevant reason.

Respond to the reason for the delay

Silence does not reveal whether the issue is timing, budget, internal approval or a change in priorities. Once the client replies, replace the generic sequence with a specific next action.

  • “We need more time.” Ask when it would be useful to reconnect and record that date.
  • “The budget is lower.” Discuss a smaller scope or a later phase. Do not automatically offer the same work at a lower price.
  • “Another person must approve it.” Ask what information that person needs and when the review is expected.
  • “We want something different.” Clarify the change and issue a clearly identified revised proposal if appropriate.
  • “We are not proceeding.” Acknowledge the decision, record the outcome and stop following up.

If you are considering a price adjustment, revisit your own cost and time assumptions first. The guide to calculating a freelance hourly rate explains how billable capacity affects your pricing foundation.

Track the next action, not just the proposal date

A list of proposals sent is incomplete if it does not show what to do next. Keep one record for each opportunity with:

  • Client or company name and the relevant contact.
  • Project name, proposal date and estimated value.
  • Current stage and last contact date.
  • Next action and next follow-up date.
  • Short notes on the client's review process.
  • The outcome when the opportunity is won, lost or deferred.

For example: “Awaiting finance review; send the requested scope clarification; reconnect on the client's agreed date.” That is more useful than a note saying only “Follow up.”

The Dovea Follow-Up Command Center organizes leads, proposal dates, next actions and follow-up dates in Excel and Google Sheets. Its Follow-Up Planner distinguishes overdue, due-today and upcoming actions, and the workbook includes message templates and a weekly review.

You still send the messages and update the records yourself. The tool does not automatically send emails, calendar alerts, notifications or push reminders, and it does not guarantee replies or sales.

Review the pipeline and close stale opportunities

During a regular review, check whether each active opportunity has a credible next action. Update changed dates, record decisions and remove declined projects from your active follow-up workload. Treat an estimated deal value as an opportunity, not as confirmed revenue or cash.

When a client accepts, move from proposal follow-up to a clear project handoff: confirm the agreed scope, required inputs and next delivery step. If additional requests arrive after approval, use the process for handling scope creep before taking on extra work.