Twelve tools, no overview: how to consolidate the stack
Tool sprawl never comes from one decision but from twelve small ones. Each was right on its own. Together they produce costs nobody has a view of, and data that is complete nowhere.
In short
- Four questions per tool decide keep or switch off — the most important is where the leading data sits.
- A tool becomes a problem when it holds contact data that is complete nowhere else.
- Five to six tools are enough for most small companies: website, contacts, sending, analytics, storage, appointments.
- Switching off works in three steps — and the last one, the shutdown date, is the one forgotten most often.
How it happens
Always the same way: someone needs something at short notice, finds a fitting tool, sets it up in an hour. That repeats twelve times over two years. Every single decision was reasonable.
The problem is not the number but what follows from it: contact data sits in four places, none of them complete. Nobody knows which tools are still being paid for. When someone leaves, access is lost.
The four questions per tool
1. Has it been used in the last three months?
Not "we might need it sometime." Actual use. If no: a candidate for switching off, provided no data sits in it.
2. Does it hold data that is complete nowhere else?
The most important question. A tool with unique contact data cannot simply be switched off — it needs a migration first.
3. Does it overlap with another?
Two tools both managing contacts are a problem — regardless of how good each is on its own. Where there is overlap: one wins, the other goes.
4. Who knows the credentials?
If the answer is "one person", that is a failure risk. If it is "nobody any more", a payment may be running for something nobody uses.
Worth knowing
The most expensive part of the sprawl appears on no invoice: it is the time lost because a question cannot be answered in one system.
"Did this customer get our last newsletter, and what did they enquire about before that?" — if the answer sits in three systems, it takes ten minutes instead of ten seconds. At twenty such questions a week that is several hours. That time appears in no cost breakdown and is nonetheless the largest item.
What a small company genuinely needs
| Area | Needed? | Note |
|---|---|---|
| Website and content | yes | with or without a CMS, depending on the build |
| Contacts and cases | yes | from about 2–3 people in customer contact |
| Email sending | yes | separate from the ordinary mailbox |
| Web analytics | yes | one, not two in parallel |
| Storage and collaboration | yes | one place, not three |
| Appointments and tasks | yes | often already part of the contact system |
| Design, images, video | as needed | often the biggest area of sprawl |
| A dedicated automation platform | rarely | worth it only with several running processes |
Consolidating in three steps
- Take stock. List every tool — including the ones running on a personal card. Per tool: purpose, cost, last use, who has access, which data sits in it. Two hours.
- Settle the leading source per kind of data. Where do contacts sit in future as the leading record? Where documents? Where appointments? One place per kind, in writing. This decision is the actual core.
- Migrate with a shutdown date. Export the data from the tools being retired, import it, check it — and set a date from which the old system is only read and no longer maintained.
Taking stock regularly surfaces two things nobody expected: running payments for tools nobody has opened in over a year, and access issued to a person who is no longer with the company.
Both are quiet problems — the first costs money, the second can block access to your own data when it matters. Those two findings alone usually justify the two hours.
Help me order our stock of tools. Our tools (name, purpose, cost per month, last use, who has access, which data sits in it): [paste list] Our situation: - People in customer contact: [number] - Contacts in total: [number] - What regularly takes longer than necessary today: [bullet points] Tasks: 1. Answer the four questions per tool: used in the last three months, unique data in it, overlap with another, who knows the credentials. Mark the tools where my details are not enough. 2. Name every overlap and propose per pair which one stays and why. 3. Settle a leading source per kind of data – contacts, documents, appointments, content. 4. Name the tools that can be switched off without a migration, and those where data has to move first. 5. Work out the cost saved per year and estimate the time consolidation saves us weekly. 6. Name the risks when switching off and what we have to secure beforehand. Do not recommend replacement products.
In closing
Sprawl is not a sign of disorder but the natural consequence of many correct individual decisions. Tidying up does not happen through the number but through one decision: one leading source per kind of data.
The rest follows almost by itself — and the two hours of stocktaking usually surface enough surprises to pay for themselves before anything has been switched off at all.
Common questions
How many marketing tools does a small company need?
Five to six are usually enough: website, contacts and cases, email sending separate from the mailbox, one web analytics tool, one place for storage, and appointments. Design tools come in as needed; a dedicated automation platform is worth it only with several running processes.
How do you tell a tool can go?
By four questions: has it actually been used in the last three months? Does it hold data that is complete nowhere else? Does it overlap with another? And who knows the credentials? A tool with no use and no unique data can go immediately.
What does tool sprawl really cost?
The largest item appears on no invoice: the time lost because a question cannot be answered in one system. If the answer sits in three systems it takes ten minutes instead of ten seconds — at twenty such questions a week that is several hours.
How do you go about consolidating?
In three steps: a complete stocktake with purpose, cost, last use, access and the data held; the decision on a leading source per kind of data; and the migration with a fixed shutdown date from which the old system is only read.
What do you usually find when taking stock?
Two things nobody expects: running payments for tools nobody has opened in over a year, and access issued to a person who has left the company. The second can block access to your own data when it matters.
Marketing that sets itself up
The Studio Engine beta is live. Claim your spot and help shape it from the start.
Join the beta →