← All cases
    Case #0014Channel LinkedIn InMailIndustry FinTechSender SDRFiled 2025-12-06Sourced
    // Verdict

    THE CHAIN LETTER

    5 offenses identified across 3 categories
    C5.4/10
    93% CONF
    0CRIT
    3MAJ
    2MIN
    Exhibit A - original message
    LinkedIn InMailInMail
    S
    SDR at [Company]
    Sales Development · 500+ connections
    2025-12-06
    Hi [Name], 3As we discussed, I wanted to follow up on our conversation about payment processing optimization. 4Per our last meeting, the next step would be to schedule a technical deep-dive with your engineering team. Looking forward to 5continuing our partnership. Per the action items from our previous discussion, I've gone ahead and pulled together a draft proposal covering the integration scope, projected savings, and rollout timeline. I'll loop in our solutions architect once we lock the meeting so we can hit the ground running. Please confirm a time that works for your team this week so we can keep momentum. Best regards, Daniel
    1OVER-LENGTHmajor
    Execution

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

    Merge Fail -> Triple False History -> Manufactured Partnership
    This message references a conversation that never happened, a meeting that never occurred, and a partnership that doesn't exist.
    It's not outreach — it's fiction.
    The merge tag failure in the first word makes the deception immediately obvious.
    §07

    Tag scope ledger

    How each offense was applied · 5 total

    Document
    2
    Subject line
    0
    Phrase
    3
    Document scope· 2
    • OVER-LENGTHmajor
      Span · entire body104 words · 644 chars
      “Hi [Name], As we discussed, I wanted to follow up on our conversation about payment processing optimization. Per our last meeting, the next…”
    • CTA-MISSINGmajor
      Span · entire body104 words · 644 chars
      “Hi [Name], As we discussed, I wanted to follow up on our conversation about payment processing optimization. Per our last meeting, the next…”
    Phrase scope· 3
    • REPLY-ALL-ENERGYminor
      Span · phrase3 words · 15 chars
      “As we discussed”
    • REPLY-ALL-ENERGYminor
      Span · phrase4 words · 20 chars
      “Per our last meeting”
    • FALSE-FAMILIARITYmajor
      Span · phrase3 words · 26 chars
      “continuing our partnership”

    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 CHAIN LETTER - Case #0014
    C · 5.4/10
    Worse than 54% of all audited messages
    Next: #0015 · THE WRONG AUDIENCE →