For years, I was a productivity app person. Notion was the hub. Zapier ran automations in the background. Make handled the edge cases. Google Sheets picked up whatever didn't fit anywhere else. Apple Notes for quick thoughts.

It felt like a solid system. But I was spending more time maintaining the stack than doing actual work. The automations broke. The Notion databases drifted out of date. I'd spend a weekend "fixing the system" instead of using it.

Then I started using Claude Code. And slowly, without really planning it, I stopped opening most of those apps. I've been trying to replace notion with AI for a while now, without even naming it that. This is what that actually looks like in practice.

Why Productivity Apps Create Their Own Overhead

Every tool you add is a thing you have to maintain. That sounds obvious, but it's easy to miss when you're in the middle of building a system that feels productive.

Notion wants you to think in databases. Zapier wants you to think in triggers and actions. Sheets wants rows and columns. Each tool has its own mental model, and switching between them takes more energy than it looks like on paper.

The real cost isn't the monthly fee. It's the context-switching. The reformatting. The "I need to update that in three places now" problem.

When I started to replace notion with AI tools, the main thing I noticed wasn't the features I gained. It was the overhead I lost.

Files First: Markdown and HTML Instead of Databases

The biggest change was format. Everything I write now lives in HTML or Markdown files. A flat folder. No database, no sync infrastructure, no proprietary format.

I have over 1,200 published stories from Medium and Substack. All of them in one folder as plain HTML. That used to live scattered across Notion, Apple Notes, and the platforms themselves.

Getting it all in one place was a Claude Code afternoon. Deduplication, cleanup, consistent naming. What would have taken me a week took a few hours of prompting.

The reason this works as a way to replace notion with AI is simple: plain formats are readable by everything. A Notion database with linked views and custom properties is readable by almost nothing except Notion itself. If Notion changes its pricing, its export format, or its business model, you're stuck. An HTML file never goes anywhere.

Simple formats age well. Complex formats don't.

Automations That Live in Your Project Folder

Zapier, Make, n8n. Good tools. I used all three. The problem is that every automation is something that can break silently. The API updates. The trigger endpoint moves. And now you have a broken workflow you don't remember building.

I replaced most of that with Claude Code scripts. They sit in my project folders alongside the work they support. When something breaks, I can read the script, fix it, and understand why it broke. That's not possible with a visual automation tool where the logic lives on someone else's server.

My content pipeline is a good example. Every time I publish an article, a small set of scripts runs. Social posts get generated. Blog version gets queued. Affiliate links get inserted automatically. Cross-links get found and verified against the live site. The file moves from Drafts to Published.

That used to be manual work plus a few Zapier automations I half-trusted. Now it just runs.

CLAUDE.md Files Instead of Project Databases

Notion was my project management tool. But what I actually needed wasn't project management. It was context management.

For a team, project management makes sense. Status tracking, assignments, deadlines. But for a solo person working on the same handful of projects every week, a database of tasks is overhead. You already know what you're working on.

What's actually hard is re-entering context after a break. Coming back to a project after two weeks and spending twenty minutes figuring out where you left off, what decisions were made, what the current constraints are.

That's what CLAUDE.md files solve. One short Markdown document per project. It holds the architecture decisions, the quirks, what I've tried, what to watch out for. When I open a project, I (and Claude) read it. Then I'm back up to speed in two minutes.

No database. No linked views. One file. It's a better way to replace notion with AI for solo work than anything I've tried.

Building Small Apps Instead of Forcing Sheets

Some problems don't fit a general tool. I used to force them into Sheets anyway, because building something custom felt like too much work.

With AI it's not. A few hours with Claude Code and I have something that does exactly the one thing I need, with no extra features to ignore.

A tax calculator for my wife's job. A specific tracker for outreach. A CSV processor that would take forty-five minutes of formula-writing in Sheets to set up correctly. For one-off use cases, building a small purpose-built app is now faster than configuring a general tool.

It also means I'm not paying monthly for SaaS products that do the thing plus thirty features I don't want. If you're curious about the broader picture of building solo with AI, I wrote about what actually changed when I started building apps with AI.

What I Still Use (Honestly)

Apple Notes. Still there. It's always available on Mac and iOS without setup. I use it for quick captures and things that don't belong in a project folder. It's fast and I don't have to think about where to put things. I wrote about why I moved to Apple Notes from Notion a while back. Still applies.

Google Sheets shows up maybe once a month for genuinely tabular data. But I don't live in it.

That's mostly it. If you want the full picture of what my stack looks like now, I covered it in my solo creator tools roundup.

The Honest Downsides

You need to be comfortable with code, or at least comfortable following along when Claude Code explains what it's doing. If you've never looked at a script before, this approach has a real learning curve.

The other thing: cost. Using Claude Code heavily is not free. If you're running a lot of automations or long context sessions, it adds up. Factor that in before you cancel your Zapier subscription.

And there's maintenance. Scripts still break. File structures drift. The difference is that when something breaks, you know where it is and why. That's a meaningful improvement, but it's not zero effort.

If you're wondering whether Notion is still worth it for your workflow, I have a separate piece on Notion for writers in 2026. For some people and some workflows, it still makes sense.

The Short Version

To replace notion with AI isn't a single switch you flip. It's a gradual shift that happens when you start preferring simple formats over structured databases, local scripts over hosted automations, and context files over status dashboards.

The productivity stack I have now has fewer moving parts. It's easier to maintain. Most of it I understand end to end.

That's worth more to me than any feature any of those apps had.

A writer is nothing without a reader. If you found this helpful, consider becoming my dear email friend. Nothing would make me happier.