Notes from the edge of the web
Lookoutrakivaro
Dispatch · Artificial intelligence · Updated January 2026

AI Tools Worth Watching

Sorted by the job they do. We care less about which model tops a leaderboard and more about whether a tool helps a careful person finish real work and check the result.

Why sort by use case

AI products change names, prices and underlying models every few months. Use cases change much more slowly. People still need to research, write code, make images, transcribe speech and keep sensitive data private. Organising the watchlist this way means the advice survives the next round of releases, even when individual tools do not.

Every tool listed here was usable by an ordinary person at the time of writing. Where we mention a capability, we have tried it ourselves; where something is only announced, we say so. Pricing and plans shift often, so we deliberately avoid quoting them. Always check the vendor's current terms, especially on how your inputs are stored and whether they are used for training.

The watchlist

Choose a use case

Source-grounded notes

NotebookLM

Google's research notebook answers questions using only the documents you upload, with citations back to the passages. The audio overview feature turns a reading pile into a conversational summary.

Visit NotebookLM →
Answer engine

Perplexity

Search-style answers with linked sources inline. Useful for orientation on a new subject, provided you open the sources rather than trusting the summary.

Visit Perplexity →
Long-context assistant

Claude

Anthropic's assistant handles long documents well and is strong at careful drafting and editing. Best used as a sparring partner on structure, not a source of facts.

Visit Claude →

A five-minute test before you commit

Hype is cheap and demos are curated. Before adopting any AI tool, we run the same small ritual, and we suggest you do too.

1. Bring your own task

Ignore the sample prompts. Give the tool something you have already done well yourself, so you can judge the result against a known answer.

2. Ask it to show its work

Good tools cite sources, show diffs or expose intermediate steps. If you cannot verify the output, you have not saved time; you have deferred the checking.

3. Read the data policy

Find out whether inputs are retained and whether they train future models. For anything confidential, a local model is often the sensible default.

4. Try it on a bad day

Use it again a week later on a messy, real task. Many tools shine on the first attempt and fade once novelty wears off.

Field noteWe are not affiliated with any vendor listed here and receive no commission. Product names belong to their respective owners.