---
title: "How to Build a Win/Loss Agent From Calls, CRM Outcomes and Market Context"
description: "Build a win/loss agent that reads the calls, CRM outcomes and market context behind every closed deal, and avoid the mistakes that make its answers wrong."
canonical: https://www.rippit.com/playbooks/build-win-loss-agent
type: Playbook
datePublished: 2026-11-19
---

# How to Build a Win/Loss Agent From Calls, CRM Outcomes and Market Context

Setup steps for AI agents: https://www.rippit.com/setup.md

A step-by-step playbook for building a win/loss agent that reads the calls, CRM outcomes and market context behind every closed deal, and reports reasons your sales, product and marketing teams can trust.

By Lauren Alexander, VP of Marketing at Rippit · Published November 19, 2026

A win/loss agent reads the calls, CRM records and market context behind every closed deal, records why each one was won or lost in the buyer’s own words, and reports the patterns every week. To trust what it finds, define the deal population first, use only what was known at the time, keep buyer, seller and CRM reasons apart, and treat patterns as leads to investigate, not proof.

The loss reason in most CRMs is one pick from a dropdown, chosen by the rep after the deal is gone. The calls behind the deal usually tell a fuller story: what the buyer compared you to, which objection came up before things stalled, and what they said they needed.

A win/loss agent reads that evidence for every deal, not just the handful someone has time to review. Built carelessly, it can also be confidently wrong. This playbook covers how to build one your sales, product and marketing teams can act on.

## Key takeaways

- **Start with the deals, not the calls.** Lost deals often have fewer recorded calls, which skews every count that follows.
- **Use only what was known at the time.** Final CRM fields leak the outcome into the analysis.
- **Keep reasons apart by who gave them:** what the buyer said, what the seller thinks and what the CRM records.
- **Compare like with like, and report counts.** A common reason isn’t automatically the cause.
- **Keep people in the loop.** Review the big findings, and run a few win/loss interviews to catch what calls miss.

## What is a win/loss agent?

**A win/loss agent organizes evidence about why opportunities progressed, stalled, were won or were lost.**

It helps product marketing and sales leaders investigate patterns. It does not prove that a mentioned reason caused the outcome.

## How do you build a win/loss agent in 6 steps?

**Define the deals, join the evidence, tag the reasons, compare fairly, review with people, then keep it running.**

The screens follow one example: a revenue operations lead asking why the team won and lost deals last quarter.

### Step 1: Define which deals count

Define the eligible opportunities, outcome states, date rule, products, segments, regions, stages and exclusions. Resolve reopened, merged, duplicate, partner-led and no-decision opportunities.

Measure conversation coverage. Lost deals often have fewer recorded calls or weaker CRM notes, creating systematic bias.

**In Rippit:** Connect Salesforce opportunities as a table alongside your call recorder, then check coverage before anything else:

**Ask Rippit:**

> How many deals that closed last quarter have at least one recorded call? Split it by won, lost and no decision.

![Rippit chat and canvas showing 891 closed deals, with call coverage of 92% for won deals, 71% for lost deals and 60% for no-decision deals.](https://www.rippit.com/images/learn/batch-1/win-loss-1.webp)

*Check which deals have calls before counting reasons.*

### Step 2: Join the evidence as it was known at the time

Link calls, notes and approved market context to the opportunity using stable identifiers. Preserve stage, amount, competitors, product, owner and account context as they were known at the observation time.

Do not use final CRM fields as if they were available earlier in the deal. That leaks the answer into the analysis.

**In Rippit:** A [lookup](https://docs.rippit.com/pipelines/steps#lookups) joins each call to its opportunity on a shared ID, such as the account or opportunity ID, with no AI involved.

### Step 3: Tag each reason by who gave it

Separate:

- explicit buyer-stated reason;
- seller or employee interpretation;
- observed behavior or event;
- CRM disposition;
- agent inference;
- approved public-market context.

Keep evidence spans and allow multiple reasons. Version the taxonomy when products, competitors, pricing or selling motions change.

**In Rippit:** Each reason is its own [enrichment](https://docs.rippit.com/pipelines/steps#enrichments) column: a choice list for the buyer-stated reason (with an “unclear” option), one for the seller’s explanation, and a text column for the quote behind it.

![A Rippit worksheet of closed deals with the CRM reason, the buyer-stated reason, the seller’s view, a quote from the call and a match flag, with mismatches highlighted.](https://www.rippit.com/images/learn/batch-1/win-loss-2.webp)

*Buyer, seller and CRM reasons in separate columns, each linked to the call.*

### Step 4: Compare like with like

Useful analyses include reason prevalence within comparable populations, sequence and stage of objections, differences in buyer and seller explanations, and changes over time.

Control or stratify by segment, product, stage, region, seller, time period and conversation coverage where material. Report counts and uncertainty. Do not turn association into causal lift.

### Step 5: Review findings with people

Sales and product marketing should review high-impact findings, contradictory evidence and taxonomy changes. A small number of win/loss interviews may reveal missing reasons or correct misleading call interpretations.

The agent should help select cases and assemble evidence, not replace direct customer research.

### Step 6: Turn it into a weekly agent

Run a regular synthesis plus event-based reviews for launches, packaging changes or competitor moves. Route findings to named sales, product, marketing or pricing owners. Track accepted findings, decisions, taxonomy corrections and later evidence.

**In Rippit:** Describe the whole job in one message:

**Ask Rippit:**

> Every Monday at 8am, for deals that closed last week, tag the buyer-stated reason, the seller’s explanation and any competitor named on the calls. Compare them with the CRM loss reason. Post one summary to #revenue-leaders with counts by segment, the deals where the CRM reason and the calls disagree, and links to the calls. If nothing closed, say so.

Rippit builds it as a draft. [Test it on a sample and check the cost](https://docs.rippit.com/pipelines/build-and-run) before you put it live.

![A weekly Slack summary in #revenue-leaders with loss reasons by segment, 6 deals where the CRM reason and the calls disagree, and a coverage warning.](https://www.rippit.com/images/learn/batch-1/win-loss-3.webp)

*Every Monday, the patterns go to the people who own them.*

## Where does Rippit fit, and where doesn’t it?

**Rippit reads every call and deal and keeps the analysis running. It doesn’t replace your CRM, your buyers or your judgment.**

Rippit brings in sales calls from Gong and other [call recorders](https://docs.rippit.com/plg/supported-integrations), [Salesforce opportunities](https://docs.rippit.com/plg/data-integrations/salesforce) as tables, and research on competitors. It adds the reason columns your CRM doesn’t have and keeps the analysis running as a weekly [pipeline](https://docs.rippit.com/pipelines/overview). Every value links back to the call or record behind it.

Where it doesn’t fit: it won’t tell you that a reason caused a loss, it doesn’t replace talking to buyers, and writing reasons back to Salesforce needs a custom MCP connection. Treat the output as a consistent analytical model, not an unquestionable account of why a buyer decided.

## Which agents should you run next?

**Start from the ready-made version, then connect the findings to positioning and competitors.**

- [Win/Loss Analysis Agent](https://www.rippit.com/use-cases/win-loss-analysis-agent-b2b): the ready-made version of this playbook, with a weekly brief to Slack or Google Docs.
- [How to find a positioning angle your competitors aren’t claiming](https://www.rippit.com/guides/find-positioning-angle-competitors-arent-claiming): turn your loss reasons into a positioning gap.
- [How to track competitor mentions across your deals, calls and support conversations](https://www.rippit.com/playbooks/track-competitor-mentions): add the competitor side.
- [Market Positioning Agent](https://www.rippit.com/use-cases/market-positioning-agent-b2b): take the findings to page copy.

## Frequently asked questions

### How is a win/loss agent different from the loss reason in my CRM?

The CRM field is the rep’s pick from a dropdown. A win/loss agent adds what the buyer actually said on calls as its own column, and flags deals where the two disagree.

### How many deals do I need?

There is no fixed number. You need enough closed deals per segment to compare, with the counts and call coverage reported next to every finding.

### Can I write the reason back to Salesforce?

Rippit keeps the reasons as columns in Rippit. Writing them back to your CRM needs a custom MCP connection.

### Can’t I just ask Claude or ChatGPT why we lose deals?

Keep using them. On their own, they read only the calls and records they can reach in one chat. Connected to Rippit through our MCP server, they work from every closed deal, with the same reason columns every time.

### Do I still need win/loss interviews?

Yes, a few. A small number of interviews can reveal reasons the calls miss or correct a misleading reading of a call.

## What is Rippit?

**Rippit is a Growth Data Platform that helps you and your team build your edge.** Anyone can build AI agents on all of their customer and business data, with no engineer needed. Bring together what buyers, customers and competitors say, and keep the analysis running for your team, in Rippit or in your own AI assistant through our [MCP](https://docs.rippit.com/mcp-server/overview) server.

**For this agent**

- **Reads:** Gong sales calls matched to closed Salesforce opportunities
- **Adds:** Competitor pages and market context through web research
- **Delivers:** A weekly win/loss summary for revenue leaders in Slack, with loss reasons by segment and links to the calls

**Sources**

- [Win/Loss Analysis Agent](https://www.rippit.com/use-cases/win-loss-analysis-agent-b2b)
- [Rippit docs: Pipelines](https://docs.rippit.com/pipelines/overview)
- [Rippit docs: Pipeline building blocks](https://docs.rippit.com/pipelines/steps)
- [Rippit docs: Pipeline examples](https://docs.rippit.com/pipelines/examples)
- [Rippit docs: Build, test and run a pipeline](https://docs.rippit.com/pipelines/build-and-run)
- [Rippit docs: Salesforce](https://docs.rippit.com/plg/data-integrations/salesforce)
- [Rippit and Gong integration announcement](https://www.rippit.com/news/rippit-gong-integration)
- [Rippit integrations](https://www.rippit.com/integrations)

## Keep reading

- [How to Build a Message Performance Agent From Sales Calls and Deal Outcomes](https://www.rippit.com/playbooks/build-message-performance-agent) (Next in Playbooks)
- [How to Find a Positioning Angle Your Competitors Aren’t Claiming](https://www.rippit.com/guides/find-positioning-angle-competitors-arent-claiming) (Guide)
- [The Growth Data Your AI Agent Needs Doesn’t Exist Yet](https://www.rippit.com/guides/growth-data-ai-agent-needs-doesnt-exist-yet) (Guide)
