Memory.wiki Strategic Pivot and Product Evolution

The documents chronicle memory.wiki's strategic evolution from a basic markdown sharing tool to an AI-native knowledge graph platform, with multiple rounds of scope refinement to achieve a focused launch strategy.

Key claims

  • [EXTRACTED] The core value proposition is "A memory.wiki URL is an API for any AI" - users can paste URLs into ChatGPT, Claude, Gemini, or Cursor [doc-1, doc-2]
  • [EXTRACTED] The project underwent a major rebranding from "mdfy.app" to "memory.wiki" between v6 and v7, with the domain secured and finalized [doc-1, doc-7]
  • [EXTRACTED] The system operates on a 3-tier architecture: "수집/소화/활용" (Capture/Digestion/Utilization) where users author content, AI organizes it into graphs, and any AI can consume it via URLs [doc-1, doc-3]
  • [EXTRACTED] The launch scope was dramatically reduced from "8개 → 3개" features (8 to 3 features) to make the 16-week deadline achievable [doc-7]
  • [INFERRED] The project positioning shifted from being another note-taking app to serving as "LLM 서비스의 기본 지원 메모리 레이어" (fundamental memory layer for LLM services), targeting the knowledge delivery problem rather than AI memory [doc-5, doc-8]
  • [AMBIGUOUS] The business model and pricing structure underwent multiple revisions, settling on a 3-tier approach (Free/Pro/Team), though specific pricing details remain undefined [doc-7]

Cross-references

  • The "URL as API" concept appears consistently across all versions, remaining the core architectural principle despite other strategic pivots [doc-1, doc-2, doc-5]
  • The founder's motivation (doc-5) directly connects to the product specification's "delivery problem" framing, reinforcing the strategic thesis [doc-3, doc-5]
  • The scope reduction in v7-revised reflects lessons learned from the ambitious v7 plan, showing iterative refinement of the launch strategy [doc-1, doc-7]

Open questions / gaps

  • Technical architecture details for how URLs actually function as APIs across different AI platforms
  • Specific pricing tiers and monetization mechanics for the Free/Pro/Team model
  • Implementation timeline for post-launch features like Bundle Spec RFC and public hub sharing
  • Competitive differentiation strategy against established players like Notion and emerging AI memory solutions

Provenance

  • [doc-1]: Original v7 business plan establishing the core vision and 3-tier architecture
  • [doc-2]: Duplicate content reinforcing the central value proposition
  • [doc-3]: Product specification defining technical requirements and brand positioning
  • [doc-4]: Meta-commentary on the business plan evolution and architectural principles
  • [doc-5]: Founder's manifesto articulating the knowledge delivery problem and solution rationale
  • [doc-6]: Product specification synthesis focusing on the dual-door vision
  • [doc-7]: Revised v7 plan with dramatically reduced scope for achievable launch
  • [doc-8]: Simplified explanation of the core concept and competitive positioning