There is no magic number; a tool count is only a problem when it creates friction. The real warning signs are overlapping tools doing the same job, data copied by hand between systems, a stack nobody fully understands, and cost that outpaces value. Too many is when your tools cost more attention than they save.
Information current as at 5 July 2026
People ask for a number, and there genuinely is not one. A business running smoothly on many tools has fewer problems than one struggling with a handful that do not fit. The right question is not how many tools you have, but whether they cost you more attention than they save. Here is how to judge that honestly, and what to do if the answer is yes.
It is tempting to imagine a threshold, some count above which you have too many tools, but there is not one. A business can run happily on many tools if they fit well, connect cleanly, and each earns its place. Another can be miserable with only a few that overlap, do not talk to each other, and force constant manual work. The count is a poor measure because it ignores fit and connection, which are what actually determine whether tools help or hinder. So set aside the number. The real question is about friction, and a stack of twenty well-chosen tools can produce less of it than a stack of five badly-chosen ones.
What you watch for is friction, and it has recognisable shapes. Overlap: two or more tools doing substantially the same job, so you pay twice and split your data across both. Manual copying: people moving the same information between tools by hand, which is slow and error-prone. A stack nobody fully understands, where no one person can explain what every tool does or why it is there. Constant context switching, the day spent hopping between logins and interfaces. And cost that has quietly outpaced the value the tools return. When several of these appear together, you have too many tools regardless of the actual number, because the stack has started taking more than it gives.
If you have made something and it needs to become real, send it over. We will tell you honestly what it needs to be live, safe and yours, whether that is a quick fix you can do or a proper build. No obligation.
A crowded, poorly-connected stack costs more than its subscriptions. There is the mental load: every tool is one more thing to remember, learn, log into, and keep secure, and that load falls hardest on small teams where a few people hold everything. There is the copying: hours spent moving data by hand between tools that will not share it. There is the error rate: every manual transfer is a chance to introduce a mistake. And there is the fragility: more tools means more accounts, more passwords, more places something can break or leak. None of this appears as a line on a bill, which is why a crowded stack can feel affordable while quietly costing a great deal in attention, time and risk.
If the signs point to too many, the fix is deliberate, not drastic. Start by auditing what you have and why, so you can see the overlap and the orphans clearly. Cancel the tools nobody uses or can account for. Consolidate the overlapping ones into whichever does the job best. Where several tools are each doing part of one workflow and forcing manual copying between them, consider whether a single system that fits your work could replace the cluster, which for a genuine tangle is often a fraction of a legacy build. Do this carefully, keeping data safe through each change, rather than cancelling in a burst. The goal is not the fewest possible tools; it is a stack where every tool earns its place and the friction is gone.
Trimming the stack once is easy to undo, because the same forces that grew it are still at work. A busy week, a new problem, a quick trial that becomes a paid plan, and the sprawl quietly rebuilds. The way to hold the ground you gained is to add a little friction to adding tools. Before signing up for anything new, ask whether an existing tool already does the job, whether the new one will connect to what you have or become another island, and who will own it. Keep the list of what you pay for somewhere visible, and revisit it on a regular schedule rather than only when the total alarms you. None of this means refusing useful tools; it means adopting them on purpose rather than by accident, so that each addition is a decision you would defend rather than one you forgot you made. A stack stays lean not because someone cleaned it up heroically, but because the business developed the habit of only keeping tools that clearly earn their place, and of noticing quickly when one stops.
For most businesses, trimming and consolidating is as far as this needs to go, and cancelling the dead weight while merging the overlaps solves the problem well. But there is a point past which consolidation naturally becomes a case for building. It arrives when you find that no single off-the-shelf tool can absorb the cluster, because the way those tools connect in your business is specific to you, and any ready-made option would leave you back in the same patchwork of exports and manual copying. At that point a custom system that holds the whole workflow in one place stops being an extravagance and starts being the honest answer to the sprawl, and for a genuine tangle it is usually a fraction of a legacy build. This is not the outcome for a business with a few too many tools that mostly fit; those should simply trim. It is the outcome for a business whose core way of working has grown across a set of tools that were never designed to work together, where the sprawl is not clutter but a structural mismatch between how your business runs and how rented tools are shaped. Recognising which situation you are in is the difference between a sensible tidy-up and a decision to own the system that runs your operation.
If you have made something and it needs to become real, send it over. We will tell you honestly what it needs to be live, safe and yours, whether that is a quick fix you can do or a proper build. No obligation.
Whether you can name exactly what you want built, or you just know something is leaking, the next step is the same conversation.