--- title: "Memory.Wiki v8 Strategy and Vision" url: https://memory.wiki/eqjANq9c updated: 2026-05-27T07:55:34.450Z hub: https://memory.wiki/hub/raymindai concept_count: 12 source: "auto-synthesis" --- # Memory.Wiki v8 Strategy and Vision > The collected documents outline Memory.Wiki's evolution toward becoming a cross-AI knowledge layer, positioning itself as the URL delivery system for AI context rather than another note-taking app. The v8 direction emphasizes sustainable craftsman SaaS growth while solving the core problem of users having to re-explain context across different AI tools. ## Key claims - \[EXTRACTED\] Memory.Wiki is "the URL delivery layer for your AI knowledge" with three URL primitives: Documents (`memory.wiki/`), Bundles (`memory.wiki/b/`), and Hubs (`memory.wiki/hub/`) \[doc-1\] - \[EXTRACTED\] The external thesis is "Stop re-explaining your context to every AI. Put your knowledge in one URL they can all read" \[doc-2, doc-3\] - \[EXTRACTED\] The founder goal is "지속 가능한 craftsman SaaS. 5년에 ARR $2-5M. NPS 70+. 1k-10k paid 사용자가 정말로 *사랑하는* product" \[doc-2\] - \[INFERRED\] OpenAI/Anthropic cannot build a cross-AI memory layer because it would require feeding competitors, creating a structural wedge for Memory.Wiki \[doc-1, doc-3\] - \[EXTRACTED\] The strategic framework follows "CAPTURE → ORGANIZE → USE" with an indispensability loop, measured by Weekly Recapture Rate \[doc-2\] - \[AMBIGUOUS\] Embedded chat may not be essential for launch since it directly competes with ChatGPT/Claude, while the real strength is providing "perfect context URLs" \[doc-3\] - \[EXTRACTED\] Functional differentiation should focus on "AI-optimized context packaging" rather than raw document storage \[doc-4\] - \[EXTRACTED\] Intent-adaptive bundles could provide the same graph with different contexts (coding, fundraising, research) via URL parameters like `memory.wiki/project-x?intent=coding` \[doc-4\] ## Cross-references - The "cross-AI" positioning appears in \[doc-1\] as a core primitive and in \[doc-3\] as a strategic wedge against big AI companies. Both emphasize this as Memory.Wiki's unique advantage. - Bundle functionality is described technically in \[doc-1\] as "curated groupings of docs" and strategically in \[doc-3\] as part of the launch magic moment where "AI가 bundle을 만든다." - The shift from feature complexity to focused simplicity appears in both \[doc-2\] (reducing from 8 features to 3) and \[doc-3\] (questioning even the embedded chat priority). ## Open questions / gaps - How will the intent-adaptive bundles technically work beyond URL parameters? - What specific AI optimization techniques will differentiate Memory.Wiki from simple RAG wrappers? - How will temporal memory with graph edges (valid_from, valid_to, supersedes) be implemented? - What are the specific metrics and timeline for achieving the "Weekly Recapture Rate" goal? - How will the pricing model support the $2-5M ARR goal with 1k-10k users? ## Provenance - \[doc-1\]: Comprehensive current state audit and homepage source defining Memory.Wiki's three URL primitives and capture surfaces - \[doc-2\]: Strategic v8 plan with founder goals, architectural framework, and success metrics - \[doc-3\]: Strategic analysis emphasizing cross-AI positioning strength and questioning embedded chat priority for launch - \[doc-4\]: Technical differentiation ideas focusing on AI-optimized context packaging and intent-adaptive bundles --- ## Summary Memory.Wiki v8 aims to become a cross-AI knowledge layer that delivers user context via shareable URLs (Documents, Bundles, Hubs) to eliminate the need to re-explain information across different AI tools, with sustainable SaaS growth targeting 1k-10k power users and $2-5M ARR in five years. The strategy emphasizes AI-optimized context packaging and bundles over embedded chat, leveraging a structural advantage that prevents competing AI companies from building their own cross-platform memory layer. ## Themes - Cross-AI context layer - URL-first architecture - Craftsman SaaS positioning - Context reuse problem - AI-optimized packaging ## Key takeaways - Memory.Wiki positions itself as 'the URL delivery layer for your AI knowledge' with three primitives: Documents, Bundles, and Hubs, enabling single-URL context sharing across all AI tools. - The core external thesis is 'Stop re-explaining your context to every AI. Put your knowledge in one URL they can all read,' addressing the friction of context loss across AI applications. - The founder goal targets sustainable craftsman SaaS: 5-year ARR of $2-5M, NPS 70+, and 1k-10k users who deeply love the product. - Strategic framework follows CAPTURE, ORGANIZE, USE cycle with an indispensability loop measured by Weekly Recapture Rate. - Functional differentiation should prioritize AI-optimized context packaging over raw document storage, with embedded chat deprioritized for launch. ## Insights - Memory.Wiki's structural advantage comes from competitors (OpenAI/Anthropic) being unable to build a cross-AI memory layer without feeding rivals, creating a durable wedge that pure feature parity cannot overcome. - The shift from embedded chat to focused context delivery suggests the founder has recognized that competing with ChatGPT/Claude directly dilutes the core value proposition of being the 'perfect context URL' layer. - Intent-adaptive bundles via URL parameters could solve the same underlying graph serving different contexts without duplicating data, suggesting a metadata/parameterization solution rather than structural replication. ## Open questions / gaps - How will intent-adaptive bundles function technically beyond URL parameters to serve different contexts from a single graph? - What specific AI optimization techniques will differentiate Memory.Wiki from generic RAG wrappers? - How will the pricing model achieve $2-5M ARR with only 1k-10k paid users? ## Concepts in this document - **memory.wiki** _(entity)_ The core product platform managing knowledge capture and AI-assisted workflows. - **Knowledge Management** _(tag)_ Overarching domain of personal and organizational information systems - **Chrome Extension** _(entity)_ Browser capture tool for one-click knowledge saving - **Claude** _(entity)_ Anthropic's AI assistant, key target for cross-AI compatibility - **ChatGPT** _(entity)_ OpenAI's AI assistant, primary competitor and integration target - **Capture-Organize-Use Framework** _(concept)_ Strategic framework for knowledge workflow with AI-powered organization - **Intent-adaptive bundles** _(concept)_ Technical feature concept allowing dynamic context packaging for different use cases (coding, fundraising, research) via URL parameters. - **AI Integration** _(tag)_ Technical capability to work seamlessly with multiple AI platforms - **Product Strategy** _(tag)_ Strategic planning and positioning for sustainable growth - **URL Primitives** _(concept)_ Three-tier architecture of Documents, Bundles, and Hubs as deployable URLs - **Markdown Publishing** _(tag)_ Core technical approach using markdown as universal format - **Capture → Organize → Use** _(concept)_ The core strategic framework defining Memory.Wiki's three-stage value delivery pipeline, locked as decision #1. ## Concept relations (within this doc's concepts) - **Capture → Organize → Use** defines product **memory.wiki** - **memory.wiki** targets platform **Claude** - **memory.wiki** targets platform **ChatGPT** - **Chrome Extension** captures to **memory.wiki** - **Claude** loads context from **memory.wiki** - **memory.wiki** implements via **URL Primitives** - **memory.wiki** implements through **URL Primitives** - **memory.wiki** implements **Capture-Organize-Use Framework** - **memory.wiki** is built on **URL Primitives** - **Capture-Organize-Use Framework** drives product strategy **memory.wiki** - **memory.wiki** is structured by **URL Primitives** - **memory.wiki** instantiates **Capture-Organize-Use Framework** - **AI Integration** targets **Claude** - **AI Integration** targets **ChatGPT** _Hub canonical:_ https://memory.wiki/hub/raymindai _Concept digest:_ https://memory.wiki/raw/hub/raymindai?digest=1&compact=1