YourOutreachSUCKS
    ← All cases
    Case #0034Channel LinkedIn InMailIndustry DevToolsSender SDRFiled 2026-01-28Verified submission
    // Verdict

    THE INTEGRATION DUMP

    6 offenses identified across 4 categories
    ⚑ AUTO-FAIL⚑ EXTREME SCORE
    F0.1/10
    79% CONF
    2CRIT
    4MAJ
    0MIN
    Exhibit A - original message
    LinkedIn InMailInMail
    S
    SDR at [Company]
    Sales Development · 500+ connections
    2026-01-28
    Hi! 3I noticed you're a Staff Engineer at 4[Company]. We've built an observability platform that integrates with Datadog, New Relic, Grafana, PagerDuty, OpsGenie, Slack, Jira, and ServiceNow. Our platform provides 5distributed tracing, log aggregation, custom metrics, anomaly detection, SLO tracking, and incident management - all in one unified dashboard. 6Over 500 engineering teams use us. Want to see a demo? Adding a bit more context so this is not just a random connect request. We work with DevTools teams that are dealing with deployment noise, incident routing, and developer workflow drag. The thing we built is a layer that groups noisy alerts into the actual failing service, and one platform team reduced false pages by 58% without replacing its current stack. If any of that sounds remotely relevant, let me know your thoughts. Happy to send more details, compare notes, or point you toward a customer story. If not, no worries at all. We have worked with bigger names too, including a few logos everyone recognizes, and our leadership team has been quoted in the usual industry outlets. I know that probably sounds like a lot of vendor chest-thumping, but I wanted to include the credibility in case it helps. Our approach leverages a configurable operating model for scalable execution across teams, with a modular framework that helps stakeholders operationalize measurable outcomes. In simpler terms, it is supposed to make the work less manual.
    1OVER-LENGTHmajor
    Execution

    Message runs 202 words; healthy ceiling for this channel is ~100. Beyond 150 words, reply rates drop ~50% [Lavender 2024] because the reader has to commit before they can evaluate the offer.

    1/6
    Offenses · 6
    "

    Cargo-cult Title Mention : following the structure without understanding why each element exists.

    Title Mention -> Integration List -> Feature List -> Social Proof -> CTA
    →Two lists back to back: integrations and features.
    →Both are comprehensive and both are useless without context.
    →The sender knows the recipient's title but nothing about their stack, their pain points, or their current tooling.
    →The demo ask at the end assumes interest that was never generated because the message spent all its space on what the product does, not why this person should care.
    §07

    Tag scope ledger

    How each offense was applied · 6 total

    Document
    2
    Subject line
    0
    Phrase
    4
    Document scope· 2
    • OVER-LENGTHmajor
      Span · entire body202 words · 1289 chars
      “Hi! I noticed you're a Staff Engineer at [Company]. We've built an observability platform that integrates with Datadog, New Relic, Grafana,…”
    • CTA-MISSINGmajor
      Span · entire body60 words · 411 chars
      “Hi! I noticed you're a Staff Engineer at [Company]. We've built an observability platform that integrates with Datadog, New Relic, Grafana,…”
    Phrase scope· 4
    • BUZZWORD-LOADmajor
      Span · phrase13 words · 110 chars
      “distributed tracing, log aggregation, custom metrics, anomaly detection, SLO tracking, and incident management”
    • VANITY-PROOFmajor
      Span · phrase6 words · 33 chars
      “Over 500 engineering teams use us”
    • VAGUE-ICPcritical
      Span · phrase8 words · 46 chars
      “I noticed you're a Staff Engineer at [Company]”
    • MERGE-FAILcritical
      Span · phrase1 word · 9 chars
      “[Company]”

    Note. Document-scope tags evaluate the whole message (length, formatting, deliverability). Subject-scope tags evaluate the subject line alone. Phrase-scope tags pin to a specific quoted span shown in the evidence above.

    Final verdict
    THE INTEGRATION DUMP - Case #0034
    F · 0.1/10
    Worse than 95% of all audited messages
    Next: #0035 · THE README PITCH →
    // Related cases, shared offense types
    #0026F · 0.1
    THE ESSAY
    BUZZWORD-LOADVANITY-PROOFOVER-LENGTHCTA-MISSING
    #0017C · 5.5
    THE NARCISSIST
    VANITY-PROOFBUZZWORD-LOADOVER-LENGTHCTA-MISSING
    #0006F · 3.3
    THE WORD AVALANCHE
    BUZZWORD-LOADVANITY-PROOFOVER-LENGTHCTA-MISSING