The Tool That Finally Stuck
I’ve been around the block with project management software. Wrike. Monday.com. ClickUp. Notion. Tried them all. Built custom workflows in most of them. Ran teams of two doing the work of six, and teams of six doing the work of twelve.
So when I tell you I fully switched, it wasn’t an impulse decision. Most recently I used ClickUp all the way through August of last year. And I loved it.
What ClickUp Got Right
ClickUp earned its spot in my stack for a long time. It hit all the right buttons:
- Visual flexibility. Custom dashboards, multiple views, drag-and-drop customization.
- Gamification. They made task management feel almost fun.
- Freedom to build. You could create nearly any workflow you imagined, from media production to marketing campaigns.
I ran everything through it. Social media content production. Video editing pipelines. Email campaigns. Teams of full-timers, part-timers, interns, and remote contractors all shared one place.
For a long time, it was the best tool out there. And then MCP changed that.
" The tool that wins isn't always the one with the most features. It's the one that connects best to where things are going. "
Why I Left in August
I started learning about Model Context Protocol, MCP servers. The short version: MCP lets AI like Claude connect directly into your apps and actually work inside them.
Notion built an MCP server. ClickUp didn’t.
That what I made the decision on.
When I realized that my AI of choice, Claude, both Claude Chat and Claude Code could connect directly to my Notion, I knew the gap was only going to get bigger. I made the off-ramp decision in August. I was completely out of ClickUp by December.
What Notion + Claude Actually Looks Like
Here’s a real example. My son runs a social media content business. He creates and edits content for clients, manages delivery timelines, collects assets, gives feedback, and keeps everything moving. It’s a grind. Lots of back-and-forth. Lots of waiting on clients to send things.
We’re building a system where:
- Claude helps move projects forward — organizing tasks, updating databases, flagging what’s stuck.
- Clients get a web-facing dashboard — they can see exactly what posts are in progress and what assets they still need to send, right from their phone.
- Tight parameters replace endless decision-making — instead of vague requests and subjective feedback, clients work inside a structured interface that tells them exactly what to do.
The goal is an 80–85% reduction in friction. More actual work getting done.
We’re still building it out and I’ll demo it in a future issue. But what’s already changed is real.
What Scripture Says About Good Tools
" By wisdom a house is built, and through understanding it is established; through knowledge its rooms are filled with rare and beautiful treasures. "
The right tool, used wisely, multiplies what you can build.
I didn’t switch to Notion because it was trendy. I switched because I could see where AI-assisted work was heading, and I wanted a foundation that could support it. A house built on the right structure holds up.
“Whatever you do, work at it with all your heart, as working for the Lord, not for human masters.” — Colossians 3:23
That applies to the how as much as the what. Working with all your heart means working with wisdom, not grinding through friction when better tools exist.
Resource Cards
Notion MCP Server Docs
Official Notion developer documentation — start here to understand how Notion connects with AI tools through MCP.
Read moreClaude + MCP Integration Guide
Anthropic’s guide to connecting Claude with MCP servers, including how to set up Notion as a live workspace Claude can act on.
Read more