Meet the Team

Our team in one paragraph

AI Tool Hub is run by a small distributed team: a lead reviewer (Lin, San Francisco), a senior engineer (Marcus, Seattle), a product designer (Sofia, Mexico City), a marketing lead (Daniel, Austin), and an academic reviewer (Aisha, Boston). We are all practitioners first, reviewers second. The tools we recommend are the tools we use for our own work. The reviews we write are the reviews we wish existed when we were trying to choose our own tools.

How we work together

Our editorial process is built around the fact that we are all in different time zones (PST, CST, EST, and CST in Mexico). The workflow:

1. Monday: The team meets async to assign tools to reviewers. Each tool is assigned to the reviewer whose expertise is closest (writing tools to Lin, coding tools to Marcus, etc.).
2. Weeks 1-2: The reviewer tests the tool on their own work, keeping a daily log. The other team members see the log in real time and add comments.
3. Week 3: The reviewer writes the first draft of the review. The other team members read and add comments.
4. Week 4: Lin (Lead Reviewer) does the final editorial pass: fact-checks the pricing, writes the verdict, and publishes the review.
5. Every 6 months: The tool is re-tested. The score may go up or down.

The whole team sees every review before publication. If we cannot agree on a verdict, we do not publish. (It has happened twice in 18 months.)

Meet the team

What we will never do

As a team, we have agreed on the things we will not do, regardless of pressure:

• Publish a review we have not personally tested
• List a tool that does not meet our quality threshold, no matter how much we are paid to list it
• Use AI to write the body of a review (we use AI for editing and ideation only)
• Remove a negative review in exchange for payment
• Publish sponsored content disguised as editorial review
• Share user data with third parties (we do not collect user data, period)
• Make up a quote, a stat, or an experience in a review

If you see us doing any of these, please tell us immediately. We will fix it and update the public changelog.

How to contact individual team members

For topic-specific questions, you can reach the relevant reviewer directly:

• Writing tools, content, editorial: Lin at lin@ai-tool-hub.example
• Coding tools, developer workflow: Marcus at marcus@ai-tool-hub.example
• Design tools, image/video generation: Sofia at sofia@ai-tool-hub.example
• Marketing tools, SEO, content workflow: Daniel at daniel@ai-tool-hub.example
• Research tools, academic workflows: Aisha at aisha@ai-tool-hub.example
• Partnerships, press, general: partnerships@ai-tool-hub.example
• Errors, corrections: corrections@ai-tool-hub.example

For everything else, use the contact form.

How to join the team

We occasionally onboard new reviewers who have hands-on experience with a specific tool category. The right fit:

• You use AI tools daily for your own work (we are practitioners, not journalists)
• You have a track record of writing honest reviews (on your own blog, in a publication, or for your employer)
• You are willing to be transparent about any conflicts of interest (e.g. if you used to work at a vendor)
• You can commit to 5-10 hours per week (for a single review)

If this sounds like you, email join@ai-tool-hub.example with a writing sample, a list of the tools you use daily, and 2-3 reviews you would write if you joined. We respond within 2 weeks.

Our editorial process (for the curious)

For the full editorial guidelines, see our editorial guidelines page. For the scoring methodology, see our methodology page. For the changelog of what we have published, see our changelog.