Your Tech Stack Is a Throughput Problem, Not a Tooling Problem
Key Takeaways
- Software bloat is a throughput problem, not just an annoyance. Every unnecessary platform adds context-switching cost, onboarding friction, and data fragmentation that compounds across your team.
- Knowledge workers toggle between apps roughly 1,200 times per day, costing nearly 4 hours per week in reorientation time alone (Source: Harvard Business Review, 2022).
- A tool is only justified if it replaces multiple steps, not if it adds a new destination. Use the 5-step inventory exercise in this post to identify overlap and consolidate one workflow this week.
- AI integration becomes dramatically easier after simplification. Fewer data sources, cleaner inputs, and less ambiguity about where outputs go means faster adoption and better governance.
- We consolidated our own stack around M365 with Copilot and Claude, cutting software costs and reducing context switching across the team. The same discipline we teach clients starts in our own practice.
I sat down the other day to train our new Executive Assistant on the systems I use to run the business. Within 20 minutes, we both saw the same problem.
I was asking a smart person to memorize a maze.
Dozens of logins. Too many platforms. Constant tab switching. A process that “worked” only because I had the context in my head.
That is not a system. That is tribal knowledge with a monthly subscription.
This post is about why simplicity is not a preference. It is an operational advantage.
Software bloat is not a tooling problem. It is a throughput problem.
Most teams think software bloat is annoying. It is worse than that.
Software bloat creates friction, and friction becomes cycle time.
If you have ever watched a project schedule slip, you know the pattern. The work itself is not always the issue. The handoffs are. The rework is. The waiting is. The “where is that file” and “who owns this step” and “what system is the source of truth.”
The research backs this up. A 2022 Harvard Business Review study found that the average knowledge worker toggles between applications roughly 1,200 times per day, costing nearly four hours per week just reorienting after each switch. That is approximately 9% of total work time lost to digital friction (Source: Harvard Business Review, 2022). Research from the University of California, Irvine found it takes an average of 23 minutes and 15 seconds to fully regain deep focus after a significant interruption (Source: UC Irvine / Mark, Gonzalez, Harris, 2005). And the American Psychological Association has documented that frequent task-switching can consume up to 40% of a person’s productive time due to cognitive load (Source: APA, 2020).
A bloated tech stack amplifies all of this across your entire team:
More logins means more time lost to context switching. More platforms means more places for data to drift out of sync. More “tools” means more standard operating procedures to maintain. More complexity means slower onboarding for every new hire. More moving parts means more failure modes in your delivery process.
Engineers already understand this principle. If you want a plant to run reliably, you reduce unnecessary valves, instruments, and handoffs. You simplify the flow path. You standardize.
Your business operations deserve the same discipline.
The ROI question: does this tool reduce steps or create steps?
Some software is absolutely worth it. If a platform truly eliminates steps, reduces rework, and improves visibility, it can be a net-positive return on time and money.
The problem is the slow creep of “one more tool.”
One tool for scheduling. One tool for docs. One tool for internal notes. One tool for forms. One tool for signatures. One tool for a dashboard. One tool for approvals. One tool for client updates. One tool for tasks.
Every tool sounds small until you stack them. According to Okta’s 2024 SMBs at Work report, businesses of all sizes now average around 93 applications, and even companies with fewer than 200 employees use an average of 42 SaaS tools (Source: Okta, SMBs at Work 2024). Those SaaS portfolios are growing at roughly 33% year-over-year (Source: Zylo, 2025 SaaS Management Index).
A practical filter I use with clients: A tool is only justified if it replaces multiple steps, not if it adds a new destination.
Here is how to tell if a tool is creating drag instead of leverage:
| Signal: Tool Creates Drag | Signal: Tool Creates Leverage |
|---|---|
| You use it weekly but maintain it daily | Setup is minimal and the tool runs without babysitting |
| You still export data to “finish the job” elsewhere | Outputs are usable where they land, no second step needed |
| People keep building parallel processes in spreadsheets | The tool is the single source of truth for its function |
| Training new hires requires a live walkthrough, not a checklist | A new team member can follow documented steps independently |
| The tool’s features overlap with capabilities you already pay for | The tool does something no other platform in your stack handles |
That last row is the big one.
The simplest stack is often “fewer platforms, deeper capability”
During the EA training session, we found several places where I had bought “point solutions” that were duplicative. In a few cases, the core platform we already used could handle 80% to 90% of what we needed, if we set it up properly.
Here is what I tell clients: we went through the same exercise in our own business. We had accumulated separate tools for presentation generation, meeting scheduling, event registration, document collaboration, and more. When we stepped back and evaluated, we consolidated our core stack around Microsoft M365 with Copilot for everyday business operations and Claude as our high-horsepower LLM for deep analysis and content work. The result was fewer software subscriptions, lower monthly costs, reduced context switching for the team, and fewer “work surfaces” each person had to manage daily. Most importantly, our data landed in fewer places, which made it more usable for AI workflows and more governable for security.
That consolidation matters for two reasons:
Reduced switching cost. Every time you move from one platform to another, you pay a mental reset. The Asana Anatomy of Work Index found that knowledge workers switch between 9 apps per day, and the majority feel overwhelmed by them. Over half (56%) feel they must respond to notifications immediately, fragmenting their deep work time (Source: Asana, Anatomy of Work Index 2022). Multiply that across your team and you have a real productivity tax.
Simpler SOPs and onboarding. If your workflow lives inside fewer systems, training becomes repeatable. You can document it once. You can assign it. You can audit it. You can improve it.
A “simple” stack is rarely minimal. It is coherent.
Coherence means your team knows where work enters the system, where decisions happen, where outputs live, what “done” looks like, and who owns each step.
That clarity beats another shiny tool every time.
A practical simplification exercise you can do this week
If your stack feels bloated, do this quick inventory. It takes 30 to 45 minutes and it surfaces the obvious.
Step 1: List every platform involved in delivery. Include everything used to take a job from request to completion: intake, estimating, proposals, scheduling, project execution, QA/QC, client communication, invoicing and closeout.
Step 2: For each platform, write its single job. One sentence only. If you cannot define its job in one sentence, that is a red flag.
Step 3: Mark overlap. Circle any platform whose job overlaps with another. Overlap is where simplification usually starts.
Step 4: Count credentials, not tools. The real pain is not the number of logos on your app list. It is the number of identities your team must maintain. If a workflow requires three logins to finish one task, you have friction baked into the process.
Step 5: Pick one workflow to consolidate. Choose something repeatable and visible: new project kickoff, change order processing, weekly client updates, quote follow-up, or closeout package assembly. Do not start with “everything.” Start with one pipeline.
This is the same “map the workflow, find the waste, address the constraint” sequence we use in every engagement. Lean waste elimination and Theory of Constraints analysis apply to your internal operations just as much as they apply to engineering delivery.
Where AI fits: after the stack is simplified
A lot of teams try to add AI on top of a messy process.
That is like adding a high-end flow meter to a line full of leaks. You get better data, but you still have leaks.
After implementing AI across 40+ engineering projects, here is the order that consistently produces results:
- Map the workflow end to end
- Remove waste and reduce handoffs
- Identify the real constraint
- Automate what is rule-based
- Use AI where judgment, drafting, summarization, or pattern work slows humans down
- Measure with clear KPIs, then scale
This “constraint first” approach is how we run our AI integration and roadmap engagements. We avoid tool-first decisions. We start with the bottleneck tied to outcomes, then design the pilot around that reality.
That is also why simplification and AI go together. When you consolidate platforms and clarify the process, AI becomes easier to integrate responsibly: fewer data sources to connect, cleaner inputs to your AI workflows, less ambiguity about where outputs should go, easier governance and review, and faster training and adoption.
In my practice, we have found that firms who simplify their stack before layering in AI see measurable results in weeks rather than months. The renewal happens in the right order: clean up the process, then amplify it with better tools. Renewal, not just addition.
The onboarding test: would a new hire survive your stack?
Here is a concrete way to think about it.
If you hired a new coordinator tomorrow, could you hand them one system for tasks and status, one system for files and templates, one system for client communication history, and one documented checklist per recurring process?
Or would you need to say: “Ok, here is Tool A for this, Tool B for that, Tool C for when Tool A fails, and also check this spreadsheet because the real status lives there.”
That gap is the cost of bloat. And it compounds every time someone joins, leaves, or changes roles.
The simplest systems scale the best
Complex stacks create dependence on the person who built them. Simple systems create independence. If you want to grow without adding chaos, take the same mindset you use in engineering: reduce friction, standardize interfaces, remove unnecessary components, make the system observable, and improve the constraint, then repeat.
We test everything in our own engineering firm first. Our tech stack consolidation was not a theoretical exercise. It was a real operational decision that reduced costs, improved onboarding speed, and positioned our data to work harder through AI integration. That is the same approach we bring to every client engagement.
If your stack feels like a maze and you are not sure where to start, download the free AI Integration Blueprint. It is a simple tool that pinpoints where simplification and AI can save your team hours and free them to focus on the work that matters most.
