YourOutreachSUCKS
    ← All cases
    Case #0110Channel LinkedIn InMailIndustry PropTechSender SDRFiled 2025-11-05Verified submission
    // Verdict

    THE COLD CLOSE

    4 offenses identified across 3 categories
    B6.8/10
    80% CONF
    1CRIT
    1MAJ
    2MIN
    Exhibit A - original message
    LinkedIn InMailInMail
    S
    SDR at [Company]
    Sales Development · 500+ connections
    2025-11-05
    Hello, 215 minutes this week Intro 3I would be most grateful 4your loosing money short message with no substance no unsubscribe mechanism provided Best, Avery Adding a bit more context so this is not just a random connect request. We work with PropTech teams that are dealing with maintenance routing, appraisal turnaround, and tenant response times. The thing we built is a queue that routes requests by property, urgency, and vendor availability, and one operator cut average maintenance response from 18 hours to 4. I would like to get 20 or 30 minutes on the calendar this week to walk you through it. Tuesday morning, Thursday afternoon, or Friday before noon all work on my side, so feel free to pick whichever is least painful. 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. Sorry if this is not the rite person. Their are a few ways this could help, but I did not want to overcomplicate the note before knowing weather this is on your plate.
    1OVER-LENGTHmajor
    Execution

    Message runs 207 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/4
    Offenses · 4
    "

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

    Guilt → Persistence → Ask
    →This message commits 6 offenses across 4 categories.
    →The primary issue is premature ask, compounded by generic subject, robot voice, mechanical failure, under length, no opt out.
    §07

    Tag scope ledger

    How each offense was applied · 4 total

    Document
    1
    Subject line
    0
    Phrase
    3
    Document scope· 1
    • OVER-LENGTHmajor
      Span · entire body207 words · 1206 chars
      “Hello, 15 minutes this week Intro I would be most grateful your loosing money short message with no substance no unsubscribe mechanism prov…”
    Phrase scope· 3
    • PREMATURE-ASKcritical
      Span · phrase4 words · 20 chars
      “15 minutes this week”
    • ROBOT-VOICEminor
      Span · phrase5 words · 24 chars
      “I would be most grateful”
    • MECHANICAL-FAILUREminor
      Span · phrase3 words · 18 chars
      “your loosing money”

    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 COLD CLOSE - Case #0110
    B · 6.8/10
    Worse than 29% of all audited messages
    Next: #0109 · THE SURFACE SCAN →
    // Related cases, shared offense types
    #0026F · 0.1
    THE ESSAY
    ROBOT-VOICEPREMATURE-ASKOVER-LENGTH
    #0006F · 3.3
    THE WORD AVALANCHE
    PREMATURE-ASKROBOT-VOICEOVER-LENGTH
    #0055B · 6.2
    THE WRONG NUMBER ENERGY
    PREMATURE-ASKMECHANICAL-FAILUREOVER-LENGTH