Start with the problem, not the product
Before picking a tool, write two sentences on what specifically is failing in your current setup. "I save things and never find them again", "I have no place for reflections next to links", "I want to share saves with context". A tool is worth switching to only if it fixes that specific failure — feature-count alone is a trap.
Ten features to evaluate
1. Capture speed and friction
If saving is friction-heavy, you will not save. Test the tool by trying to save five things in two minutes. If it feels slower than a browser bookmark, capture will quietly fall off within weeks.
2. Supported content types
Most people save more than links. Check the tool handles the media you actually use: articles, text notes, images, PDFs, videos. A tool that only stores URLs will send you back to a notes app anyway.
3. First-class reflections, not just notes
One of the clearest quality signals is whether your reflection lives next to the source or gets buried in an unrelated notes canvas. This is the difference between saving-and-forgetting and saving-and-reusing. See how to reflect on an article, book, video or podcast for why this matters so much.
4. Organisation model
Labels, projects, folders, tags — the specific vocabulary matters less than whether the model is light enough to actually maintain. If it forces every save to belong to a hierarchy, you will stop saving. If it offers no structure at all, retrieval will fail. See organise saved content without overcomplicating it for the framework.
5. Search that respects intent
Full-text search is table stakes. The differentiator is whether you can search by your own reflections — the words you would use to look for the idea, not the words the author used.
6. Rediscovery features
A review view, a scheduled prompt, a way to see older saves — anything that makes the pile older than three months visible. Without this, most saved libraries decay silently. Detail in how to rediscover ideas you saved months ago.
7. Sharing with context
Can you share a saved item with your reflection attached, or does the recipient just get the original link? The difference in how the piece lands with them is enormous.
8. Data portability and ownership
Can you export your saves, reflections and structure? In what format? A vendor that treats your library as leverage rather than yours is one you will regret.
9. Ease of maintenance
Does a weekly review take five minutes or fifty? If maintenance is heavier than the value you get, the tool is quietly costing you more than it saves.
10. Pricing model and long-term cost
Watch for pricing that rises steeply with usage, and features gated behind tiers that make basic use awkward. A predictable, honest pricing model tends to be a good proxy for a healthy product.
A scoring rubric
Score each of the ten features from 1 (weak) to 5 (excellent) for each tool you are comparing. Add the totals. A tool you would score below 3 on capture speed or data portability rarely survives long-term use, whatever else it scores well on.
| Feature | Tool A | Tool B | Tool C |
|---|---|---|---|
| Capture speed and friction | — | — | — |
| Supported content types | — | — | — |
| First-class reflections, not just notes | — | — | — |
| Organisation model | — | — | — |
| Search that respects intent | — | — | — |
| Rediscovery features | — | — | — |
| Sharing with context | — | — | — |
| Data portability and ownership | — | — | — |
| Ease of maintenance | — | — | — |
| Pricing model and long-term cost | — | — | — |
| Total | / 50 | / 50 | / 50 |
Common pitfalls when evaluating apps
- • The feature-count trap — more features rarely means more value; often the reverse.
- • Underestimating migration cost — moving three years of saves is more work than it looks.
- • Tool-hopping — the best system is usually the one you already have, used more consistently.
- • Optimising for the demo, not the daily grind — a beautiful onboarding says nothing about week ten.
A short decision path
- Name the specific failure in your current setup.
- Score two or three candidates against the ten features above.
- Trial the top scorer for a fortnight, doing real work in it.
- Only migrate the saves you can honestly imagine reusing.
Related reading
Frequently asked questions
What's the difference between a note-taking app and a second-brain app?
A note-taking app centres on writing you produce. A second-brain app centres on content you save from elsewhere, with your reflections attached. Many people use both; the two do genuinely different jobs.
Is it worth switching apps if my current setup mostly works?
Usually not. The cost of migration is high and the value of a new app is often less than promised. Switch when the current tool has a specific failure you can name — 'I lose things I saved', 'I can't share with context' — rather than for novelty.
How much should a second-brain app cost?
There is no correct figure, but a useful benchmark is: it should cost less than the value of ten minutes a week saved by finding things faster. Anything more than that needs to justify itself with genuine, ongoing value.
What if I outgrow it in a year?
That is a data-portability question. Before you commit, check whether the app lets you export your saves, reflections and structure in an open format. A tool you cannot leave is a tool you are stuck with.