Proposal tracking tells you what the client did with the document after you sent it: whether they opened the current version, what they asked, and whether they decided. Proposal analytics is what you do with those events once you have more than a handful of them.
Most freelancers need far less of this than the software category implies. Four signals decide almost every deal. The rest is decoration that makes a dashboard look busy.
What proposal tracking actually records
A tracked proposal produces a small set of events:
| Event | What it tells you |
|---|---|
| First open | The proposal reached a human and the link works |
| Repeat opens | Someone is re-reading, often before an internal conversation |
| New viewer | The document moved to a second person, usually a decision maker |
| Client message | A specific objection you can answer |
| Accept or reject | The decision, with a timestamp and a version attached |
That is the useful list. Time-on-page, scroll depth, and per-section heatmaps sound sharper than they are, because a proposal is short and the reader is not browsing. Someone who spends nine minutes on your pricing page may be doing the maths, or may have walked away from the desk.
The four signals that actually predict a decision
Nobody opened it. After three or four days, silence on an unopened proposal is almost never a rejection. It is a delivery problem. The link went to spam, the contact is on leave, or you sent it to the person who briefed you rather than the person who signs. Chase the delivery, not the decision.
Opened once, then nothing. The most common state and the most misread. One open with no reply usually means the proposal did not answer the question the client actually had. Follow up by adding information rather than asking for a status.
Opened repeatedly, or by new people. This is the strongest buying signal you get. Repeat views mean the proposal is being circulated or defended internally. Your job is to make that internal argument easier, so send the thing that helps them sell it upward.
Opened, then a question. Already the best case. The client is engaged enough to spend effort on you. Answer fast, in the same place as the proposal, so your answer stays attached to the scope it modifies.
See what happens after send
Want to send professional proposals in less time?
Create the proposal in your account, send it to the client, and keep their responses with the proposal.
7 days free. No card required. No automatic charge.
Why email open tracking gets it wrong
Email pixels are the oldest form of this and the least reliable. A tracking pixel fires when an image loads, which means it reports opens that never happened and misses opens that did.
Gmail routes images through a proxy and caches them. Apple Mail Privacy Protection pre-fetches images for every message, so a proposal can register as opened by a client who never looked at it. Corporate gateways scan links and attachments on arrival, which can trip both open and click tracking before the email lands in anyone's inbox. In the other direction, plenty of readers block remote images and stay invisible.
Tracking on a proposal page is more honest because it records a deliberate action. Someone had to follow the link and land on the document. It is still not perfect, but the error rate is much lower than an inbox pixel.
One thing to insist on: your own previews must not count as client activity. If opening your own proposal to check a typo registers as a client view, every number after that is noise.
Version-aware tracking is the part people skip
Tracking that is not tied to a version will eventually lie to you.
You send a proposal. The client opens it. You spot an error in the payment terms and send a corrected file. The activity feed says "viewed twice" and you conclude they are interested. In fact they read the wrong version once and the right version never.
Any record worth keeping should answer three questions together: who acted, when, and which version were they looking at. This matters commercially, because the version the client accepted is the one that describes what you owe them. It is the same reason a clean approval record is worth having if a scope disagreement ever turns serious, which is covered in is a quote legally binding.
What to measure once you have volume
Per-proposal events guide a single deal. Aggregate numbers change how you sell. After roughly thirty proposals, four ratios start to mean something:
- Open rate. Below about 80 percent, you have a delivery or a contact problem, not a sales problem.
- Open-to-response rate. How often a read proposal produces any reply. Low numbers usually mean the document ends without a clear next action.
- Win rate by source. Referrals and cold enquiries almost always convert at different rates. Averaging them hides which channel is worth your time.
- Time to decision. Gives you a real follow-up schedule instead of a guess. If your median accept lands on day six, chasing on day two is noise and chasing on day twenty is too late.
Win rate on its own is the vanity metric here. A 90 percent win rate usually means the prices are too low, not that the proposals are excellent.
Tell clients what you record
Proposal tracking is not covert surveillance, and treating it as a secret is how it becomes a problem. Recording that a business contact opened a document you sent them is ordinary commercial practice, but it is still personal data under the GDPR and similar regimes, so it belongs in your privacy notice with a stated retention period.
There is also a practical argument for being open about it. "I can see the proposal has been opened a few times, so I assume there are questions" is a reasonable thing to say to a client. It only sounds creepy if they had no idea you could tell.
Avoid the trap of quoting your tracking data back at people as pressure. "I noticed you opened this three times yesterday" reads as monitoring. Use the signal to choose your timing, not as evidence in the conversation.
Turning a signal into a message
The point of tracking is a better-timed, better-informed follow-up, not more follow-ups. A rough mapping:
Unopened after 4 days. Reply in the original thread: "Checking this reached you, the proposal link is below. Happy to send a PDF if that is easier for your system."
Opened once, silent for a week. Add something instead of asking for news: "One thing I should have included: here is how the timeline changes if you want the launch before the end of the quarter."
Opened several times, no reply. Offer to help the internal case: "Happy to put together a one-page summary for anyone else who needs to review this, or join a call to answer questions directly."
The follow-up guide covers the wording in more depth. If the answer eventually comes back as no, what to do with a rejected proposal is the other half of the workflow.
Proposa's proposal tracking software records genuine client opens, questions, and decisions against the version the client actually saw, and keeps your own previews out of the numbers.
Built for freelancers
Want to send professional proposals in less time?
Create the proposal in your account, send it to the client, and keep their responses with the proposal.
7 days free. No card required. No automatic charge.