Open your stack. Not the one in your head - the real one. Every trial you forgot to cancel. Every tool one teammate uses but nobody else does. Every integration glued to the seams of your workflow. Count them. The number is almost always worse than you think.
Most founders I audit are running somewhere between 40 and 120 tools across their company. Not "using" in any deep sense. Subscribed to. Paying for. Half-logged-in to. Building mental dependencies around.
The standard response is to call this a spend problem. It's not, at least not primarily. Ten tools at $20/month is $2,400/year - a rounding error for any company doing real revenue. The real bill is paid in cognitive overhead, integration friction, and the slow erosion of your team's attention.
This essay is about why the instinct to add another tool is almost always wrong, what the hidden costs actually look like, and what it takes to run with a stack that fits in your head.
Why adding tools feels like progress
Every tool has a sales page built around one promise: this will make you faster. Better analytics. Cleaner workflow. Fewer meetings. More leads. More retention.
Read enough of them and you start to believe that the gap between you and the people you admire is a tooling gap. It's comforting. It's actionable. A Saturday afternoon of signing up for things feels like work.
It isn't. Adding tools creates a local optimization at the cost of a global one. Your CRM gets better; your data is now in two places. Your task manager gets sharper; your team now has to check two inboxes. Your project template gets tighter; nobody except you understands the system.
You don't have a marketing problem. You have a sequencing problem, a decision problem, or an execution problem - and a new tool won't solve any of those.
Founders reach for tools when they don't want to admit the underlying issue is harder to fix than a Stripe subscription.
The four hidden costs
When I ask founders what their tools cost them, they tell me the monthly bill. That's the smallest of the four costs. Here are the others.
1. Context switch tax
Every tool is a different UI, shortcut system, and mental model. The research on task switching is unambiguous: a single context switch costs 10-20 minutes of effective work before you re-enter deep focus. A founder toggling between 15 tools a day is paying that tax dozens of times over. You can't schedule your way out of it - you can only reduce the denominator.
2. Data fragmentation tax
Customer data lives in your CRM, your email tool, your support desk, your analytics, your billing provider, your onboarding SaaS, your community platform. None of them fully agree on who your customers are. Every "360-degree view" product exists because somebody got rich solving a problem nobody should have had in the first place. The tool sprawl caused the fragmentation. The unification tool is its tax.
3. Integration tax
Every tool needs to talk to every other tool. You solve this with Zapier or Make or a pile of webhooks, and now you have an infrastructure. When something breaks, it's not clear which tool broke. When you swap one, you re-wire six. This is why most ten-person teams have a "tools person" on staff whose entire job is operating the Rube Goldberg machine of their stack.
4. Onboarding tax
Every new hire is now a curriculum. Here's our CRM, here's our wiki, here's our project tracker, here's where we actually write docs, here's the tool we say we use for meeting notes but nobody does, here's the Slack channel where decisions get made that contradict all of the above. Three weeks in, they're still finding tools you forgot to mention. At the end of month one, they've absorbed your chaos and become part of it.
Where the bloat actually comes from
Nobody wakes up intending to run 80 tools. The stack grows in predictable ways, and recognizing them is the first step to reversing them.
Vendor marketing. SaaS companies have become extraordinarily good at convincing you that a narrow tool is a non-negotiable category. Most of the categories on G2 don't need to exist. They exist because a vendor needed a category to own.
FOMO on AI. Every week there's a new AI tool promising to save you hours. Some do. Most don't. But the framing - "you'll fall behind if you don't adopt" - is designed to bypass evaluation and go straight to signup. The right question isn't "is this AI tool good?" but "is this job actually bottlenecked in a way a new tool solves?" Usually it isn't.
Team silos. Marketing buys a tool without telling ops. Ops buys an overlapping tool without telling marketing. A year later, you're paying for three things that do the same job because three departments each had a credit card. The longer the company runs, the more this compounds.
The free trial trap. "It's free for 14 days, what's the harm?" The harm is that in week two you'll integrate it with something, build a process around it, and by day 15 the switching cost is high enough that you pay. Free trials are a pricing strategy, not a generosity.
The principle: fewer tools, not more
The alternative isn't asceticism. It's discipline. The principle I use with every founder I work with is this:
A tool earns its place by solving a real, recurring problem that nothing in your current stack solves adequately - and keeps earning it every quarter.
Read it again. Every clause matters.
A real problem - not a theoretical one. If the job-to-be-done happens once a quarter, a tool is overkill.
Recurring - a one-time need is a one-time purchase or a manual workaround, not a subscription.
That nothing in your current stack solves - before signing up for the specialized tool, check whether the one you already have can do the job at 80% quality. Usually it can.
Keeps earning it every quarter - tools don't earn their place once. They earn it continuously. Run a quarterly audit or you'll wake up in three years with eighty of them.
How to run a brutal audit
Once a quarter, open your billing dashboard and your password manager. Make a list of every tool anyone in the company is paying for or logged into. For each, answer five questions. Be honest.
- What's the job-to-be-done? State it in one sentence. If you can't, the tool probably doesn't belong.
- Who uses it and how often? "The whole team, weekly" is a different answer than "one person, sporadically."
- What happens if we cancel it tomorrow? If the answer is "nothing urgent," cancel it.
- Is there a tool we already pay for that does this? 80% of the time, yes.
- What's the true cost? Add license + the time someone spends managing it + integration maintenance + the cognitive load of one more login. It's always 3-5x the subscription.
At the end of the audit, you'll have three piles: keep, kill, consolidate. Expect to cut 20-30% of your stack the first time through. If you cut less, you weren't honest.
What to cut first
Some categories almost always carry bloat. If you haven't audited in a year, start here.
Analytics overlap. If you have Google Analytics and PostHog and Mixpanel and a warehouse query tool, you have three analytics tools too many. Pick the one your team actually opens and cancel the rest. See our Google Analytics to Plausible guide for one way to simplify.
Communication sprawl. Slack plus Microsoft Teams plus Discord plus WhatsApp groups plus one channel per tool's "Slack integration." Pick one primary and route everything else through it.
AI tool proliferation. If every person on your team pays for ChatGPT, Claude, Perplexity, Cursor, Gemini, and a half-dozen niche AI tools, you're paying $100+/person/month and nobody is sure which wins at which task. Pick a primary (see our ChatGPT to Claude guide for a framework) and let specialists keep only their specialty tools.
Note-taking chaos. Notion for docs, Obsidian for personal, Apple Notes for quick, Google Docs for collaborative, Coda for structured, Linear for tickets-that-became-docs. Pick one for team docs and one for personal. Ruthlessly.
Automation spaghetti. Zapier for this, Make for that, custom scripts for the other. Consolidate the automation layer. Our Zapier to Make guide covers one direction; the principle applies either way.
Where to hold the line
Fewer tools, not zero tools. Some categories genuinely need specialists and trying to collapse them into one general tool produces worse work. My short list of places to not compromise:
Your primary writing environment. Writers need writing tools. Don't force a senior marketer to write in Linear just because you consolidated.
Design files. Figma is Figma. It's not a productivity tool, it's a profession-specific instrument. Keep it.
Version control. GitHub/GitLab for code, not Notion pages with "v3_FINAL_v2" in the title. Boring principle, rarely followed.
Accounting. Whatever your accountant uses. This is not a place to optimize.
The one tool each person uses for 80% of their day. If your head of sales lives in HubSpot and is shipping deals, the answer to "should we switch CRMs" is "why are we even having this conversation?"
The compound interest of discipline
None of this is novel. Every founder knows, in principle, that a smaller stack is better. The reason most of them still run an 80-tool bazaar is that each individual signup felt rational in the moment. The compounding - the quiet accumulation into chaos - happens in the background.
Reversing it requires the same quiet discipline: one audit a quarter, one cancellation at a time, one default of "no" to the next shiny launch. You will not feel the benefit in week one. You will feel it in month six, when a new hire is productive in three days instead of three weeks. You will feel it in year two, when the question "where does X live?" has exactly one answer.
The pitch of this site is embedded in its name. Fewer tools. Not no tools. Not cheap tools. Fewer tools, chosen deliberately, stress-tested quarterly, and owned - not just paid for.
That's the job.
Want help cutting your stack?
I audit stacks, find the 30% you can cancel this week, and consolidate what's left into a system that actually holds.
Work with me →
Further reading
- The Tools Directory - 270+ tools with opinions, verdicts, and pricing.
- Stacks - curated stacks by use case, so you don't build yours from scratch.
- Stack Doctor - tell us your current stack; get a prescription.
- Dead Pool - tools on their way out. Don't build new workflows on these.
- Switch Guides - step-by-step migrations for the most common consolidation moves.