New ResearchCorpBenchSee the results ↗AI models tested on real business tasks.

Sales

On demand

Win/Loss Evidence Synthesis Agent

Learn why buyers choose or leave.

Summarise why recent deals were won or lost and identify lessons for future sales conversations.

Take it into your workspace

Use Win/Loss Evidence Synthesis

Choose where you want to use this blueprint, then copy the prompt to get started.

Choose your agent platform

Use Revensi in ChatGPT

Connect once, then paste your prompt below.

Add to ChatGPT

Personalise with Revensi
Win-loss evidenceIllustrative demo

Summarise what we learned from these closed deals and the buyers' feedback.

  1. Read the request and supporting information

What it does

Turn closed-deal feedback into ideas to test.

Summarise why recent deals were won or lost and identify lessons for future sales conversations. Built for sales enablement and product marketing leads.

  1. Check the closed-deal sample

    Provide closed-deal notes and any feedback received directly from buyers. Buyer interviews and proposal history can add detail beyond CRM reason codes.

  2. Separate reasons from theories

    Group recurring reasons while keeping buyer feedback separate from the sales team's interpretation.

  3. Prepare actionable learning

    Get a summary of patterns, supporting examples and ideas worth testing.

How it works

Summarise why recent deals were won or lost and identify lessons for future sales conversations. Built for sales enablement and product marketing leads.

Agent architectureTools · knowledge · outputs · oversight
Approved documents and context
Separate buyer-confirmed reasons from rep hypotheses and retain conflicting explanations. Count distinct deals with explicit denominators and propose bounded enablement changes rather than broad causal conclusions. Links to the original information and the date it was checked Optional: attributed post-decision buyer interviews and correspondence, to compare stated reasons with internal explanations. Optional: final proposal versions, competitor mentions and deal timelines, to understand the options and conditions at decision time.
Understand recurring reasons behind outcomes
Compare common reasons and examples while keeping buyer feedback distinct from the sales team's interpretation.
Choose improvements worth testing
Review small messaging or process changes tied to the patterns found, giving the team a basis for its next experiments.
Salesforce · Read validated closed-deal outcomes (read)
Define the cohort without mixing open deals.
Google Drive · Read consented deidentified buyer interviews (read)
Separate buyer statements from sales hypotheses.
Google Sheets · Prepare reason-count matrix (draft)
Expose denominators and conflicting evidence.
Human review and permissions
Sales enablement and product marketing leads review the win-loss summary and any unanswered questions. Check that the information is still current before sending a message or changing a record.
  1. 01Gather the context

    Bring together the relevant information from Salesforce, Google Drive, Google Sheets.

  2. 02Check what matters

    Group recurring reasons while keeping buyer feedback separate from the sales team's interpretation.

  3. 03Prepare the result

    Common deal outcomes and reasons, with buyer feedback clearly distinguished from sales opinions. What is ready to use and what still needs checking before taking action.

  4. 04Review proposed changes

    Sales enablement and product marketing leads review the win-loss summary and any unanswered questions. Check that the information is still current before sending a message or changing a record.

Integrations

CRM

Examples:
  • Salesforce
  • HubSpot

Documents

Examples:
  • Google Drive
  • Microsoft OneDrive

Structured records

Examples:
  • Google Sheets
  • Airtable
  • Notion databases

Choose the platforms your team already uses—you don’t need every example shown. Confirm the required features and configure access during implementation.

What you get

Use patterns across won and lost deals to choose more informed changes to your messaging and sales process.

Understand recurring reasons behind outcomes
Compare common reasons and examples while keeping buyer feedback distinct from the sales team's interpretation.
Choose improvements worth testing
Review small messaging or process changes tied to the patterns found, giving the team a basis for its next experiments.

More for sales teams

Start with a blueprint. Build it around your business.

We’ll adapt it to your workflows, connect your systems and build an agent your team can put to work.

30 minutes. One bottleneck. Leave with a clear system concept.