YourOutreachSUCKS
    ← All cases
    Case #0138Channel EmailIndustry PropTechSender BDRFiled 2026-06-22Sourced
    // Verdict

    THE OLD FRIEND

    4 offenses identified across 3 categories
    ⚑ LOW CONFIDENCE
    B7.7/10
    55% CONF
    0CRIT
    1MAJ
    3MIN
    Exhibit A - original message
    ✉ EMAILcold · unsolicited
    Subject: property valuation tool for PropTech Hi there, 3per our last conversation 4maybe we should chat Cheers, Drew For context, I am reaching out because teams in PropTech usually tell us the same three things are eating time right now: maintenance routing, appraisal turnaround, and tenant response times. We built a queue that routes requests by property, urgency, and vendor availability, and one operator cut average maintenance response from 18 hours to 4. I am not sure whether that maps to your priorities, but it seemed adjacent enough to put in front of you. 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. 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. I will follow up in a couple of days if I do not hear back.
    1OVER-LENGTHmajor
    Execution

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

    Cargo-cult Urgency → FOMO → Hard Close : following the structure without understanding why each element exists.

    Urgency → FOMO → Hard Close
    →This message commits 2 offenses across 2 categories.
    →The primary issue is reply all energy, compounded by vague cta.
    §07

    Tag scope ledger

    How each offense was applied · 4 total

    Document
    2
    Subject line
    0
    Phrase
    2
    Document scope· 2
    • OVER-LENGTHmajor
      Span · entire body166 words · 952 chars
      “Hi there, per our last conversation maybe we should chat Cheers, Drew For context, I am reaching out because teams in PropTech usually tell…”
    • NO-OPT-OUTminor
      Span · entire body166 words · 952 chars
      “Hi there, per our last conversation maybe we should chat Cheers, Drew For context, I am reaching out because teams in PropTech usually tell…”
    Phrase scope· 2
    • REPLY-ALL-ENERGYminor
      Span · phrase4 words · 25 chars
      “per our last conversation”
    • VAGUE-CTAminor
      Span · phrase4 words · 20 chars
      “maybe we should chat”

    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 OLD FRIEND - Case #0138
    B · 7.7/10
    Worse than 13% of all audited messages
    Next: #0137 · THE MANIFESTO →
    // Related cases, shared offense types
    #0030AF · 3.7
    THE RELATIONSHIP FAKER
    REPLY-ALL-ENERGYOVER-LENGTHNO-OPT-OUT
    #0025B · 6.9
    THE CLICKBAITER
    REPLY-ALL-ENERGYOVER-LENGTHNO-OPT-OUT
    #0084D · 4.9
    THE FLATTERY BOT
    REPLY-ALL-ENERGYOVER-LENGTHNO-OPT-OUT