YourOutreachSUCKS - Forensic Audits of Cold Outreach

Case #0030AChannel EmailIndustry SaaSSender SDRFiled 2026-01-09Verified submission

// Verdict

THE RELATIONSHIP FAKER

6 offenses identified across 4 categories

F3.7/10

85% CONF

1CRIT

3MAJ

2MIN

Exhibit A - original message

✉ EMAILcold · unsolicited

Subject: Great meeting you at SaaStr! Hi, 4It was great connecting with you at SaaStr last week! 5I really enjoyed our conversation about scaling customer success teams. 6As I mentioned, our platform helps CS teams automate health scoring and predict churn 90 days in advance. I'd love to continue our conversation with a proper demo. Does Thursday at 2pm work? Best, Lisa For context, I am reaching out because teams in SaaS usually tell us the same three things are eating time right now: trial activation, expansion revenue, and churn prevention. We built a workflow that flags accounts before usage drops turn into churn, and a team at roughly your stage used it to recover 18 points of at-risk renewal pipeline. 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 182 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/6J/K

Offenses · 6

Cargo-cult Fabricated Meeting : following the structure without understanding why each element exists.

Fabricated Meeting -> Manufactured Rapport -> False Continuity

→This message invents an entire prior relationship.

→A conference meeting, a conversation topic, a follow-up reference.

→If the reader attended SaaStr, they might doubt their own memory.

→That's the point — and it's why this tactic is corrosive.

§07

Tag scope ledger

How each offense was applied · 6 total

Document

Applied to the entire message body — a property of the whole artifact.

Subject line

Applied to the subject line as a unit — evaluated independent of body.

Phrase

Pinned to a specific span of text inside the message body.

Document scope· 3

OVER-LENGTHmajor
Span · entire body182 words · 1035 chars
“Hi, It was great connecting with you at SaaStr last week! I really enjoyed our conversation about scaling customer success teams. As I ment…”
NO-OPT-OUTminor
Span · entire body182 words · 1035 chars
“Hi, It was great connecting with you at SaaStr last week! I really enjoyed our conversation about scaling customer success teams. As I ment…”
CTA-MISSINGmajor
Span · entire body62 words · 374 chars
“Subject: Great meeting you at SaaStr! Hi, It was great connecting with you at SaaStr last week! I really enjoyed our conversation about sca…”

Phrase scope· 3

FALSE-FAMILIARITYmajor
Span · phrase10 words · 52 chars
“It was great connecting with you at SaaStr last week”
FAKE-RESEARCHcritical
Span · phrase10 words · 70 chars
“I really enjoyed our conversation about scaling customer success teams”
REPLY-ALL-ENERGYminor
Span · phrase3 words · 14 chars
“As I mentioned”

Final verdict

THE RELATIONSHIP FAKER - Case #0030A

F · 3.7/10

Worse than 83% of all audited messages

Next: #0043 · THE DRIVE-BY →

// Related cases, shared offense types

#0027F · 2

THE FALSE FRIEND

FALSE-FAMILIARITYFAKE-RESEARCHOVER-LENGTHCTA-MISSING

#0014C · 5.4

THE CHAIN LETTER

REPLY-ALL-ENERGYFALSE-FAMILIARITYOVER-LENGTHCTA-MISSING

#0054F · 3

THE LINKEDIN LURKER

FALSE-FAMILIARITYFAKE-RESEARCHOVER-LENGTHCTA-MISSING