You sent the proposal three days ago. You check email on your phone at 7am, noon, 3pm, 8pm. Nothing. You have no idea if they opened it, ignored it, or forwarded it to a competitor. You’re flying blind. There’s a better way to work.
Proposal analytics don’t tell you whether someone will say yes. They tell you what’s stopping them from saying yes. That’s a more useful question, and it’s one most freelancers never think to ask because they’ve accepted “sent and waiting” as a normal state.
It isn’t. Every hour you spend in the dark costs you either a deal you didn’t follow up on correctly, or mental energy wasted on a lead that went cold three days ago. Knowing what to do, and when, changes both.
The four signals that matter (and what they tell you)
Not all proposal engagement is equal. These four patterns cover most of what you’ll actually see, and each one calls for a different response.
Opened within 2 hours, 8+ minutes on-page, revisited twice. This is a hot lead. They read it carefully. They came back. That second visit almost always means they’re showing it to someone else internally, a co-founder, a finance lead, a manager who needs to sign off. They aren’t stalling. They’re building internal consensus.
Follow-up within 24 hours of the first open: “I saw you had a chance to review the proposal, happy to answer any questions before you move forward, or jump on a quick call if it helps.” Short. No pressure. Assumes a yes is coming.
Opened once, 60–90 seconds on-page. They skimmed it. Given average reading speeds and a standard proposal length, 90 seconds means one thing: they scrolled directly to price, looked at the number, and closed it. They may not have read a single word of your scope or your case study.
The wrong follow-up here is “do you have any questions?”, they didn’t read enough to have questions. The right move is to reframe before the number has a chance to calcify: “Quick note on the proposal, the $7,500 breaks down to discovery and strategy ($2,200), design ($2,800), and development and launch ($2,500). Happy to walk through what each phase covers if it helps put the number in context.” You’re not lowering the price. You’re showing them the work behind it.
Not opened after 48 hours. Before you assume disinterest, consider the more likely explanation: spam folder. Or a busy inbox. Or a vacation. Or a wrong email address you don’t know about. Non-opens after 48 hours are a delivery problem at least as often as they’re a motivation problem.
Send this: “Wanted to make sure the proposal made it to your inbox, they can get buried in busy weeks. Happy to resend or drop you a direct link if easier.” This message does two things. It gives them a graceful out if the proposal did land and they’ve been avoiding it. And it legitimately rescues deals where there was a delivery issue.
Opened by multiple viewers. Some proposal tools show unique viewer counts or access from different locations. Multiple viewers means you’re in a committee decision. Your contact read it and passed it up the chain, which is exactly what you want. The problem is that the people now reading your proposal weren’t on the discovery call. They don’t have the context your contact has.
Don’t wait for them to come to you. Follow up with your original contact: “I noticed the proposal’s been shared internally, that’s great. If it would help to do a short call with the full team so I can answer questions directly, I’m happy to set one up. Otherwise, I can put together a one-page overview that’s easier to circulate.” Make it easy for your champion to champion you.
The follow-up timing rules that actually work
Generic follow-up advice says “don’t be too pushy.” That’s not useful. Here’s a specific cadence with the reasoning behind each step.
| Timing | Action | Why |
|---|---|---|
| 0–24h after first open | Brief “any questions?” follow-up | Catch them while the proposal is still fresh, this is the moment they’re most likely to respond |
| Day 3, no response | Send a value-add (relevant case study, short insight tied to their project) | Not a nudge, a reason to re-engage without pressure |
| Day 7, no response | One direct ask: “Is this still a priority, or has timing shifted?” | Gives them a clean way to tell you the truth; removes ambiguity from your pipeline |
| Day 14, no response | Release message (see below) | The most counterintuitive and most effective step in the sequence |
The Day 14 release message: “I’m going to assume the timing isn’t right, completely understandable. I’ll close my end of this out, but I’m happy to revisit whenever it makes sense on your side.”
That’s the whole message.
The release message at Day 14 closes more deals than the Day 7 follow-up. It works because it does the one thing every other follow-up avoids: it gives the client permission to say no. And that permission is exactly what a client who wants to say yes, but hasn’t pulled the trigger yet, actually needs. When the pressure disappears, the decision becomes easier.
The other thing the release message does: it clears your pipeline. Proposals that have been sitting in “pending” for two weeks are rarely about to close. Getting a clear answer, even a no, is worth more than false hope you’re checking on every morning.
The aggregate view, using analytics to improve your proposals over time
Most advice on proposal analytics stops at the individual proposal level: what did this client do, and how should I follow up? That’s useful. But the more valuable data lives in patterns across all your proposals, and almost no freelancer looks at it.
Which section kills engagement. If clients who spend less than 30 seconds on a proposal consistently bail at the pricing section, the problem isn’t the price, it’s the value framing that came before the number. Fix the scope section and the results summary, not the price itself.
Average time from send to first open. Proposals opened within 2 hours of sending almost always correspond to discovery calls that went well. The client left the meeting ready to move. Proposals that sit unopened for 48 hours or more tend to correspond to shopping situations, the client is collecting quotes, not selecting a specific vendor. That distinction matters for how you manage the rest of the conversation.
Which proposal structure closes fastest. Fixed-price proposals close faster than time-and-materials proposals, which close faster than open retainer proposals. If your default structure is hourly, this is a data point worth acting on. Clients don’t like approving uncertainty. A fixed price takes that off the table.
The 7-day cliff. Most proposals that are going to close close within 7 days of the send date. Proposals that are still open after 14 days close at a much lower rate. Knowing this doesn’t mean giving up at day 8, it means adjusting your expectations and your tactics. A proposal still open at day 10 needs a different follow-up than a proposal at day 3.
These aggregate patterns take a few months of data to emerge, but once they do, they’re the most actionable numbers in your business. They tell you where to fix the proposal itself, not just how to chase any individual client.
What to do when analytics say the proposal is dead
Unopened after 5 days. Or one quick visit, no return. The data is pointing the same direction. You’re not ready to walk away, but you know the standard follow-up cadence isn’t working. Three options.
Resend with a changed subject line and fresh context. Don’t forward the same email. Start a new thread: “I’ve been thinking about [specific thing they mentioned in the meeting] and wanted to add one thing to the proposal before you look it over.” This gives you a reason to re-engage that isn’t “did you read this yet?” It signals you’ve been thinking about their project specifically, which resets the energy around the proposal.
Propose a smaller starting point. The full proposal may feel too big, too much commitment, too much to approve internally, too many moving parts. Give them a way in that’s lower stakes: “Instead of the full project, what if we started with just the discovery phase? Three days, $1,200. You’d get a complete brief and project plan, and we’d both have a clearer picture of scope before committing to the rest.” A yes to the smaller thing is still a yes. And discovery work almost always converts to the full project.
Walk away cleanly and set a reminder for 30 days. Some proposals die because the timing is genuinely wrong, the client has competing priorities, budget cycles that don’t line up, or internal decisions that haven’t been made yet. None of that is your fault and most of it will resolve on its own. Send the release message, close the file, and put a note in your calendar for 30 days out: “Timing may not be right this month. I’ll check back in Q3, the project and the need will still be there.” The freelancers who do this consistently have a pipeline of warm leads reopening every quarter. The ones who don’t have nothing to show for deals that went cold.
From reactive to informed
The shift proposal analytics creates isn’t just tactical, it changes the fundamental dynamic of the post-proposal phase. Instead of waiting and hoping, you’re reading signals and responding to them. Instead of one generic follow-up sequence, you have four different playbooks depending on what the data shows.
That’s a better position to be in. Not because it guarantees a yes, nothing does, but because you’re asking the right question. Not “will they say yes?” but “what’s in the way of a yes, and can I remove it?”
Most of the time, you can.
Waco3 tracks open time, time spent per section, and revisit count for every proposal you send. The follow-up timing and scripts above are built around exactly those three signals. If you’re sending proposals without any of that visibility, you’re leaving real information on the table.
Related reading: How to Write a Freelance Proposal That Gets Accepted covers the structural framework that generates strong analytics in the first place. How to Follow Up on a Proposal Without Being Annoying goes deeper on tone and timing for the follow-up sequence. When a proposal is opened but the reply never comes, A Client Opened My Proposal but Didn’t Respond decodes the pattern. To compare tools, see The Best Proposal Tracking Software and Best Proposal Analytics Tools.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
