# Supermemory: From Chaos to Clarity How we rebuilt Supermemory's documentation from scratch in 23 days — and turned it into their strongest sales asset. --- ## Results | Metric | Value | |--------|-------| | Answer Success Rate | +30% | | Enterprise Deals Closed | Multiple | | Reception on Twitter | Viral | | Kickoff to Launch | 23 Days | --- > "Supermemory has some of the best docs I've ever seen." > — Michael Chomsky, October 2025 --- ## Philosophy: Outcomes Over Output Developers are a no-bs audience — they care about getting something done fast. My docs philosophy is centered on **"outcomes."** The flow of information and every particular page should help developers achieve *critical outcomes*: - Making them fall in love with your product - Helping them achieve their tasks Docs are as much about marketing messaging as they are about developer experience. You have to figure out how you *want* people to use your product, because that is how you can ensure they succeed fast, realize its value, and convert. --- ## The Problem: Internal Clarity Crisis Before writing, you need CLARITY on what you want people to achieve with your product. And then handhold them through it. > **I CAN'T STRESS THIS ENOUGH.** We lacked this internal clarity at Supermemory. They have two core products: the **Memory API** and the **Memory Router**. Both overlapped and sounded similar. Both solved "memory." Customers were confused. I got on a call with Dhravya Shah (CEO) and asked him just one thing: For what outcome is the Memory API best, and for what outcome is the Memory Router best? We finally locked it in: | Product | Best For | |---------|----------| | Memory API | Granular control & custom solutions | | Memory Router | Simplicity — only for "chat" apps | From then on, everything reinforced that idea. --- ## Research: Detective Work I scraped Discord messages, tweets, asked Dhravya to forward emails from customers complaining, and got on many calls with the engineers to find every bit of feedback possible. I wrote everything down and skimmed through the docs myself. Then came one of my biggest realizations: > **The best docs have the best mental flow of information. Navigation > writing.** The first thing people see is your sidebar, and that communicates a lot about how much care you've put in. Does it make sense to me in my head step-by-step, or is it all over the place? --- ## Strategy: Mapping Zero to Aha I sat down and mapped the journey from zero to "aha." 1. What is Supermemory? 2. What are the two products? 3. How do I choose between them? 4. How do I get started fast? > **That structure alone killed 70% of the confusion.** This process repeats for each individual product. For the Memory API, I realized a dev's first step is: "How do I add a document?" So the flow had to be: Add → Check status → Query → Iterate. Once I saw that pattern, the rest of the structure basically wrote itself. --- ## Creation: Writing by Hand I made a structure doc, got approval from Dhravya, and linked every page to a concrete outcome: ingesting data, filtering, searching, etc. — in order of how devs should use the product. I opened the OpenAPI spec and started writing every endpoint by hand. Then I'd refer to the codebase to find things that weren't covered. > **Discovery:** While reading the codebase, I found SQL-based metadata filtering that wasn't documented anywhere. Added that in. Cursor and vibe-docing were a huge help. I'd ask Cursor to read the SDK definitions and OpenAPI spec and produce a first draft. Then I'd spend ~3.5–4 hours refining it, testing snippets, fixing explanations, and ensuring things made mental sense. A lot of the content it generated was fluff, and a lot of the code snippets were bad, but that's alright. You still have to think. --- ## Polish: Diagrams & Visuals Can't emphasize enough how important visuals are to prevent your docs from becoming walls of text. > **Good visuals have elevated Supermemory's docs so much.** All credit to Souptik for the visual work. --- ## Key Learnings **Documentation is critical thinking** You can't have good docs unless you actually CRITICALLY think about everything — outcomes, mental model, messaging. **No silos** The best thing about Supermemory was that I had complete access to their engineers, designers, and CEO at all times. **You have to care** You need to give a shit to not create shit. I did about Supermemory and its users. **Navigation > Writing** The sidebar communicates how much care you've put in. Structure your docs like a journey, not a dump. --- ## Want Results Like This? We ship documentation that developers love and that drives business results. Let's talk about your docs. [Book a Conversation](https://savvycal.com/manicule/intro) | [View Live Docs](https://supermemory.ai/docs/introduction) --- © 2026 Manicule, Inc.