Activity is context, not a promise
A proposal view tells you that a document was opened. Time spent on a section, return visits or a PDF download may help you understand how the proposal is being reviewed, but they do not prove purchase intent. A shared link, a background tab or a download for a colleague can produce activity without a buying decision.
Review the sequence
Look at the proposal as a whole. Did the visitor reach the scope and budget? Did they return to the schedule? Was there a comment, form submission or explicit acceptance? Direct actions usually provide more useful context than a single duration metric.
Prepare a specific question
Use the information to make your follow-up relevant. If the schedule needs clarification, ask whether the proposed milestones fit the client's constraints. If scope questions remain unresolved, offer to review the deliverables. Avoid claiming to know why someone stayed on a particular section.
Respect consent and access
Analytics is optional for recipients. In Mideo, declining analytics does not prevent essential actions such as reviewing a proposal or submitting a response. Missing analytics can therefore reflect a consent choice rather than a lack of interest. A password-protected proposal should remain protected when translated or exported.
Treat AI insights as assistance
AI can summarize the activity supplied to it and suggest a follow-up. Check the underlying data, distinguish observations from interpretations and use your knowledge of the client. An unavailable or failed analysis is not evidence of low engagement and should never be presented as a successful recommendation.