Lost-for-product Agent
Separate the deals genuinely lost because a capability was missing from the ones merely marked as product, and give Product the buyer evidence and deal value behind each gap.
- Trigger: a deal is marked lost on product
- AI steps: test the stated reason, then name the specific missing capability
- Output: a gap report for Product with buyer evidence and associated deal value
Agent breakdown
A blueprint to adapt, not a fixed recipe. Set the trigger, thresholds, and methodology that fit your team, and each step builds on the last, using the conversation and CRM context you already capture.
Run when a deal is lost on product
The agent runs when a deal is marked as lost on product. Because product can be the easiest reason to select, the stated reason starts the review rather than deciding its outcome.
- Trigger: An opportunity is marked as lost on product
- Entry point: The stated lost reason
Pull the stated reason and deal value
Next, the agent pulls the stated lost reason and the value of the opportunity. This keeps the original claim attached to the deal while the following steps check whether the buyer conversations support it.
- Field: Stated lost reason
- Field: Deal value
Pull the conversations from the whole deal
The agent then pulls the calls and transcripts from the whole deal. Looking beyond the final conversation matters because a buyer may have raised price or another concern earlier, even if the deal was later marked as lost on product.
- Include: Every recorded buyer call linked to the opportunity
- Coverage: The full deal, not only the final calls
Test whether the deal was really lost on product
Using the full conversation history, the agent checks whether a missing capability genuinely caused the loss. It quotes the moment that supports the conclusion and says plainly when the buyer evidence points to another reason.
Decide whether this opportunity was genuinely lost because a capability was missing.
Input: the stated lost reason, the deal value, and the calls and transcripts from the whole deal.
- Review the full deal history, not only the final conversation.
- Identify the reason the buyer gave for not proceeding.
- Decide whether a missing capability was the reason the deal was lost.
- Quote the moment in the buyer conversation that supports your conclusion.
- If the deal was not lost because of a missing capability, say so plainly and state the reason supported by the buyer evidence.
Rules: treat the stated lost reason as a claim to check, not as evidence. Use only what the buyer said in the calls and transcripts. Do not infer a product loss when the buyer did not connect the missing capability to their decision.
Return the determination, the reason for it, and the supporting buyer quote.
Name the specific capability that was missing
For each deal confirmed as lost on product, the agent names the specific capability the buyer needed. It uses the buyer’s own words instead of translating the request into a broad product area.
Name the specific capability that was missing for each deal confirmed as lost because of product.
Input: the conclusion and buyer evidence from the previous step, together with the calls and transcripts from the deal.
- Describe the specific thing the buyer said they needed.
- Use the buyer’s wording wherever possible.
- Keep the capability specific rather than naming a broad product area.
- Include the buyer quote that supports the capability name.
Rules: do not broaden, reinterpret, or combine the buyer’s request with other product gaps. Do not name a capability that the buyer did not describe.
Return the specific missing capability in the buyer’s words and the supporting quote.
Create the product gap report
Finally, the agent creates a gap report for Product. It brings together the confirmed product losses, the specific capabilities buyers said were missing, the supporting evidence, and the associated deal value.
- Creates: A gap report of confirmed product losses and missing capabilities
- Includes: Stated lost reason, buyer evidence, and associated deal value
- Recipient: Product
Confirmed product losses, missing capabilities, buyer evidence, and deal value in a gap report for Product
See which deals were genuinely lost because a capability was missing, what each buyer asked for, and how much the opportunity was worth. Each entry keeps the original lost reason alongside the conclusion and supporting quote, so Product can review the gap with the buyer evidence attached.
- For Product: Review the specific capabilities behind confirmed product losses and the associated deal value.
AI Agents that pair well
Same data, different jobs. Run them together for a fuller picture.
Learn more about GTM & Revenue Operations
RevOps Lab Podcast
50+ Free GTM & RevOps Cheat Sheets
Free RevOps Community (1k+ members)
.webp)