How We Test
We publish a review only after using the product. No exceptions: our build refuses to publish a review that is not marked as tested with a real copy, has fewer than three of our own screenshots, or lists fewer than two downsides.
What a test includes
- A real account. We get access from the vendor (a review copy) or buy it. The review says which.
- A real project. We build something a buyer would build: a planner, a KDP interior, a printable set, a listing.
- Our own screenshots and video. Every image on a review page was captured by us during the test.
- The full funnel. We list the front-end price and every upsell (OTO), and say which upgrades are worth it.
- Refund terms. We record the refund policy shown at checkout.
How we score
Every third-party product gets five scores from 0 to 10. The overall score is their plain average, so you can check it.
| Criterion | What we look at |
|---|---|
| Does what the sales page promises | Each headline claim, tried on our own project |
| Time to a first usable result | Minutes from login to something we could publish |
| Quality of the output | Print or screen quality, errors, how much fixing it needed |
| Value against the full funnel price | Front-end price plus the upsells you realistically need |
| Docs, support and refund terms | Tutorials, a support reply, the refund policy at checkout |
The verdict is one of Recommended, Worth considering or Skip it.
Our own products are never scored. When we write about a TopToolsKit product, the page says so at the top and shows no score or rating.
What we do not do
- We do not copy the vendor’s claims as facts. Income claims are never repeated.
- We do not publish testimonials, ratings or reviews from people we cannot verify.
- Vendors never see or approve a review before it goes live.
When a product changes, we update the page and show the update date.