BUYER'S CRITERIA
9 cold email software factors that actually matter
Not a vendor ranking. The factors worth evaluating before choosing any cold email platform — whichever one you end up picking.
10 min readWHY THIS MATTERS
Why evaluating the right factors matters more than comparing feature lists
Most cold email platforms support the basics — sequences, sending, some form of reporting. A feature-list comparison between them tends to produce a near-tie, because almost every platform can check almost every box at a surface level. What separates them isn't whether a feature exists, but how it actually works underneath: whether a cost is visible before it's spent, whether a safeguard actually blocks a bad send or just logs a warning, whether data control is a real option or a marketing phrase.
The nine factors below are the ones worth evaluating on that basis, in roughly the order they tend to matter — from cost visibility and deliverability safeguards through to compliance documentation. Each factor is framed generically here, evaluable against any platform, not just one.
01
Enrichment cost transparency
Whether the platform shows cost per enrichment action before it runs — a line-item ledger showing provider, cost, and status — or bundles enrichment into opaque tier pricing with no per-action visibility.
More on enrichment ledger.
02
Pre-send deliverability safeguards
Whether SPF, DKIM, DMARC, inbox warmup status, and list verification are checked and can actually block a campaign from launching, or whether problems are only discovered after sending.
More on pre-send checklist.
03
Self-hosting and data sovereignty
Whether the platform offers a genuine self-hosted deployment option — a VPS running via Docker — for direct data control, or is SaaS-only with no path to hosting your own data.
More on self-hosting.
04
Inbox warmup approach
Whether warmup runs on a real peer-to-peer network of inboxes with gradual ramp logic, or is a synthetic or basic implementation that doesn't build genuine sending history.
More on warmup guide.
05
Pricing model
Per-seat, per-client, or flat/workspace pricing — and whether the headline price actually reflects the real monthly cost, or whether add-ons and separate product lines push the real number higher.
More on no per-seat pricing.
06
List verification
Whether email addresses are verified — format check, MX record lookup, and mailbox check — before sending, to protect bounce rate and sender reputation.
More on email verification.
07
Inbox rotation and multi-inbox management
Whether sending can be distributed automatically across multiple connected inboxes to manage volume and spread reputation risk, rather than concentrating all sends on one address.
More on inbox rotation.
08
Reply handling
Whether replies are captured in a unified inbox with full thread view, or scattered across individual mailboxes with no single place to track a conversation.
More on unified reply inbox.
09
Data processing and compliance documentation
Whether a vendor publishes a clear Data Processing Agreement stating where data is hosted and processed, rather than leaving that information undocumented.
More on Data Processing Agreement.
CONFIRM, DON'T ASSUME
Two of these are worth checking directly, not just reading about
Authentication status and domain reputation aren't static — they can change after a platform is chosen, not just before. Whichever platform you evaluate or already use, both are worth confirming directly rather than assumed from a sales page.
Check SPF, DKIM, and DMARC are passing → DNS Health Checker
Check a domain's current standing → Blacklist Checker
WHERE FORGESEND LANDS
ForgeSend's approach to these nine — one option among several
This isn't the only correct way to answer these nine questions, and ForgeSend isn't positioned here as the automatic right pick for every team. It's one option, evaluated against its own criteria:
Enrichment cost transparency
A line-item enrichment ledger logs provider, cost, and status for every action before it's spent.
Pre-send deliverability safeguards
A pre-send guardrail checklist validates SPF, DKIM, DMARC, warmup status, and list verification, and blocks launch on failure.
Self-hosting and data sovereignty
A genuine self-hosted deployment via Docker on your own VPS, alongside a cloud tier hosted in the UK.
Data processing and compliance documentation
A published Data Processing Agreement covering UK GDPR directly for the cloud tier.
Whether that combination fits depends on the other eight factors mattering the same way for your team that they do here — worth weighing against your own priorities, not taken as given.