How to compare AI tools without fooling yourself.
Tool comparisons are easy to make unfair by accident. One product gets a detailed prompt, another gets a rushed instruction, or the reviewer scores a flashy answer without checking whether it is correct. A better comparison starts with the same task and the same rules.
1. Choose one real task
Pick a task you actually need to complete, such as turning meeting notes into an action list, explaining a difficult concept, or drafting a short product description. Avoid a vague goal like “which AI is smarter?”
- Write down what a successful answer must include.
- List common mistakes that would make the answer unusable.
- Use fictional or non-sensitive sample data.
2. Keep the test fair
Give each tool the same prompt, source material, output format and constraints. If a product needs a special setup, record it. Do not quietly give one tool extra context or unlimited retries while another gets one attempt.
3. Score the work, not the marketing
Use a simple scorecard. Rate each item from 1 (poor) to 5 (excellent), and keep notes explaining the score.
- Task completion: did it follow the instructions?
- Accuracy: can important claims be verified against the source?
- Coverage: did it miss required details?
- Editing effort: how much work was needed before you could use it?
- Consistency: does it perform acceptably on more than one example?
- Total cost: include setup, review time, usage limits and subscription cost where relevant.
4. Count human review time
A quick first draft is not automatically a faster workflow. Include the time spent checking facts, fixing tone, reformatting, retrying prompts and moving information between tools. If a tool creates a polished but inaccurate answer, the review burden matters.
5. Repeat before declaring a winner
Try several representative examples, including one that is awkward or ambiguous. Record the date, product version or plan if visible, prompt, inputs, outputs and limitations. A single good answer is an anecdote, not a reliable ranking.
A reusable scorecard
Copy this checklist into your notes for each tool:
- Task and success criteria:
- Test date and product/plan:
- Prompt and sample input:
- Task completion (1–5):
- Accuracy (1–5):
- Editing effort (1–5, where 5 means little effort):
- Approximate total time:
- Privacy, licensing or security concerns:
- What failed or surprised me:
- Decision: keep testing, use with review, or reject:
Make the conclusion proportional to the evidence
Instead of saying “Tool A is the best,” write something narrower and more useful: “On these three sample tasks, Tool A followed the requested format more consistently, while Tool B needed less editing on the long-form draft.” State what you tested and what you did not.
CurioLab standard: we will only publish product rankings or test results after documenting the method and evidence. Sponsored relationships, if any, must be disclosed.
Explore proposed experiments ↗