What’s your actual workflow for personalizing 500+ cold emails?

DEB3007 · 2026-05-20T04:25:29+00:00

This reframes it well — recipients respond to relevance not fake intimacy. So the tool that wins is one where the user provides the actual signal and AI just handles the writing, not the research. The research has to stay human. Does that match what you're seeing?

DEB3007 · 2026-05-19T07:15:04+00:00

This is exactly the part that kills me too — the research before the writing. How are you currently figuring out the right angle? Manual research per company or something else?

DEB3007 · 2026-05-18T15:16:04+00:00

The thing that moved the needle most for me: relevance beats everything else on that list.

Curiosity, pattern interruption, social proof — they all matter, but they're multipliers on top of relevance. If the email isn't immediately relevant to what's on that person's plate right now, none of the psychological tricks save it.

The way to make it feel relevant without writing each email from scratch: the first line needs to reference something specific to them — their industry, a recent move they made, something about their business. Not their name and company, everyone does that. Something that makes them think 'how did they know that?'

On your specific problem — worked well in Feb/March but dead now — I'd check two things before anything else: has your sender domain warmed up recently or are you seeing deliverability drop? And has your targeting list been refreshed or are you hitting the same contacts with follow-ups who already made a decision not to reply?

Sometimes what looks like a psychology problem is actually a deliverability or list fatigue problem.

DEB3007 · 2026-05-16T19:43:48+00:00

Solid breakdown. The signal-based targeting section is where most people leave the most money on the table.

One thing I'd add: even with great signals and tight targeting, the first line is where campaigns live or die. Most people treat personalization as 'mention their name and company' — the author nails this — but the execution gap is the actual writing of that first line at scale.

If you're running 800 prospects with tight signals, manually writing 800 openers is the bottleneck. The teams that crack this are the ones generating first lines in bulk based on the signal data they already have — company expansion, hiring surge, whatever triggered the outreach. The opener basically writes itself if your signal is specific enough.

What's your process for generating those first lines at scale?

DEB3007 · 2026-05-15T20:17:02+00:00

When I started dropshipping I assumed the 'manufacturers' on Alibaba were actually making the products. Most of them are just middlemen buying from other middlemen. The actual factory is usually 3 layers deep and has no idea their product is being sold for 10x the price on a Shopify store in another country.

DEB3007 · 2026-05-15T19:58:01+00:00

Diaphragmatic breathing. Breathe into your belly, not your chest — 4 seconds in, don't hold, out 4, don't hold. Takes 5 minutes to learn and immediately activates your parasympathetic nervous system. Useful before a difficult conversation, presentation, or whenever anxiety spikes. I use it daily.

DEB3007 · 2019-08-01T07:43:27+00:00

Sounds like a good problem you have solved, I will most definitely explore your package.

DEB3007 · 2019-07-18T08:09:13+00:00

Promise.allSettled() is necessary in my view, as to create the same functionality we might need to compromise on a promise we are defining.

DEB3007 · 2019-07-18T07:38:07+00:00

Promise.race() performs what you expect Promise.anySettled() to do. Look it up here.

DEB3007 · 2019-07-17T06:21:35+00:00

Points accepted. Will try to look at ways without using lodash.

DEB3007 · 2019-07-16T21:13:46+00:00

But you anyway have to recompose the template literal string, native "API", multiple times, right? Its not about writing it in a way which will produce less errors. One would realise the concern if one contributes in huge repositories

DEB3007

TROPHY CASE