How to Follow Up After Sending an IT Proposal (Without Being Annoying)

You sent the proposal. You are proud of it. And now you are waiting.

A day passes. Then three. Then a week. The silence starts to feel like rejection, even though you have no evidence either way. You want to follow up but you do not want to seem desperate. So you wait a little longer. Then a little longer. And by the time you do reach out, two weeks have passed and the momentum is gone.

This is the most common and most avoidable part of losing a deal after submitting a strong proposal.

Following up is not annoying. Following up badly is annoying. There is a significant difference, and this is how to stay on the right side of it.

Why follow-up matters more than most consultants think #

Evaluators are busy. Your proposal lands in an inbox alongside twelve other things that needed attention yesterday. This is not disrespect — it is the reality of how decisions get made inside organisations.

A well-timed follow-up does three things. It confirms the proposal was received and reviewed. It gives the client a natural opening to raise questions or concerns before they become reasons to say no. And it keeps you in the conversation at the moment the client is making a decision, rather than after they have already moved on.

The consultants who win the most proposals are not always the ones who wrote the best document. They are the ones who stayed professionally present throughout the evaluation period.

The follow-up framework #

Day 1 — The delivery confirmation #

Send this on the same day you submit the proposal, or within a few hours.

This is not a follow-up. It is a handover message. Short, professional, no pressure.

Subject: Proposal submitted — [Project Name]

"Hi [Name], I've just sent through the proposal for [project]. Please let me know if you have any trouble accessing it or if anything needs clarification before your review. Happy to walk through any section on a call if that would be useful. Looking forward to hearing your thoughts."

This message does something important: it opens a door for the client to ask questions early, before any hesitation becomes a decision to go with someone else.

Day 3–5 — The first follow-up #

If you have not heard back, follow up three to five business days after submission. For most IT consulting engagements, this is the right window — long enough that the client has had time to read the proposal, short enough that you are still fresh in their mind.

Subject: Re: Proposal — [Project Name]

"Hi [Name], just checking in to see if you had a chance to review the proposal. Happy to answer any questions or adjust any part of the scope before you make a decision. Let me know if a quick call would be helpful."

Keep it short. One question, one offer. No summary of the proposal. No restating why you are the right firm. They have the document — your job here is to open a conversation, not to resell.

Day 10–14 — The second follow-up #

If there is still no response after 10 to 14 days, send one more message. This one is slightly different in tone — it acknowledges the timeline while keeping the door open.

Subject: [Project Name] — still available if timing has shifted

"Hi [Name], I wanted to check in one more time on the [project] proposal. I understand these decisions take time and there may be internal factors at play. If the timeline has shifted or the scope has changed, I am happy to revisit. Otherwise, just let me know where things stand when you have a moment."

This message accomplishes two things. It demonstrates patience and professionalism. And it gives the client an easy exit — acknowledging that sometimes procurement stalls for reasons that have nothing to do with the vendor.

Day 21+ — The final check-in #

After three weeks of silence, one last message is appropriate. After this, let it rest.

Subject: Closing the loop — [Project Name]

"Hi [Name], I have not heard back regarding the [project] proposal and I do not want to keep filling your inbox. I will assume the timing was not right for now — if anything changes or a new project comes up, I would be glad to pick up the conversation. Wishing you well."

This message closes the loop with dignity. It does not burn the relationship. And it occasionally prompts a response from clients who had genuinely lost the thread and feel guilty about the silence.

How to read the silence #

Not all silence means the same thing. Learn to distinguish between them.

Silence with open reads — if you have proposal tracking enabled and you can see the client has opened the proposal multiple times, silence does not mean disinterest. It often means internal discussion is happening. Follow up with a question, not a status check.

"I noticed you have had a chance to look through the proposal — happy to answer any questions that came up during your review."

Silence after a specific conversation — if the client was enthusiastic on a call and has gone quiet since, something changed internally. Budget freeze, new priority, change of decision-maker. Follow up with an open question.

"Has anything changed on your end since we spoke? Happy to adjust the scope or timing if that would help."

Complete silence from the start — no read confirmations, no response to any message. This can mean the proposal was not the right fit, or it went to the wrong contact. After the second follow-up, try a different channel — a LinkedIn message or a brief phone call — before giving up entirely.

What not to do #

Do not follow up every two days. It signals desperation and trains the client to ignore your messages. Space your follow-ups as outlined above.

Do not restate your proposal in follow-up emails. The client has the document. Summarising it again suggests you do not trust them to have read it, which is not the relationship you want to establish.

Do not ask "have you made a decision yet?" This frames the follow-up around your need for an answer, not their need for information. Always orient the message around the client's project and any help you can provide.

Do not drop your price unprompted. If you have not had a conversation about budget concerns and you offer a discount in a follow-up email, you signal that your original price was not your real price. This damages trust and invites the client to negotiate on every future engagement.

When to stop following up #

After four contact points across three to four weeks with no response, stop. Send the closing message and move on.

This is not giving up — it is protecting your time and your reputation. Persistent follow-up past this point shifts from professional persistence to pressure, and the relationship you are trying to build cannot start from a place of pressure.

The clients who are right for your practice will respond. The ones who do not were unlikely to be good long-term clients regardless of whether you won that first project.

The follow-up cadence at a glance #

What this looks like in practice #

The consultants who follow up well share one habit: they treat the post-submission period as part of the sales process, not a waiting room.

They stay informed about what the client is reading. They respond to signals — a question, a re-read, a forwarded proposal — with targeted follow-ups instead of generic check-ins. And they accept silence as data, not as failure.

If you are spending hours on proposal documents but giving no thought to what happens after you hit send, you are leaving deals on the table that your proposal already won.

For more on building proposals that hold up under evaluation, read our IT consulting proposal template and our guide on common IT proposal mistakes.