YourOutreachSUCKS
    ← All cases
    Case #0077Channel LinkedIn InMailIndustry DevToolsSender SDRFiled 2025-06-02Sourced
    // Verdict

    THE NO-TARGET

    5 offenses identified across 4 categories
    ⚑ LOW CONFIDENCE
    D4.8/10
    74% CONF
    1CRIT
    3MAJ
    1MIN
    Exhibit A - original message
    LinkedIn InMailInMail
    S
    SDR at [Company]
    Sales Development · 500+ connections
    2025-06-02
    Hi there, 2leaders like you 3built three companies in the space that all exited Please find attached 4trusted by Fortune 500 companies 5I would be most grateful Thanks, Jordan 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. 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 171 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/5
    Offenses · 5
    "

    Cargo-cult Casual → Assumption → Vague CTA : following the structure without understanding why each element exists.

    Casual → Assumption → Vague CTA
    →This message commits 5 offenses across 5 categories.
    →The primary issue is vague icp, compounded by humble brag pivot, channel deaf, logo soup, robot voice.
    §07

    Tag scope ledger

    How each offense was applied · 5 total

    Document
    1
    Subject line
    0
    Phrase
    4
    Document scope· 1
    • OVER-LENGTHmajor
      Span · entire body171 words · 1052 chars
      “Hi there, leaders like you built three companies in the space that all exited Please find attached trusted by Fortune 500 companies I would…”
    Phrase scope· 4
    • VAGUE-ICPcritical
      Span · phrase3 words · 16 chars
      “leaders like you”
    • VANITY-PROOFmajor
      Span · phrase9 words · 50 chars
      “built three companies in the space that all exited”
    • VANITY-PROOFmajor
      Span · phrase5 words · 32 chars
      “trusted by Fortune 500 companies”
    • ROBOT-VOICEminor
      Span · phrase5 words · 24 chars
      “I would be most grateful”

    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 NO-TARGET - Case #0077
    D · 4.8/10
    Worse than 66% of all audited messages
    Next: #0076 · THE SURFACE SCAN →
    // Related cases, shared offense types
    #0034F · 0.1
    THE INTEGRATION DUMP
    VANITY-PROOFVAGUE-ICPOVER-LENGTH
    #0026F · 0.1
    THE ESSAY
    ROBOT-VOICEVANITY-PROOFOVER-LENGTH
    #0006F · 3.3
    THE WORD AVALANCHE
    VANITY-PROOFROBOT-VOICEOVER-LENGTH