About · Method
About This Publication
An independent editorial project covering automation workflows for subscription businesses — written by practitioners, priced from official pages.
What we do
AI Email Marketing Automation publishes workflow-first guides to lifecycle email: onboarding sequences, trial nurture, billing triggers, dunning, upgrades, cancellations, and winback. Every comparison starts from the question a SaaS team actually asks — which tool runs this workflow reliably at 2 a.m. — rather than from feature checklists. The homepage comparison explains the fit of each platform for those jobs.
How we evaluate
We compare trigger depth, lifecycle coverage, AI assistance, segmentation, and pricing fairness. Billing-awareness carries extra weight because this site focuses on subscription workflows; commerce and creator teams should use the wrong-fit notes and re-rank for their own needs.
Verification policy
We publish only pricing figures taken from official vendor pricing pages, each linked beside the claim. Our verified pricing snapshot lists the current confirmed numbers for eleven platforms — Brevo, Loops, Resend, Customer.io, ActiveCampaign, Mailchimp, Klaviyo, Drip, MailerLite, Resend marketing, and Kit — with deep dives in our ten vendor guides. Where we cannot verify a figure, we say so plainly and direct readers to the vendor. Figures were last reviewed in September 2026; vendors change prices, so the linked official page is always the authority.
Independence and funding
This site is written for readers, not vendors. Rankings come from the five-axis rubric published on this page, and outbound links go to official vendor pages so every figure can be re-checked in one click. Where a specialist fits better — commerce flows, creator funnels, pure transactional APIs — we say so explicitly on the page.
Vendor guides such as our Brevo guide, Loops guide, and Resend guide — joined by seven more profiles covering Customer.io, ActiveCampaign, Mailchimp, Klaviyo, Drip, MailerLite, and Kit in our guides index — describe real product capabilities without inventing features. If a capability matters to your decision, confirm it on the vendor's official documentation before purchasing.
Method · the five axes
The scoring axes, defined
The same five axes are applied to every tool on the homepage comparison, in the same order, with the same weights. The weights are deliberately not neutral. Billing-awareness sits inside trigger depth and pricing fairness, which is why billing-native suites rise for subscription teams while broadcast-first platforms sink — through no fault of their own. Commerce and creator programs should invert the top two weights and re-rank accordingly.
| Axis | What it measures | Weight |
|---|---|---|
| Trigger depth | Payment, subscription, and product events — payment succeeded, trial ended, seats changed — not just list joins and link clicks | Highest |
| Lifecycle coverage | Whether one platform runs the five stages end to end: welcome, nurture, convert, retain, win back | High |
| AI assistance | Whether AI drafts whole sequences, branches, and send logic — or only suggests subject lines and copy variants | Standard |
| Segmentation | Billing state, plan tier, and usage as first-class fields, versus flat tags maintained by hand | High |
| Pricing fairness | Whether growth itself is taxed: per-contact climbs versus pay-per-send models and unlimited contact storage | Highest |
A tool can be excellent and still rank lower here. A broadcast platform with perfect deliverability tooling and weak billing triggers will lose to a billing-native suite on this rubric, and the guide will say exactly that — along with the audience for whom the ranking should be thrown away.
Scope · what we are and aren't
What this site is — and isn't
What it is
- A workflow-first comparison of 15 automation tools for subscription teams
- Ten vendor guides with pricing pulled from official pages and dated
- A verified pricing snapshot covering eleven platforms on one page
- Forty-eight staged operational debates with pinned editorial takeaways
- An editorial rubric with its weights published on the page itself
- A published rubric you can disagree with, sitting on the page itself
What it is not
- A user forum — there are no accounts, posts, member counts, or votes
- A review site — nothing here is a reader testimonial or customer quote
- A paid-placement marketplace — no vendor pays for coverage or placement
- A pricing guarantee — the linked vendor page always wins over our number
- An enterprise procurement guide — the reader is an operator or founder
- A feature encyclopedia — unsupported capabilities stay out of the copy
People · who does the work
Who writes this site
Editorial
Elena Markovic is the pen-name editor for this site. She reads vendor pricing pages, documentation, and changelogs; records the check date for each claim; and rewrites comparisons around the workflow a SaaS operator needs to choose. She does not claim to have run campaigns or accounts with the vendors covered here.
Research
Pricing and capability claims are checked against official vendor pages, documentation, and changelogs, with the check date recorded beside every figure. Approximate numbers are labeled approximate; nothing ships invented precision to fill a table cell.
Structure
Each page is drafted, source-checked, and dated by the same editor. There is no separate community layer or vendor approval step.
Readers · who this is for
Who should read what
Process · how a page gets made
Editorial workflow
Every guide and pricing row passes the same eight steps before it ships:
- Frame the decision: name the exact operator question the page answers — which tool runs dunning unattended, what a profile costs at 10,000 records — before any prose exists.
- Pull vendor sources: take every claim from official pricing pages, documentation, and changelogs, and record the check date beside the figure.
- Score against the five axes: trigger depth, lifecycle coverage, AI assistance, segmentation, pricing fairness, with billing-awareness weighted on top.
- Score in the open: the winning tool's weak axes stay in the copy beside its strengths, not in a footnote nobody reads.
- Write the wrong-fit cases: every tool gets the situation where it is the wrong purchase, named explicitly, with the alternative that actually fits.
- Model the math: entry prices ship only when verified; scaling estimates are labeled approximate rather than invented to fill a table cell.
- Wire the exits: each claim links its official source; each page links the pricing snapshot and the guides index.
- Date-stamp and ship: the verification month goes into the copy, and scheduled re-checks update the page in place rather than appending corrections.
Sources · when figures get re-checked
Verification schedule
| Figure type | Cadence | Example |
|---|---|---|
| Headline entry price | Quarterly, plus immediately on any vendor announcement | Brevo Starter from $9 per month; MailerLite Comfort from $12 |
| Free-tier limits | Quarterly | Brevo 300 emails per day; Kit free to 10,000 subscribers |
| Scaling tiers | Spot-checked quarterly; labeled approximate when vendors hide the grid | Per-contact prices at 5,000 and 25,000 contacts |
| Feature gates | On major vendor changelog entries | Automation unlocks, send multipliers, A/B testing tiers |
| Billing integrations | On vendor integration announcements | Checkout and subscription webhooks from the payment processor |
When a vendor page and this site disagree, the vendor page is correct. Treat our figure as stale; the page is corrected the moment the two diverge, and the verification month moves with it.
Corrections and contact
Found a stale figure or a dead vendor link? Treat the official vendor page as canonical for any purchase decision, and consider this page corrected the moment the two disagree. Substantive errors — a wrong price, a broken claim, a tool that changed its billing model — are fixed in place with the verification date updated; we do not stack correction notes at the bottom and hope nobody notices.
This is a small editorial operation. There is no comments section, no community manager, and no engagement team chasing activity metrics — just pages meant to be read once, carefully, and acted on. If a page helped you wire a workflow or model a bill, the highest compliment is that you never had to open it again.
TL;DR · the whole policy
Method at a glance
| Area | Policy |
|---|---|
| Scope | Subscription SaaS teams first; commerce and creator teams invert the weights |
| Other vendor links | Official pages only; no paid placement, no pre-publication review |
| Pricing figures | Sourced from vendor pages, verified September 2026, re-checked quarterly |
| Unverifiable figures | Not published — the gap is stated instead of filled with estimates |
| Rankings | Five-axis methodology with billing-awareness weighted, published on the page |
| Corrections | Made in place with the verification date updated; the vendor page always wins |
| Reader accounts | None anywhere on the site — it is read-only by design |
Questions · straight answers
About this publication
How do you handle tools that do not fit subscription SaaS?
By naming the better audience outright. Commerce-heavy catalogs belong with Klaviyo or Drip, SMS-first programs with a multichannel suite, newsletter-only creator businesses with Kit — and every page says so where it applies. The rubric is weighted for subscription workflows, so a tool can lose here and still be the right purchase elsewhere; the wrong-fit notes exist so that loss is legible instead of silent.
How often is pricing re-checked?
Headline entry prices and free-tier limits are re-checked quarterly and whenever a vendor announces a change. Scaling tiers that depend on contact count or send volume are spot-checked on the same cadence and labeled approximate when the vendor hides the grid. Every figure links its official pricing page so you can confirm the live number at the moment you buy — the vendor page is canonical, always.
Why does billing-awareness carry the most weight?
Because the audience is subscription and SaaS teams whose lifecycle email is welded to payment state: trials end, cards fail, seats change, plans renew. A platform that cannot trigger on those events forces manual exports and webhook glue, which is exactly where workflows break at 2 a.m. Broadcast newsletters have the opposite priority — deliverability and cost per send dominate — which is why we publish the full rubric here so the bias can be inverted rather than merely complained about.
Do vendors approve or pay for coverage?
No vendor sees copy before publication, and no vendor pays for placement. Vendor pages, docs, and changelogs are read as sources, not published as prose. Guest posts and vendor-contributed articles are refused precisely because the line this page exists to keep sharp would blur the moment third-party marketing copy entered the CMS.
What is the difference between a guide and a pricing row?
A guide in the guides index is a deep vendor dive: billing axis, limits that bite, lifecycle fit, and wrong-fit alternatives. A row in the pricing snapshot is the verified minimum — free tier, paid entry, pricing model, official source — for eleven platforms on one page. Read the comparison to shortlist, the snapshot to budget, the guide to decide.
What happens when you cannot verify a figure?
The figure does not publish. Vendors such as Userlist, Encharge, Postmark, and SendGrid are absent from the snapshot for that reason — we will not invent a number to make a table look complete. The gap is stated in a notice on the pricing page with a link to the vendor, and the same rule applies to feature claims: if the documentation does not say it, the guide does not say it either.
Can I reuse your pricing tables?
The figures come from public vendor pages — cite the vendor, not us, for any price that matters at checkout. The playbooks and rubrics are editorial work: link rather than copy. Vendor pages remain canonical for every number in every table.