Post discusses a new method for calculating churn scores by integrating multiple data sources.

{
  "signal_id": "938cafa9-9f70-43ae-a6e6-839e2fd5b1e5",
  "signal_type": "linkedin-post-company",
  "signal_subtype": "linkedinPost",
  "detected_at": "2026-08-13T10:23:02.67+00:00",
  "company": {
    "name": "ZoomInfo",
    "domain": "zoominfo.com"
  },
  "data": {
    "tags": [
      "Analytics & Insights",
      "Data Management",
      "Sales Operations",
      "Customer Retention & Development",
      "CRM"
    ],
    "summary": "Post discusses a new method for calculating churn scores by integrating multiple data sources.",
    "post_url": "https://www.linkedin.com/posts/zoominfo_most-churn-scores-are-built-by-one-system-activity-7493277393734832128-WJj9",
    "num_likes": 10,
    "post_text": "Most churn scores are built by one system, reading its own data.\n\nThe CS platform sees product usage. The CRM sees the renewal date. Conversation intelligence sees the calls.\n\nEach returns a confident number from a partial view, and none of them is wrong exactly. They are just incomplete.\n\nThe play John Lloyd, MBA walks through on Revenue Architects Episode 6 changes what the score is made of, not how it’s calculated.\n\nOne agent queries all four sources at once through an MCP connection, weighs call sentiment against product usage, renewal proximity and competitive intent, and returns a single 0 to 100 score for every account in the book.\n\nNo new data was bought to make that work. Every input already existed in the stack. What changed is that one question could finally reach all of it.\n\nThen the part that decides whether a score is worth anything: the accounts in the critical tier come back with the outreach already drafted, referencing the specific problem raised on the call.\n\nA score nobody acts on is a report.\n\nJohn Lloyd runs through the full build on Revenue Architects Episode 6. Link in the comments.",
    "initiatives": [
      {
        "topic": "integrating product usage, CRM, and call data",
        "urgency": 0.6
      },
      {
        "topic": "developing a unified churn score",
        "urgency": 0.6
      },
      {
        "topic": "automating outreach based on churn score",
        "urgency": 0.6
      }
    ],
    "pain_points": [
      {
        "topic": "incomplete customer data for churn scores",
        "intensity": 0.75
      },
      {
        "topic": "siloed data systems for customer insights",
        "intensity": 0.6
      },
      {
        "topic": "scores not acted upon leading to inefficiency",
        "intensity": 0.5
      }
    ],
    "posted_date": "2026-08-12T12:09:09.028Z",
    "num_comments": 1,
    "technologies_mentioned": [
      {
        "name": "CS platform",
        "status": "using"
      },
      {
        "name": "CRM",
        "status": "using"
      },
      {
        "name": "MCP connection",
        "status": "integrated"
      }
    ]
  }
}

curl https://signals.autobound.ai/v1/signals/938cafa9-9f70-43ae-a6e6-839e2fd5b1e5 \
  -H "X-API-KEY: $AUTOBOUND_API_KEY"

curl -X POST https://signals.autobound.ai/v1/companies/enrich \
  -H "X-API-KEY: $AUTOBOUND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"zoominfo.com","limit":20}'