Complete source notes
The library pilot begins October 12. Twenty volunteers are invited. Priya owns setup. The equipment budget is capped at $600. Feedback is due October 19. A data-retention period has not been decided.
Practical guide · 4 min read
Try the same real task in two assistants and find out which one earns a place in your routine.
What you’ll finish with A repeatable comparison based on your own work, rather than a model leaderboard.
AI-generated guide · Content revised · Allow about 20 minutes for the exercise
Choose a short document you need to summarize, an email you need to rewrite, or a decision with clear constraints. Use a copy with private details removed. A task with a known answer makes errors easier to spot.
Include the intended reader, source material and desired output. Start fresh in each tool. Keep the first response as well as the improved version so you can count how much work it took to get something usable.
Point out a missing detail or ask for a shorter answer. Check whether the tool fixes the issue without losing facts that were already right. Good follow-up behavior matters when you use a tool every day.
Compare factual errors, edits needed, time spent and any limits you hit. Repeat with a second task before paying. Familiarity with one interface can be worth more than a small difference in answer quality.
Replace the bracketed sections with your own details.
Use only the notes below to write a 150-word briefing for a colleague. Separate confirmed facts, unresolved questions and next steps. Preserve names, dates and numbers. If a detail is missing, say so rather than filling it in. Notes: [paste your notes]
Use the same small briefing task in two fresh chats. The notes and candidate answers below are fictional; they show how to score a response, not how any named model performed.
The library pilot begins October 12. Twenty volunteers are invited. Priya owns setup. The equipment budget is capped at $600. Feedback is due October 19. A data-retention period has not been decided.
Swipe or scroll across the table to see every column.
| Candidate | Answer | What the check catches |
|---|---|---|
| A | The pilot starts October 12 with 20 volunteers. Priya owns setup, the budget cap is $600, and feedback is due October 19. Retention is unresolved. | Preserves the five stated facts and the unknown. |
| B | The library launches publicly October 12. Priya will spend $600, collect feedback October 19, and delete records after 30 days. | Turns a pilot into a public launch, a cap into a spending commitment, and invents retention. |
Task and known answer: Tool and model/settings: Wrong or invented facts: Missing required facts: Corrections before usable: Minutes to usable result: Usage/cost shown by provider: Account/device limits encountered: Would I use this result? Why?
Treat invented facts as a failure even when the prose reads well. Run a second task from your routine before choosing. If both outputs are accurate, prefer the workflow that requires less correction and fits your device, access needs and budget. Leave cost unknown when the interface does not expose it; a token-price calculation is not a measured subscription cost.
A polished answer hides an invented commitment.
Ask: “Which source sentence supports the 30-day retention period? Remove unsupported claims and keep the budget as a cap.” Check the corrected answer against the original notes.
All five facts survive, retention remains unresolved, and your scorecard records the work required to get there.
Compare free tiers before paying: Gemini’s includes Canvas and Deep Research, Claude’s includes artifacts, and ChatGPT’s Free and Go plans use GPT-5.6 Luna rather than GPT-6. Pay when a specific limit or missing feature repeatedly interrupts useful work, and check whether API use is billed separately.
References checked October 22, 2026. Feature access, sharing and plan limits can change; check the linked documentation before committing.
Choose around the task and access you have. These are options to try, not a measured ranking.

OpenAI
A broad all-rounder with the largest ecosystem: Codex for coding, Sites for publishing, Dots for ongoing work and plugins for other apps.
Read the overview →Visit ChatGPT ↗
Anthropic
Long documents, careful writing and coding, and turning a conversation into a document, deck or dashboard.
Read the overview →Visit Claude ↗
People who live in Google’s apps and Android, and anyone who wants a capable free tier with Canvas and Deep Research included.
Read the overview →Visit Gemini ↗
SpaceXSI (formerly xAI)
People who also use X or Cursor, since one plan now covers all three, and anyone who wants image and video generation in the same app as chat.
Read the overview →Visit Grok ↗
Microsoft
Households and businesses already paying for Microsoft 365, where Copilot works inside the documents and email they use every day.
Read the overview →Visit Microsoft Copilot ↗Meta
US users who want an agent that completes errands for them, inside apps they already use such as WhatsApp.
Read the overview →Visit Meta Muse ↗
DeepSeek
Developers who want a cheap API for tasks with checkable answers, especially batch work that can run in off-peak hours at half price.
Read the overview →Visit DeepSeek ↗
Moonshot AI
Testing long-document and coding work against other model families. K3.1 Pro and its Highspeed variant have separate API offerings.
Read the overview →Visit Kimi ↗
Ollama
Keeping data on your own hardware, working offline, or connecting open models to your own apps without per-token bills.
Read the overview →Visit Ollama ↗



Match the benchmark to your task, keep model settings attached and check whether the gap matters.
Read guide 3 min read



Build a brief you can trace back to its sources, including the places where they disagree.
Read guide 3 min read



Start with a small change, a clear check and a way to undo it.
Read guide