The 100 Worst Cold Messages I've Ever Received

By Wes Lemos, Sales Connector.

These are real, anonymized. Names changed, identifying details obscured, numbers fudged just enough that nobody gets sued. The patterns are exactly as they appeared in my inbox.

If you do outbound for a living, the goal here is not to make you feel bad. The goal is to make you better. Every single one of these has a fix.

SECTION 01Personalization failures (1-22)

001The fake personalization

Hi {firstName}! I noticed you work at {company} and I think we could really help you achieve your goals!

Failure: the variable didn't even render.

Wes's reaction: I am cackling. Even your bot didn't believe in the message.

What to do instead: if your variables fail, your monitoring is broken. Fix the monitoring.

002The 700-word essay

[redacted, but it was 700 words long]

Failure: wall of text.

Wes's reaction: if you can't say it in 60 words, you don't know what you're saying.

What to do instead: open with one observation and one question. The pitch can come later.

003The misnamed prospect

Dear Robert,

Failure: my name is Wes.

Wes's reaction: the worst part is they followed up. Twice. Still calling me Robert.

What to do instead: if you're using a tool that fills in names, verify the data source. Apollo gets it wrong about 8% of the time.

004The fake intro

John from your team mentioned you'd be a good fit for this.

Failure: there is no John on my team.

Wes's reaction: lying to start a sales conversation is the single fastest way to ensure it never starts.

What to do instead: if you don't have a real intro, lead with what got your attention. Specificity beats fake warmth.

005The desperate

Hi! I've reached out a few times and would love to connect. We have great solutions for {company}. Are you available for a 15-minute call?

Failure: they had reached out twice. Both messages were the same.

Wes's reaction: "great solutions" tells me you don't know what's specifically broken at my company. So why are you confident you can fix it?

What to do instead: by message three, you should have something new to say. If you don't, stop messaging.

006The AI hallucination

I noticed your recent post about how Sales Connector helps companies hire 50 SDRs in their first month.

Failure: I have never said that, never written that, and the math is impossible.

Wes's reaction: this is what happens when AI generates personalization without checking sources. The output reads convincingly until you actually read it.

What to do instead: if you're using AI to personalize, the human reviewing the draft has to actually verify the claims.

007The brag

I'm Vice President of Strategic Partnerships at [Fortune 500] and I'd like to discuss a potential partnership opportunity with Sales Connector.

Failure: the title is the entire message.

Wes's reaction: I'm not impressed by your title. I'm impressed when someone has a specific, well-considered idea.

What to do instead: lead with the idea, not the credential.

008The "synergy"

I see strong synergies between our companies. Let's explore!

Failure: the word synergy. The lack of any specifics. The exclamation point.

Wes's reaction: what synergies, friend? Be specific or be silent.

What to do instead: name one specific overlap. Even if you're wrong, you've shown you thought about it.

009The pitch in the connect request

[Connect request with 1,500-character note pitching their product, including a calendar link.]

Failure: the connect note isn't an open. It's an introduction. Pitching here is like asking someone to marry you on a first hello.

Wes's reaction: this is somebody who has never been on the receiving end of their own outbound.

What to do instead: the connect note should be a single line. Pitch comes after the connection is accepted.

010The follow-up that doesn't follow up

Just wanted to make sure you saw my last message.

Failure: "just wanted to" is the universal signal that you're filling space because you have nothing to say.

Wes's reaction: I saw your message. I chose not to reply. Asking again doesn't change either of those things.

What to do instead: in a follow-up, say something genuinely new. Or don't follow up.

011The double-rendered variable

Hi Wes Wes, hope you're having a great week at Sales Connector Sales Connector!

Failure: the merge field fired twice and nobody read the output.

Wes's reaction: I love being addressed as if my parents stuttered.

What to do instead: every templated send needs a real person reading three random samples before the campaign goes live. Three is enough to catch this.

012The bracketed ghost

Hi Wes, I was looking at [PROSPECT'S RECENT POST] and wanted to reach out.

Failure: the placeholder text from the template made it into the live message.

Wes's reaction: this is what happens when you copy-paste from a Google Doc and never proofread anything in your life.

What to do instead: any merge field that isn't actually filled should fail the send, not ship empty brackets. Build a linter into your sending tool, or build one yourself in 20 lines of code.

013The merged-from-a-spreadsheet disaster

Hi Wes, congrats on your role as Director of Engineering at TechCorp Inc.

Failure: I am not Director of Engineering at TechCorp Inc, and have never been. They merged the wrong row.

Wes's reaction: somewhere out there, an actual Director of Engineering at TechCorp got a message congratulating them on running Sales Connector. We're now confused brothers.

What to do instead: before merging from a spreadsheet, verify the join key isn't off-by-one. Sample the first ten rows. Look at them with your eyes.

014The wrong industry

As a fellow SaaS leader in the cybersecurity space, I wanted to reach out.

Failure: Sales Connector is not in cybersecurity.

Wes's reaction: I'd love to know what list they pulled me from. I'd buy that list a drink and ask it some questions.

What to do instead: if you're filtering by industry, sample the output. ZoomInfo and Apollo both miscategorize at meaningful rates. Check before you spray.

015The wrong company entirely

Hi Wes, I see Salesforce is hiring aggressively right now and thought you might be interested in our recruiting platform.

Failure: I do not work at Salesforce. I have never worked at Salesforce.

Wes's reaction: I checked my LinkedIn after this one just to make sure I hadn't gotten promoted in my sleep.

What to do instead: the company name in your message should match the company name in their profile. If you can't get that right, automate less.

016The wrong role

Hi Wes, as a marketing leader at Sales Connector, you probably struggle with...

Failure: I'm the founder. I don't work in marketing. The site says this.

Wes's reaction: when someone clearly has not looked at a single thing about me, the "personalization" is just an insult with extra steps.

What to do instead: if you're filtering by role, the role field in your CRM has to actually be accurate. Founder and CMO are not interchangeable.

017The phantom recent post

Loved your recent post about scaling outbound. Really resonated with my own experience.

Failure: my last post was three months ago and was about Pi-based hardware. There was no outbound post.

Wes's reaction: this is the cold-message equivalent of someone telling you they loved your hat when you're not wearing one.

What to do instead: if you're going to reference a post, paste the actual phrase from it. Forced specificity prevents fabrication.

018The phantom podcast appearance

Listened to your interview on The Founder Show last week, fantastic insights.

Failure: I have never been on a podcast called The Founder Show. I have never been on any podcast that week.

Wes's reaction: I almost replied "thanks" just to see how long they'd ride the lie.

What to do instead: never invent a credit. Real flattery is "I read your March essay on X and the part about Y stuck with me." Specific. Verifiable. True.

019The wrong nickname

Hey Wesley!

Failure: my name is Wes. It says Wes in every single profile, signature, byline, and DNS record I own.

Wes's reaction: my mother calls me Wes. My grandmother called me Wes. Where did Wesley come from.

What to do instead: use the name the person uses publicly. If someone signs their LinkedIn posts as Wes, do not Wesley them. Don't formalize what they've already informalized.

020The wrong nickname, the other direction

Hey Wes-man!

Failure: unsolicited nickname from a stranger.

Wes's reaction: we are not friends. You do not have nickname privileges. Stop.

What to do instead: match the formality of how they introduce themselves. If they sign Wes, you write Wes. Not Wes-man, not Wes-y, not Wesley. Just Wes.

021The wrong pronoun

Hi Wes, I think she would love what we're building.

Failure: they were emailing me about me.

Wes's reaction: this happens when AI mid-rewrite forgets which character it's playing.

What to do instead: if you're using AI to draft, never let it pronoun-shift mid-message. Read the draft. The bar for sending is "would a human have written this." It's a low bar. Clear it.

022The wrong language

[first three lines in Spanish, then a switch to English mid-paragraph]

Failure: the personalization layer translated the first lines but the body template was English.

Wes's reaction: I appreciate the bilingual ambition. I do not appreciate the seam in the middle of the shirt.

What to do instead: if your campaign translates, every component has to translate, or none of them do. Mixed-language messages are worse than monolingual ones.

SECTION 02Length failures (23-30)

023The 1,200-word manifesto

[a single email, 1,200 words long, 11 paragraphs, ending in "let me know your thoughts!"]

Failure: I am not your editor.

Wes's reaction: if you wrote 1,200 words to a stranger, you wrote them for yourself. I am not the audience for your therapy.

What to do instead: kill 80% of the draft. Lead with the line you'd lead with if you only had one line. The rest is for your followups, if you earn them.

024The "about us" preamble

[four paragraphs explaining who they are and what their company does, then one sentence asking for a call]

Failure: I read four paragraphs to find out you wanted my time. Now I know two things about you and one of them is that you don't respect my time.

Wes's reaction: I bailed at paragraph two. The ask never reached me. Most cold readers bail at sentence two.

What to do instead: the ask comes in the first three lines or the message dies. Save the company backstory for your About page.

025The five-bullet feature dump

Here's what we offer:

- AI-powered prospecting

- Multi-channel sequencing

- Real-time analytics

- Native CRM integration

- 24/7 support

Failure: five interchangeable bullets, no point of view, no relevance to me.

Wes's reaction: every B2B SaaS company has these five bullets. You've told me nothing.

What to do instead: if you have five features, pick the one that matters most for this prospect and write one sentence about it. The other four are noise in a cold open.

026The poem

[a four-stanza rhyming poem about the value of automation]

Failure: yes, this happened. Yes, it rhymed.

Wes's reaction: I respect the bravery. I do not respect the result.

What to do instead: creativity is good. Forced creativity that takes 10x as long to read as a normal email is not creativity, it's friction. Write a normal email.

027The story that buries the lede

When I was 22, I worked at a company where our outbound just didn't work. Every Monday morning we'd...

Failure: 200 words of personal narrative before the ask.

Wes's reaction: I'm happy you grew as a person. I'm not happy I had to read about it to find out you wanted to sell me something.

What to do instead: if your story is the lede, fine, but make it 30 words. If it's longer than the ask, cut it.

028The case study before the relevance

Last quarter we worked with a 500-person company that increased outbound reply rates by 47%. Here's how we did it: [600 more words]

Failure: I am not a 500-person company. The case study has nothing to do with me.

Wes's reaction: if your case study has to be that long, the takeaway isn't memorable enough.

What to do instead: lead with the relevant number for the company you're emailing. One sentence. "Companies your size typically see X." Then earn the rest.

029The full pitch deck pasted into the email

[a 15-slide pitch deck rendered as text, complete with "SLIDE 1" headers]

Failure: the pitch deck made it into the body verbatim. Including the slide numbers.

Wes's reaction: this is somebody who has confused "preparing thoroughly" with "communicating well."

What to do instead: a pitch deck is a meeting artifact, not an opener. The cold message gets you the meeting. Don't skip the steps.

030The agenda before the meeting

Here's a proposed agenda for our 30-minute call: 1) Intro... 2) Pain points... 3) Demo... 4) Q&A... 5) Next steps.

Failure: the agenda for a meeting I have not agreed to.

Wes's reaction: I haven't said yes. There's no call. Stop scheduling around me.

What to do instead: ask a question that earns the meeting. The agenda is for after the yes, not before.

SECTION 03Tone failures (31-44)

031The desperate close

Please, I really need this meeting. My quarter is on the line.

Failure: their problem is not my problem.

Wes's reaction: I felt sad for them and then I deleted it. I'd rather buy from someone who doesn't need the sale.

What to do instead: never make your prospect responsible for your number. Ever. The instant your urgency becomes their problem, you've lost.

032The arrogant

You'd be foolish not to take this meeting.

Failure: insulting the prospect's judgment.

Wes's reaction: I would be foolish to take it now. Specifically because of this sentence.

What to do instead: confidence is fine. Contempt is not. The line between is "would you say this out loud at a dinner party."

033The fake-friend opener

Hey buddy! Hope you're having an amazing week! Big fan of you!

Failure: three exclamation points, two false intimacies, zero specifics.

Wes's reaction: every word of this is wrong and the sum is wronger than the parts.

What to do instead: match the energy a peer would use. Strangers don't say "buddy." Strangers don't say "big fan." Strangers say their name and what they want.

034The "I'll keep this simple"

I'll keep this simple for you: we help companies like yours grow revenue.

Failure: the condescension is the entire message.

Wes's reaction: "I'll keep this simple for you" tells me you think I can't handle the complicated version. So now I'm offended and I still don't know what you sell.

What to do instead: if you have to announce that you're being simple, you're not being simple. Just be simple.

035The synergy framework enablement leverage

We'd love to leverage our enablement framework to drive synergistic outcomes across your go-to-market motion.

Failure: every word is a buzzword and they're stacked.

Wes's reaction: I have read this sentence eight times and I still cannot tell you what they sell.

What to do instead: if you remove every buzzword and the sentence still says nothing, the sentence said nothing. Write what you do as if you were explaining it to a friend who doesn't work in tech.

036The fake fan

I'm a HUGE fan of your work. I've been following you forever.

Failure: they followed me 12 minutes before sending this. The receipt is in their connection metadata.

Wes's reaction: "forever" is a load-bearing word and they overloaded it.

What to do instead: if you actually read something they wrote, quote a specific phrase. If you didn't, don't fake it. "Saw your post on X" beats "huge fan" every time.

037The "why haven't you replied"

I've sent you three messages and haven't heard back. Did I do something wrong?

Failure: turning my silence into your grievance.

Wes's reaction: yes. You sent the third message.

What to do instead: silence is information. After two unanswered messages, the prospect has told you "no" without using the word. Respect that.

038The over-explainer

Just to clarify, when I say "platform", I mean a software platform, which is to say a piece of software, that platforms a workflow...

Failure: they explained the explanation of the explanation.

Wes's reaction: the more you explain, the less I trust you understand it.

What to do instead: define a term once, in passing, with one example. If you need a paragraph to define it, the term is wrong for a cold message. Pick a simpler term.

039The fake humility

I know you're super busy and I really hate to bother you, but I just thought maybe possibly you might consider...

Failure: five hedges before any content.

Wes's reaction: if you hate to bother me, the move is "don't bother me," not "extensively apologize for bothering me."

What to do instead: assume you're worth their attention. State your business. If you don't believe you're worth their attention, you have a bigger problem than the message.

040The chest-pounding humility

I know you're busy. I'll be brief. We're the #1 platform in the space.

Failure: brevity claim followed immediately by a brag.

Wes's reaction: the second sentence cancelled the first sentence and then the third sentence cancelled the brand.

What to do instead: if you say you'll be brief, be brief. Don't promise short and deliver self-congratulation.

041The lecture

Most founders don't realize that their outbound is fundamentally broken because they're using outdated playbooks from 2015...

Failure: lecturing the prospect on what they don't realize.

Wes's reaction: you have no idea what I realize. You've never met me. Get off the soapbox.

What to do instead: ask a question instead of declaring an answer. "How are you thinking about X?" beats "you're wrong about X."

042The sigh

[opens with] Sigh. Another day, another Monday.

Failure: opening a sales message with a sigh.

Wes's reaction: you are tired and you are making me tired.

What to do instead: never bring your bad day to the prospect. The cold message is not your diary.

043The compliment that's an insult

I love what you're trying to do at Sales Connector!

Failure: "trying" is doing a lot of work in that sentence.

Wes's reaction: thanks for noticing my effort. The condescension is a nice touch.

What to do instead: never compliment with adjectives that imply incompleteness. "Love what you're doing" is fine. "Love what you're trying to do" reads as pity.

044The premature familiarity

Hey Wes, hope the kids are good!

Failure: I do not have kids. We have never spoken.

Wes's reaction: the false intimacy felt like a stranger reaching for my wallet.

What to do instead: keep cold messages cold. Warmth is earned across the conversation, not faked in line one. If you wouldn't ask about a stranger's kids in an elevator, don't ask in a cold email.

SECTION 04Honesty failures (45-54)

045The made-up referrer

Sarah suggested I reach out.

Failure: there are 47 Sarahs I know. None of them suggested this.

Wes's reaction: when "Sarah" is your bridge, every Sarah I trust gets a tax. So now Sarah is a tax word.

What to do instead: if you have a real intro, name them in full and say what they said. If you don't, don't fake one. The cost of getting caught is enormous.

046The 1,400% ROI

Our last client saw a 1,400% ROI in their first 30 days.

Failure: that's a 14x return in a month. Math says no.

Wes's reaction: I work with founders. We can all do percentages. You did not pass that test.

What to do instead: use real numbers from real customers, ideally with a name attached, ideally a number that's actually believable. "Our average customer sees 2.1x in 90 days" is more persuasive than 1,400% in 30.

047The fictional case study

We helped a company exactly like yours go from $10M to $100M ARR using our outbound playbook.

Failure: that ten-bagger has never happened from outbound alone in the history of B2B.

Wes's reaction: this is what happens when sales theater eats sales reality.

What to do instead: specific, modest, true. "We helped a 30-person SaaS company double reply rates over six weeks" is more believable and more persuasive than fantasy.

048The phantom urgency

Last chance! Spots are filling up fast!

Failure: there are no spots. There is no end date. There is no scarcity.

Wes's reaction: if I take you at your word, your spots have been filling up fast for nine months straight. Calendars don't work that way.

What to do instead: real urgency is real or it's nothing. If your offer has no end date, don't pretend it does. The lie compounds the longer the campaign runs.

049The 1,000 companies lie

We've helped over 1,000 companies just like yours.

Failure: they were a six-person company. They had not helped 1,000 of anyone.

Wes's reaction: the math of a six-person team servicing 1,000 customers means they spent 27 minutes per customer total. I do not want my 27 minutes.

What to do instead: brag about your real numbers. If your real number is 12, say 12. Twelve specific is more powerful than 1,000 generic.

050The manufactured exclusivity

I only work with five founders this year and I'd like to talk to you.

Failure: they sent this to 4,000 people. The math is public.

Wes's reaction: I checked their LinkedIn engagement. The "five" was sent to a five-figure crowd.

What to do instead: real exclusivity is verifiable. If you only take five clients, your roster page lists five clients. Otherwise, scarcity is a lie that any prospect can fact-check in 90 seconds.

051The award no one heard of

As a Top 40 Under 40 honoree...

Failure: the award was a $200 entry fee LinkedIn list with no editorial standard.

Wes's reaction: I love an award. I love it less when I can buy one.

What to do instead: if you must reference credentials, reference ones the reader can independently verify. Otherwise the credential makes you look smaller, not bigger.

052The fake degree

As a Stanford-educated engineer...

Failure: they took a one-week online course at Stanford Continuing Studies.

Wes's reaction: that is not what "Stanford-educated" means and you know it.

What to do instead: be honest about credentials. "Took a great Stanford workshop on X" is fine. "Stanford-educated" without a degree is a lie waiting to be found.

053The phantom press

As featured in Forbes, Inc, and TechCrunch...

Failure: featured meant "quoted in a 1,200-word article by a contributor who took $300 to write it."

Wes's reaction: Forbes Contributor Network is not Forbes. We all know this. Stop.

What to do instead: if your press is paid placement or contributor content, do not use the parent publication's name as a credential. The first prospect who clicks through will eviscerate you.

054The fake "personalized" video

I made you a personalized video walking through your website.

Failure: the video was a 30-second template with my logo overlaid via tool. They made one for 800 prospects that day.

Wes's reaction: "personalized" used to mean something. We let it slip away.

What to do instead: if the only personal thing in the video is the logo, it's not a personalized video. It's a templated video with a logo. Call it what it is, or actually personalize it.

SECTION 05Format failures (55-66)

055The connect request pitch deck

[connect request: 280 characters of pitch followed by a Calendly link]

Failure: they used a connection request as a sales channel.

Wes's reaction: asking for a meeting before a connection is the LinkedIn equivalent of pitching the bouncer.

What to do instead: the connection note is a single sentence: who you are and one line of why they'd want to know you. Pitch comes after acceptance. Always.

056The connect request dropping a Loom

[connect request: "Hi Wes, here's a Loom for you" followed by a 14-minute video link]

Failure: I'm not watching 14 minutes from someone I haven't connected with.

Wes's reaction: the asymmetry of effort is fascinating. They invested 14 minutes hoping to extract 14 minutes. The trade is uneven and they made it uneven.

What to do instead: Loom is a great tool for a warm conversation, not a cold open. Save it for the second message, after you've earned a sliver of attention.

057The triple-blast in 60 seconds

[Connect request, then a follow-up DM, then an email, all within 60 seconds, with the same message in three slightly different wordings.]

Failure: they automated all three channels at once.

Wes's reaction: I see all three notifications at once. I see what you did. We all see.

What to do instead: if you're going to multi-channel, space the channels out by days, not seconds. And vary the message meaningfully. Identical content across channels reads as automation, not effort.

058The cold InMail with no preamble

[InMail with subject "Quick question" and body "When can you talk?"]

Failure: zero context, zero ask, zero name, zero anything.

Wes's reaction: I have a question for you too: who are you.

What to do instead: every cold message needs the four basics. Who you are, why you're writing this person specifically, what you want, and how long it'll take. Four sentences. Not three.

059The voice note from a stranger

[a 90-second voice note as the first contact]

Failure: the voice note has no preview, no summary, no skim option.

Wes's reaction: you're asking me to set aside 90 seconds to find out if this is worth 90 seconds. The math doesn't work.

What to do instead: voice notes are for people who already know you. Cold contact gets text, because text can be skimmed in five seconds.

060The Calendly with no context

Hi Wes, here's my Calendly: [link]

Failure: that's the entire message.

Wes's reaction: I do not book calendars on faith.

What to do instead: a calendar link is the close, not the open. Earn the meeting by stating why it matters in two sentences. Then drop the link.

061The 50MB PDF

Hi Wes, attached is our company overview. Looking forward to your thoughts!

Failure: the attachment was 50MB. It crashed Mail.

Wes's reaction: I almost got the meeting just to find out what was inside the file. Almost.

What to do instead: never attach to a cold email. Link to a hosted version. Better, summarize the relevant page in three sentences and link to the rest only if they ask.

062The TypeForm intake as the open

Hi Wes, I'd love to learn more about your needs. Please fill out this 14-question intake form.

Failure: they asked for my time before earning even a second of it.

Wes's reaction: I'm a stranger. You want me to do data entry. The order of operations is broken.

What to do instead: intake forms are for after a real conversation has happened. The cold message earns the conversation. Don't skip steps to save your team work.

063The contact form they pasted into LinkedIn

Name: ___ Email: ___ Company: ___ Pain Points: ___

Failure: they pasted a webform into a DM and asked me to fill it out.

Wes's reaction: I've now seen everything.

What to do instead: if your CRM requires structured intake, your sales motion handles that internally. Never push your intake debt onto a stranger.

064The unscheduled phone call

[received a phone call from an unknown number, voicemail says "Hi, this is Eric from XYZ, I'd love to chat about your outbound, call me back"]

Failure: unsolicited phone call from a stranger to a personal cell.

Wes's reaction: how did you get this number, who hurt you, do not do this again.

What to do instead: phone is for people who have opted into phone. If you got the number from a database, the database does not constitute permission. Don't.

065The fax

[I have received a fax. In 2026.]

Failure: somebody sent me a fax as a cold pitch in 2026.

Wes's reaction: I have a fax machine because of legal documents and that's it. Now I have a sales fax. I am unwell.

What to do instead: novelty is not a strategy. Channels exist for reasons. Fax exists for legal documents. Use channels people are open to receiving on.

066The Slack DM in someone else's workspace

[a stranger DMed me in a community Slack with their pitch]

Failure: they used a community channel as a sales channel.

Wes's reaction: the community has rules. You broke them. I reported you to the community.

What to do instead: if a community is not explicitly for sales, do not sell in it. The reputational cost of getting kicked out for spamming exceeds the value of any deal you would have closed.

SECTION 06Following-up failures (67-80)

067"Just checking in"

Just checking in!

Failure: "just checking in" is the universal "I have nothing new to say but I want to remain in your inbox."

Wes's reaction: if you have nothing new to say, the right move is silence. Silence is a feature.

What to do instead: every follow-up needs new information, a new angle, or a new reason. If you don't have one, wait until you do.

068"Bumping this to the top"

Bumping this to the top of your inbox!

Failure: the metaphor doesn't even work. Email isn't a stack you can re-order.

Wes's reaction: my inbox is sorted by date, not by who screams "bump."

What to do instead: if your message deserves a re-read, the re-read should be triggered by you saying something new. "Wanted to share that we just released X" is bumping. "Bumping this" is just whining.

069The identical follow-up

[same message as the prior one, sent four days later, word for word]

Failure: they did not even change the date stamp.

Wes's reaction: if you can't be bothered to write a new sentence, I can't be bothered to read the old one twice.

What to do instead: every follow-up needs different content. Different angle, different example, different ask. If you copy-paste, you're sending the same message twice and demonstrating that you have no second thought.

070The fifth follow-up

Following up again. Did you see my last message?

Failure: there were four prior messages, three of which were "just checking in," and now we're on five.

Wes's reaction: the fifth follow-up is a confession that you cannot read the room.

What to do instead: two follow-ups, max. After that, you wait three months and try a wholly new angle. If your manager is requiring a fifth follow-up, your manager is wrong.

071The angry follow-up

I've reached out multiple times now and I'd really appreciate the courtesy of a reply.

Failure: anger as a tactic.

Wes's reaction: the courtesy of a reply is earned by writing a message worth replying to. You did not.

What to do instead: silence is a no. Treat it as one. Anger after a no is the fastest way to ensure the no becomes a no in writing, on every channel, forever.

072The passive-aggressive close

I'll assume this isn't a priority for you and stop reaching out.

Failure: the goal of this is to guilt the prospect into responding.

Wes's reaction: correct. It isn't a priority. Glad we agree.

What to do instead: if your closer is designed to manipulate the prospect, you have lost the plot. Closers can be honest: "I'll stop here unless I find a new reason to reach out." That's it.

073The "last attempt" that wasn't

[follow-up titled "last attempt" followed by four more messages over six weeks]

Failure: they cried wolf with the last-attempt label.

Wes's reaction: I can count to five. I noticed.

What to do instead: if you say it's your last attempt, it's your last attempt. Otherwise the words mean nothing and your future closes mean less.

074The "I see you opened my email"

I noticed you opened my email but didn't reply. Anything I can clarify?

Failure: open tracking. Confessing that you're tracking opens makes you sound creepy and hostile.

Wes's reaction: I now know your tool tracks me. I now block your tool.

What to do instead: open tracking is for your internal scoring, not for prospect-facing language. Never mention that you saw an open. Never. The signal is for you, not for them.

075The "I see you read my LinkedIn message"

I noticed you read my message but didn't respond.

Failure: see #74. The same logic but on LinkedIn. Worse, because LinkedIn shows read receipts more prominently.

Wes's reaction: the surveillance angle is unflattering on every platform.

What to do instead: read receipts are not consent to follow up. Treat them as nothing. They cost you trust the moment you reference them.

076The fake deadline follow-up

Hi Wes, our pricing goes up next week, wanted to make sure you didn't miss out!

Failure: the prices did not go up.

Wes's reaction: I marked the date. I checked the next week. The prices were the same.

What to do instead: if you create a deadline, honor it. If you can't honor it, don't create it. One discovered lie is more expensive than 100 deadlines successfully fired.

077The "circling back"

Just circling back on this.

Failure: "circling back" is a cousin of "just checking in" and shares its DNA.

Wes's reaction: if you're circling, the orbit is not productive.

What to do instead: name the thing you're circling about and what's new. "Circling back with the case study you asked for" is fine. "Just circling back" alone is a stalling tactic dressed as a follow-up.

078The "wanted to make sure this didn't fall through the cracks"

Wanted to make sure this didn't fall through the cracks!

Failure: the implication that I am uncoordinated.

Wes's reaction: nothing fell through the cracks. I read it. I chose not to engage.

What to do instead: the cracks framing assumes the prospect is the problem. The prospect is rarely the problem. The message is the problem. Improve the message, not the framing of the silence.

079The 90-day-resurrection

Hey Wes, I know it's been a while, but I wanted to reach out again to see if anything's changed.

Failure: nothing on their side has changed. They just want a fresh attempt.

Wes's reaction: I noticed you returning. I appreciate the patience. I am not buying it.

What to do instead: if you reactivate after months, lead with what's changed on YOUR side. New product, new case study, new founder, new pricing. "Anything changed on your end" is asking the prospect to do the work of selling you back to themselves.

080The "moving on" that doesn't

If I don't hear back from you, I'll assume the timing isn't right and move on.

Failure: the move-on is followed by another message a week later.

Wes's reaction: you said you would move on. You did not move on. You are the boy who cried boundary.

What to do instead: if you say you'll stop, stop. The respect of stopping when you said you would is a brand asset. Burning it for one more attempt is a bad trade.

SECTION 07AI failures (81-90)

081The hallucinated fact

I saw that Sales Connector recently raised a $40M Series B, congratulations!

Failure: Sales Connector is bootstrapped. There is no Series B. There is no Series A.

Wes's reaction: I should be flattered the AI picked a generous number, but mostly I'm tired.

What to do instead: any AI-generated message that references a fact about the prospect needs human verification of that exact fact. Treat AI output like a junior writer with a confidence problem.

082The hallucinated quote

I loved your line "outbound is dead, only inbound matters" from your recent talk.

Failure: I have never said that. I do not believe that. The opposite, actually.

Wes's reaction: the quote was so confidently delivered. Then I read it and felt my own brand briefly slipping out of my body.

What to do instead: AI confabulates quotes constantly. If your tool generates a quote, that quote needs to exist somewhere on the public internet, verbatim, before you put it in a message.

083The hallucinated company

I see you also work closely with Helix Dynamics, exciting partnership!

Failure: Helix Dynamics is not a real company. Or if it is, I have no relationship with it.

Wes's reaction: somewhere in a vector store, my logo is sitting next to a logo that doesn't exist.

What to do instead: if you reference a relationship, that relationship should be visible somewhere I can verify. Press release, podcast, joint announcement. Otherwise it's fabrication and I will catch it.

084The mid-message name swap

Hi Wes, I think your team at HubSpot would benefit from... [later in the same email] ...so John, let me know your thoughts.

Failure: the AI mixed two prospects in one draft.

Wes's reaction: I am Wes at Sales Connector. I am also, briefly, John at HubSpot. The multiverse is exhausting.

What to do instead: AI drafts need a single source variable per message. If your prompt is being asked to merge two prospects' data, the prompt is wrong. Single-prospect, single-pass, human review.

085The "As an AI" confession

Sure, here's a draft email for Wes Lemos: Hi Wes, As an AI assistant, I cannot...

Failure: the prompt leaked into the live email.

Wes's reaction: the AI was so polite about its limitations. The human shipping the AI was not.

What to do instead: any send pipeline needs a regex that catches the obvious AI tells before send. "As an AI" should be a hard fail. "I cannot" in line one should be a hard fail. "I'm sorry" without context should be a hard fail.

086The robotic phrasing

I am reaching out to discuss the potential for a mutually beneficial business relationship.

Failure: this is what AI writes when you tell it to be professional.

Wes's reaction: no human has ever said "mutually beneficial business relationship" out loud. Why are we writing it.

What to do instead: read the draft out loud. If it sounds like a business school case study, it sounds like a robot. Rewrite until it sounds like a person.

087The emoji shotgun

Hi Wes! Hope you're doing great this week. I wanted to reach out.

Failure: seven emojis in three lines.

Wes's reaction: every emoji subtracted credibility. By emoji four I was actively rooting against them.

What to do instead: at most one emoji per message, and only if it earns its place. AI tools default to emoji-spam to feel "friendly." It feels like a tween's diary.

088The AI-ass bullet list

I'd love to discuss how we can help you:

- Streamline your outbound processes

- Optimize your conversion funnel

- Enhance your prospect engagement

- Maximize your team's productivity

- Drive measurable revenue growth

- Unlock new market opportunities

- Accelerate your go-to-market strategy

- Elevate your sales operations

Failure: eight verbs that all mean "do business stuff."

Wes's reaction: I scanned for any specific noun and found none.

What to do instead: if your bullets are all verb-noun-adjective with no concrete number or name, your bullets are doing nothing. Replace with one specific outcome: "We helped the Adler team go from 12 replies a month to 41."

089The em dash sweep

I wanted to reach out , quickly , to chat , if you have time

Failure: four em dashes in one sentence. AI tools love em dashes.

Wes's reaction: the em dash is the tell of our era. They might as well sign it "yours, GPT."

What to do instead: if your draft has more than one em dash, your draft was probably written by AI without revision. Strip them, replace with periods or commas, read again. The cadence usually improves.

090The AI-translated metaphor

I want to put my best foot forward and circle the wagons on this one.

Failure: two clichés in one sentence, neither of them coherent.

Wes's reaction: the metaphor was assembled, not chosen.

What to do instead: when AI mixes idioms, it's because the underlying intent is unclear. Replace with literal language. "I'd like to send you a thoughtful proposal." That's all the metaphor was trying to do.

SECTION 08Special edge cases (91-100)

091The astrology pitch

As a fellow Capricorn, I think we'd really click on a quick call.

Failure: they assumed my sign and used it as a hook.

Wes's reaction: I am not a Capricorn. I do not consent to this conversation. Mercury is not in retrograde, you are.

What to do instead: never invoke pseudoscience as a personalization vector. The reader's reaction is "you don't know me" no matter how charitable they're feeling.

092The fake birthday wish

Happy birthday Wes, hope you have a wonderful year! [later in the message: pitch]

Failure: the birthday was wrong by four months.

Wes's reaction: I appreciate that they tried to celebrate me. I do not appreciate that they got the date wrong AND used it as a sales lever.

What to do instead: never combine personal warmth with a sales ask in the same message. Especially not a fake personal warmth. A wrong birthday is worse than no birthday.

093The "we don't know each other but"

We don't know each other but I just wanted to say hello and ask if you have 15 minutes for a call.

Failure: acknowledging the lack of relationship doesn't earn you a meeting.

Wes's reaction: the awareness was charming for half a second. Then it asked for 15 minutes and the charm evaporated.

What to do instead: the fact that you're cold is not a feature you should announce. Demonstrate value in one line. The cold-ness becomes irrelevant if the line is good.

094The pitch from a "friend"

Hey, I'm a friend of your old colleague Mark from your time at Acme Corp.

Failure: I have never worked at Acme Corp. There is no Mark.

Wes's reaction: they got my entire backstory wrong on the way to faking a friend. The compounding lies are almost impressive.

What to do instead: never invent shared connections. Real warm intros are worth their weight in gold. Fake ones poison every future cold approach you'll ever make to that prospect.

095The advice trap

Hi Wes, I'm a huge admirer of what you've built. Could I get 15 minutes of your time to ask for advice on launching my own startup?

Failure: the advice ask was a setup. The actual ask, revealed later, was for me to invest.

Wes's reaction: I'd have respected the direct ask. I do not respect the bait.

What to do instead: if you want money, ask for money. If you want advice, ask for advice. Don't disguise one as the other. The discovery that you lied is more damaging than the original "no" would have been.

096The fake question

Quick question: have you considered automating your outbound?

Failure: the question is a pitch. There is no curiosity behind it.

Wes's reaction: "have you considered" is sales for "let me tell you why you should."

What to do instead: if you're going to ask a question, ask one whose answer you actually want. "What's the bottleneck in your outbound right now?" beats "have you considered automating?" because the first one earns information.

097The fake survey

Hi Wes, we're conducting a brief 3-question survey on B2B outbound. As a thank-you, you'll receive a free 30-minute consultation with our team.

Failure: the survey is the pitch. The consultation is the close.

Wes's reaction: every "free consultation" is a sales call. We all know. Stop pretending.

What to do instead: if you want to get on a call, ask for the call. Don't disguise the ask as a survey. The disguise insults the prospect's intelligence.

098The MLM

Hi Wes! I love your entrepreneurial spirit and wanted to share an exciting opportunity I'm building. Are you open to a side income stream?

Failure: the side income stream was an MLM. The "opportunity" was for me to recruit others.

Wes's reaction: I am too old, too tired, and too solvent. We are not doing this.

What to do instead: if your business model requires recruiting from your personal network, you do not have a business. Do something else.

099The crypto bro

Wes! I've been crushing it with our new web4 protocol that's about to flip the entire SaaS industry. Want in early?

Failure: there is no web4. The protocol is vapor. The "early" is the pitch.

Wes's reaction: I miss when crypto bros only ruined Discord. Now they DM me.

What to do instead: if your message includes manufactured jargon and breathless tense, the prospect's pattern-match is "scam." That's the right pattern-match. Don't write that message.

100The "would love your feedback" sales pitch

Hi Wes, I have huge respect for what you've built and I'd genuinely love your honest feedback on something I've been working on. No agenda, just want a sharp eye on it.

[Then, after the call is booked, a 30-minute pitch deck for me to invest, partner, integrate, retweet, or ideally all four. No mention of feedback. No question asked of me. Calendly was for them.]

Failure: the feedback was the bait. The meeting was the pitch. Every word of "no agenda" was an agenda.

Wes's reaction: this is the boss-level cold message. Every other entry on this list is honest about what it is. This one wears a costume. The costume is "I respect you," and once you're in the meeting and realize the respect was a lever, the entire interaction sours, the brand sours, every future contact from that company sours, and you remember it for years. I remembered it for two before I wrote this. The damage from a bait-and-switch lasts longer than any deal that could have come out of it.

What to do instead: if you want feedback, ask for feedback and stop. If you want to pitch, pitch and stop. If you want both, pick one to do this week and the other to do six months from now after the first conversation actually happened. The single most important sentence in cold outbound is also the simplest: be honest about what you want. The trust you build by being plainly clear about your ask is the only durable asset in this whole game. Everything else, including this list, is just receipts.

SECTION 09Postscript

If you've made it to 100, you've probably recognized a few of your own messages. That's fine. Everybody has sent a bad cold message. The first step is reading 100 of them in a row and letting the embarrassment do its work. The second step is rewriting every message you have queued for next week.

If you want help doing that systematically, that's what we built Sales Connector for. But this list works without us. Just don't write any of these.

Wes