I’ve been A/B testing different message lengths with my outreach, and I’m getting mixed signals (pun intended).
My gut tells me that shorter is better. Like, if I keep my message to 2-3 sentences with a strong hook and a clear ask, people are more likely to respond because the friction is lower. Less to read, easier to reply to.
But then I’ve sent some longer messages (like 4-5 sentences, with a bit more context about why I’m reaching out and what I understand about their situation) and gotten replies too. Sometimes the longer ones perform better depending on the recipient.
I’m trying to figure out if there’s actually a data-backed answer here or if it’s just context-dependent. Like, maybe shorter works for ultra-senior people (C-suite) but longer context works for mid-market buyers who want to understand the full picture? Or is that just me rationalizing inconsistent results?
Also, I haven’t been totally systematic about this. I’ve been sending different lengths to different people without controlling for who I’m messaging. So my data is probably contaminated—I could be accidentally comparing “tight message to a VP” against “longer message to a manager,” which tells me nothing useful.
Have you guys run controlled tests on this specifically? And if so, what actually won. Did shorter win across the board, or did it depend on something else—like the prospect’s seniority, industry, or the actual content of the hook?
Okay, so this is partly true and partly a red herring. Message length doesn’t matter. Hook strength matters. The length just needs to be whatever it takes to deliver that hook.
I’ve seen 1-line messages convert at 15% and 6-line messages convert at 18%, and vice versa. The common denominator in high-converting messages isn’t length—it’s specificity. The hook was so good that it made the prospect go “wait, how does this person know this about me?”
Here’s my system: I write the shortest version of my hook that still makes the recipient feel seen. If I can do it in 1 sentence, I do. If I need 2-3 to properly set context, then 2-3. Then I add one call to action. That’s the message structure.
What people mess up is they write a long message with a weak hook and think “oh, I need to pad it with more background.” No. You need a stronger opening line. Cut everything else.
So stop thinking about length as the variable. Start thinking about: “Does this opening line make this person WANT to respond?” If yes, send it (whatever length). If no, rewrite the opening.
One more thing—seniority does matter, but not in the way you think. C-suite doesn’t respond well to short and vague. They respond to short and specific. “Hey, quick question” is short but vague. “Saw your company just raised Series B and hired 3 VPs of Sales—congrats, and curious how you’re structuring the GTM for that” is short and specific. The second one wins.
From a testing perspective, you’re right that your current methodology is contaminated. To get real data, you need to control for at least three variables: prospect seniority, industry, and company size. Then test message length while keeping those constant.
What the data actually shows: message length has a weak correlation with reply rates. Hook specificity has a strong correlation.
In other words, you could send a 1-line message or a 5-line message, and if the hook is equally strong, your reply rate will be almost identical. But if your hook is weak, length doesn’t help. Adding more words to a weak hook just gives the prospect more opportunities to say no.
So the answer to your question: focus 80% of your energy on the hook. Spend 20% optimizing length to whatever feels most natural for the hook you’ve written. You’ll get better results that way.
I tested this pretty rigorously last quarter, honestly. I sent 100 short messages (2 sentences) and 100 longer messages (5-6 sentences) to matched segments—same titles, same industries, same company sizes.
Short: 3.2% reply rate
Long: 3.4% reply rate
So basically identical. The difference wasn’t meaningful. But when I looked at which messages got replies—across both groups—the common thread was that they all had something specific about the person or company. The length was irrelevant.
I switched to writing whatever length made sense for the hook, and my overall rate went to 4.1%. So yeah, hook first. Length is just the vehicle.
What’s your hook strategy right now? Are you going after specific company signals or more generic “I help people like you” stuff?
Great question, and here’s the simple answer: length doesn’t matter if your personalization is specific.
Think about it from the prospect’s perspective. If you send them something that’s clearly generic (whether it’s 1 line or 10), they’re not reading past the first sentence anyway. But if your opening line shows you understand something about them specifically, they’ll read the whole thing, whether it’s 2 sentences or 2 paragraphs.
So here’s my advice: write to the hook, not the line count. If your hook requires 1 sentence to land, send 1 sentence. If it needs 3, send 3. But every word should be there for a reason—none of it should be filler (like “hope you’re having a great day!”).
Also, test this properly by keepingeverything else constant and just varying length. Otherwise you’re not learning anything actionable.
Quick safety note: if you’re testing message variants, make sure you’re not sending multiple versions to the same prospect. That’s a fast way to get flagged as spam or pestering someone.
Best practice: decide on a segment, send version A to half of it, version B to the other half, wait for results, then iterate. Don’t test on the same person twice.
This is actually something you can measure quite precisely if you have your data organized right. Pull your message variants into a sheet, tag them by length, and compare reply rates.
But actually, here’s what I’d recommend: instead of testing length directly, test hook type. Like, message type A: recent job change hook. Message type B: company milestone hook. Message type C: posted about a problem I solve.
I bet you’ll find that the hook category matters way more than message length. And once you know your strongest hook type, you can write it however long it needs to be.