How to Follow Up After You Send a Proposal (Without Begging)

Set the follow-up date before you hit send

The follow-ups that never happen are the ones waiting for a good moment. So set the reminder the minute you hit send. Make it the step right after sending, not something you'll get to.

• Ask for a decision date inside the proposal itself. The best time to agree it is at the end of the discovery call.
• Plan the first follow-up for just after that date, if they gave one.
• Plan it a few business days after sending, if they didn't.
• Put the date in your sales pipeline under "Proposal sent", not in your head.

Follow-up won't rescue a proposal sent to the wrong buyer or at the wrong price. It does make sure a good proposal gets an answer.

Three touches, each with a reason to exist

How many is enough? Self Employed's proposal guide follows up at three days, one week, and two weeks. I think that's about right. The rule that matters most is that each touch should add something, never just "checking in."

Touch 1: make sure it landed

Hi [Name], I sent the proposal for [project] on [day]. Did it come through all right? Happy to answer anything before your decision on [date].

Touch 2: add something useful

Answer a likely question, clarify one line of the scope, or offer a smaller scope or a later start.

Hi [Name], one thing that often comes up: [question]. The short answer is [answer]. If timing's the issue, a [later start / smaller first phase] is an option.

Touch 3: ask for the decision

Hi [Name], does [date] still work for a decision on [project]? If priorities have shifted, that's fine to say.

Close the loop

After the third touch, send one last short message. It gives the client an easy yes, no, or not-now, and it ends your chasing.

Hi [Name], I haven't heard back, so I'll assume the timing isn't right and close the file on [project] for now. If that changes, reply here and we'll pick it up.

Then stop.

Mark the deal lost or not-now in your pipeline. Knowing when to stop is part of following up, not a failure of it.

What makes a follow-up sound desperate

Following up isn't the problem. Frequency plus empty messages is.

• Drop "just checking in." Replace it with one specific question or piece of information.
• Drop the apology. You're checking on a decision they agreed to make.
• Space them out. Days apart, not a day apart.
• Skip invented deadlines. Mention a deadline only if it's real, like the proposal's expiry date or a start slot you can't hold.
• Keep it short. A few sentences each. The clear next action guide covers ending every message with one ask.

When they say "not now"

Thank them, ask when it makes sense to check back, put that date in your pipeline, and stop the sequence.

Thanks for letting me know, [Name]. When would it make sense to check back? I'll make a note and leave it until then.

When the answer is yes, send the deposit invoice under your payment terms, then onboard the client.

Illustrative example (fictional)

A web designer sends a proposal on Monday with a decision date of the following Friday. On Wednesday she confirms it arrived. The next Monday she answers a question about hosting. After the Friday decision date she asks whether it still works. A week later she sends the close-the-loop note and marks the deal not-now with a check-back date.

For writing short messages like these, the Better Messages Kit has a guide, a workbook, and reusable prompts.

Pick the date for your first follow-up before you send your next proposal.