About SaaS Email Marketing Tools

Elena Ward is the pen name of the person who writes and maintains this site. The name is a byline, not a résumé: there is no claimed employer, no claimed years in the industry and no claimed certification behind it. What the byline does promise is consistency. Every page here is written and checked by the same editor against the same method, and it is described below so you can judge the work by what it shows rather than by who is signing it.

What this site covers

SaaS Email Marketing Tools is about email for software companies: welcome and onboarding sequences, trial-conversion messages, activation nudges, product-update announcements, billing-aware reminders and retention campaigns. The core coverage is the tools built for that work, namely Loops, Customer.io, Userlist, Encharge, Vero, Bento, Intercom and Ortto, along with the general-purpose senders that SaaS teams often start on, such as Mailchimp, MailerLite, Brevo and Kit. You will find head-to-head comparisons, alternatives pages for a tool you are thinking of leaving, and guides to email for particular SaaS audiences and jobs.

How the editor researches

The work is desk research on public material. That means reading vendor pricing pages, product documentation, help-center articles and changelogs, then recording what each page actually says. Where a vendor's price is driven by a slider or selector, such as a subscriber count, the editor moves the control and writes down the figure displayed at each step, instead of guessing between steps. When a number cannot be read from a public page, for example a plan that says "talk to sales," the page says so and leaves the number out.

Prices are re-checked on the date shown at the top of each comparison. Screenshots are captured from the live public pricing page on the date in the caption and are not edited or cropped to hide anything. If a capture fails, the page carries a note saying no screenshot is shown, instead of using a stand-in image. Pricing pages change often, so treat any figure here as a snapshot and confirm it on the vendor's own page before you buy.

How tools are compared

Each comparison starts with the billing unit, because it decides the real cost: subscribers, profiles, users, seats, or email volume. Then the page looks at what the plan includes and where limits bite, such as send caps, contact caps, number of automations or events, and which features sit behind the next tier. After that come automation depth, how segmentation and data models work for people and companies, integrations and API access, deliverability-related features that vendors state publicly, and the effort of moving in or out. Prices are shown at several list sizes with the arithmetic visible where a vendor gives a formula, and every comparison ends with who should pick which and what to expect when migrating.

How a price gets onto a page

The path is the same every time. The editor opens the vendor's current public pricing page, records each plan name with the figure shown next to it and the billing basis, and notes whether the page was showing monthly or yearly prices. Promotional offers, such as a first-year discount, are written down separately from list prices, because a promotion ends and the list price is what you pay afterward. Taxes, regional currency conversion and negotiated enterprise discounts are left out, since they differ by buyer. When two vendors bill on different units, the page picks a scenario, such as 10,000 contacts sending four emails each, and states its assumption so you can swap in your own numbers.

Quotes and figures that cannot be matched to the vendor's page are dropped. That rule is why some tables on this site have gaps where a vendor does not publish a price past a certain size; a visible gap is more useful than a guess.

Where to start

If you are choosing between two tools you already know, go to the comparisons hub for a verdict, a side-by-side table, costs at three list sizes and migration notes. If you are leaving a tool, the alternatives index lists what to move to and who it suits. If your question is about an audience or job, such as onboarding, billing notices or accessibility updates, the guides match tools to that work. Everything links back to the method on the how we evaluate page.

What the editor does not claim

The comparisons describe published capabilities and prices. The editor does not claim to hold accounts with every vendor, to have run your kind of campaign, or to have measured inbox placement or open rates. No customer quotes, ratings, review counts or test results appear on the site unless they come from a linked source. Where a vendor's page is vague, the page says that.

Why a tool appears on some pages only

Not every tool belongs on every page. A sender built around billing events, such as trial-ending reminders or failed-payment notices, is covered on the pages about lifecycle, billing and retention work, and left off pages about newsletters or creator audiences where its documented strengths do not apply. General-purpose senders appear more widely, because onboarding sequences and product announcements are within what their docs describe. The same source checks and scenario criteria apply to every tool on a page, whichever pages it appears on. The full method is on the how we evaluate page.

Corrections

If a price or feature on a page no longer matches the vendor's current public page, the vendor's page is the authority. Each comparison shows the date its figures were checked, so you can see how old a number is before relying on it. You can start with the comparisons hub or the alternatives index.