Writing Follow-Up Emails After a Proposal: When Clients Go Silent or Push Back on Price

You send a proposal. Days pass. Nothing. Or the client responds with "Can you do this for less?" or "We need it done in half the time." Your follow-up email often decides whether you keep the deal, lose it, or renegotiate on bad terms.

Follow-up emails fail for one reason: they either sound desperate or defensive. You either back down on price and scope, or you come across as annoyed. Neither closes deals at the rate you quoted.

This guide covers how to write three types of follow-up: the silence-break, the price-objection response, and the timeline-pushback reply. Each has a clear structure, a common mistake to avoid, and a way to check your work before hitting send.

The Silence-Break Email (5–7 Days After Sending)

A client who doesn't respond in the first week is either busy, undecided, or your proposal landed in spam. Assume nothing. Your job is to assume they're interested but distracted, and to make a response easy without sounding impatient.

Structure:

• One-line subject: "[Project name] proposal – quick check-in"
• Open with something specific from your earlier conversation: "When we talked about the API integration, you mentioned needing it live by Q3."
• Restate one value element from the proposal in plain language (not a price): "The three-stage testing plan I outlined catches edge cases before launch."
• Ask one question that moves the conversation forward: "Do you want me to walk through the timeline, or is there a specific section you'd like to discuss?"
• Close with a clear next step: "I'm free for a 15-minute call Thursday or Friday this week."

Common mistake: Resending the entire proposal as an attachment or repeating the price. Silence means the proposal wasn't the blocker—indecision or competing priorities were. Your follow-up should lower the friction to say yes, not reargue the value.

How to check it: Read the email as if you're the client. Does it sound like you're chasing them, or like you're helping them move forward? If you cringe at the tone, rewrite it.

The Price-Objection Response

A client says: "This is more than we budgeted. Can you do it for $X?" or "Our last developer charged half that." This is the most delicate follow-up because you must defend your rate without sounding inflexible or hurt.

Structure:

• Acknowledge their constraint without apologizing for your price: "I understand budget is a real factor—most teams have guardrails."
• Connect price to a specific scope element they care about: "The $X you're asking would mean dropping the staging environment testing or reducing the API security audit. Which one does your team need least?"
• Offer a single, defensible alternative: "I can scope down to [specific deliverable] and deliver it in [fewer hours] for $Y. That removes [explicit cost driver], but we keep [the part that matters to them]."
• Do not offer a small discount just to close. Discounting without scope change trains clients to always negotiate you down.
• Close with a specific deadline: "Let me know by Friday if the scoped-down version works, otherwise I'll move to my next project."

Common mistake: Offering a 10–15% discount without changing the scope. This signals your original price was padded, and the client will remember it next time. Instead, link the lower price to a smaller deliverable.

How to check it: Can you explain exactly which deliverable or hours you're removing? If you can't, you're just discounting—don't send it.

The Timeline-Pushback Response

Client says: "Can you finish this in 4 weeks instead of 8?" This is a scope negotiation disguised as a schedule question. Rushing without adjusting scope or price ruins your project—and the next one.

Structure:

• State your constraint directly: "The 8-week timeline includes two rounds of client review and a one-week testing buffer for bug fixes. A 4-week compression means one of those goes."
• Offer the tradeoff clearly: "We can compress to 6 weeks if you commit to feedback within 48 hours of each deliverable. Or we stick to 8 weeks with normal review windows."
• Do not add hours to your estimate just to make it fit. You already built in risk buffer; compressing the timeline uses it up.
• Add a financial consequence if appropriate: "If we compress to 4 weeks, the rate is $[higher rate] because it requires parallel work and reduces my buffer for other clients."
• Reframe the tradeoff as their choice: "Both work. Which constraint matters more—delivery speed or staying on budget?"

Common mistake: Saying yes to the shorter timeline and hoping to make up hours later. You won't. You'll either deliver incomplete work or burn yourself out and resent the client.

How to check it: Would you be annoyed to work on this project at the new timeline? If yes, you've already agreed to lose money. Renegotiate now.

Universal Mistakes in Follow-Up Emails

Tone slips. Re-read your email out loud. If it sounds formal, hurt, or sarcastically patient, rewrite it. Neutral and helpful is the target.

Reopening old arguments. Don't rehash why your estimate is right. Clients know it's right—they're signaling a budget or timeline issue. Address the real constraint, not the estimate.

Forgetting the ask. Every follow-up email should end with a specific, time-bound question or action. "Let me know what you think" is not an ask. "Can you confirm by Wednesday?" is.

Sending multiple follow-ups in quick succession. One follow-up per state change. If they don't respond in a week, one more. After that, move on.

Checklist Before You Send

• Does the email reference something specific from our earlier conversation?
• Does it lower friction to respond (or does it add friction)?
• If I'm defending price or timeline, am I linking it to a specific scope element?
• Does it end with a clear ask and a deadline?
• Would I be comfortable if the client forwarded this email to their manager?

When to Stop Following Up

After two follow-ups with no response, stop. After a price objection with no reply to your counter, stop. Clients who go silent after a second touch are either broke, stalled in internal approval, or not seriously interested. Following up a third time wastes your time and damages your reputation as someone who respects boundaries.

Instead, close the door politely: "I'm going to assume this isn't the right timing. Happy to revisit in a few months if circumstances change." This keeps the door open without chasing.

Originally published at Forged Goods. The ready-made version: Freelance Developer Client Scoping & Proposal Prompt Pack.