YourOutreachSUCKS
    ← All cases
    Case #0030Channel EmailIndustry FinTechSender SDRFiled 2026-01-08Verified submission
    // Verdict

    THE CALENDAR BULLY

    5 offenses identified across 3 categories
    C5.2/10
    88% CONF
    1CRIT
    3MAJ
    1MIN
    Exhibit A - original message
    ✉ EMAILcold · unsolicited
    Subject: Quick sync? Hey there, 3I know you're slammed but I've been trying to reach you. 4Can we lock in 30 minutes this Thursday or Friday? I'll send the invite. 5If neither works, how about Monday? Cheers, Bryan For context, I am reaching out because teams in FinTech usually tell us the same three things are eating time right now: payments operations, compliance reviews, and reconciliation work. We built a tool that routes exceptions to the right owner before month-end close, and one finance team cut manual reconciliation queues by 42% in six weeks. I am not sure whether that maps to your priorities, but it seemed adjacent enough to put in front of you. You can grab time on my calendar, look at the deck, skim the case study, join the webinar next week, or just reply here and I can send whichever version is easiest. If none of those are useful, tell me who owns this and I will route it over to them instead. I will follow up in a couple of days if I do not hear back.
    1OVER-LENGTHmajor
    Execution

    Message runs 164 words; healthy ceiling for this channel is ~150. 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 Direct Calendar Ask : following the structure without understanding why each element exists.

    Direct Calendar Ask
    →No hook, no value, no context.
    →Opens by acknowledging they're bothering the reader, then immediately asks for time.
    →Three date options compete for attention with no reason to pick any of them.
    §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 body164 words · 903 chars
      “Hey there, I know you're slammed but I've been trying to reach you. Can we lock in 30 minutes this Thursday or Friday? I'll send the invite…”
    • NO-OPT-OUTminor
      Span · entire body164 words · 903 chars
      “Hey there, I know you're slammed but I've been trying to reach you. Can we lock in 30 minutes this Thursday or Friday? I'll send the invite…”
    Phrase scope· 3
    • DESPERATION-SIGNALmajor
      Span · phrase11 words · 55 chars
      “I know you're slammed but I've been trying to reach you”
    • PREMATURE-ASKcritical
      Span · phrase10 words · 49 chars
      “Can we lock in 30 minutes this Thursday or Friday”
    • CTA-OVERLOADmajor
      Span · phrase6 words · 34 chars
      “If neither works, how about Monday”

    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 CALENDAR BULLY - Case #0030
    C · 5.2/10
    Worse than 58% of all audited messages
    Next: #0029A · THE INFORMATION VACUUM →
    // Related cases, shared offense types
    #0100D · 4.9
    THE CALENDAR GRAB
    PREMATURE-ASKCTA-OVERLOADOVER-LENGTHNO-OPT-OUT
    #0101F · 2.6
    THE COLD CLOSE
    PREMATURE-ASKDESPERATION-SIGNALOVER-LENGTHNO-OPT-OUT
    #0108D · 4.1
    THE CALENDAR GRAB
    PREMATURE-ASKCTA-OVERLOADOVER-LENGTHNO-OPT-OUT