Most people collect tools. The leverage is in choosing a few that talk to each other, and naming a leader.
For years my answer to almost any problem was another app. A better to-do system. A different notes tool. A new platform that promised to be the one that finally tied it all together. I had subscriptions I'd forgotten I was paying for and a home screen that looked like a craft-fair table: everything laid out, nothing quite working with anything else.
It feels productive, collecting tools. It's actually the opposite. Every app you add is another seam: another login, another place your information lives, another join where things fall down the gap between two systems that were never built to talk. The sprawl doesn't multiply your capability. It multiplies the number of places you can lose the thread.
I learned this most sharply rebuilding the shop. It had grown sixty-four plugins, each one solving a small problem and quietly creating two more where it rubbed against the next. The fix wasn't a sixty-fifth. It was getting it down to eleven. Fewer, better-chosen, and made to fit together. The site got faster, calmer, and easier to reason about, all from subtraction.
So when I came to build a whole AI operation (several Claude sessions working at once across two Macs, which I've written about as the Control Tower), I started from that scar tissue. Not "what tools could I add," but "what's the smallest stack that actually holds this together?" Here's what it came down to, and why each one earns its place:
- Claude is the spine. Not one tool among many: the leader. The thinking and most of the doing happens here, and everything else exists to serve it. If you can't name the leader of your stack, you don't have a stack; you have a pile.
- Google Workspace is the documents and the drive, the boring, reliable place the actual files live and move.
- Notion is the live board — the single source of truth where every piece of work, every status, every decision is tracked, and which every session reads and writes. One place, not five.
- Craft is where I read the story back: the narrative surface, for when I want to see what's happening rather than manage it.
- Tailscale is the quiet wiring, the thing that lets the machines reach each other without my thinking about it. You only notice it when it's missing.
Five. Not fifty. And the test isn't whether each one is impressive on its own; it's whether they integrate, whether the handovers between them are clean. The tool that wins a category but doesn't talk to the others is a liability dressed as an upgrade.
I'll be honest about the lesson that taught me this, because I got it wrong first. I tried to coordinate the whole thing through a folder-sync service I already had, because it was there, one less tool. It was the wrong tool for that job, and it leaked in exactly the ways folder-sync leaks. The fix wasn't more tools or fewer; it was the right one in that slot: a proper version-controlled layer for the rules, the live board in the place built to be a live board. Simplifying a stack is more than cutting. It's putting each job where it actually belongs, and refusing to make one tool pretend to be three.
The deeper thing underneath all of it: a sprawling stack is usually a sign you haven't decided what matters. You're hedging, keeping six tools open because you can't bear to commit to one. But the commitment is the whole point. Choose the leader. Choose the few that serve it and talk to each other. Delete the rest, and feel how much quieter the work gets.
Your whole stack should fit in a sentence. Mine does: Claude, with Workspace, Notion, Craft and Tailscale around it. If yours takes a paragraph, that's the craft-fair table dressed up as sophistication, and the thread's already falling down one of the gaps.
I'm writing up exactly how to stand up your own version (the machine you actually need, the lanes, the guardrails, the shared board, the prompts) as Build Your Own Multi-Lane Claude CoPilot. Want the early version? The signup's at creativepath52.com.
— Damian
