Skip to main content
← All posts
Anderson Goncalves8 min readproposalstrackingclosing

How Do I Know If a Client Read My Proposal?

Five ways to tell whether a client actually opened your proposal, what each one can and cannot prove, and how to read the signal without guessing.

You sent the proposal on Tuesday. It is now Friday. There has been no reply, and you have re-read your own message four times looking for the thing you said wrong.

The honest answer to "did they read it?" is that most freelancers never find out. They guess, and then they act on the guess — usually by waiting too long, and occasionally by sending a follow-up so early it reads as anxious.

This page is about how to actually know, and what each method can genuinely prove.

Why the Question Matters More Than It Sounds

"Did they read it" is really three questions wearing one coat:

  1. Did it arrive? Deliverability, spam folders, a typo'd address.
  2. Did they look at it? Opened, at all, once.
  3. Did they engage with it? Which parts, for how long, and did they come back.

Those are not the same, and the tools that answer the first one are frequently mistaken for tools that answer the third. Most of the frustration around proposal follow-up comes from having an answer to question 1 and making decisions as if it answered question 3.

The reason it matters is timing. A client who opened your proposal twice and spent four minutes on the pricing section is in a completely different state from a client who has not opened it at all — and the correct next message is different in each case. Without the signal, you send the same generic nudge to both, and it works on neither.

A Quick Comparison

MethodProves it arrivedProves a human lookedShows what held attentionSurvives forwarding
AskingOnly if they replyOnly if they replyNon/a
Read receiptsWeaklyNo — declinableNoNo
Tracking pixelsNo — proxies fire itNoNoNo
File-link analyticsYesMostlyPage numbers onlyPartly
Tracked pageYesYes — bots filteredYes, per sectionYes, as a new visit

The rest of this page is what sits behind each row.

Method 1: Just Ask

Free, immediate, and better than its reputation.

"Just checking you got the proposal — happy to walk through any of it." Sent 2–3 days after, it is normal professional behaviour and nobody has ever lost work because of it.

What it proves: whether they will tell you. Some will say "sorry, not yet — this week is mad", which is genuinely useful information.

What it does not prove: anything, if they do not reply. And the non-reply is exactly the case you wanted information about. Asking works well when the relationship is warm and poorly when it is the moment you actually need it.

Method 2: Email Read Receipts

Most mail clients can request one. Outlook has it built in; Gmail has it on Workspace accounts.

What it proves: very little. The recipient is asked whether to send a receipt, and can decline. Many clients silently suppress them. A missing receipt is not evidence of a missing read.

The trap: it also tells the client you are watching, before you have any rapport. A read-receipt request on a first proposal reads as distrust.

Method 3: Email Tracking Pixels

A 1×1 transparent image embedded in the email. When the mail client loads the image, the sender learns the mail was opened.

This is what most "email tracking" browser extensions do, and it is worth understanding why it has become unreliable:

  • Image proxying. Apple Mail Privacy Protection, on by default since 2021, pre-loads images through a proxy — so the pixel fires whether or not a human ever looked. Gmail proxies images too.
  • Images-off clients. Many corporate clients block remote images by default, so a genuine read fires nothing.

The result is a metric that is wrong in both directions: false opens from proxies, and missed opens from blocked images. A tracked email that shows "opened 6 times" may mean a mail server checked it six times.

What it proves: that the message was processed by something. Not that a person read your proposal.

Send the proposal as a link rather than an attachment — Google Drive, Dropbox, DocSend and similar — and the platform records views.

This is a real step up. You are now tracking the document, not the envelope. Link-based document tools generally report opens, and the better ones report time on each page.

What it proves: that the document URL was opened, and often for how long.

The limits: a PDF in a viewer gives you page numbers, not meaning — "page 3 for 40 seconds" only helps if you remember what page 3 was. Downloads usually end the tracking entirely; once it is on their disk, you see nothing. And a forwarded link may report one viewer while three people read it.

Method 5: A Tracked Proposal Page

The proposal is a web page rather than a file. Because it is your page, it can report what a file cannot: which section is on screen, for how long, whether they scrolled back, and whether they returned a day later.

This is the approach ClosingMoment takes, and it is worth being precise about the mechanism rather than hand-waving at "analytics". A small script reports five events: visit start, section enter, section exit, a periodic heartbeat while the page stays open, and visit end. Section timing comes from the enter/exit pairs, so "3 minutes on Pricing" is measured, not inferred from a single ping.

Two details matter for whether you can trust the number:

  • Bot filtering. Link scanners in corporate email open every URL. Visits under three seconds with no section views are flagged as bots and excluded, so an "open" means a human.
  • Your own views do not count. Opening your own proposal to check it fires nothing.

What it proves: that a person opened it, which parts held attention, and whether they came back.

What it still cannot prove: who. If your contact forwards it to a business partner, you see a second visit, not a second name.

What the numbers actually mean

Time-on-section is only useful if you read it correctly, and there are three traps worth naming.

Long is not always good. Four minutes on Pricing usually means serious consideration. Four minutes on Scope can mean it was unclear. The same number means opposite things depending on where it lands, so read section time as attention, not approval.

Short is not always bad. A returning client who already knows how you work may spend ninety seconds and say yes. First-visit duration correlates with unfamiliarity as much as interest.

A single open is weak evidence either way. The signal that has consistently mattered is the second visit. One open is someone triaging their inbox. Two opens, on different days, is someone thinking about it.

The privacy question, since it should be asked

Tracking how someone reads a document you sent them is a reasonable thing to feel uneasy about, and the honest framing is this: you are measuring engagement with your own commercial document, not the person. There is a real line here, and it is worth being deliberate about which side you are on.

What is defensible: knowing your proposal was opened, which sections held attention, and whether someone returned. This is the same category of information a shop gets from a customer lingering at a shelf.

What is not: presenting inferred behaviour back to the client as if you were watching them. "I saw you were on the pricing page for four minutes" is technically true and socially disastrous. Use the signal to decide what to send and when — never as something to quote.

The mechanics should also be honest about their own limits. Section timing measures a section being on screen, not a human reading it; a tab left open is caught by the heartbeat and looks like sustained attention. Treat the numbers as strong hints, not testimony.

What to Do With the Answer

The signal is only worth having if it changes what you send next.

They have not opened it (3+ days). Assume delivery or attention, not rejection. Reply in the existing thread — or on WhatsApp, if that is where the conversation lives — with a fresh link and one line. Do not rewrite the pitch; they have not read the first one.

They opened it once, briefly. They skimmed and parked it. This is the most common state and the one people misread as rejection. A short message naming a specific decision they need to make usually beats a general nudge.

They spent real time on pricing. Price is live in their head. That is not a bad sign — it is the sign that they are considering it seriously. Do not discount preemptively. Address the value at that number, or offer a payment structure.

They came back a second or third time. This is the strongest buying signal you get without a reply. Something is keeping them there and something is stopping them. This is the moment to ask directly what would need to be true to move forward.

They opened it and went quiet for two weeks. Circumstances changed, or the project died. One clean closing message — "assuming the timing is not right, let me know if that changes" — beats five hopeful ones.

The Short Version

Read receipts and tracking pixels answer a question about email infrastructure. Link analytics answer a question about a document. Only a tracked page answers the question you actually asked, which is whether a person engaged with what you wrote and which part of it mattered.

If you take one thing: stop sending proposals as attachments. The attachment is the reason the question is hard. A link is trackable, updatable, and works on a phone — which is where most first reads happen.

See what a tracked proposal looks like — it is a real one, and you can open it without signing up.

If you need the document before you need the tracking, the proposal templates are free to copy with no signup — scope, timeline and client FAQs for web design, consulting, marketing retainers and a dozen other kinds of work.

Send your next proposal as a tracked link — free →

Continue reading