Stop Juggling AI Tools — How to Build a Second Brain That Actually Works for You

ChatGPT, Claude, NotebookLM — they all use the same underlying pattern. Here's what that means for how you choose tools, and the 3-step framework that ends the constant switching.

Every AI tool promises to be your second brain. ChatGPT, Claude, NotebookLM, Perplexity — they all claim to remember what matters. None of them actually do, at least not the way you think. The reason is a pattern called RAG (Retrieval-Augmented Generation), and once you see it, you realize every tool you're switching between is running the same system underneath. Here's what that means, what I built to prove it, and the 3-step framework that finally ended the juggling.

---

Do you ever feel like you're drowning in a sea of AI tools?

Notion AI, ChatGPT, Claude, NotebookLM, Perplexity … They all promise to be your "second brain", but instead of feeling smarter, you're just more scattered.

I've tried them all. Some days, one tool feels more useful than the others. But there's never a clear winner, never that one tool that truly earns the title of "my second brain". They all seem so similar on the surface, yet each one insists it's fundamentally different.

That strange tension, between sameness and difference, sat in the back of my mind for months. I'd switch between tools based on mood, project, or whatever shiny new feature caught my attention. The constant switching was exhausting, but I never give it much thought until recently, when I was building a personal website and started experimenting with RAG (Retrieval-Augmented Generation).

As part of my GenAI 30 project challenge, I set out to create something that felt personal and practical: an AI that actually understands my writing and can talk back with context.

What I discovered in the process changed everything, not just about AI tools, but about how to think strategically about the ones we already use.

What you'll go through with me:

• What RAG actually is — the pattern behind every AI "second brain" tool
• Building one from scratch — 30+ articles indexed for $0.03, and what that revealed
• RAG is everywhere — Obsidian, Cursor, NotebookLM all run the same system
• The Anti-Juggling Framework — 3 steps to pick your foundation tool and stop switching

1. What Is RAG, Really?

If you're like me, not so deep into technical details, the first time you hear "RAG", it might sound like another AI buzzword: mysterious, essential, maybe even overhyped.

But once I built one, I realized: at its core, RAG is just smarter search.

Unlike keyword search, which only finds exact word matches, RAG understands meaning. For example:

Keyword search for "dog"

• Finds: documents with the word "dog"
• Misses: "puppies," "canines," "golden retrievers"

RAG search for "dog"

• Finds: all of the above, plus related topics like pet care, training, and veterinarians

RAG perfectly captures the famous saying in linguistics:

You shall know a word by the company it keeps.

When you ask a question, RAG turns your question into a meaning-code (called an embedding), finds content with similar meanings, and feeds that context into a language model to generate a grounded response.

2. Building the System: RAG Integration

I set out to build a RAG system that could serve as a personal AI assistant, one that actually understands my writing, remembers my topics, and can answer questions with my context.

The Goals:

1. Fetch and process my Substack articles
2. Create semantic chunks optimized for retrieval
3. Generate embeddings for similarity search
4. Build a chat interface that feels natural and responsive
5. Provide source citations so users know where information comes from

The Architecture

I chose a three-phase approach that balanced functionality with cost-effectiveness:

Phase 1: Content Processing

• Fetched 30+ articles automatically from my feed
• Broke content into 500-word chunks with 50-word overlaps
• Extracted titles, URLs, publication dates, and topic tags

Phase 2: Embeddings & Search

• Used OpenAI's text-embedding-3-small for vector representations
• Implemented cosine similarity for finding relevant chunks
• Stored everything locally in JSON to keep costs minimal

Phase 3: Chat Interface

• Built a responsive floating chat widget
• Added proper markdown rendering for human friendly responses
• Included source citations with similarity scores

The Results & Numbers

• 30+ articles processed and indexed
• 250 semantic chunks, each embedded with OpenAI
• 2,436-dimensional vectors per chunk
• Seconds response times for most queries
• Similarity scores ranging from 0.3–0.8 (with higher scores = better matches)
• Total embedding cost: ~$0.03
• Zero hallucinations—all answers grounded in my content

What I Learned

Chunking Strategy Matters 500-word chunks with overlaps preserved meaning while keeping search sharp. Go too small, you lose context. Too big, and results get fuzzy.

Semantic Search Feels Like Magic Even vague queries like "How do I build an AI workflow?" surfaced the right ideas. It understood intent behind the words.

User Experience Is Everything Having a chat interface right on the site made it feel human. And markdown formatting? Underrated.

3. The Revelation: RAG Is Everywhere

After building this project, I found myself thinking: Wait, that's it? That's RAG?

It almost feels deceptively simple. But that shift—from matching keywords to understanding intent—is what makes RAG so powerful.

And once I saw it working in my own system, I couldn't stop thinking: What if many of the tools we already use as our "second brains" (e.g. Obsidian, Notion, Cursor) are quietly using RAG-like concepts under the hood?

🧠 Obsidian: The Structured Mind

Obsidian might be the closest thing we have to a "second brain" in its raw form. It's a local-first, Markdown-based note app with bi-directional linking and a knowledge graph. Out of the box, it has no AI, no embeddings, just structure.

But once I added plugins and connected it to LLM API, something magical happened. I could analyze writing patterns, summarize content, and expand on ideas with contextual awareness.

⚙️ Automation + Notion + AI

I built a system using n8n to pull AI-related emails from Gmail, send them to an API, and store both original and AI-enhanced content in a Notion database. Once the data's there, querying it feels like semantic search.

💻 Cursor: My Silent Second Brain

If I were to rebuild my RAG website today but have it operating fully locally, I'd just open Cursor, point it to my folder of writing, and ask questions directly.

Cursor works by embedding your files, running similarity search, and feeding that context into a language model, just like the RAG architecture I built from the challenge project.

⚡ Real-Time RAGs You're Already Using

Take Unsplash. You search "cozy winter cabin", and it returns exactly that, even without matching filenames. It's not keyword search. It's using image-text embeddings, just like CLIP.

Or NotebookLM, Google's AI notebook. You upload documents, and it answers questions by retrieving relevant content and generating responses. That's RAG in action. For recordings specifically (paid courses, Zoom calls, cohort replays), this pipeline covers the audio extraction and NotebookLM indexing step.

These tools may not say RAG, but behind the scenes, they're doing the same thing:

retrieve → understand → respond.

4. The Strategic Shift: Choosing the Right Second Brain (For *You*)

Once I realized all these tools share the same underlying logic, I finally understood why I kept jumping between them, I was treating them as different species when they're really different breeds of the same animal.

Instead of comparing feature lists, I started asking the right questions:

• What kind of content does this tool retrieve best?
• How does it understand context?
• What style of response fits my thinking?

The tools aren't really competing, they're optimized for different types of thinking.

The Anti-Juggling Framework

Step 1: Map Your Thinking Patterns

Before choosing any tool, spend one week tracking when and why you reach for AI help. Notice:

• Do you need quick answers while writing? (That's retrieval-heavy)
• Are you brainstorming and connecting ideas? (That's exploration-heavy)
• Do you work with structured data and documents? (That's organization-heavy)

Step 2: Choose Your Foundation Tool

Based on your dominant pattern, pick ONE primary tool:

• Retrieval-heavy: Start with Cursor or NotebookLM
• Exploration-heavy: Obsidian with AI plugins
• Organization-heavy: Notion AI

Step 3: Build Your RAG Mindset

Feed them your actual work, not random prompts. Upload your documents, connect your projects, import your notes. The magic happens when the tool understands your specific context.

Ask questions that build on previous context. Instead of starting fresh each time, reference earlier conversations, build on previous insights, create threads of thought.

Treat their outputs as thinking partners, not final answers.

The Depth Principle

The magic isn't in the tool, it's in creating a consistent context that gets smarter over time. Every conversation, every document you add, every question you ask builds a richer understanding of your work and thinking patterns.

This is why tool-jumping is so counterproductive. Each time you switch, you lose that accumulated context.

Your Turn To Start

Pick your foundation tool tonight. Based on your dominant thinking pattern, choose one tool and commit to it for at least 30 days.

Tomorrow, spend 10 minutes feeding it something you're actually working on. Ask it one real question about your work — not a test question, but something you genuinely want to explore.

The juggling stops when you commit to depth over breadth. The tools aren't competing for your attention, they're here to support how you think, how you create, and how you want to work.

Choose depth in one. Let the pattern do the rest.

— Jenny