Questions we answerProcess and ownership
We have too many tools. What should we cut?
Count problems, not tools. Ten tools each doing one job cleanly are fine; three holding the same customer list are not.
Free · a few minutes · starts from “Something in the team isn't working”
The short answer
Count problems, not tools. Ten tools that each do one job cleanly are not a problem; three tools holding different versions of the same customer list are, and cancelling subscriptions does not fix that — it is an ownership and integration problem wearing a cost problem's clothes. Cut where data is duplicated, where nobody owns a tool, or where you are paying for seats nobody opens. Consolidating everything onto one platform trades many small dependencies for one large one.
Two different problems arrive under this heading and they need opposite responses. One is cost: licences nobody uses, renewals nobody reviews. The other is coherence: the same information living in three places, none of them authoritative, with somebody re-keying between them.
The first is an afternoon with a card statement. The second is not solved by having fewer tools, and attempts to solve it by consolidating often make it worse, because the new single platform inherits the same unowned data and adds a migration.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- Somebody can name a piece of information that exists in three systems and disagrees between them.
- You are paying for seats that have not been opened this quarter.
- Nobody can say who decides whether a tool stays.
Signs it's something else
- Each tool does one job, has an owner, and is used. That is a stack, not sprawl.
- The discomfort is the length of the list rather than anything it is costing you.
- The real problem is a process that hands work between people badly, and the tools are just where you notice it.
What's usually behind it
- A renewal or a cost review that surfaced how many subscriptions exist.
- Somebody spending real time copying information between systems.
- Tools adopted by whoever needed them, with nobody deciding who owns them afterwards.
What people usually get wrong
- Consolidating onto one platform for tidiness, and discovering the lock-in is worse than the sprawl was.
- Cancelling a tool somebody depends on because nobody owned it well enough to say so.
- Quoting circulated statistics about software sprawl. Most of them are enterprise-sourced, unattributed, or years old.
The options, and when each one fits
In no particular order. Which of these fits depends on your situation, not on the question you typed.
Do a seat audit
The concern is cost. Compare what you pay for against what is actually opened.
Fix duplicated data
The same record lives in several places. Decide which one is authoritative before touching anything else.
Integrate rather than consolidate
Each tool is genuinely good at its job and the pain is what happens between them.
Leave it alone this quarter
Nothing is being duplicated or wasted, and the discomfort is aesthetic rather than operational.
When doing nothing is the right call
If no data is duplicated and nothing is being paid for unused, the number of tools is not a problem worth a project. Naming an owner for each one costs an hour and prevents most of the ways this goes wrong later.
What the diagnostic asks
- What is actually going wrong, and how long it has been going on.
- Who owns this today and how much is written down.
- How repeatable the work between tools is.
- Whether software is already in place that covers it.
“I don't know” is always an answer. Nothing is assumed on your behalf.
The routes it weighs
Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.
Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
Do nothing yet
Record the issue, set a revisit date, and decide what would change your mind.
Redistribute
Move ownership of the work to where it fits, and make that explicit.
AI Assist
Keep a person in charge and give them AI for drafting, summarising, checking or analysis.
Specialist support
Bring in a freelancer, consultant or specialist for a defined piece of work.
What changes the answer
- The same data in more than one place is the clearest signal that this is real rather than cosmetic.
- Tools with no named owner tend to be the ones that rot, whatever they cost.
- Heavy manual re-keying between systems points at integration rather than at cancellation.
Get your own read
A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.
Related questions
- Nobody owns this work. What do I do?Give it an owner. That is almost always the first move, and it is faster and cheaper than anything else on the list.
- Is my business too small for a CRM?Often yes, for now. A CRM solves a handoff problem, not a memory problem — and a half-adopted one is a worse record than the spreadsheet it replaced.
- Should we build custom software or buy something off the shelf?At this size, almost always buy. The cost that sinks small-business builds is not the build — it is owning it in year two without a developer.
- Is this a process problem or a people problem?More often process than managers expect. If your most capable person would struggle in the same seat, the work is badly shaped. If one person struggles where others do not, the answer is about that person.
- Nobody has written our processes down. Is that a problem?Only where a process runs regularly and one person knows it. Documenting everything is a project small teams abandon; documenting a broken process makes the bad version official.
- Should I document the process before automating it?Yes, and not because documentation is virtuous. Writing it down is how you find the steps that should not exist — which is most of the value automation ever delivers.