How We Evaluate SaaS Email Tools

This page is the rulebook behind every ranking, price and screenshot on the site. If a table here disagrees with a vendor's own page, the vendor's page wins, and the notes below explain how to tell how old a number is and where it came from.

The criteria we rank on

A SaaS team usually wants the same few answers from an email tool, so the comparisons are organised around them rather than around feature counts:

• Billing unit. Whether the vendor charges per contact, per profile, per user, per seat or per email decides what happens to your bill as the list grows, so it is the first thing recorded.
• Event and data model. Can the tool trigger from product events sent by API, and does it understand companies as well as individual people?
• Automation depth. Branching, wait steps, goals and exit conditions, as described in the vendor's documentation.
• Transactional boundary. Whether password resets and receipts can go through the same account, or need a separate sender.
• Integrations. Only the integrations a vendor names on its own pages are counted.
• Switching effort. What has to be rebuilt when you move in or out: lists, templates, automations and tracking code.

Each tool is placed by the job it suits, which is why a lean SaaS sender and a CRM-linked platform can both be recommended on the same page for different readers.

How we read prices

Every figure is taken from the vendor's public pricing page on the date shown next to it. Where a price depends on a slider, such as subscribers or contacts, the editor moves the slider to a stated size and writes down what the page displays at that size, with the date. Loops is an example: its pricing page shows a free plan covering up to 1,000 contacts, $99 a month at about 10,000 and $249 at 50,000, and those are slider readouts, not a published formula. Figures that sit between two readouts are not interpolated.

Monthly and annual prices are kept apart, and a first-year promotion is never presented as the list price. Taxes, currency conversion and negotiated enterprise discounts are left out. When a vendor shows only "contact sales," or the page would not load cleanly, the comparison leaves the number out and says so.

A worked example: reading a slider

On its pricing page Loops shows a free plan for early products, limited to 4,000 sends in any rolling 30 days to your 1,000 newest contacts and carrying a small "Powered by Loops" footer. Drag the slider to 9,998 subscribers and the Growing Audience plan reads $99 per month; at 49,989 it reads $249. We write down each readout with the date and the plan name, then describe what the plan includes separately: unlimited sends to subscribers, transactional sends to users outside your audience, and no per-seat charge. Keeping price and scope apart stops a cheap-looking number from hiding a limit.

How a list gets ordered

Order follows fit for the job named in the page title, not price or popularity. The tool at number one is the best match for that audience, and every entry says why in plain words. When two tools fit equally well, the one whose free plan covers a realistic early volume goes first, because that is what a team can test without a card. Lists are fixed in the source, so they do not reshuffle between visits, and a tool that does not fit a page's job is left off that page rather than ranked low.

Screenshot policy

A screenshot on this site is a capture of the vendor's public pricing page taken on the date in its caption, and the caption links the page it came from. We do not crop out prices, edit figures or reuse one vendor's image for another. If a capture fails, the page carries a short note saying that no screenshot is shown, rather than a stand-in image. A screenshot proves what a page showed that day; vendors change pricing without notice.

Coverage: why a tool appears on some pages only

A tool is included only on pages whose job matches what its own documentation describes. A sender built around billing-triggered SaaS email, such as trial, renewal and failed-payment messages, appears on the lifecycle, billing and retention pages and is left off pages about newsletters or unrelated audiences. A general-purpose sender with documented onboarding and automation features appears more widely. Every tool on a page is checked against the same criteria and the same pricing method described above, whichever pages it appears on.

Who is behind the byline

Elena Ward is a pen name. The editor behind it does desk research on public sources and does not claim to hold an account with every vendor, to have migrated a list, or to have measured inbox placement or open rates. For that reason no test results, customer quotes, star ratings or review counts appear on the site unless they link to a real source. More on the editor is on the about page.

The limits of this method

Reading public pages tells you what a vendor publishes: plans, limits, named integrations and documented behaviour. It cannot tell you how fast support answers, how a sending domain performs in the inbox, or how pleasant an editor is after a month of daily use. Where a recommendation leans on one of those things, the page says it is a judgement and not a measurement. If your decision depends on deliverability or on a specific integration, use the vendor's trial to test it with your own data before you move a list.

Corrections

If a figure no longer matches the vendor's page, treat the vendor as correct. The date beside each price tells you when it was last read, and the comparisons and alternatives hubs show where each tool is covered.