Editorial policy

Where every number on this site comes from

Software marketing has a low bar for factual claims. This page sets out the rules this site is written under, so you can hold us to them - and tell us when we fail.

Sourced and dated Named author Corrections made openly

In short

Every figure on this site is either measured from the running product, quoted from a named source with the date it was checked, or labelled as an estimate. Competitor prices link to that competitor's own pricing page. Nothing is presented as a customer result until a real customer has agreed to it. All content is written by a named person with a bio, and corrections are made to the page rather than quietly.

Product figures: Measured, not estimated
Competitor prices: Their own page, linked and dated
Testimonials: None until a real buyer agrees
Author: Named, with a bio
Corrections: Made on the page, date changed

The rules

What we hold to

Numbers about our own product

Measured on the running product, not estimated from a spreadsheet
The cost per message figure comes from real traffic through a live installation
Test counts are the actual number of assertions the suites run
Where a figure is a range, it is written as a range rather than as the flattering end of it
Where something has not been measured at scale, the page says so

Numbers about other companies

Read off that company's own pricing page, never from a comparison blog
Linked, so you can check it yourself in one click
Dated, because software prices change without notice
Their annual-billing rate where they publish one, stated as such
No feature listed as missing without checking their documentation first

Claims about outcomes

No invented customer quotes, names or logos anywhere on this site
No "businesses save X hours a week" without a business that measured it
No review-site badges we have not earned
Example messages and briefings are illustrative, and are written as examples rather than as screenshots of a real customer

What we say about ourselves

Every feature page names what that feature will not do
The comparison pages name where a competitor beats us, including on price
The security page lists the certifications we do not hold
The about page states the risk of buying from a one-person business

Who writes it

One named person, not a content team

Everything on this site is written by Davinder Singh, who built the product. That is the reason the technical detail is specific and the reason the limitations are stated - both come from having written the code rather than a brief.

No part of this site is outsourced to a content agency, and nothing is published under an invented byline. Each guide carries the date it was last reviewed.

One author, named, with a bio and a location
No ghost-written or agency content
Every guide shows when it was last reviewed
Technical claims are checked against the code before being written down

Tell us about

An out-of-date price: Yes, please
A wrong claim about you: Yes, please
Arithmetic in a table: Yes, please
A broken link: Yes, please
Disagreeing with a conclusion: Also welcome

When we get it wrong

Corrections, not quiet edits

Prices change, we make mistakes, and a page written in good faith goes stale. When a figure on this site is wrong, the page is corrected and its checked date is updated, so a reader can tell the difference between a page that was reviewed and one that has sat untouched.

If you find something wrong - a competitor price, a claim about their product, an arithmetic error in one of our tables - tell us. Corrections from competitors are as welcome as corrections from buyers, and they get the same treatment.

Send it to the address on the contact page
A factual error is corrected within one working day where we can verify it
The page's checked date is updated when it changes, so staleness is visible
If we cannot verify a claimed error, we will say so rather than silently ignoring it