You Don't Have an IT Problem. You Have a Decision Problem.

Most small business owners I speak to start the conversation the same way. They describe a technology frustration. The software that doesn't do what they thought it would. The process that takes twice as long as it should. The system that worked fine two years ago but now feels like it's held together with sellotape and good intentions.

And almost every time, the thing they're describing isn't actually a technology problem.

It's a decision that hasn't been made yet.

The subscription graveyard

Here's something that still surprises people when I mention it. Research from Spendesk, who analysed over 332,000 subscriptions across businesses, found that only 34% of software subscriptions are actively used. That means roughly two thirds of what companies pay for every month is delivering zero value. Worse still, 47% of subscriptions continue being paid for long after the last person actually logged in.

Now, those numbers come from businesses of all sizes. But in my experience, the pattern hits smaller businesses harder because there's no one whose job it is to notice. At a larger company, there's procurement. There's an IT team doing quarterly licence reviews. At a 10 person business, the person who signed up for that project management tool three years ago might not even work there anymore, but the direct debit is still going.

This isn't a technology problem. Nothing is broken. Everything is working exactly as designed. The problem is that no one has sat down, looked at what's actually being used, and made a decision about what stays and what goes.

The demo trap

I see this one constantly. A founder or operations manager goes to a software demo. The demo is brilliant. The sales rep is polished. The tool looks like it does everything. So they sign up, start the onboarding, and three months later the team is using maybe 15% of the features while the rest sits untouched.

The tool isn't the problem. The decision process before the tool is the problem.

Nobody asked the hard questions first. What specific issue are we solving? What does our current workflow look like, step by step? What would "fixed" actually look like in practice? What are we already paying for that might do this if we configured it properly?

These aren't technical questions. They're thinking questions. And when you skip them, you end up collecting tools instead of solving problems.

UK organisations are wasting around 20% of their software spend because tools are underused, poorly implemented, or too difficult for employees to navigate. That's according to research highlighted by SecurityBrief UK in late 2025. They also found that system complexity is costing businesses roughly 7% of their annual revenue. For a business turning over half a million, that's £35,000 in friction, delays, and workarounds that nobody has the bandwidth to fix.

Not because the technology is bad. Because the decisions around it were never properly made in the first place.

The "we'll sort it later" pile

Every growing business has one. That collection of things everyone knows aren't quite right but nobody has the time, confidence, or energy to address.

The CRM that nobody trusts because the data is patchy. The onboarding process that's different every time because it was never properly documented. The spreadsheet that started as a quick fix and is now somehow load-bearing infrastructure for half the operation.

These aren't technology failures. They're decision deferrals. And the longer they sit, the more expensive they get to deal with. Not just in money, but in time, energy, and the slow erosion of confidence in how the business operates.

A report from Fortray noted that SMEs frequently make ad hoc technology decisions based on immediate needs rather than aligning them with broader business objectives. They called it "tech debt," and it's a perfect description. Every quick fix you don't come back to compounds. Eventually you're spending more time managing the workarounds than you would have spent making a proper decision in the first place.

Why this keeps happening

There's no shame in any of this. It happens for understandable reasons.

First, most small business owners aren't technology people. They're good at running their business, serving their customers, managing their teams. Technology is something they have to deal with, not something they trained for. So when a tech decision lands on their desk, the natural instinct is to either make a fast call and move on, or avoid it entirely until something forces their hand.

Second, the technology industry doesn't make it easy. Every vendor is telling you their solution is the answer. Every comparison site has a different recommendation. Every "ultimate guide" is written by someone who's selling something. When the information landscape is that noisy, it's rational to feel paralysed.

Third, and this is the one people don't talk about enough, there's a confidence gap. If you've never made a major platform decision before, or migrated a system, or evaluated whether your current setup is fit for purpose, then of course those decisions feel risky. You don't know what you don't know, and the fear of getting it wrong is enough to keep the status quo in place indefinitely.

The Startups 100 survey for 2025 found that 82% of UK businesses are experiencing pressure to adopt emerging technologies. But only 29% of SMEs use data to guide their strategic decisions. That gap between pressure and preparedness is where most of the pain lives.

The reframe

Here's what I've learned from over a decade of dealing with technology decisions at organisations of very different sizes.

The technology is almost never the hard part.

The hard part is getting clear on what you actually need. Understanding what the real problem is, not the symptom. Having someone who can look at your situation without an agenda and tell you honestly what makes sense and what doesn't. Someone who'll say "actually, what you've got is fine, stop worrying about it" just as readily as "this needs attention and here's why."

When I worked at Just Eat Takeaway, the challenges that took the most time to solve were rarely about the technology itself. They were about alignment. Getting people clear on the actual problem. Understanding what success looked like before jumping to solutions. Working through the trade-offs honestly rather than pretending every option was equal.

Those same challenges exist in a business of five people. The scale is different. The thinking is identical.

What you can do right now

If any of this sounds familiar, here are three things you can do this week that don't cost anything and don't require any technical knowledge.

Make a list of every tool and subscription your business pays for. Check your bank statements, your card transactions, your email for renewal notices. You will almost certainly find things you'd forgotten about. For each one, ask: who uses this, and when did they last use it? If the answer is "I'm not sure" or "nobody," that's a decision waiting to be made.

Pick the process that frustrates you most and write down every step. Not how it should work. How it actually works right now, including the workarounds, the manual steps, the bits where someone has to copy something from one place to another. Often just writing it down makes it obvious where the problem is. And often the fix is simpler than you think.

Write down the tech decision you've been putting off. The one that's been sitting on your mental to-do list for months. The system you know isn't right. The tool you've been meaning to evaluate. The conversation you keep deferring. Write it down, and write down what's stopping you from dealing with it. Usually it's not time. It's confidence. And that's fixable.

The point

Your technology probably isn't as broken as it feels. What's more likely is that there are a handful of unmade decisions creating most of the friction, and once those decisions are made clearly and with the right information, things start to move.

The real question isn't "what technology do we need?" It's "what decisions are we avoiding, and what would it take to make them properly?"

That's not an IT problem. That's a thinking problem. And thinking problems have solutions.

If you're a small business owner or founder dealing with technology decisions that feel bigger than your current expertise, that's exactly what I help with. No jargon, no overselling, just clear thinking about what actually needs to happen. Book a free discovery call and we'll figure it out together.