How to make technology decisions that actually move the needle — and avoid the ones that don’t.

In twenty years of working with businesses across technology and operations, I’ve seen the same pattern repeat itself more times than I can count.

A business owner or MD decides the business needs to “sort out its technology.” They speak to a few vendors, get shown some impressive demos, and sign up for a new CRM, ERP or operations platform. Six months later, the system is half-implemented, the team isn’t using it properly, and the problems it was supposed to fix are still there — with an additional bill on top.

This isn’t a technology problem. It’s a decision problem. And it’s more common in Melbourne’s mid-market than most business owners would like to admit.

The pattern: buying technology as a substitute for fixing process

The most expensive technology mistake a business can make is implementing a system on top of a broken process and expecting the system to fix it.

It doesn’t work that way. Technology automates and accelerates what already exists. If what already exists is inefficient, manual or poorly structured, the technology will automate and accelerate that too — usually at significant cost and with significant disruption.

The businesses that get technology right fix the process first. They understand exactly what they’re trying to achieve, map how work currently flows through the business, identify where the real friction is, and then ask what technology could do to remove it. That sequence matters. Reversing it is where the waste happens.

The five most common wrong decisions

These are the technology mistakes I see most frequently in mid-sized Melbourne businesses:

  1. A CRM that nobody actually uses. The business buys Salesforce or HubSpot, runs a two-day training session, and six months later the sales team is still working from spreadsheets and email threads. The CRM has become an expensive data entry burden rather than a sales tool. The problem is almost never the software — it’s that the sales process wasn’t defined before the system was chosen.
  2. An ERP implemented before the business is ready for it. Enterprise resource planning systems are powerful — and complex. Businesses at $20M to $30M turnover often don’t yet have the operational maturity or internal capability to implement and run one properly. The result is a multi-year implementation that consumes enormous management bandwidth and delivers a fraction of the expected benefit.
  3. AI without a use case. The pressure to “do something with AI” is real. But implementing AI tools without a clear, specific use case tied to a business problem produces novelty, not value. I’ve seen businesses spend significant money on AI implementations that solved problems they didn’t have, while the problems they did have went unaddressed.
  4. Multiple disconnected tools that don’t talk to each other. A business with separate systems for quoting, invoicing, project management, customer communication and reporting — none of which integrate — has created a manual data handling problem that often costs more in staff time than the systems save. Integration should be a requirement, not an afterthought.
  5. Building when they should be buying. Custom software development is expensive, time-consuming and risky. Most business problems that prompt a custom build request can be solved with existing off-the-shelf products, configured correctly. The exceptions are real, but they’re rarer than most software vendors would have you believe.

Why it keeps happening

There are three reasons mid-sized businesses consistently make poor technology decisions.

Vendor pressure. Software vendors are excellent at selling. Their demos are polished, their case studies are compelling, and their sales teams are persistent. A business owner evaluating technology without independent advice is negotiating against professionals whose entire job is to close the deal.

FOMO. The fear of being left behind — particularly around AI right now — drives investment decisions that haven’t been properly thought through. The businesses winning with technology aren’t the first movers. They’re the ones who move deliberately, with a clear use case and a realistic implementation plan.

No independent advice. Most mid-sized businesses don’t have a CTO or technology director. Technology decisions get made by the MD, often with input from the vendor and little else. An independent operator who understands both the technology landscape and how businesses actually run can change the quality of that decision significantly.

What a good technology decision actually looks like

A good technology decision starts with a problem statement, not a product shortlist.

It asks: what is the specific business problem we are trying to solve? What does solving it look like in practice? How will we know when it’s working? What will it cost us in time and money to implement, and is that justified by the benefit?

It also asks the questions vendors won’t ask: Is this the right time? Does the team have the capacity to implement this properly? Is the underlying process sound enough to build on? Would a simpler solution achieve 80% of the outcome at 20% of the cost?

That last question is worth sitting with. In most cases, the answer is yes.

How to evaluate before you commit

Before committing to any significant technology investment, a mid-sized business should be able to clearly answer the following:

  • What specific problem is this solving, and how is that problem currently costing us money or time?
  • Have we mapped the current process and confirmed it’s sound enough to build on?
  • Who internally owns this implementation, and do they have the capacity?
  • Have we evaluated at least three alternatives, including simpler and cheaper ones?
  • What does success look like in 12 months, and how will we measure it?
  • What happens if this doesn’t work as expected, and what’s the exit?

If any of those questions don’t have a clear answer, the decision isn’t ready to be made.

The starting point

If your business has a technology decision coming up — or a technology implementation that isn’t delivering what it was supposed to — the first step is an honest, independent assessment of where things actually stand.

That’s what the Black Belt Business Diagnostic is designed to do. Technology is one of four areas assessed in a structured two-week process that gives you a clear picture of what’s working, what isn’t, and what to do about it.

Book a consultation with Andrew Barton

Andrew Barton is the founder of Black Belt Consulting, a Melbourne-based consulting practice working with mid-sized businesses on operations, technology and project delivery. He has held CEO, GM and director roles across technology and services businesses and has consulted to organisations and government.