← All cases
    Case #0011Channel LinkedIn InMailIndustry SaaSSender SDRFiled 2025-11-30Verified submission
    // Verdict

    THE COPY-PASTE

    3 offenses identified across 2 categories
    ⚑ AUTO-FAIL⚑ EXTREME SCORE
    F0.1/10
    98% CONF
    3CRIT
    0MAJ
    0MIN
    Exhibit A - original message
    LinkedIn InMailInMail
    S
    SDR at [Company]
    Sales Development · 500+ connections
    2025-11-30
    Hi 1{{first_name}}, I see you're the {{title}} at {{company}}. 2Impressive work on {{recent_achievement}}! At DataSync, we help {{industry}} companies like {{company}} 3solve {{pain_point}} with our {{product_feature}}. Would love to chat about how we can help {{company}} achieve {{desired_outcome}}. We've helped {{customer_logo_1}}, {{customer_logo_2}}, and {{customer_logo_3}} cut {{metric}} by {{percentage}}% in under {{timeframe}}. Our {{integration_count}}+ native integrations mean you can be up and running in {{onboarding_time}}, with full ROI typically realized by {{roi_milestone}}. I'd love to put together a custom {{deliverable}} for {{company}} based on your {{tech_stack}}. Let me know if {{day_1}} or {{day_2}} works for a quick {{meeting_length}}. Best, {{sender_name}}
    1MERGE-FAILcritical
    Execution

    Literal merge token visible in the rendered message. No QA pass ran on the sequence; the reader sees template scaffolding instead of personalization.

    1/3
    Offenses · 3
    "

    Cargo-cult Total Merge Failure : following the structure without understanding why each element exists.

    Total Merge Failure -> Exposed Template Logic
    This is the platonic ideal of a merge failure.
    Every single field — name, title, company, achievement, industry, pain point, feature, outcome, even the sender's name — is a visible placeholder.
    The template logic is fully exposed.
    The recipient is reading the source code of the outreach sequence.
    §07

    Tag scope ledger

    How each offense was applied · 3 total

    Document
    0
    Subject line
    0
    Phrase
    3
    Phrase scope· 3
    • FAKE-RESEARCHcritical
      Span · phrase4 words · 41 chars
      “Impressive work on {{recent_achievement}}”
    • MERGE-FAILcritical
      Span · phrase5 words · 49 chars
      “solve {{pain_point}} with our {{product_feature}}”
    • MERGE-FAILcritical
      Span · phrase1 word · 14 chars
      “{{first_name}}”

    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 COPY-PASTE - Case #0011
    F · 0.1/10
    Worse than 95% of all audited messages
    Next: #0012 · THE COMPETITOR BASHER →