Blog · Consolidation · Updated · By the FitMySaaS team
Too many apps at work? How small teams cut tool fatigue
Short answer: Too many apps at work has a measurable cost. A Harvard Business Review study found workers toggled between apps nearly 1,200 times a day, losing just under four hours a week to refocusing. For a small team, the fix is one home per job, fewer notifications and clear rules on where work lives. The caveat: dropping a tool clients rely on can cost more than it saves.
What does the research say about switching between apps?
Two studies are worth knowing. They measure different things, so the numbers are not directly comparable.
| Study | Who was studied | Key finding |
|---|---|---|
| Harvard Business Review, August 2022 | 137 users on 20 teams at three Fortune 500 companies, tracked for five weeks | Nearly 1,200 toggles a day per person; each cost a little over two seconds; just under four hours a week, about 9% of work time, spent reorienting |
| Lokalise tool fatigue survey, 2025 | 1,000 US knowledge workers across 11 industries, self-reported | 33 switches a day on average; 51 minutes a week lost to tool fatigue; 56% say it hurts their work each week |
The HBR figures come from tracked activity, so they count every tab change. The Lokalise figures are what people remember, which explains the gap. Both point the same way.
One more number from the Lokalise survey stands out: 79% of respondents said their company had not taken steps to reduce tool fatigue or consolidate platforms. Most teams know there is a problem and leave it alone.
How do you know your team has too many apps?
Look for these signs. Two or more usually means it is time to act.
- People ask "where is that?" more than once a day.
- The same task is tracked in two places, such as a chat thread and a task board.
- New hires need a list of logins on day one and still miss some.
- Client details live partly in the CRM, partly in a shared doc and partly in email.
- Nobody can say which tool is the "real" one for a given job.
- Notifications arrive from four or five tools for the same piece of work.
The count of apps matters less than overlap. A team with eight tools that each do one clear job is often fine. A team with five tools where three of them hold tasks is not.
How many apps should a small team use?
There is no reliable published benchmark for small businesses, so treat any single number with caution. A better test is one tool per job. List the jobs your team does and check each has exactly one home.
| Job | One home | Common overlap to remove |
|---|---|---|
| Team messages | One chat tool | Chat in the task tool and in a second chat app |
| Tasks and projects | One task tool | Tasks in chat, docs and spreadsheets |
| Docs and notes | One docs tool | Notes split between a docs tool and a shared drive |
| Clients and deals | One CRM | Client lists in spreadsheets |
| Customer requests | One help desk or shared inbox | Requests handled from personal inboxes |
| Meetings | One scheduling and video setup | Two scheduling links on the same team |
How do you cut tool fatigue without disrupting work?
Change one thing at a time. A big switch on a Monday morning creates more confusion than it removes.
- List every tool and its job. Use card statements and your admin console. Step one of our guide to cutting your team's SaaS bill shows how.
- Mark the overlaps. Any job with two or more tools is a candidate.
- Pick the keeper by usage, not features. Keep the tool most of the team already opens every day.
- Set a move date and a read-only date. Move active work first. Keep the old tool read-only for a month, then cancel it before its renewal.
- Turn off duplicate notifications. If a task tool posts into chat, decide which one people should act from and mute the other.
- Write down where things live. A one-page note ("tasks live here, client notes live here") does more than any setting.
Some tools should stay even if they overlap. If clients use your scheduling link, or a partner shares a workspace with you, the cost of changing falls on them too.
Does connecting apps with integrations fix the problem?
Sometimes. Integrations and automation tools stop people copying data by hand, which is useful. But they don't reduce the number of places people look, and each connection is one more thing to maintain when a tool changes.
Use integrations when each tool is needed for its own reasons. If you are connecting three tools only so they act like one, consolidation may be simpler. The software consolidation guide covers how to decide.
When one system makes more sense
If your team uses five or six tools for one workflow and only a few features from each, one system can remove the switching and the overlap at once. The free SaaS cost calculator shows what those tools cost today at list price. FitMySaaS builds one system with just the features your team uses; the team uses a working version free for a week before deciding.
Questions
What is app fatigue?
App fatigue, also called tool fatigue, is the strain of switching between many work apps, logins and notification streams. It shows up as lost time, missed messages and work tracked in more than one place.
Is it better to use an all-in-one tool or several best-of-breed tools?
It depends on how deep each job goes. A support team handling thousands of tickets may need a dedicated help desk; a 15-person team that mainly needs tasks, docs and chat can often use fewer tools.
How do you convince your boss the team has too many apps?
Bring two numbers: the monthly cost of overlapping tools from your card statements, and one concrete example of work lost between two tools. Specific beats general.
Will removing apps upset the team?
It can, if people lose a tool they like without a clear reason. Ask the team which tool they open most for each job, keep that one, and explain the move date in advance.