Count your tabs.
That number is a tax on your margins.
Every tool you add to your stack feels small in isolation. One more SaaS subscription. One more login. But complexity in your toolstack compounds exactly the same way complexity in your org chart does — and almost nobody audits it, because no single tool ever feels like the problem.
Glance at your laptop. Count the tabs open. Count the apps your team switches between just to complete one workflow — onboarding a client, processing an invoice, shipping a piece of work. If that number is anywhere near ten, this isn’t a minor inconvenience. It’s a switching tax, and it’s quietly eating your margins without ever appearing as a single line item.
Digital friction is the most literal, most visible expression of operational complexity. It’s complexity you can actually see on a screen. Here are the three moves that fix it.
Move 1
Run the tool-to-task audit
Pick one core workflow — taking a new client from signed contract to first delivery. Map every tool that workflow touches, step by step, with someone who actually does the work.
Most leaders are stunned by the result: eight, ten, sometimes fifteen separate tools, none of which talk to each other, each requiring a manual handoff of information already entered elsewhere.
The rule: every one of those handoffs is a moment where data can be lost, delayed, or duplicated. That’s not just an efficiency cost — it’s an error cost and a morale cost.
Move 2
Consolidate the tech stack into a value stack
Growing businesses default to solving every new problem by buying a new tool. Nobody removes anything — they only add. A stack of fifty apps is a liability, no matter how good each individual app is. A stack of five deeply integrated systems is an asset.
The question isn’t “does this tool solve a problem?” Almost any tool solves some problem. The question is whether it justifies its existence within an integrated system, or creates a new island.
The rule: every tool that doesn’t talk to the rest of your stack is a future shadow workflow waiting to happen — the same operational debt that compounds quietly over time.
Move 3
Make integration a procurement criterion
From today, no new tool gets approved without answering one question first: how does this integrate with what we already have? If a department head wants new software, integration capability becomes a non-negotiable line in the business case — not an afterthought discovered three months after rollout.
The rule: this single procurement discipline moves you from reactive tool sprawl to deliberate tool architecture.
Closing Phase 2 — Mastering Chaos and Complexity
Across six posts: the growth-complexity crossing → the founder’s trap → operational debt → the hybrid trap → digital friction. The thread running through all of them: complexity isn’t your enemy. It’s the natural consequence of growth. What separates clean scaling from chaotic scaling is whether someone is deliberately architecting the systems that absorb it.
“Your operations should feel like a paved highway, not a digital obstacle course.”
The A in PATH 2 SCALE — Actionable Strategy and Process Optimisation — exists precisely to build that highway. Not by adding more tools, but by ensuring the ones you keep are talking to each other and earning their place.
Most businesses don’t fail to scale. They leak value faster than they can create it. Digital friction is one of the most visible — and most fixable — leaks of all.
Free diagnostic
Find where your business is leaking value
The Stop the Leaks assessment identifies exactly where value is leaving your business — and what to do about it first.