12 November 2025

Choosing the right technology: why the decision matters as much as the tool

Every technology project starts with a choice. Which platform, which system, which partner. It can feel like a small step compared to the actual work, but in practice it decides a large part of how the whole project ends up. The right choice makes the work smoother, cheaper and easier to maintain. The wrong one can follow a company for years.

Why does the first choice matter so much?

Once a system is in place, everything else gets built around it. Your team learns how to use it, your data ends up in it, and other tools get connected to it. Changing direction later is possible, but it costs time and money, and often means doing a large part of the work twice.

That's why a tool that looks cheaper or more impressive at the start isn't always the better deal. What matters is how well it fits the way the business actually works, and whether it can grow with you.

Why do so many IT investments turn out badly?

In our experience, the problem is rarely the technology itself. Most tools on the market are good at what they were built for. The problem is that they get chosen for the wrong reasons, or by the wrong people.

We often see decisions made by someone who won't be using the system day to day, or who doesn't have the technical background to see what the choice leads to later. Sometimes the decision is driven by a sales pitch, sometimes by what a competitor uses, and sometimes simply by what someone has heard is popular. The people who would have spotted the problems, the ones who actually work with the system, get involved only after the contract is signed.

The result is a system that technically works but doesn't fit. Staff build workarounds, costs grow, and eventually the company pays again to replace it.

Who should be part of the decision?

A good technology decision usually needs three perspectives:

• The people who will use it every day. They know what the work actually looks like and where the problems are.
• Someone with technical understanding. They can see what the choice means for maintenance, security, integrations and future changes.
• The person responsible for the budget. They make sure the solution makes sense for the business as a whole.

When one of these is missing, the risk of a bad investment grows quickly.

Look at the total cost, not just the price

The price on the offer is only one part of what a system costs. Licences that grow with every new user, extra modules that turn out to be necessary, training, integrations with other tools and the time it takes to keep everything updated can easily add up to more than the original purchase.

Before deciding, it is worth asking a few simple questions. What will this cost per year, not just this year? What happens to the price when we grow? And how much of our own time will it take to run? A slightly more expensive option that is easy to live with is often the cheaper one in the long run.

Don't get locked in

Some systems are easy to get into and hard to leave. Your data is stored in a format that cannot be exported, or the whole setup depends on one supplier who knows how it works. That is not always a problem, but it should be a conscious choice rather than a surprise.

Good questions to ask: can we get our data out in a usable format? Can another partner take over if needed? Is the solution built on common, well supported technology, or on something few people know? The answers say a lot about how much freedom you will have later.

What does a good decision look like in practice?

When one of our clients needed a webshop, the simplest option that did the job was the right one. They wanted customers to be able to buy their products without complications, and they wanted to keep the shop separate from their existing website. A well set up Shopify store matched those needs better than a custom build would have, and it kept costs predictable.

For another client, the most important part wasn't the platform at all. It was making sure their own staff could update and manage the site themselves. A technically impressive solution that only a developer can touch would have been the wrong choice for them, however good it looked on paper.

In both cases the answer came from starting with the business, not the tool.

How to make better technology decisions

• Start with the problem, not the product. Be clear about what you need before you look at options.
• Involve the people who will use it before the decision is made, not after.
• Get an outside view from someone who doesn't benefit from selling you a specific product. Vendor neutral advice is worth a lot when the stakes are high.
• Think a few years ahead. Ask what happens when you grow, when staff change, or when you want to connect new tools.
• Try before you commit. A trial period or a small pilot with real users reveals more than any demo.
• Plan the introduction. Set aside time for setup and training, so the new system is actually used the way it was intended.

The bottom line

The right technology choice rarely feels dramatic. It just works, and the work built on top of it goes smoothly. Most of the difference is made before anything is built, in who gets to decide and what the decision is based on.

If you are facing a technology decision and want an honest second opinion, we are happy to help. Our advice is vendor neutral, so the only thing we are trying to find is the option that fits your business best.