How We Evaluate SaaS Automation Tools
What we read, how a price ends up on a page, what a screenshot proves, and what we leave out. Short version: we read vendor pages and write down what they say, with the date.
What the evaluation is, and is not
This site is edited by Rowan Ellis, a pen name. The editor works from what vendors publish: pricing pages, documentation, security and trust pages, integration directories and changelogs. That is a desk review. We do not build your workflow in each product, we do not run lab tests, and we do not claim to have used a tool for a project. When a page says a tool "can" do something, it means the vendor's own documentation says so, and the sentence links to that page where it matters.
Because of that limit, a recommendation here is a statement about fit, not a score. We say which job a tool suits, which billing unit it uses, and where the trade-off sits. There are no star ratings and no 1-to-10 numbers anywhere on the site.
How a price gets onto a page
- Open the vendor's public pricing page. Not a review site, not a cached article and not a number remembered from an earlier version of our own page.
- Copy the figure with its unit. A price is only comparable once you know whether it is per seat, per task, per execution, per contact or per monthly email volume. We write the unit next to every figure, because the unit decides what the tool costs when you grow.
- Record the date. Each page that quotes prices states when they were read. Pages revised in October 2026 say October 2026. If you see a figure with no date and no vendor link beside it, treat it as a defect and tell us.
- Do the arithmetic in view. Where a vendor publishes a formula or a tier table, we multiply it out at a stated volume, such as a number of seats, tasks or contacts, and show the working. We do not round a quote-based price into an estimate. If a plan is "contact sales", the page says it is quote-based and gives no number.
- Link the source. The figure links the vendor page it came from, so you can verify it in a minute.
Screenshots
When a page carries a screenshot of a pricing page, it was captured from the vendor's live public page on the date in the caption, and it is shown as captured. We do not crop out prices, edit the image or combine screenshots. A screenshot is evidence of what the page said on that day, not of what it says today: vendors change plans without notice, so use the caption's date and follow the link for the current figure. If a capture fails or comes out half-loaded, we leave the screenshot out rather than substitute another image.
Why prices and limits change
Automation vendors revise tiers often, and they change the billing unit more often than the headline price. A connector can move from counting tasks to counting runs, a CRM can move a feature to a higher plan, and a free tier can lose a limit. For that reason we favour the unit and the limit over the monthly figure when summarising a tool, and we date every comparison. When we find a stale figure on our own pages, we re-read the vendor page and replace the claim, with the new date.
What we do not do
- No invented numbers. No made-up recovery rates, conversion lifts, customer quotes, review counts or "we tested 15 tools" claims. A statistic stays only with a source link next to it.
- No paid placement in rankings. The order of a list reflects the job and the trade-offs we describe, and the reason is written next to each entry.
- No claims about results we have not measured. We do not say how much a tool will save you or how many failed payments it will recover. We say how to measure that on your own data.
Corrections
If a price, a limit or a claim on this site is out of date, write to hello@saasautomationtools.com with the page and the claim. We check it against the vendor's page first, then change ours. For who runs the site and what it covers, see About. Page updated October 7, 2026.