[OW 3]: 📫 👍 Quick Teardown of a Great Cold Email I Received
Outbound Weekly 3.13.22
On this week’s edition of Outbound Weekly we’ll take a quick look at a great cold email I received and what made it great.
Btw - want to listen to in-depth, audio case studies outbound sales campaigns? Check out my podcast here: Outbound Metrics
Here’s the email…
FYI - Dylan was reaching out on behalf of the company’s CEO for a podcast interview.
So what made this an effective email?
A. Subject Line - Dylan knows that I publish a podcast and used an episode number in the subject line to get my attention. This subject line is. a lot different than anything else in my inbox.
B. Opener - He mentions specific parts of the episode that he mentioned in the subject line to hold my attention.
C. Value Add - He says that he’ll drop a link to my podcast in the company newsletter. This helps get my podcast in front of a new audience and increase its reach. This is a value add to me.
D. Call to Action - His ask is to introduce me to someone in the SaaS space. This gets me curious…curious enough to respond so I can figure out who this mystery person is.
This email was effective but I don’t think it’s necessary in every context to do this level of research. This type of outreach can be effective for content creators but most people don’t create content.
For example, if you’re selling enterprise B2B software it would serve you better to focus intently on the pain your prospects are experiencing, the specific problem that you solve, and the results that you can deliver.
If you can package that info up with scroll-stopping personal facts about someone (make sure it’s not too creepy) without wasting a ton of time doing “research”, that’s great.
If not, focus on nailing down your persona and messaging while finding prospects that are an ideal fit for what you offer. Why should they buy and why should they buy now?
That’s all folks! Feel free to reply with any questions or comments. If you got value out of this newsletter, please forward it to a friend.
Thanks for reading,