Guides

How to Write a Cold Email When You Don't Know Their Pain

Blip AI Team6 min read

You don't need to know a prospect's exact problem to write a good cold email. Pair a fact you can see with one question they can correct. Templates included.

Quick answer: You don't need to know a prospect's exact problem. Open with something you can actually see about their company (a hire, a launch, a new market), connect it to one likely problem, and ask whether it applies. One fact and one question per email. If you guess wrong, their correction becomes your discovery call.

Why guessing their pain point backfires

A thread in r/sales this week asked a question every founder and new rep runs into. Everyone says cold emails should focus on a specific problem, but how do you know which problem a prospect has before you've spoken to them? And if your service solves several, which one do you lead with?

The best answers agreed on one thing: you don't need to know the problem. You need a credible reason the conversation might be relevant. Listing every pain your product solves reads as generic, and claiming they have a problem you can't see reads as presumptuous. Both get ignored.

The fix: an observable fact plus one hypothesis

The most upvoted reply split the email into two parts:

  1. A fact you can see. Something true and public about them: they're hiring several sales reps, they just launched in a new country, they opened a second location, their careers page lists ten open support roles.
  2. A hypothesis, asked as a question. A problem that fact often causes, asked so they can easily say no: "That often makes handoffs between prospecting and closing inconsistent. Is that something you're dealing with, or is the process already standardized?"

The fact makes the email specific. The question makes it easy to reply, even if only to correct you, and a correction tells you what their real problem is.

Cold email templates that don't guess

Observation + question

Hi [Name], I saw [company] is hiring [observable fact]. When teams grow like that, [likely problem] tends to show up. Is that on your radar, or have you already got it covered?

Peer proof

Hi [Name], we recently helped [similar company] with [specific result]. Not sure it applies to [company], but if [related situation] sounds familiar, happy to share how they did it.

The correction invite

Hi [Name], my guess is that [hypothesis] is harder for [company] than it looks from the outside. Am I right, or is the bigger headache somewhere else?

Keep each one under about 100 words, with one question and no feature list.

Test hypotheses instead of guessing once

One reply described a simple way to stop guessing: pick three triggers you can see from the outside, write one email per trigger with one likely problem each, and send each version to 30 to 50 prospects from the same customer profile. Whichever gets replies tells you which problem is real for that market.

Others suggested doing the same across a sequence: each follow-up tests a different problem, instead of cramming them all into the first email. That's the opposite of the common advice to name two or three pain points up front, and it's easier to read.

Make sure the emails arrive

None of this matters if the email lands in spam. If your prospects use Gmail, Google's sender guidelines apply (checked on 5 October 2026):

  • Every sender needs SPF or DKIM set up for the sending domain, a TLS connection, valid DNS records, and spam complaints in Google Postmaster Tools kept below 0.3%.
  • Senders of more than 5,000 messages a day also need SPF, DKIM and DMARC, a From: domain aligned with SPF or DKIM, and one-click unsubscribe on marketing messages.

Sending fewer, genuinely relevant emails is also the simplest way to stay well under that complaint rate.

How Blip AI speeds up personalized cold email

The method above works because every email has a specific first line, and specific first lines take time to write. The research is worth it; typing every opener from scratch is where volume dies. We build Blip AI, a dictation app that types polished text into any app with a text field, including Gmail, Outlook on the web, LinkedIn and your sales tool in the browser.

  • Say the personalized opener. With the prospect's site or LinkedIn open, click into the email, hold Fn on Mac, Ctrl + Win on Windows or Ctrl + Super on Linux, and say the fact and the question. Speech runs at about 150 words per minute against about 52 for the average typist, so the opener takes seconds. More on the numbers in is voice typing faster than typing?
  • Clean text, not a transcript. Blip removes filler words and fixes punctuation and formatting, so it reads like a written email. Read it once before sending.
  • Draft replies with Action Mode. When a prospect answers, start with "Hey Blip" and describe your reply, for example "Hey Blip, thank them for the correction and ask if 15 minutes on Thursday works to hear more." Blip drafts the email for you to check and send.
  • Company and product names spelled right. Add your product name and target company names to Blip's dictionary.
  • History stays on your device. Dictation history is stored locally, not on Blip's servers.

Blip runs on Mac, Windows, Linux, iOS and Android, and the free plan includes 2,000 words a month. Download Blip AI. Once the replies start coming in, see how to spend less time on email.

FAQ

How do you write a cold email if you don't know the prospect's problem? Lead with an observable fact about their company, such as hiring, a launch or expansion, then ask whether one problem that fact often causes applies to them. You're testing a hypothesis, not claiming to know their pain, and a correction is still a useful reply.

How many pain points should a cold email mention? One. Mentioning several makes the email generic and harder to answer. Test different problems in different emails or across follow-ups in a sequence, and let the replies show which one is real.

What should the first line of a cold email be? Something specific and true about the recipient that you couldn't have copied into anyone else's email, like a recent hire, launch or announcement. Compliments and introductions about yourself can wait.

How do I test which pain point works in cold email? Pick three triggers you can observe, write one email per trigger with one likely problem each, and send each version to 30 to 50 prospects from the same customer profile. Compare reply rates and keep the version that gets real conversations.

What do I need to set up so cold emails reach Gmail inboxes? Under Google's sender guidelines, every sender needs SPF or DKIM, a TLS connection and spam complaints below 0.3%. Senders of more than 5,000 messages a day also need DMARC, an aligned From: domain and one-click unsubscribe for marketing email.

Keep reading