About

About SaaS Software Tools

Comparisons of the tools a software company runs on: billing platforms first, then the email, analytics, support and customer-success tools that sit around them.

The editor

Julian Pryor edits SaaS Software Tools. The name is a pen name.

Julian compares tools by reading vendor pricing pages, documentation and changelogs. Every price on a page was read from the vendor's public page on the date shown there, and pricing-page screenshots are captured on the day they are dated. Julian does not run these products in production and does not claim to have tested them: when a page describes a feature, the description comes from the vendor's own documentation, and the page links to it.

What this site covers

The centre of the site is billing: Stripe Billing, Paddle, Lemon Squeezy, Chargebee, Recurly and Polar, and the decision between a payment processor and a merchant of record. The comparisons around that centre cover the tools that react to billing events. Those are lifecycle and transactional email services, product analytics, help desks and customer-success platforms.

Pages are organised around a purchase decision: which tool fits a given team, what it costs at real volumes, which limits catch people out, and what moving away costs. Where a vendor does not publish a price, the page says the vendor sells by quote and leaves the number out.

How prices and facts are handled

  • Prices come from vendor pages. The vendor's pricing page is linked next to the number, and the page carries the date it was read. Slider-based vendors are recorded at the volumes the slider showed that day.
  • Screenshots are captured, not edited. A pricing-page screenshot is taken from the live public page and the caption gives the date. If a capture is unreadable or shows a different currency, the caption says so or the page carries no screenshot.
  • No invented data. The site does not publish star ratings, conversion or recovery percentages, or customer stories unless they link to a real source.
  • Corrections. If a price or limit has moved, write via the contact page. The vendor's page wins, and the date on the corrected page changes.

The full method is on How we evaluate.

It appears where its design fits the question, for example billing-triggered email for a product that runs on Stripe or Paddle, and as a short, factual box rather than a ranking on pages about other tools.

What the site claims about Sequenzy comes from its pricing page and public documentation: a free plan of 2,500 emails, paid plans priced by emails sent with unlimited contacts, integrations with Stripe, Paddle and Lemon Squeezy, and dunning emails sent when a payment fails. The site has not compared Sequenzy's deliverability or sequence builder with other tools, and no page says it outperforms them.

No vendor pays for a place on a list or for a favourable verdict. If a page treats a vendor unfairly, including Sequenzy, tell us and the claim will be checked against the vendor's own pages.

How to read a comparison page

Every head-to-head page follows the same order, so you can skip to the part you need. The short answer at the top says who should pick which tool. The first table lists each vendor's published prices and what the plan includes, with the date they were read and a link to the vendor's page. A worked case follows, usually at two or three real volumes, with the arithmetic written out so you can swap in your own numbers.

The middle of the page deals with the question this site exists for: what happens when billing events meet email. That means how each tool receives a failed payment, a plan change or a cancellation, as far as the vendors' documentation describes it, and which plan that feature sits on. The page ends with migration steps, a decision section and questions readers ask. Anything we could not read from a vendor page is marked as such; it is never filled with an estimate.

Pricing units, translated

Most of the work in comparing SaaS tools is converting prices into the same unit. The pages use these conversions, and the vendor's own page decides which one applies.

  • Percentage of each payment. Payment processors and merchants of record, for example Stripe's standard 2.9% + 30ยข per domestic card payment. The cost rises with revenue and the flat part hurts small tickets most.
  • Percentage of billing volume. Subscription-management layers such as Chargebee, which lists plans as a share of invoicing volume.
  • Contacts or profiles. Email marketing and lifecycle tools such as Customer.io, Loops and ActiveCampaign. A large list that is rarely mailed still costs the full tier.
  • Emails sent. Transactional services and Sequenzy. A small list mailed often costs more here than under contact pricing.
  • Events or tracked users. Product analytics such as Mixpanel and Amplitude, where one busy user can cost more than many quiet ones.
  • Seats, plus usage. Help desks. Intercom, for instance, lists a price per seat and a separate charge per AI outcome.
  • Quote only. Enterprise engagement and customer-success platforms. Pages say "pricing on request (quote-based)" and compare the pricing unit instead.

What this site cannot tell you

A price page and documentation cannot show how a tool behaves under your traffic. They do not show whether messages reach the inbox, how quickly support answers, whether an integration breaks when the vendor ships a change, or how a team reacts to the interface. Those answers come from a trial with your own data and a named owner, which is why many pages end with the smallest pilot that would settle the choice, such as replaying one failed-payment webhook through each candidate.

The site also does not rank products on feature counts. A longer feature list is not evidence that a tool fits, and the cheapest plan is often the one that locks the feature you need behind the next tier. Where a page recommends a tool, it says for whom, and names the case where the other tool is the better choice.

What would change a recommendation

A vendor changing a price or a limit is the common trigger, and the page is corrected against the vendor's page. A second trigger is a vendor changing what it is: a pricing page that moves behind a sales call, a product folded into a bigger platform, or a plan that now includes a feature that used to cost extra. A third is a reader pointing out a case the page missed, such as a volume where the cheaper tool changes. Each of these edits the line where the old claim stood, with the date.

Where to start

Spotted an out-of-date price?

Send the page and the line, and it will be rechecked against the vendor's page.

Contact Us