I was paying it for longer than I want to admit before I even had a name for it.

There was a period in my business where I had more tools than I could confidently explain to someone, more processes than any one person could hold in their head at once, and more offers than my marketing could actually support properly. Each piece had been added for a good reason. Each tool solved a real problem when I brought it in. Each process existed because something had broken without it. But at some point the whole thing had quietly become heavier to run than the business itself warranted, and I was spending a significant chunk of my week just managing the complexity I’d built rather than doing the work that actually moved things forward.

That’s the complexity tax. It’s the cost you pay, in time, money, and mental bandwidth, for running a business with more moving parts than it needs. And the reason it’s so easy to miss is that it doesn’t announce itself. It just shows up as a general sense that everything takes longer than it should.

What the complexity tax actually looks like day to day

It looks like a Monday morning where it takes the better part of an hour to reconstruct where you left off on something, because the information lives across three different platforms and none of them are quite talking to each other the way you set them up to. It looks like a team member who can’t move forward without your sign-off on something that should have been handled by a system eighteen months ago. It looks like a launch that was supposed to be straightforward taking three times as long as it needed to because the backend is a collection of workarounds held together with Zapier and goodwill.

None of those things feel catastrophic in the moment. That’s kind of the point. The complexity tax is death by a thousand small frictions, and because each one is manageable on its own, you adapt to each one rather than stepping back and asking why the whole thing feels so much heavier than it used to.

By the time most people recognise what’s happening, they’ve been paying the tax for a while. And the instinct at that point is usually to add something to manage it, a project management tool to track everything else, a VA to help wrangle the systems, a new SOP to address the breakdown in the old one. Which, if you follow that logic, just adds more to the pile.

Where it tends to accumulate

Tech stacks are the most obvious place, and the one I have the most direct experience with. I went through a full consolidation a few years back and it was one of the better decisions I’ve made for the business. I had been running on a collection of tools that each did their thing reasonably well in isolation, but the integrations between them were fragile, diagnosing problems when something broke meant mentally reconstructing a map of how everything was connected, and the cognitive overhead of just knowing which platform held what was real and ongoing. I consolidated down to one primary platform, saved about five thousand dollars a year, and got back a meaningful amount of mental energy that had been quietly going into software management instead of strategy. If you want the full breakdown of what that process looked like, I wrote about it in detail and linked it at the bottom of this post.

Offer suites are another place it accumulates, and this one surprises people. There’s a version of growth that looks like adding more offers, more tiers, more entry points, because more ways for people to say yes feels like a good thing. And up to a point it is. But there’s a tipping point where the number of offers you’re maintaining costs more in delivery, marketing bandwidth, and ongoing attention than the revenue they’re generating. When every offer needs its own funnel, its own content, its own onboarding, and its own client experience, the business starts to fragment in a way that makes it genuinely hard to grow any one thing particularly well.

Team and delegation structure is the third one, and probably the most underestimated. When a business grows without intentional systems, the founder tends to become the connective tissue between everything. Team members learn to route questions upward because that’s what the culture trained them to do. Decisions that should be made at the team level come back to the top because there’s no clear framework for making them otherwise. That’s not a team problem. It’s a systems problem. And it means the founder is paying a complexity tax in availability and decision-making bandwidth that quietly limits how much the business can actually scale.

What it does to your thinking

This is the part that doesn’t get talked about enough. When your mental bandwidth is being consumed by the operational weight of keeping everything running, the kind of clear, forward-looking thinking that actually moves a business forward becomes harder to access. You end up reactive because you’re always dealing with something. You end up in maintenance mode because maintenance is always more urgent and growth requires a kind of sustained attention that a cluttered business makes hard to protect.

You feel busy all the time without a clear sense that the busyness is producing anything proportional to what it’s costing you. And that is a demoralising way to run a business you worked hard to build.

That’s not a mindset problem. It’s a design problem. The business is structured in a way that doesn’t leave room for the thinking it needs, and no amount of mindset work or productivity hacking fixes a structural issue.

What actually reducing the complexity tax looks like

It starts with getting honest about what you’re actually running. Every tool, every offer, every recurring process, every system that requires ongoing attention. Not to judge any of it, just to see the full picture clearly, probably for the first time in a while. Then the question is straightforward even if the answer isn’t: what’s doing real work for the business, and what’s there because it made sense at some earlier point and nobody ever made a deliberate decision to stop.

Cut or consolidate what isn’t earning its complexity. That might mean retiring an offer that’s not converting well enough to justify its footprint. It might mean platform consolidation. It might mean building cleaner delegation structures so fewer things route back to you by default. None of these are trivial decisions, but the cumulative effect of making them is a business that’s easier to run, easier to grow, and frankly easier to show up for on a Wednesday afternoon when your energy isn’t at its peak.

If the tech stack is where the complexity is sitting for you, How Simplifying My Tech Stack Reduced My Software Costs (and Finally Made My Business Feel Coherent) walks through exactly what that process looked like for me and what changed on the other side of it.

And if the complexity is showing up more in how you’re spending your time as a founder, Why Your Business Still Depends on You (And the One Hour That Changes That) gets into the structural shift that actually changes that pattern.

If your business has started to feel more complicated than it needs to be and you’re not sure what’s worth keeping and what’s just adding weight, let’s look at it together.

Book a call and we’ll figure out where the complexity tax is highest and what to tackle first. Grab a time here.

We’ve also covered business simplification, tech stack decisions, and sustainable growth on the Acquire Podcast. Start listening here.