YourOutreachSUCKS
    ← All cases
    Case #0082Channel LinkedIn InMailIndustry DevToolsSender SDRFiled 2025-01-07Verified submission
    // Verdict

    THE PRETEND READER

    7 offenses identified across 5 categories
    F3/10
    86% CONF
    1CRIT
    3MAJ
    3MIN
    Exhibit A - original message
    LinkedIn InMailInMail
    S
    SDR at [Company]
    Sales Development · 500+ connections
    2025-01-07
    Hey, I've been 3impressed by what you're building. 4Only 3 spots left in our pilot program — want to grab one? 5As we discussed, 6I would be most grateful for a 7FREE demo session to show you the platform. Worth a quick chat? Thanks, Sam 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. Also worth mentioning that we are only opening a few pilot slots this month, and the incentive expires Friday. I realize that sounds salesy, but I did not want you to miss the window if this is already on your roadmap. 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 227 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/7
    Offenses · 7
    "

    Cargo-cult Flattery → Pitch → Ask : following the structure without understanding why each element exists.

    Flattery → Pitch → Ask
    →This message commits 5 offenses across 4 categories.
    →The primary issue is fake research, compounded by fomo bait, reply all energy, robot voice, spam trigger.
    §07

    Tag scope ledger

    How each offense was applied · 7 total

    Document
    2
    Subject line
    0
    Phrase
    5
    Document scope· 2
    • OVER-LENGTHmajor
      Span · entire body227 words · 1307 chars
      “Hey, I've been impressed by what you're building. Only 3 spots left in our pilot program — want to grab one? As we discussed, I would be mo…”
    • CTA-MISSINGmajor
      Span · entire body45 words · 236 chars
      “Hey, I've been impressed by what you're building. Only 3 spots left in our pilot program — want to grab one? As we discussed, I would be mo…”
    Phrase scope· 5
    • FAKE-RESEARCHcritical
      Span · phrase5 words · 33 chars
      “impressed by what you're building”
    • FOMO-BAITmajor
      Span · phrase8 words · 38 chars
      “Only 3 spots left in our pilot program”
    • REPLY-ALL-ENERGYminor
      Span · phrase12 words · 56 chars
      “As we discussed, I would be most grateful for a FREE dem”
    • ROBOT-VOICEminor
      Span · phrase5 words · 24 chars
      “I would be most grateful”
    • SPAM-TRIGGERminor
      Span · phrase1 word · 4 chars
      “FREE”

    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 PRETEND READER - Case #0082
    F · 3/10
    Worse than 87% of all audited messages
    Next: #0081 · THE EVERYONE PITCH →
    // Related cases, shared offense types
    #0087F · 3.5
    THE BAIT AND SWITCH
    FOMO-BAITREPLY-ALL-ENERGYSPAM-TRIGGEROVER-LENGTHCTA-MISSING
    #0107D · 4.5
    THE PRETEND READER
    FAKE-RESEARCHFOMO-BAITSPAM-TRIGGEROVER-LENGTHCTA-MISSING
    #0030AF · 3.7
    THE RELATIONSHIP FAKER
    FAKE-RESEARCHREPLY-ALL-ENERGYOVER-LENGTHCTA-MISSING