Most people's productivity stacks have quietly ballooned to 30+ tools. Here's the case for cutting ruthlessly — and the framework we use to decide what stays.
There's a specific kind of productivity anxiety that only affects people who spend time thinking about productivity: the feeling that you're using the wrong tool. That the app you haven't tried yet is the one that would finally make everything click.
It's why most people who care about their workflow end up with a stack that spans four note-taking apps, three task managers, two calendar tools, and a Notion database they set up eighteen months ago and haven't opened since.
The stack doesn't make you more productive. The stack is the procrastination.
The switching cost nobody accounts for
Every tool in your stack has a maintenance cost that doesn't show up in the pricing page. There's the time spent checking it, the mental overhead of remembering which things live where, and the context-switching cost of moving between tools during a working day.
For a single tool, this cost is negligible. Across a 30-tool stack, it compounds into something significant — maybe an hour a day spent navigating tools instead of doing work.
The framework for cutting
The question that clears stacks fastest: "What would break if I removed this tomorrow?"
Not "is this useful" or "do I use this sometimes." What would actually break. The tools that survive that question are the ones worth keeping. Most don't survive it.
A secondary question worth asking: "Am I using this, or am I using it to feel organised?" The latter category — tools that exist to make you feel like you have a system rather than to do specific work — is where most stack bloat lives.
What a ten-tool stack looks like
The people with the most functional stacks we've talked to tend to have fewer tools than you'd expect. One writing tool. One task manager. One communication tool. One calendar. One notes app. The rest of what they need is handled by the operating system, a browser, or a piece of paper.
The specifics matter less than the principle: every tool in your stack should do one job you'd miss if it disappeared. If you can't name the job, the tool probably shouldn't be there.
