# convrgent.ai Win/Loss Deal Analysis

> convrgent.ai Win/Loss Deal Analysis is a paid API for AI agents from convrgent.ai, paid per call via x402, $2/call, status unknown (last checked 2026-09-15).

Analyzes a completed sales deal retrospectively to identify turning points, personality fit score, and reengagement strategy based on buyer personality type.

## Facts

- Endpoint: POST https://convrgent.ai/api/kyb/winloss
- Price: $2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/convrgent-ai-dee77e27
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LyVpdH-CdvmCTg3xDiH7c

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability convrgent-ai-dee77e27 -d '<json body>'
```

Example prompt: Run a win/loss post-mortem on the deal I just lost with Marcus Chen — he came across as highly analytical and skeptical, we used a narrative-heavy pitch and he ghosted after the pricing call. What were the turning points, how well did our approach fit his personality, and how should we reengage him?

## When to prefer this

Choose this endpoint after a deal has concluded (won or lost) when you need a structured retrospective that combines personality psychology with sales outcome analysis. Particularly valuable when you want to understand the mismatch between sales approach and buyer personality, identify specific conversation turning points, and generate a data-driven reengagement strategy — rather than just a generic deal review.

## Known failure modes

- Insufficient conversation history or deal context provided — returns incomplete or low-confidence analysis
- Missing buyer personality signals — personality fit score degraded or unavailable
- Invalid or malformed request body — 400 error
- Payment not included or insufficient — 402 payment required
- Service unavailable or timeout — 5xx error

## How this service works

Win/Loss Deal Analysis — post-deal retrospective analyzing what worked, what failed, and lessons for this buyer personality type. Returns turning points, personality fit score, and reengagement strategy.

## Output

Returns a structured retrospective including identified turning points in the deal, a personality fit score quantifying how well the sales approach matched the buyer's behavioral profile, lessons learned specific to this buyer type, and a tailored reengagement strategy for future outreach.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "bodyType",
    "body",
    "method"
   ],
   "properties": {
    "body": {
     "required": [
      "product",
      "outcome",
      "conversation_summary"
     ],
     "properties": {
      "outcome": {
       "enum": [
        "won",
        "lost",
        "stalled"
       ],
       "type": "string"
      },
      "product": {
       "type": "string",
       "description": "Description of what you were selling"
      },
      "deal_value": {
       "type": "number"
      },
      "key_moments": {
       "type": "array",
       "items": {
        "type": "string"
       }
      },
      "kyh_profile": {
       "type": "object",
       "description": "Full KYH personality portrait"
      },
      "partial_data": {
       "type": "object",
       "description": "Partial personality data"
      },
      "sales_cycle_days": {
       "type": "number"
      },
      "buyer_description": {
       "type": "string",
       "description": "Text description of the buyer"
      },
      "competitor_lost_to": {
       "type": "string"
      },
      "conversation_summary": {
       "type": "string",
       "description": "Overview of the sales interaction"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "mode": "inferred",
  "analysis": {
   "what_failed": [
    "Didn't address CTO security concerns proactively"
   ],
   "what_worked": [
    "Strong initial demo resonated with VP Sales"
   ],
   "missed_opportunities": [
    "Could have provided SOC 2 report before CTO review"
   ]
  },
  "turning_points": [
   {
    "impact": "negative",
    "lesson": "Address technical stakeholders' concerns before they become deal blockers",
    "moment": "CTO security review at week 3"
   }
  ],
  "personality_fit": {
   "score": 0.45,
   "assessment": "Approach was optimized for the VP (driver type) but missed the CTO's analytical decision style"
  },
  "reengagement_strategy": "Wait 6 weeks, re-approach with completed SOC 2 report and security architecture walkthrough",
  "recommended_adjustments": [
   "Lead with security documentation for analytical buyers",
   "Map the full committee before demo stage"
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/convrgent-ai-dee77e27/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from convrgent.ai](https://www.zero.xyz/host/convrgent.ai/llms.txt)