The Follow Up Message That Does Not Feel Desperate

by Eric Hanson, Backend Developer at Clean Systems Consulting

The difference between a follow-up that works and one that damages your position is tone, timing, and whether you are adding something or just asking for something.

The Follow-Up Problem

Every contractor has had the experience of sending a proposal or ending a conversation, hearing nothing for a week, and sitting with the uncomfortable question: do I follow up? How? When?

The discomfort comes from a real tension. Following up too soon or too often reads as desperate and puts pressure on a potential client in a way that feels uncomfortable. Not following up at all means opportunities slip through that might have converted with one more prompt.

The goal is a follow-up that moves the conversation without making the recipient feel chased.

The Tone That Signals Position

Desperate follow-ups have a recognizable signature: they over-explain, over-apologize for reaching out, or make the reader aware of the sender's anxiety about not hearing back.

"Hi again — just wanted to follow up on my proposal from last week. I know you're busy but I just wanted to make sure you received it and see if you have any thoughts?"

This sentence is three qualifications deep before it gets to a point. It signals uncertainty. The reader picks up on that energy and, often, it lowers their confidence in the contractor.

A follow-up that does not signal desperation is direct and adds something:

"Following up on the proposal. I also had a thought on your timeline question — if it helps, we could structure the first phase around the authentication system and defer the reporting dashboard to reduce pressure on the initial launch. Happy to jump on a call if you want to talk through it."

That message moves the conversation forward. It adds a thought that shows continued engagement with the client's problem. It is confident without being pushy.

The Timing

The right window for a first follow-up is typically three to five business days after sending a proposal, unless you agreed on a different timeline in the conversation. Earlier than that and it reads as impatient. Later and the conversation may have already mentally closed.

For a second follow-up after no response: seven to ten days after the first. Brief, direct, acknowledging that you have not heard back:

"One more check-in — happy to chat if the timing or scope needs adjusting."

Two follow-ups without response is usually the limit before you have your answer. A third message in the same cycle crosses from professional to persistent in a way that rarely produces a positive outcome.

Adding Something vs Just Checking In

The quality of a follow-up often comes down to whether it is adding something or just asking for something.

"Any update?" adds nothing. It asks the potential client to do work (update you) without offering anything in return.

A follow-up that adds something might include:

  • A thought about the project that emerged since the conversation.
  • A relevant article or resource you came across.
  • A specific offer to make the next step easier — "I can send over a revised scope if that would help move things forward."

This is not about dressing up a sales message. It is about making the follow-up a genuine contribution to the conversation rather than a status request.

When No Response Is an Answer

Not every non-response is an opportunity waiting to be unlocked. Sometimes silence means the client has made a different decision and does not want to have the conversation about it.

After two professional follow-ups with no response, the most useful thing you can do is close the loop yourself:

"I'll take the silence as a sign this isn't the right time. If circumstances change and you'd like to revisit, I'm easy to reach. Good luck with the project."

This is confident, closes cleanly, and occasionally produces a response — because the act of closing the loop triggers the client to respond. It is the lowest-pressure version of a follow-up: it does not ask for anything, and it is clearly the last message.

A good follow-up does not beg for attention — it earns it by adding something worth noticing.

Scale Your Backend - Need an Experienced Backend Developer?

We provide backend engineers who join your team as contractors to help build, improve, and scale your backend systems.

We focus on clean backend design, clear documentation, and systems that remain reliable as products grow. Our goal is to strengthen your team and deliver backend systems that are easy to operate and maintain.

We work from our own development environments and support teams across US, EU, and APAC timezones. Our workflow emphasizes documentation and asynchronous collaboration to keep development efficient and focused.

  • Production Backend Experience. Experience building and maintaining backend systems, APIs, and databases used in production.
  • Scalable Architecture. Design backend systems that stay reliable as your product and traffic grow.
  • Contractor Friendly. Flexible engagement for short projects, long-term support, or extra help during releases.
  • Focus on Backend Reliability. Improve API performance, database stability, and overall backend reliability.
  • Documentation-Driven Development. Development guided by clear documentation so teams stay aligned and work efficiently.
  • Domain-Driven Design. Design backend systems around real business processes and product needs.

Tell us about your project

Our offices

  • Copenhagen
    1 Carlsberg Gate
    1260, København, Denmark
  • Magelang
    12 Jalan Bligo
    56485, Magelang, Indonesia

More articles

Why Your Commit History Tells More About You Than Your Code Does

Your code shows what you built. Your commit history shows how you think — whether you work in logical units, whether you communicate intent, and whether you consider the people who come after you.

Read more

Charging What You Are Worth Is Hard Until You Understand What You Are Actually Selling

Contractors who struggle to charge high rates are usually selling the wrong thing. The shift from selling time to selling outcomes changes everything about the pricing conversation.

Read more

Virtual Threads in Java — What Changes, What Doesn't, and How to Migrate

Virtual threads are production-ready in Java 21 and change the scalability profile of I/O-bound Java services without requiring reactive programming. Here is the precise model, the traps, and a migration checklist.

Read more

The Client Who Seems Difficult Is Often Just Unclear. Here Is How to Handle It.

Most contractor-client friction is not a personality problem — it is an information problem. Understanding that changes how you respond to it.

Read more