← All cases
    Case #0054Channel LinkedIn InMailIndustry RecruitingSender FounderFiled 2026-01-08Verified submission
    // Verdict

    THE LINKEDIN LURKER

    6 offenses identified across 5 categories
    F3/10
    88% CONF
    1CRIT
    5MAJ
    0MIN
    Exhibit A - original message
    LinkedIn InMailInMail
    F
    Founder at [Company]
    Sales Development · 500+ connections
    2026-01-08
    3Been admiring your work from afar, Rachel! 4Your posts on talent acquisition are SO on point. I actually built something that 5solves everything you've been talking about. It's an 6AI-powered talent graph that maps passive candidates across 40+ data sources. Would love to get your take on it! Free for a quick chat this week? 🙌 Adding a bit more context so this is not just a random connect request. We work with Recruiting teams that are dealing with time-to-hire, passive candidate sourcing, and interview bottlenecks. The thing we built is a sourcing workflow that identifies candidates already showing buying signals, and one search team filled senior roles 36% faster across three open reqs. 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. I have been following what your team is doing for a while and thought your recent work was impressive. Per our earlier thread, or at least the notes I have here, it felt like the timing might be right to reconnect and keep the conversation moving.
    1OVER-LENGTHmajor
    Execution

    Message runs 241 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 Flattery → Pivot → Feature → CTA : following the structure without understanding why each element exists.

    Flattery → Pivot → Feature → CTA
    →Classic humble-brag-pivot executed poorly.
    →The compliment is vague ('your work'), the pivot is abrupt ('I built something'), and the feature description is pure buzzwords.
    →LinkedIn InMails with genuine content references get 3x the response rate, but this one name-checks the topic without demonstrating any actual engagement with it.
    §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 body241 words · 1464 chars
      “Been admiring your work from afar, Rachel! Your posts on talent acquisition are SO on point. I actually built something that solves everyth…”
    • CTA-MISSINGmajor
      Span · entire body56 words · 329 chars
      “Been admiring your work from afar, Rachel! Your posts on talent acquisition are SO on point. I actually built something that solves everyth…”
    Phrase scope· 4
    • FALSE-FAMILIARITYmajor
      Span · phrase6 words · 33 chars
      “Been admiring your work from afar”
    • FAKE-RESEARCHcritical
      Span · phrase9 words · 48 chars
      “Your posts on talent acquisition are SO on point”
    • VANITY-PROOFmajor
      Span · phrase6 words · 43 chars
      “solves everything you've been talking about”
    • BUZZWORD-LOADmajor
      Span · phrase3 words · 23 chars
      “AI-powered talent graph”

    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 LINKEDIN LURKER - Case #0054
    F · 3/10
    Worse than 87% of all audited messages
    Next: #0053 · THE WALL OF WORRY →