Contact

Corrections First

Spot a wrong price, an outdated feature, or a claim that doesn't match what you experienced with a tool? Tell us the specific page and the specific thing that's off. We check corrections against the vendor's current offering (or our own recent testing notes) and update the article with a note on what changed — corrections are usually the fastest thing we act on, often the same week.

If You Work at a Vendor

We take submissions for tools to test, and we take partnership conversations, but both go through the same door. Include your company, the product, and a real point of contact. We won't promise a score or a timeline in exchange for a partnership — see our Disclosure page for the full policy on that.

Press and Research Requests

If you're citing our scores, our methodology, or a specific review for an article or a paper, tell us what you're working on and when you need a response by. We're generally quick to confirm how a number was calculated or to point you at the specific testing behind a claim.

"Which Tool Should I Use" Questions

We get a lot of these, and we'd rather answer directly than send you back to a page you've already read. Tell us what you're actually trying to accomplish, roughly what you're willing to pay, and whether an API matters to you — that's the same information our own Best AI Tools picks are built from.

Before You Send That Message

Quick check: pricing and limits questions are usually already answered inside the review itself, "which tool is right for me" is covered category-by-category on the Best AI Tools pages, and "how do you calculate a score" is fully explained on Methodology. Ten seconds there might save you the wait for a reply.

What Happens to What You Send Us

Your name, email, and message go to us and nowhere else — not to a mailing list, not to any vendor we cover, not to a third party. It's used strictly to answer whatever you asked.

Response Times, Honestly

We're a small team, not a support desk with shift coverage. Corrections typically get a response within a few business days; everything else within a week. If something is genuinely time-sensitive, say so and why, and we'll bump it up the queue.

Something Broken on the Site Itself

Broken link, a filter that isn't behaving, an image that won't load — that's a different kind of message than a content correction, and it helps to say so explicitly so it doesn't get triaged as a pricing dispute. Include the page URL and, if you can, what browser or device you were on when it happened.

If You Just Want to Say Something Worked

Not every message needs to be a problem. If a specific review or comparison actually helped you make a decision, we read those too, and it's genuinely useful feedback for deciding what to keep doing more of.

Requesting a Tool We Haven't Covered Yet

If there's a specific AI tool you'd like tested that isn't on the site, tell us which one and what you'd use it for. We prioritize new coverage partly by reader requests, alongside how actively a tool is maintained and how much genuine search demand it gets — a direct request from someone who actually wants the answer counts for more than either of those on its own.

Requesting a Specific Comparison

Want to see two particular tools tested head-to-head that we haven't covered yet? Say which two and why you're weighing them against each other specifically — that context helps us prioritize which pairings to test next, since we build comparisons around genuine reader decisions rather than an arbitrary matrix of every tool against every other one.