How-to guide · Winning work

How to follow up on a proposal

By the WorkKitly Team · Last updated: November 2026 · 7 min read

When a proposal meets silence, the silence usually means busy, not no. Follow up on a ladder: three short messages across about two weeks — a delivery check two or three days after sending, a value nudge around day seven, and a closing-the-file message around day fourteen that makes replying effortless. Each message asks something specific or adds something useful; none of them apologises for existing, offers a discount, or nags. Most proposals are not beaten by a better competitor — they die quietly in an inbox nobody followed up on. This guide sets out the ladder, with the wording.

Why proposals go quiet

A silent inbox feels like a verdict, but it is usually a queue. The proposal is sitting behind one of four common causes — and each one needs a different nudge, which is why the ladder below asks questions instead of repeating "any update?":

  • Internal approval. Your contact likes the proposal and cannot sign it off alone; it is travelling through people you have never met, at their pace, not yours. The nudge that helps is ammunition — something short and useful they can forward.
  • Competing priorities. The problem the proposal solves is real, but it is not this week's fire. Nothing about your document is wrong; it is simply not urgent — yet. The nudge that helps is an honest reason the timing matters, if one exists.
  • The decision-maker changed. Your contact has moved roles, gone on leave, or lost the budget to someone else. The proposal may be orphaned, not rejected. The nudge that helps is the delivery check: it surfaces a new owner.
  • The price needs a conversation. The number is the sticking point, but raising it feels awkward, so nobody does. The nudge that helps is an easy exit — a message that makes "no", or "not at that price", cheap to say.

The ladder: three messages, about two weeks

The ladder borrows its discipline from chasing an unpaid invoice — one message per stage, each arriving on a rhythm rather than on impulse; our guide to asking for late payment professionally is the same idea pointed at money instead of a decision. Three touches, then stop. Send each one in the same thread as the proposal, subject line unchanged, so the document sits one scroll away: a fresh subject reads as a new demand, while the same thread reads as a conversation continuing. And write each message as if it were the only follow-up you will send — because the next one is a week away.

Days 2–3: the delivery check

Job: confirm the proposal arrived, with the right person, and reopen the conversation without demanding a decision nobody is ready to give. Tone: pure logistics — you are checking the plumbing, not the verdict. Keep it under 40 words; this version is 38, placeholders included:

Hi [Name] — just checking the proposal reached you: I sent the quote for [project] on Tuesday, price and timeline included. Happy to walk through any part of it on a short call this week if that's easier.

Notice what it does not do: no "just following up", no re-summary of the proposal, no pressure. It asks one question with an easy answer — and offers a call, because some clients will decide out loud faster than they will ever reply in writing.

Days 6–8: the value nudge

Job: give the decision something new to feed on — one useful, relevant thing: a similar finished project, a short case note, the answer to a question they raised on the call. Tone: a colleague adding material, not a salesperson repeating himself. Around fifty words; this version is 48:

Hi [Name] — one thing that may help your decision: I finished a similar [project type] for [client type] last month, and the write-up is attached — same scope, same shape. If the timeline in the proposal still works, I can hold the start date until Friday week.

One honesty rule governs this stage: the timeline note only works if it is true. "My calendar is filling" from an empty calendar is fake scarcity — clients can smell it, and it spends exactly the trust the closing message will need. If no date is genuinely at risk, send the example on its own. It is enough.

Days 13–15: closing the file

Job: end the wait — yours and theirs. Assume the answer is a polite no, make declining effortless, and leave the door genuinely open. Tone: unhurried and final; this is the last message, and it should sound like it costs you nothing. This version is 46 words:

Hi [Name] — I'll close the file on the [project] proposal at the end of this week, so the start date in it stops holding. No hard feelings either way: if the timing's wrong, just say so, and if things change later, the door stays open.

Expect this one to draw the most replies of the three. That is not a trick: a real, near deadline turns an indefinite "later" into one small decision today, and many clients were only ever waiting to be asked clearly. A deadline to decide is a kindness, not pressure — and treat every reply it earns, yes or no, as the ladder working rather than failing.

What never to do

Four habits turn a follow-up from professional into costly:

  • Never discount into silence. A price cut offered to an empty inbox reprices the proposal you already sent — and teaches the client that waiting makes your work cheaper. If price turns out to be the blocker, that is a scope conversation: something comes out of the project, or the schedule changes. Silence alone is not evidence about price.
  • No guilt, no grievance. "I spent a long time on that proposal" may be true; it becomes the client's problem only if you make it one — and making it one ends the relationship along with the sale.
  • No empty bumps. "Just bumping this to the top of your inbox" adds nothing, asks nothing, and announces that you had nothing to say. Every follow-up must carry a question or a contribution.
  • No fourth, fifth or sixth chase. The ladder ends at closing the file. Beyond it, persistence stops reading as confidence and starts reading as the reason the answer was no.

When they reply no

A no is a result — the ladder's job was a decision, not only a yes. Answer it the same day, in three lines:

Thanks for letting me know, [Name] — a clean no is genuinely useful, and I mean that.
Out of curiosity, was it the price, the timing, or the fit? A word either way helps me.
And if [type of work] comes up again, I'd be glad to hear from you.

The middle line asks the one learning question — price, timing or fit — once, and never argues with the answer. Whatever they say is the cheapest market research you will ever get, and some "not now" replies turn into next quarter's brief. The goodwill is the real asset: the relationship you protect in this exchange is the same one that later produces referrals and the testimonials your next proposals quote.

Prevention: agree the follow-up before you send

The easiest follow-up is the one the client is expecting. Set it at the close of the discovery call: "I'll send the proposal on Tuesday, and I'll check in on Thursday if I haven't heard." Then repeat the line inside the proposal itself, beside the next steps — sections eleven and twelve of our proposal template, section by section are where it lives. A follow-up that was announced in advance is not an interruption; it is a kept appointment.

Give the proposal a validity date, too. A price with an honest expiry — "this price and start date hold for 14 days" — behaves differently from an open-ended one: it makes the closing-the-file message a fact rather than a tactic. The estimate generator builds a valid-until date into every estimate it produces, and the proposal generator does the same for proposals. Set a date you mean, and the ladder largely runs itself.

Keep the ladder on rails with a list so simple it survives a busy week: one line per open proposal — client, date sent, the date of the next rung, and the date the file closes. Update it when a message goes out, not from memory at the end of the month. Most follow-up systems fail because they live in the sender's head, where a crowded inbox quietly deletes them; a five-line list does not. When the closing date passes with no reply, mark it closed — and mean it.

Questions

Three times, on a ladder: a delivery check at day two or three, a value nudge around day seven, and a closing-the-file message at about two weeks — then stop. A fourth or fifth chase rarely changes a decision; it mainly changes what the client thinks of you. The closing message, not more persistence, is the touch that most often earns the reply.
First at day two or three — early enough that a lost or misrouted proposal is still easy to fix, late enough not to hover over the send. Space the rest about a week apart: days six to eight, then days thirteen to fifteen. Announce each next step as you go, so every message arrives as an appointment kept rather than a surprise.
No. A discount offered into silence reprices the proposal already sent, and teaches the client that waiting makes your work cheaper. If price genuinely is the blocker, that is a conversation about scope — something comes out of the project, or the schedule changes — not a percentage off for replying. And silence alone is not evidence that price is the problem.
Welcome it, and re-quote honestly. The price and the start date were held for a window that has now passed, so check both before reissuing: your calendar may have filled in the meantime, and your rates may have moved. Most clients accept a refreshed date without argument — closing the file was never a door slammed, just a wait ended.

Related: the proposal they went quiet on

A follow-up can only rescue a proposal worth rescuing. If the document itself was thin, rebuild it on the full structure with the proposal generator — deliverables, timeline, price, payment schedule and a validity period in one printable document — and run the next first conversation on the discovery call script, so next time the follow-up is agreed before the proposal even exists.