Match a prospect to a reference
Find the best-fit customer proof for a live deal, then request it the right way.
Matching is for the moment you need proof in a real conversation. Give ProvenTen the prospect context you already have — from the CRM or typed in — and review the suggested references before you request anyone.
Run a match
- Open the opportunity in ProvenTen, or start a match from the CRM record if the integration is on.
- Confirm industry, region, deal size, and the problem the prospect cares about. Fix anything the CRM got wrong.
- Review the suggested references. Prefer consented, recent, and not overused advocates.
- Request the reference or pull content-only proof if a live call is not needed.
When the list looks wrong
- Check CRM field mapping — bad industry or region data produces bad matches. See CRM sync.
- Your library may be thin in that segment. Add a reference rather than forcing a poor fit.
- If every deal suggests the same three advocates, talk to an admin about contact caps and library coverage.
Related guides
- Advocates, consent, and permissions
Record who said yes, how they want to help, and when to stop asking.
- References and the proof library
How the library is organised, what belongs in a reference, and how to keep it trustworthy.
- Connect your CRM
Link Salesforce, HubSpot, Dynamics 365, or Pipedrive so matching can use live deal context.
- Sales content and proof in deals
Drop verified quotes, metrics, and stories into decks, proposals, scripts, and RFPs.