LinkedIn Comments

{
  "signal_id": "b99a32af-43fb-554f-8ec3-43ce5a9228fa",
  "signal_type": "linkedin-comments-contact",
  "signal_subtype": "linkedinPostComment",
  "detected_at": "2026-09-20T23:48:09.116Z",
  "association": "contact",
  "contact": { // The contact who commented 
    "email": "[email protected]",
    "first_name": "David",
    "last_name": "Barajas",
    "full_name": "David Barajas",
    "job_title": "Senior Software Engineer, Billing and Monetization",
    "linkedin_url": "https://www.linkedin.com/in/david-barajas-swe" // Recommended match key 
  },
  "company": { // We also enrich with the contact's employer
    "name": "Calendly",
    "domain": "calendly.com",
    "linkedin_url": "linkedin.com/company/calendly",
    "industries": ["Software Development"],
    "employee_count_low": 1001,
    "employee_count_high": 5000,
    "revenue": "250 Million to 500 Million"
  },
  "data": { // The signal data itself 
    "comment_text": "I think the challenge is framing around what customer success looks like. Most of a SaaS DAU or MAU counts come from app usage. Logins to the site, the mobile app, interactions with the dashboard. If you let users consume you as an MCP/API and let someone else own the UX, you give up a lot of upsell opportunities. Being invisible has a cost that people start thinking \"Do I really need that service?\". I think it's a tricky balance to play but I agree. As a consumer I want everything to plug and play into a central hub. Business growth is at odds with that in the traditional sense.", // The prospect's own words - quote them in outreach
    "comment_summary": "Engineer agrees agent-first consumption is coming but warns invisible products lose upsell leverage.",
    "comment_url": "https://www.linkedin.com/feed/update/urn:li:activity:7506838202792615936?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7506838202792615936%2C7507527351925108737%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287507527351925108737%2Curn%3Ali%3Aactivity%3A7506838202792615936%29",
    "comment_posted_at": "2026-09-20T19:53:23.813Z",
    "comment_num_likes": 2,
    "comment_num_comments": 3,
    "comment_intent": "insight", // question, disagreement, celebration, praise, tagging, insight, recommendation
    "signal_quality": 0.85, // 0-1 scale, higher = more actionable
    "relationship_context": { // Inferred relationship between the commenter and the poster
      "inferred_relationship": "industry_peer",
      "confidence": 0.7
    },
    "pain_points": [
      {
        "topic": "losing upsell opportunities when others own the UX",
        "intensity": 0.7
      },
      {
        "topic": "invisible products get questioned at renewal",
        "intensity": 0.65
      }
    ],
    "initiatives": [
      {
        "topic": "balancing MCP and API exposure with product engagement",
        "urgency": 0.6 // 0-1 scale
      }
    ],
    "technologies_mentioned": [
      {
        "name": "MCP",
        "status": "considering"
      }
    ],
    "competitors_mentioned": [],
    "parent_post": { // The post they commented on - same AI enrichment as LinkedIn Post signals
      "signal_id": "2f3e2c35-8b9a-5578-a09c-cda70baf2d46", // Cross-reference to the parent post signal
      "post_url": "https://www.linkedin.com/feed/update/urn:li:activity:7506838202792615936/",
      "post_text": "If you're still focused on building AI into your product, you're missing the point.\n\nI just opened an app I use at work almost everyday.\n\nThey had a pop-up announcing new AI functionality in their product.\n\nI literally do not care.\n\nAll I care about is how I can get your API's/MCP's exposed so I can plug them into my universal agents that run everything for me.\n\nCan't stop thinking about how many eng hours were wasted on getting that feature live...\n\nThe big players have already won the race for the AI homepage.\n\nIf you're not Anthropic, SpaceX, Meta, etc., you shouldn't be spending time developing AI tools in your platform.\n\nInstead, you should be focusing on how to make your platform play well with agents. \nie. Instinct, GrokBot, Muse, Claude Agents, etc.\n\nAt this point, if I can't use your product/solution via my own internal tooling, I'm not buying it. \n\nSo think less about how to make AI work INSIDE your product, and instead think about how to make AI work OUTSIDE of your product.",
      "post_summary": "RevOps leader urges vendors to expose APIs and MCPs for agents over in-product AI.",
      "posted_date": "2026-09-18T22:14:57.855Z",
      "num_likes": 163,
      "num_comments": 71,
      "poster_name": "Mike Christensen", // The person whose post drew the comment
      "poster_job_title": "Head of Revenue Operations",
      "poster_company_name": "Redo",
      "poster_company_description": "Redo helps online retailers optimize their post-purchase operations by consolidating tech stacks and enhancing returns management, order tracking, and customer service with AI.",
      "pain_points": [
        {
          "topic": "engineering hours wasted on unused in-product AI features",
          "intensity": 0.7
        },
        {
          "topic": "products unusable through agent-based internal tooling",
          "intensity": 0.65
        }
      ],
      "initiatives": [
        {
          "topic": "plugging vendor APIs and MCPs into universal agents",
          "urgency": 0.85
        },
        {
          "topic": "evaluating products on agent interoperability before buying",
          "urgency": 0.7
        }
      ],
      "technologies_mentioned": [
        {
          "name": "MCP",
          "status": "using"
        },
        {
          "name": "Claude Agents",
          "status": "using"
        },
        {
          "name": "Instinct",
          "status": "considering"
        },
        {
          "name": "GrokBot",
          "status": "considering"
        },
        {
          "name": "Muse",
          "status": "considering"
        }
      ],
      "competitors_mentioned": []
    }
  }
}