Alex Pan
I write and test every guide on this site. Not a team, not a content farm — one person with free accounts and a notebook of what broke.
What I do here
I take an AI tool, use it the way a beginner would, and write down what actually happens: what the free plan allows, which button is where, what error message shows up when you hit a limit, and how long a job really takes. Then I check the vendor's own documentation for the numbers I cannot see from the outside, like token prices or plan limits.
Where the two disagree — and they often do — I show both numbers and say which one I could verify. The data page tracks the clearest cases, such as the free-plan figure that differs between one region's site and another.
How I test
- Free accounts for everything. Every tool discussed here is used on its free tier, signed up the normal way, no press access and no vendor cooperation.
- One paid account, and I say so. The single paid subscription I hold is Canva Pro (billed through canva.cn). When a claim depends on a paid feature, the article states that it was checked on a paid account rather than a free one.
- Every article carries a check date. The line under each headline says when the documentation was last checked. If a number is older than six months, treat it as a starting point, not a fact — pricing pages change without notice.
- Calculations are labelled as calculations. If I show what a job costs, and I did not actually pay that amount, the article says the figure is derived from the published rate card.
- Paywalls and login walls are named. When a test stops because of a verification step or a country restriction, the article says so instead of guessing what is behind it.
What I will not do
- Write about a tool I have not opened. If a guide exists on this site, I used the product.
- Claim a feature works when I only read it in a help centre. Reading is labelled as reading.
- Accept payment from a vendor in exchange for a favourable write-up. No tool has paid for coverage here, and none gets a different tone because of who owns it.
- Publish a comparison where only one side was actually tested. If a competitor could not be reached — a verification wall, a blocked signup — the comparison says which side is untested.
Where the numbers come from
Prices, limits and feature lists come from the vendor's own pages: pricing pages, help centres, developer documentation and official release notes. Each article ends with a Sources block listing the exact pages used, so you can re-check any figure yourself. Where a number appears only in a third-party blog with no date, I do not use it.
When I get something wrong
Tools ship changes constantly, and free tiers are the first thing to move. If a guide on this site no longer matches what you see on screen, tell me through the contact page and I will re-test and correct the page, with the new check date on it. Corrections are made in place, not buried in a new post.
Start here
If you are new to this, the two pages that explain the method are How we test and About this site. If you want to see the raw figures rather than the guides, go to Our data.