Proposal Engagement Triage (QA)

Proposal Engagement Triage (QA)

1. 01

   Set the engagement baseline before any proposal leaves the building

   Record what a normal open-to-sign window looks like for each retainer tier so later anomalies have something to be measured against.

2. 02

   Pull page-level dwell time for every proposal sent in the last 14 days

   Qwilr and Proposify both expose per-page view duration; export it into one sheet rather than reading it inside each vendor dashboard.

3. 03

   Flag any proposal where the pricing page was viewed twice or more without a signature

   Repeat pricing views are the strongest single signal that a scope or tier question is unresolved, and they decay fast.

4. 04

   Check whether the buyer forwarded the document to an address outside the known client domain

   A second domain usually means procurement or a finance approver entered the thread, which changes who the follow-up should address.

5. 05

   Route flagged proposals to the account lead within 24 hours with a specific question, not a nudge

   Replace 'just checking in' with the exact clause or line item the engagement data suggests is stuck.

6. 06

   Log the outcome of each triage in the CRM against the deal record

   PandaDoc and Better Proposals sync status back to HubSpot and Salesforce; capture the human reason alongside the automated status so pattern analysis stays possible.

7. 07

   Review the triage log monthly and retire templates that consistently stall on the same page

   A template that loses buyers at the same section is a content problem, not a follow-up problem.