HTMLRadar · Use case
Know the moment your proposal gets read.
You sent the proposal Tuesday. It's Friday. Do you follow up — or is that pushy? Proposal tracking replaces that guess with a fact: the client opened it Thursday at 4pm, spent four minutes on scope, and parked on the pricing section twice. Follow up Friday morning. That's not pushy; that's well-timed.
One proposal, one link per client
Upload the proposal once, then create a separate tracked link per recipient — the client, their finance lead, the partner who actually decides. Each link has its own gate: require an email, set a password, restrict to their company's email domain, or set an expiry. When the engagement closes (or goes cold), revoke the link and the document goes dark.
See which sections did the selling
Reads are measured per section — scope, timeline, team, pricing — with a three-second floor so a scroll-past doesn't count. You'll know if pricing got thirty seconds or five minutes, whether the case studies were read at all, and who inside the client's team the link was forwarded to. An email lands on the first real read, so the follow-up window never slips past you.
The SOW and the spreadsheet travel with it
Attach the contract PDF, the pricing model, the reference deck — recipients get them in a quiet corner drawer on the proposal itself, and every download is logged per viewer. Revise the proposal after a call and replace the file: the links you already sent serve the new version automatically.
Why HTML proposals?
Because that's what your tools produce now. Proposals drafted with Claude or ChatGPT, formatted as clean HTML pages, read beautifully on the client's phone — where a wide PDF makes them pinch and zoom. If you still need a file for procurement, attach the PDF; the tracked link stays the front door.
Common questions
- Will the client know the proposal is tracked?
- Free-tier links carry a small "Powered by HTMLRadar" badge; the proposal itself is untouched. The tracking is read analytics only — section dwell, scroll depth, active time. No mouse tracking, no keystrokes, no session replay, and recipients can opt out.
- Can I stop a proposal from being shared around?
- Per-link gates help: require the recipient’s email, allow-list their domain, or password the link. If it leaks anyway, you see every viewer and can revoke the link in one click — it stops working immediately.
- What happens when I update the proposal after feedback?
- Replace the file. Every link you already sent serves the new version on next open, and version history keeps a record of what changed and when.
- Do I need the client to sign in or install anything?
- No. The link opens in any browser. At most, the client types their email if you gated the link that way.
First 2 tracked links free. No credit card. AGPLv3 source on GitHub.