---
id: "claim-notion-evernote-obsolete"
type: "claim"
source_timestamps: ["00:09:24", "00:10:00"]
tags: ["tool-obsolescence", "knowledge-management"]
related: ["concept-agent-web"]
confidence: "high"
testable: true
speakers: ["Nate B. Jones"]
sources: ["s22-saas-replacement"]
sourceVaultSlug: "s22-saas-replacement"
originDay: 22
---
# Human Web tools like Notion and Evernote are structurally mismatched for AI agents

## Claim

Traditional 2010s-era note tools — [[entity-notion-d22]], Evernote, Apple Notes — are fundamentally mismatched for use as AI agent memory. They were designed for the Human Web (visual layouts, hierarchical folders, graphical toggles), not the [[concept-agent-web]] (flat structured data, APIs, [[concept-semantic-search]]).

## Why It's Structural, Not Cosmetic

- Folder hierarchies impose a human ontology that fights vector retrieval.
- Rich UI metadata (cover images, fonts, embeds) is invisible/irrelevant to an agent.
- Read APIs, when they exist, are rate-limited and pagination-heavy — not optimized for fast similarity queries.
- Bolting an AI chatbot on top is a band-aid: the chatbot still has to do RAG against an unfriendly schema.

See [[contrarian-notion-is-dead]] for the sharper framing.

## Counter-Perspective

The enrichment overlay notes that Notion AI and similar integrations *do* layer RAG on these tools and provide useful experiences for hybrid users. So 'obsolete' is sharper than 'mismatched.' For users who never plan to leave one platform, the structural critique still holds but the practical pain may be lower.

## Testability

High — you can benchmark identical agent tasks against (Notion-RAG) vs (Postgres+pgvector+MCP) memory backends and measure retrieval precision and latency.