How reports are made
A page is only called a review if I have used the product. Everything else is a comparison built from the vendor's own documentation, and says so.
Reviews and comparisons are different things
A hands-on review means I have had the product in a working account and can show it. A comparison is desk research: pricing pages, documentation, changelogs and public material, organised around one decision. Each page carries its label at the top so you know which one you are reading.
Prices get checked at the source
Plan prices and limits come from the vendor's own page on the date shown at the bottom of each report. Software pricing moves often. If a figure here is out of date, the "last checked" date tells you how old it is, and a correction gets it fixed.
Campaign data is aggregated
When a report uses numbers from my own campaigns, they are medians and ranges across several accounts. No client is named, no single account's figures are shown, and details that would identify one are left out.
How drafts are produced
Some comparison pages begin as a draft assembled with AI assistance from vendor documentation. I check every claim in a draft before it is published, and nothing goes live without that pass. Reviews and benchmark pages are written from my own use and data.
Commission does not set the verdict
Some products covered here pay a commission and some do not. A product with no partner programme still appears in a comparison when it is the right answer. The disclosure page has the detail.