Win/Loss-Reason-Tagger-Agent

Stop Losing the Same Deal Twice

Most closed-lost loss-reason fields are useless: a picklist with five options where 80% of deals get marked "price" or "timing." Product teams need a different cut — what specifically about our product caused this loss — and reps don't have time to give it. The Win/Loss Reason Tagger Agent reads the rep's actual closing notes, the loss-recap call transcript, and the recorded objections, and writes a product-relevant tag back to Salesforce on every loss.

How It Works

The agent runs daily over the prior 24 hours of stage-changes-to-closed-lost. For each deal it pulls: the rep's loss-reason notes, the last call transcript before the loss, and any objections logged during the deal. It classifies the loss into one of: missing feature, UX friction, integration gap, performance / scale, security or compliance, pricing, timing, no decision, lost to status quo, or other (with a one-line reason). The product-tag writes to a Salesforce custom field loss_category_product so PMM and product can filter losses by what the team can actually act on.

Required Connections

• Salesforce or HubSpot — opportunity records and loss-reason field
• Demodesk — last-call transcript before the loss
• Slack — weekly summary to product leadership

What Makes It Different

This is per-deal product-category tagging, complementary to win-loss-synthesis-agent (which clusters losses into themes monthly). Together they answer two questions: "why did this deal lose" and "what theme is recurring across losses this quarter."