Lemlist deserves credit for two things: it made "personalise this properly" a mainstream expectation, and it treated multichannel as normal rather than exotic. Any alternative you consider is competing with that inheritance.
So this is not a takedown. It is a guide to what actually differs underneath, because on a feature grid most of these products look interchangeable and they are not.
Question one: where do your leads come from?
This is the fork that decides everything else.
Outreach-first platforms assume you arrive with a list, and offer a B2B database to help. Those databases are assembled from corporate sources, which makes them genuinely strong for named roles at companies with a real web footprint, and structurally weak for the businesses many teams actually sell to: the trades, clinics, salons, independent retailers, small agencies and two-van operations that live on a map rather than in an org chart.
If you sell to the second group, no amount of personalisation tooling helps, because the constraint is that the right people are not in the list.
The test: run the exact search you sell into. Not their demo query. Count the results with a live website and a verified email. If that number is small, the database is your bottleneck and a different sequencer will not change it.
The alternative shape: live discovery, where the platform searches map and directory sources at request time. Contacts are current because they were found seconds ago rather than refreshed on a cycle, and they have not been sold to everyone else in your category.
Question two: is deliverability included or adjacent?
Almost every outreach platform now lists warm-up. The differences are in how it behaves.
Three things to ask, in order of how much they matter:
Does warm-up run continuously? Reputation decays, and a mailbox whose only outbound traffic is cold email has a sending profile that looks nothing like a normal one. Warm-up should keep running underneath live sending, not stop once setup is "complete".
Does verification run at send time? Verification at import is necessary and insufficient. Business email data decays at roughly 20 to 30% a year, so the address you verified in March may be gone by September. The check that protects your bounce rate is the one immediately before the send.
Is per-mailbox health visible? An aggregate deliverability figure hides the single mailbox that is quietly failing and dragging the campaign down. You want each one visible, with the ability to pull it out of rotation and reroute automatically.
If the answers are no, no, and no, you do not have a deliverability layer. You have a warm-up checkbox. Our deliverability checklist covers what a real one looks like.
Question three: what happens after someone replies?
This is the one people underestimate, because it only becomes painful when things start working.
Sixty replies arrive. Some are interested, most are "not right now", a few are objections worth answering. An outreach platform gives you an inbox. A pipeline gives you a reason to look at the March "not now" again in September.
Without stages, deal values and notes attached to the lead, the follow-up work quietly falls to memory, and memory loses. The teams who feel this most are the ones who succeeded at the sending part.
What to look for: a CRM pipeline built into the same product, not a CRM integration you configure. One record, one place a lead's history lives.
The multichannel trap
Lemlist popularised LinkedIn steps alongside email, and it is genuinely a good idea. But there is a failure mode that a feature list will never show you.
If your channels do not share a lead record, multichannel becomes multi-contacting. The prospect gets your LinkedIn note on Tuesday and your cold email on Wednesday, each opening with a different framing of the same pitch. There is no setting that prevents this. The only fix is architectural: one record, and a reply on any channel stopping the sequences on all of them.
Before you buy anything multichannel, ask directly: is this one lead record or two lists? It is the single most useful question in the whole evaluation and it takes ten seconds.
Comparing on the right axes
| Axis | Ask | Bad answer |
|---|---|---|
| Lead source | Where do contacts come from? | "Our database" with no coverage of your market |
| Freshness | When was this record last confirmed? | "We refresh quarterly" |
| Warm-up | Does it run continuously? | "It's part of onboarding" |
| Verification | Does it check at send time? | "On import" |
| Channels | One record or two lists? | "They sync" |
| Replies | Is there a pipeline or an inbox? | "You can integrate a CRM" |
| Pricing shape | Metered or included? | Credits for verification |
Where Leads Ranger fits, and where it does not
We are discovery-led. Businesses are found live from map and directory data rather than served from a stored database, verified on arrival and again at send time, and worked through email, WhatsApp and LinkedIn that share one lead record with a built-in CRM pipeline behind it. Warm-up runs continuously with per-mailbox health and automatic failover.
Where we are the wrong choice, stated plainly: if you need LinkedIn touches interleaved as steps inside a single automated email cadence, we run LinkedIn as its own campaign sharing the same pipeline, which is a different shape. And if you prospect named corporate roles from a warehoused B2B database, a database-led platform will serve you better than live discovery will.
If your buyers are businesses you could drive to, the discovery argument is the whole difference. Everything is free while we are in pilot, so the honest test is to run your own search and count what comes back.