You sent the proposal eleven days ago. The call before it was warm, the work was good, and the thread has been quiet since. You’re fine. The question you’re turning over is how many times you can write before you look desperate, and the answer turns on content rather than count. Give a message a reason to exist and it reads well at any interval a person would actually use. Send one that only asks for news and it reads as pressure the first time.
- Following up almost always keeps you in the running. Work gets lost the other way, by going quiet yourself, and by writing three messages that each ask the reader to supply the news.
- A proposal in the gap before a contract has no shared thread and no claim on anyone’s attention. That’s the situation rather than a fault in your tone, and it decides what a follow-up can usefully do.
- The strongest move after a proposal goes quiet is a smaller version of the work.
- The message that ends it well is worth more than four that keep it open. It produces an answer, and it’s the one moment you can ask why.
What pushy actually is
The fear here is that following up makes you look like somebody who needs the work. It’s a fair fear. Clients do read that, and they read it as a signal about how good you are. What they read it from is worth being precise about, because the count of messages is rarely the thing.
A question only news can answer. Any thoughts on the proposal is the standard follow-up, and it’s close to useless. It asks a person to have a position. Most readers are still forming one, so the only reply available is an admission that the thing has sat untouched, which is an unpleasant thing to write. The question produces the silence it was sent to break. Then you send it again.
An observation about their silence. I have not heard back from you. I sent this two weeks ago. Both are true, and both land as a charge. They put the reader in the wrong, and a reader in the wrong either explains themselves or avoids you. Avoidance is cheaper.
Urgency you made up. A rate that goes up on Friday, a discount that expires, a slot that will be gone by Tuesday while your calendar sits empty. Everybody has bought a mattress. The reader recognizes the mechanism instantly, and it moves your work into the category of things sold that way.
Temperature that changes across the sequence. The first message is friendly. The second is a little brisk. The third carries an edge the writer put there by accident, and the reader picks it up perfectly. Readers track the mood of a four-message sequence and forget the content.
The claim on sympathy. I put a lot of work into this. I have kept the week free. Said out loud, these ask the client to feel something for you, and a buying decision is a poor place for that ask.
Then there’s the vocabulary, which matters more than it should. Just circling back. Bumping this up your inbox. A gentle nudge. Wanted to touch base. Each one announces that the message is empty, and that announcement does the damage rather than the cliche. The word carrying most of it is just. It apologizes for the message existing, and the reader treats it accordingly.
Set all that against a message that says something. I have been thinking about the sequencing question your finance director raised, and I would do it the other way round from what the proposal says. Here is why. That one can arrive on the fourth attempt and land as useful rather than as pressure, because it’s doing the job instead of asking for one.
So the working definition, for the rest of this guide: a follow-up is pushy when its only reason to exist is your wish for an answer. Everything after that is craft in service of finding better reasons.
The sentence that makes most of this unnecessary
The best follow-up is one you already have permission to send. That permission is free at the moment the proposal goes out.
At the bottom of the covering email, name what happens next and put a date on it. I will give you a call on Thursday the eighteenth to talk it through, unless you would rather I left it with you longer. Or, if a call is too much for the size of the work, I will check in on the twelfth if I have not heard anything before then.
That sentence turns every later message into a kept appointment. A kept appointment reads as courtesy. It also hands your contact a graceful way to slow you down, and they’ll use it if they need to. Being told wait until after the board meeting on the third puts you well ahead of guessing for two weeks.
Two things are worth settling before the proposal goes out, and both are ordinary questions people answer honestly when asked directly. What is the process from here. Who else has to see this before it’s a yes. The second changes what you write and who you write it to. The first usually reveals a calendar that was invisible from outside.
Then send it at a time you can follow. A proposal that goes out at six on a Friday evening arrives into a weekend. It gets read on a phone, and it’s stale by the time anyone is back at a desk. Tuesday morning is free.
The ground before the proposal, and what to settle in the last five minutes of a scoping call so the two weeks afterwards stay warm, is a subject of its own and this collection takes it separately.
What is actually happening on the other side
One structural fact separates this from every other kind of waiting. Inside a live engagement, a stalled decision belongs to somebody. There’s a thread, an agreement, a person whose job includes your work. Before a signature, your proposal is a document with no owner, on nobody’s agenda, competing with three other documents that are also on nobody’s agenda.
So silence is the default state, and it holds until something in particular pushes against it. Most quiet proposals are being left rather than rejected. They’re waiting on a meeting that has yet to happen.
Four things are true often enough to be worth writing down.
Your contact has yet to have the conversation. She’s waiting for the right moment, or for a colleague to be back, or for a version of the argument she can win with. From where you sit it looks like indifference. It’s usually the opposite.
The comparison runs on its own clock. If you’re one of three, the pace belongs to the slowest of the three, and one of them takes a vacation in the middle of it.
The money was always looser than the conversation implied. People discuss work they’d like to do before the budget for it exists. That’s how projects get started. It also means the decision you think is pending is sometimes a decision still waiting to be scheduled.
They’ve chosen somebody else, and the note is hard to write. A no is unpleasant to send to somebody who was helpful, and silence is free. This happens more often than most people guess, and it’s why the closing message later in this guide earns its place.
From outside, the four look identical, and trying to tell them apart is where most pushiness comes from. Guessing produces a message written to a theory, and the theory leaks into the tone. So stop diagnosing and write messages that work under all four. That’s a smaller ask than it sounds. The same two things work every time: make the answer cheap to give, and give them something they didn’t have before.
The first message, and when
Wait until the proposal has had a real chance to be read once and mentioned to one other person. For a small piece of work with one decision-maker, that’s three or four working days. For anything that has to be discussed, a week to ten days. Sooner than that and you’re asking for a reaction, which is a smaller and less useful thing than a decision.
Leave the decision out of the first message. It’s early, and asking makes a reader who has yet to act feel behind, and that feeling is what produces avoidance. Two other jobs are available, and both are real.
Confirm it arrived. This is a real question. Proposals go astray at a rate that surprises people: attachments stripped by a mail gateway, a shared link that expired, a message sitting in a quarantine folder your contact checks on Fridays. I want to make sure this reached you, since attachments from outside sometimes do not, is answerable in four words by somebody who has yet to read a line of it. That’s its virtue. It gives a person with no news a way to reply.
Offer to walk through it. A proposal read alone is read at its price, since the number is the part that explains itself. A proposal walked through is read at its scope. Twenty minutes on a call is worth more to you than anything you can write, and the offer is easy to accept because it asks for time rather than a commitment. Make the slot trivial to take. A booking link that shows your real availability removes the three-message exchange that otherwise stands between the offer and the meeting, and Point can run that back-and-forth itself if you’d rather hand it over.
Keep it to five or six lines. A long first follow-up shows you’ve been thinking about this far more than they have. That’s true, and it’s yours to keep.
What a second message is allowed to carry
Here’s the rule that makes the rest of the sequence possible. Every message after the first carries something the last one lacked, and asking again counts for nothing. Send the same request twice and you’ve taught the reader that leaving your mail is free. That lesson is expensive and slow to unteach.
Five things are available, and between them they’ll carry you through six weeks.
Something you noticed. A change in their sector, a rule that lands in April, a competitor doing the thing you proposed, a piece of research that bears on the question they asked. Send it with two lines of your own view and no ask attached. It’s the most reliable way to stay in front of somebody, and it works because it arrives as a gift.
A narrowing. Reading it again, I think phase one on its own would answer the question you actually asked, and that is a third of the number. It’s the strongest move in the whole subject, and hardly anybody makes it, because it feels like a retreat. It’s an advance. It changes the decision instead of repeating it, and a smaller decision can be taken by fewer people, which is usually what’s in the way.
An answer to the objection you can guess. You know what the doubt is. It’s the price, the timing, or whether an outsider can understand their business fast enough to be useful. Pick the one you’d bet on and answer it in a paragraph. Leave the word objection out of it.
A person. The offer of a client who has done something similar and will take a call. It’s stronger than any document, and unusual enough to be remembered.
A real constraint, stated once, if you actually have one. If somebody else is genuinely asking about your November, saying so is a fact about your business rather than a threat. Where that’s true, say it once. Where it isn’t, leave it alone. Manufactured scarcity is the thing this guide opened by warning about, and the difference between the honest version and the invented one is visible to the reader more often than writers believe.
One idea per message. Keep it short. Leave out the summary of everything you’ve already sent.
When the silence is the number
A good share of quiet proposals are quiet about price, and the timing is the tell. The conversation was warm right up to the moment a figure existed, and then it stopped. Or they asked earlier about phasing, or about what could be done for less, and you answered it lightly.
The reflex is to cut the price in the follow-up, unprompted. Hold the number. An unrequested discount tells the client the first figure was decorative, and a client who knows one number was decorative will read the dates and the scope the same way. The move is one-way, too. You’ve changed what your work costs at this client for good, in exchange for a message that may have had nothing to do with price.
Change what’s in the box instead. A shorter first phase. A longer timeline with less of your time in it. One person instead of two. A version where their team does the data gathering and you do the analysis. Same rate, less of it. That protects the price and gives them a yes they can afford to take.
Raising the subject is easier than it looks, because you can put the choice on the scope. Of the three parts in there, which one would you most want done first. Somebody can answer that with no admission attached, and the answer tells you both what they value and roughly what they have.
Sometimes the honest end of this is that you’re out of their range. That’s a fine outcome, and week two is a far better place to reach it than week ten. Say so plainly, and they can stop feeling awkward. What to do when extra work arrives after you’ve started, and how to price a change rather than refuse it, is a different conversation and this collection handles it elsewhere.
The half page your contact can forward
Your proposal is a document. The decision, if it happens, gets taken in a five minute agenda item or a two line message in a chat window, by people who have read none of it. What decides those conversations is what your contact is able to say, and you can write that for them.
Send four sentences, clearly marked as something to pass on. What the work is, what it costs, what it changes, when it could start. Plain words, no preamble, ready to paste as written. A contact who can forward you as-is will forward you. One who has to rewrite you does it once.
Then give them the two answers they’ll be asked for. Why you rather than the cheaper option, in one sentence about the outcome instead of your credentials. And what happens if it goes wrong, which is the question every finance person asks and every proposal ignores. Your contact will face both in a room you’re not in, and arriving with the answers is the most useful thing you can do for somebody spending their own standing on you.
Writing so a document survives a forward on its own is a separate skill, and the status update piece in this collection sets it out properly. The point here is narrower. Make the proposal forwardable, then supply the thing that actually gets forwarded.
The date they gave you that has passed
We should have a decision by the end of the month. It’s now the fourth, and the thread is quiet.
That passed date is the best material you’ll ever have, because it’s theirs. You’re noticing a date they set for themselves. You mentioned you were hoping to have decided by the end of March. Has that moved, or is it still roughly the plan. One line answers it, it carries no accusation, and every possible answer is useful to you.
Dates set inside organizations slip as a matter of routine, and a slip says almost nothing about your chances. A committee moved, somebody was ill, a bigger thing landed. Treat the first slip as weather.
A second self-set date passing is real information. It says the decision is being left rather than taken slowly, and patience has run its course. That’s the point where the closing message below turns from a defeat into the most efficient thing available.
How many, and how far apart
The honest short answer is four to six messages across six to eight weeks. For a serious piece of work, that’s a normal pace. Spacing and content matter far more than the count.
Widen the gaps as you go. Three or four days to the first, a week to the second, two weeks to the third, three or four weeks after that. Widening gaps read as a person with other work. Narrowing gaps read as somebody watching their inbox, and readers hear the difference long before they could name it.
Keep a week between messages, and give each one something to carry. When the only reason for writing is that the last one went unanswered, wait.
And stop counting messages. Count the ones that carried something. Three with content in them beat eight empty ones. The real stopping condition is the moment your next idea would repeat an earlier one. When you reach it, close the thing rather than filling the gap.
Ending it in a way you can come back from
Past the fourth message, what you’re short of is a reply of any sort. The quickest way to one is to let the proposal go.
I am going to take this off my list for now and assume the timing was not right. If it comes round again I would be glad to look at it.
Two lines, warm, no edge. They work because declining is free and far easier than deciding. They work again because a person who’s been quiet out of embarrassment now has a way to say something true. A useful share of the time you get the yes. The rest of the time you get the truth, and the truth is worth having. A proposal you’ve genuinely let go of is capacity you can sell to somebody else. One you’re still half expecting is capacity you’re quietly wasting.
Once you’ve released it, and only then, ask the question that this moment alone makes available. If you did go another way, I would find it genuinely useful to know what tipped it. People answer that far more often than they answer a request for an update. It’s free to them, being asked is flattering, and the awkwardness has already gone. What comes back is worth more than the proposal was. Asked while you’re still trying to win, the same question reads as one more attempt, which is why the order matters.
Then treat the exit as an asset rather than a courtesy. The person who passed on you will be asked for a recommendation by somebody else within the year, and will change jobs inside three, taking their shortlist with them. Firms that lose gracefully get invited back and get named to other people. Firms that go silent, or that let a trace of injury into the last message, drop off the list. This is the part of the process with the longest tail and the least effort in it.
When it is not an email at all
Two cases where another message is the wrong instrument.
If the work is large and the relationship is warm, the follow-up is a phone call and the email is the record of it. A call gets you the sentence that begins the truth is, which an email will rarely produce. Call first, then write down what was said the same day.
If the introduction came through somebody, the follow-up may belong to them. A single line to the person who introduced you, asking whether they have any read on where it has gotten to, is faster and less awkward than a fourth message to the client. It costs the client nothing.
What Point can do here
All the judgment above stays yours. What a message should carry, whether to narrow the scope, whether the silence is about money, whether to walk away: that’s the work itself, and a mail client holds no opinion about any of it. What a tool settles is whether the thread reaches you on the day it should, and what you know by the time it does.
The first problem is that a sent proposal is an absence. The thing you’re waiting for has yet to arrive, so your inbox stays quiet about it. Your own list stays quiet too, because the next move is theirs. The only trace is a message you sent, sitting in the one folder nobody opens, plus a fact you carry around with you. That’s why proposals go quiet for five weeks and then occur to you in a parking lot. In Point, the commitment you made in the covering email becomes a dated item rather than a thing you hope to remember, and a thread nobody answered comes back to you on the date you chose rather than when it crosses your mind. The same mechanism holds the whole set, so an open proposal comes back on its date even when it’s far from the one you thought of this week.
The return is informed, too. The worst follow-up in this whole guide is the one sent to somebody who replied on Tuesday. Point notices when a thread has already moved, so a reminder that has been overtaken stays out of your way.
The second problem is knowing what to carry. Before the fourth message you want the actual words your contact used about timing and about budget. They’re somewhere in a chain of eleven messages and two forwards. Reading a long chain at the position it has reached takes a couple of minutes rather than twenty, and what you’re after is usually a half sentence somebody wrote in passing. For the material that lives outside the mailbox, a watch stated in ordinary words, such as tell me if anything is published about that company, works on things outside the inbox as well as inside it. That’s a reasonable way to have something worth sending in three weeks. You can also ask to be told the moment anyone at that domain writes, so a reply that lands while you’re in a meeting is waiting for you the moment you’re out.
Drafting is available, and it comes with one caution. Point writes from scratch as well as replying, and picks up your own patterns, so a rough note comes back as something to edit. The caution is specific to this subject. A model asked to follow up on a proposal will produce, with great fluency, precisely the just circling back email that the first section of this guide is about. The reason a message exists has to come from you. The sentences are the cheap part.
Three limits belong here rather than in a footnote. Point is a mail client, and a mail client holds no pipeline, no values, no probabilities and no win rate. If what you want is nine open proposals with numbers against them, that’s a CRM, and buying one is a fair call. Point stays quiet on whether your proposal was opened, because a mail client has no way to know; document tools report that and are their own category. And a sent message can’t be recalled off somebody else’s server, whatever any product says. Point keeps a timestamped record of everything it did, and most entries in it can be put back. A delivered message is one of the exceptions.
Each kind of action has its own place on the autonomy dial, and every one of them starts at review. A follow-up to a prospect is a good candidate for leaving on the cautious end permanently, however far you raise the rest. It’s a commercial message to somebody who has yet to sign anything, and a wrong one stays sent. What that dial actually controls is worth ten minutes before you change anything. And if the alternative you were weighing is pasting a client’s material into whichever chat window is open, the questions to put to a vendor first are worth settling before the habit forms.
Your mailbox stays put. Point works on top of your existing Google or Microsoft account, and the client you’re chasing goes on writing to the same address. Every capability is listed on benefits, the argument for a practice is on Point for consultants, and the product itself is here.
Common questions
How long should I wait before following up on a proposal?
Long enough for it to be read once and mentioned to one other person. That’s three or four working days for a small piece of work with a single decision-maker, and a week to ten days for anything that has to be discussed internally. Following up sooner asks for a reaction rather than a decision, and it tells the reader you’ve been thinking about this far more than they have. If you named a date in the covering email, use that date. A kept appointment reads as courtesy, and it’s the cheapest permission you’ll ever get.
How many times should I follow up before giving up?
Four to six messages over six to eight weeks is normal for a serious piece of work. Space them with widening gaps. Three or four days, then a week, then two weeks, then three or four weeks. A widening sequence reads as a person with other clients, and a narrowing one reads as anxiety. Content matters much more than the number. Three messages that each carry something beat eight that ask for an update. Stop at the point where your next idea would repeat an earlier one, and close it rather than filling the gap.
What do I actually say so it does not sound pushy?
Give the message a reason to exist beyond your wish for an answer. Something you noticed in their sector, a smaller version of the work, an answer to the objection you can guess, the offer of a client who will take their call. Three constructions do the damage: a question only news can answer, an observation about their silence, and urgency you invented. Cut just circling back, and cut any sentence starting with just, since the word apologizes for the message existing. One idea per message, five or six lines, and leave out the summary of what you’ve already sent.
Should I lower my price if they have gone quiet?
Hold the number unless they raise it themselves. An unrequested discount tells the client the first figure was decorative, and a client who knows one number was decorative will read the dates and the scope the same way. The move is one-way with this client, too. Change what’s in the box instead. A shorter first phase. A longer timeline. One person instead of two. Or a version where their team does the gathering and you do the analysis. Same rate, less of it. To find out whether money is really the obstacle, ask which of the parts they’d most want done first. That’s answerable with no admission attached.
They said they would decide by a date and it has passed. What now?
Use the date, because it’s theirs, and referring to a date somebody set for themselves reads as attention rather than complaint. You mentioned you were hoping to decide by the end of March, has that moved, is one line, answerable in one line, and every answer is useful. Treat a first slip as weather, since internal dates move for reasons of their own. A second self-set date passing is real information. It means the decision is being left rather than taken slowly, and at that point the message that offers to close the file will get you an answer faster than more patience.
Does no reply mean no?
Usually it means no decision rather than no, at least for the first few weeks. An unowned proposal sitting on nobody’s agenda is the default state, and it holds until something pushes. It can also be a no that somebody is finding hard to write, which is common, and which is exactly why the closing message earns its place. Saying you’ll file it away gets you a reply most of the time, occasionally a yes, and hands a quiet client an easy way to say something true. Take the answer well either way. A clear no is worth far more than a maybe, because it gives you back capacity you can sell.
The short version
A follow-up reads as pushy when its only reason to exist is wanting an answer, and that’s a content problem rather than a frequency one. The cheapest fix is to name the next contact and its date in the email that carries the proposal, which turns every later message into a kept appointment. After that, wait three or four days for simple work, and a week to ten days for anything that has to be discussed. Make the first message one that somebody with no news can answer: confirm it arrived, and offer twenty minutes to walk through it. Every message after that carries something the last one lacked. Five things are available. Something you noticed. A narrowing of the scope. An answer to the objection you can guess. The offer of a person to talk to. And a real constraint, if you genuinely have one. If the silence is about money, hold the price and change what’s in the box. Give your contact four sentences they can paste into an internal message, plus the answers to why you and what if it goes wrong, because the decision happens in a room you’re not in. Space four to six messages across six to eight weeks with widening gaps. When you run out of things to say, close it warmly. Then ask what tipped it. That question is only available after you’ve let go, and the answer is worth more than the proposal was. The inquiry that started it, the scoping call that went cold, the recap after the meeting and the scope conversation once the work begins are each taken separately elsewhere in this collection.