The gap between sending a proposal and hearing back is where most freelancers spiral. Did it land in spam? Did they open it and hate it? Are they comparing you to three other vendors? Without data, every scenario feels equally likely. With tracking, most of the anxiety disappears.
There are three distinct scenarios after you send a proposal. Each requires a different response. The mistake most freelancers make is treating all three scenarios identically, following up with the same “just checking in” email whether the proposal was never opened or opened four times.
The 3 delivery scenarios
Scenario 1: Not opened within 24 hours.
This is almost always a delivery problem, not a disinterest signal. Spam filters, a wrong email address, a client who’s traveling, a day that went sideways, all of these explain a 24-hour silence better than “they looked at it and decided not to respond.”
What to do: Send a delivery check, not a follow-up. “Wanted to make sure this reached you, it can sometimes end up in spam. Happy to resend or share a link if that’s easier.” The framing matters. You’re solving a logistics problem, not chasing a sale.
Scenario 2: Opened briefly, under 2 minutes, then no response.
They looked. They didn’t engage. This is a different signal: something in the opening stopped them. Either the subject line or the opening paragraph didn’t give them a reason to keep reading.
What to do: Follow up with a specific question that pulls them back into the document. Not “did you have a chance to review?” but something like “I wanted to highlight the pricing section, I included two options based on what you mentioned about budget flexibility. Does the breakdown make sense?” Give them something concrete to respond to.
Scenario 3: Opened multiple times, significant reading time, no response.
Multiple opens with no response is one of the clearest buying signals in the proposal process. They’re interested. Something is creating hesitation, budget, internal approval, a competing option. Follow up directly.
What to do: Don’t play it cool. “I noticed you’ve had a chance to look through the proposal, I’d love to hear your thoughts and answer any questions that came up.” Acknowledging that you know they’ve engaged is fine and normal in a tracked proposal context. Then ask: “Is there a section you’d like to talk through before deciding?”
The tools that tell you which scenario you’re in
Proposal software with built-in tracking (Waco3, Better Proposals, PandaDoc) shows you the exact open time and time spent per session. This is the most reliable data. You know within minutes of the client opening whether you’re in scenario 1, 2, or 3.
Gmail read receipts are inconsistent. Most email clients allow recipients to decline read receipts, and many organizations disable them by policy. Treat Gmail read receipt data as suggestive, not definitive.
The delivery check email works when you have no tracking. It produces a response (the client confirming receipt) or a bounce (wrong address) or continued silence (spam filter or genuinely buried). All three tell you something useful.
The delivery check email
When you have no tracking and no response after 24–48 hours, this email handles it:
“Hi [name], wanted to make sure the proposal landed in your inbox. Inboxes get busy and it can sometimes end up in spam. If you’d prefer I send a link instead of an attachment, I’m happy to.”
What makes this work: It’s not “just following up.” It identifies a specific, plausible reason for non-response (spam/buried) and offers a practical alternative (link vs. attachment). The client has an easy action to take, and you’ve moved the conversation forward without creating any pressure.
What to avoid: “I just wanted to check in and see if you’d had a chance to review the proposal I sent.” That sentence puts the full weight of the follow-up on the client’s reading schedule. The delivery check puts it on a logistics problem that you’re both solving together.
When tracking shows it was opened but the client says they didn’t get it
This happens more than you’d expect. The client genuinely doesn’t register a brief mobile open as “receiving the proposal.” Or they don’t recognize the sender name and it didn’t stick.
The right response: “I can see it was delivered on [date], let me forward it again with a clearer subject line so it’s easy to find.” Don’t argue the data. Offer the practical fix. You’re not trying to prove anything; you’re trying to get the proposal read.
If the proposal was opened on desktop for 4 minutes and the client says they “didn’t get it,” something else is happening, they’re hedging, or they need more time and don’t want to say so. In that case, resend with a note: “Sending this again in case the previous one got buried, let me know if you have questions after you’ve had a chance to look.”
The combination of tracking data and thoughtful follow-up removes almost all of the guesswork from the post-send period. You know what happened, you know which scenario you’re in, and you know what the right next step is.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
