Every feed screams that you're falling behind on AI. New model, new app, ten more to try today. That panic is manufactured — someone is selling it to you. You're not behind. You're overwhelmed. And the fix was never more tools, it's the right three.

Three months ago I had thirty tabs open and no system. Now I run my whole day on three tools that work as one stack: one I think with, one that remembers everything for me, and one that does the boring work while I sleep. Here's exactly what each one is, how I use it, and how they connect into a single workflow instead of thirty lonely tabs.

The stack at a glance

ToolRoleWhat it does
Claude + GeminiThinkMake you understand what you don't know; plan before acting
NotebookLMRememberA private, cited knowledge base you query for grounded answers
n8n / Zapier / VPSRunAutomations that do the repetitive work on a schedule, while you sleep

1. The one you THINK with

This is the front of the whole system: Claude and Gemini. Not "ask a question and copy the answer" — that's the shallow way everyone uses AI. The real move is to make it teach you what you don't know yet, and to make it plan before it acts.

Two ways I use it every day:

Why two models? They have different strengths and blind spots. Claude for deep reasoning and building, Gemini for fast research and a second brain that sees it differently. Same job, two angles.

2. The one that REMEMBERS

NotebookLM is great on its own. You load in many sources — YouTube videos, PDFs, websites, your own notes — and it answers ONLY from them, with citations. It can turn that pile into summaries, study guides, even an audio voiceover overview. On its own it's already the best way to query a stack of material you trust.

But here's the part most people never reach — my actual workflow:

I query NotebookLM from Claude Code, and then I make Claude act on what it pulled.

Say I want to build a new Claude skill but I haven't fully learned the topic. I don't need to. I do this:

  1. Load NotebookLM with sources about that topic — YouTube videos that explain skills, websites and docs that cover them.
  2. From Claude Code, query that notebook for the grounded, cited answer.
  3. Tell Claude: using what you just pulled, build me the most relevant skill for this.

So NotebookLM becomes the knowledge base, and Claude becomes the builder that turns that knowledge into a real, working thing. I get to ship something I hadn't fully learned myself, because the AI pulled the real knowledge and acted on it. Query for a purpose, then act — that's the whole point.

The connector that wires NotebookLM into Claude is a free skill, credit PleasePrompto — the same one from my first video. Full step-by-step is in the companion how-to here: "How to Connect NotebookLM to Claude." Repo: github.com/PleasePrompto/notebooklm-skill

3. The one that RUNS while you sleep

The third tool is the automation layer: the repetitive work — sorting, summarizing, scheduled jobs, posting, scraping — handed off once, then it runs on its own. You wake up to it already done. There are three real ways to do this, and they trade ease for power and cost.

Zapiern8nVPS (self-hosted)
What it isHosted no-code automationOpen-source automationYour own server running n8n / scripts / agents
EaseEasiest — click and connectMedium — visual, more controlHardest — you run the machine
PowerLimited to its integrationsVery high — custom code, any APITotal — anything you can code
CostPer-task, expensive fastFree self-host / cheap cloudCheap flat monthly
Best forQuick wins, non-technicalPower users, no server billHeavy, always-on, private workloads

What I use is a VPS. It's close to n8n — same idea of chaining steps and running them automatically — but instead of paying per task or living inside one app's limits, I have my own always-on server. No task caps, full privacy, a flat cheap monthly cost, and the freedom to run anything I can code, including AI agents overnight.

The trade-off is honest: a VPS is the most work to set up and you maintain it yourself. So the rule of thumb:

Tools & links

What most people get wrong

They collect tools instead of building a system. Ten AI apps that don't talk to each other is just ten more tabs — more overwhelm, not less. The power isn't in any single tool, it's in the handoff: you think in the first, it remembers and pulls grounded knowledge from the second, and it ships the repetitive half through the third. Three tools that hand work to each other beat thirty that sit in isolation.

One step to take today

Close every AI tab except one. Pick the single tool you actually think in and make it the front of your stack. Add the memory layer once that's a habit, and the automation layer once you have a repetitive task worth handing off. Three on purpose beats a hundred by accident.

Enter your email to read the full how-to

Confirm via the email link to unlock this and every future SharpenDaily how-to. Free.

No spam. Unsubscribe anytime.