YourOutreachSUCKS
    ← All cases
    Case #0049Channel LinkedIn InMailIndustry DevToolsSender FounderFiled 2026-03-26Verified submission
    // Verdict

    THE TECH BRO

    5 offenses identified across 3 categories
    C5.7/10
    82% CONF
    0CRIT
    4MAJ
    1MIN
    Exhibit A - original message
    LinkedIn InMailInMail
    F
    Founder at [Company]
    Sales Development · 500+ connections
    2026-03-26
    Hey! 👋 Building dev tools is hard — we know because we've been in the trenches for 5 years. 2Just shipped our v3 with a completely rewritten Rust backend. We're crushing it with 310K+ daily active developers and growing 40% MoM. Backed by Sequoia and a16z. Your tool looks cool but 4I bet your API latency is killing you at scale. We solved that problem. 5Wanna jam? — Zach, CEO 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.
    1OVER-LENGTHmajor
    Execution

    Message runs 210 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 Self : following the structure without understanding why each element exists.

    Self-Promotion -> Metric Dump -> Technical Assumption -> Casual CTA
    →The entire message is about the sender.
    →Their backend.
    →Their metrics.
    →Their investors.
    →The reader gets one sentence — and it's an insult disguised as empathy.
    →'I bet your latency is killing you' is not rapport-building.
    §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 body210 words · 1194 chars
      “Hey! 👋 Building dev tools is hard — we know because we've been in the trenches for 5 years. Just shipped our v3 with a completely rewritte…”
    Phrase scope· 4
    • VANITY-PROOFmajor
      Span · phrase10 words · 60 chars
      “Just shipped our v3 with a completely rewritten Rust backend”
    • VANITY-PROOFmajor
      Span · phrase13 words · 76 chars
      “10K+ daily active developers and growing 40% MoM. Backed by Sequoia and a16z”
    • PAIN-ASSUMPTIONmajor
      Span · phrase10 words · 46 chars
      “I bet your API latency is killing you at scale”
    • VAGUE-CTAminor
      Span · phrase2 words · 10 chars
      “Wanna jam?”

    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 TECH BRO - Case #0049
    C · 5.7/10
    Worse than 48% of all audited messages
    Next: #0050 · THE COMPLIMENT SANDWICH →
    // Related cases, shared offense types
    #0036D · 4.9
    THE COMPLIANCE SCARE
    PAIN-ASSUMPTIONVANITY-PROOFOVER-LENGTH
    #0023D · 4.8
    THE JARGON WALL
    VAGUE-CTAPAIN-ASSUMPTIONOVER-LENGTH
    #0012C · 5.7
    THE COMPETITOR BASHER
    PAIN-ASSUMPTIONVANITY-PROOFOVER-LENGTH