How we award a tick,
a tilde and a cross
A comparison table is a pile of judgements. Here is exactly how ours are made, and what we do when we get one wrong.
The three marks
✓ Full support
The vendor’s own site or help centre describes the capability as a shipped feature. Plan restrictions, regional restrictions and add-on costs go in the note underneath, not into the mark.
~ Partial, or an add-on
It exists but with a material caveat — it costs extra, it needs a third-party product to work, or it does a narrower job than the row describes. Tradify’s website is a tick with a price on it; its CIS support is a tilde because it needs Xero or Sage.
× Not documented
We could not find it described anywhere on the vendor’s own site. This is the mark we are most careful with: it means their documentation does not describe it, not that we have proven it impossible. If we have missed something, tell us and we will change the cell and say when we changed it.
Where the evidence comes from
- The vendor’s own pages only. Not review sites, not blog roundups, not our recollection. Every cell in the table names a URL on the vendor’s own domain and the date it was read.
- Prices as published. If a vendor publishes in dollars we say dollars. If a fee is a range or a typical case, we say that rather than quoting it as a fixed price.
- Where they win, they win. Three rows on the table are won outright by somebody else and are left won. A table we win every row of would not be worth reading.
- Three “Only here” badges, not seven. Once seven rows claim to be unique, none of them reads as unique. The badge is reserved for the tool register, the break-in workflow and per-property compliance.
How it stays right
The table is not written by hand. It is generated from a single data file where every cell sits next to its source, and a check runs before every deploy that refuses to publish if a cell has lost its source, if a source is undated or points at the wrong company’s website, if more than three rows claim to be unique, or if a claim we have already retracted has reappeared anywhere on the site.
That check exists because we got it wrong. In August 2026 an outside reviewer found eleven cells out of date — including one that was wrong in a competitor’s favour. Every one was corrected against the vendor’s own documentation, and the automated check was written the same day so that the next drift is caught by us rather than by a reader.
Think a cell is wrong?
Send us the page on your own site that proves it and we will change it. Competitor products move; a comparison that never changes is a comparison nobody is checking.
Tell us what we got wrong