Before You Buy: How to Evaluate a Technology Proposal

At some point, most organisations are presented with a technology proposal that looks like the answer to a problem.

It may be a new software platform, a cloud migration, an AI solution, a systems integration project or a proposal to replace something that is already in place. The supplier has identified an opportunity, explained the benefits and presented a solution, often supported by impressive demonstrations and a detailed set of specifications.

It may all look very convincing.

But a good proposal does not necessarily mean it is the right solution.

The supplier is explaining why you should buy what they are offering. Your responsibility is to establish whether it is actually the right thing to do.

That requires looking beyond the product, the presentation and the headline price.

Start with the problem, not the solution

One of the easiest mistakes to make is to accept the supplier’s definition of the problem.

A proposal may describe a requirement for a new platform when the underlying issue is actually poor integration between existing systems. It may recommend automation when the process itself needs simplifying. It may propose replacing an application when a relatively small architectural change would address the real limitation.

These are not necessarily bad proposals. They may be entirely appropriate. The important thing is to understand what problem is being solved before deciding whether the proposed solution makes sense.

I would start with a few straightforward questions.

What are we trying to achieve? What is preventing us from achieving it today? What would a successful outcome look like? Is the proposed technology addressing the underlying problem, or simply making the current process work differently?

If those questions cannot be answered clearly, it is difficult to judge whether the proposed investment is worthwhile.

Understand the alternatives

A technology proposal will naturally concentrate on the solution being offered. That does not mean it is the only option.

There may be several ways to achieve the same outcome. An existing system might be extended or reconfigured. A different product may provide a better fit. A smaller integration project may solve the problem without introducing another platform. In some circumstances, building something bespoke may be justified. In others, it would be unnecessary complexity.

There is also the option of doing nothing, at least for the time being.

That might sound like an obvious point, but it is often overlooked. Every technology decision has an opportunity cost. Money, time and people committed to one project cannot be committed to something else.

The question should not simply be whether the proposed solution works. It should be whether it represents the best use of the organisation’s resources.

Look beyond the purchase price

The headline price is rarely the whole cost of a technology decision.

There may be implementation fees, recurring licences, infrastructure, support contracts, integration work, data migration, training and ongoing administration. Some costs are explicit in the proposal; others emerge only when the system is being deployed or operated.

It is worth understanding the likely cost of ownership over a realistic period, rather than comparing suppliers solely on their initial quotation.

There are also less obvious costs. How much internal effort will be required? Will existing processes need to change? Does the organisation have the skills to operate the solution? Will additional suppliers or specialist services be needed?

A relatively inexpensive product can become an expensive solution if it introduces significant operational overhead or creates dependencies that are difficult to manage.

Examine the architecture behind the proposal

A proposal may describe what a system does without explaining how it fits into the organisation’s wider technology environment.

That distinction matters.

How will it integrate with existing systems? Where will information be stored? How will users and other systems access it? What dependencies does it introduce? How will it be secured, monitored and maintained?

It is also worth considering what happens when something goes wrong. Can the organisation continue operating if a component, supplier or external service becomes unavailable? Can the solution be recovered? Is there a practical way to move information elsewhere if the organisation needs to change provider?

These questions are particularly important when a proposal introduces a new platform or creates a significant dependency on a particular supplier.

A solution can work perfectly well in isolation while making the overall architecture more complicated, less flexible or more difficult to maintain.

This is where technical architecture becomes relevant to what might initially appear to be a straightforward purchasing decision.

Understand what you are becoming dependent on

Technology purchases are not always easy to reverse.

A new platform may become central to business operations. Information may be stored in proprietary formats. Processes may become dependent on specific features or integrations. Staff may develop specialist knowledge that is difficult to transfer elsewhere.

These are not necessarily reasons to avoid a particular supplier or product. Some degree of dependency is unavoidable in most technology environments.

The important thing is to understand the implications before committing.

What happens if the supplier changes its pricing? What if the product is discontinued? Can information be exported in a usable format? How difficult would it be to migrate to an alternative? Does the organisation retain control of its data, configuration and intellectual property?

A good proposal should give you enough information to understand these issues. If it does not, they are worth raising before the decision is made.

Challenge the assumptions

Every proposal contains assumptions.

Some relate to the technology itself. Others concern the organisation, its processes, its data or the people who will use the solution.

A proposal may assume that existing information is sufficiently clean and accessible. It may assume that an integration is straightforward, that users will adopt a new process, or that a particular performance improvement will be achieved.

Those assumptions can have a significant effect on the eventual outcome.

I would distinguish between what has been demonstrated, what has been evidenced and what is simply expected to work.

A demonstration can show that a product performs a particular function. It does not necessarily prove that it will work reliably with your data, integrate with your existing systems or deliver the anticipated business benefit.

Where an important assumption remains uncertain, it may be worth testing it through a limited proof of concept or a clearly defined pilot before making a larger commitment.

The objective is not to challenge every statement made by a supplier. It is to identify the assumptions that could materially affect the success, cost or risk of the project.

Consider security and resilience from the beginning

Security and resilience should not be treated as additional features to be considered once a solution has been selected.

They are part of deciding whether the solution is appropriate in the first place.

What information will the system handle? Who will have access to it? Where will it be processed and stored? What happens if the service becomes unavailable? How will the organisation recover if information is lost or compromised?

The answers will depend on the nature of the system and the information involved. A relatively low-risk business application will have different requirements from a platform handling sensitive customer information or supporting a critical operational process.

The important thing is to make those requirements explicit and ensure the proposal addresses them proportionately.

A solution that delivers impressive functionality but introduces unacceptable security exposure or operational dependency is not a good solution.

Make sure you know what success looks like

Technology projects can become focused on delivering the system rather than achieving the outcome that justified the investment.

A proposal should make it possible to understand what success will look like in practical terms.

Will it reduce operating costs? Improve productivity? Remove a particular operational constraint? Improve the quality or availability of information? Reduce risk? Enable something the organisation cannot currently do?

Ideally, those outcomes should be measurable.

It is also important to distinguish between what the supplier is committing to deliver and what the organisation hopes to achieve as a result. Delivering software or completing an implementation does not automatically produce the expected business benefit.

Without a clear view of the intended outcome, it becomes difficult to assess whether the investment has been successful.

Sometimes the right answer is not to buy

There is nothing wrong with deciding that a proposal is the right solution and proceeding with it.

There is also nothing wrong with asking for a different approach, undertaking a limited trial, negotiating changes to the scope or deciding that the investment is not justified.

The important thing is that the decision is based on an understanding of the problem, the available options, the costs, the risks and the longer-term implications.

Technology suppliers bring valuable product knowledge and implementation experience. Their recommendations can be extremely useful. But they are naturally focused on the products and services they provide.

An independent perspective can help establish whether the proposed solution is appropriate for the organisation, rather than simply whether the supplier can deliver it.

Make the decision before making the commitment

A technology proposal should be the beginning of a decision, not the end of one.

Before committing, make sure you understand what problem you are solving, why the proposed approach is appropriate, what alternatives exist and what the organisation will be taking on in terms of cost, complexity and dependency.

The objective is not to make every technology decision a lengthy exercise. It is to apply the right level of scrutiny before making a commitment that may be expensive or difficult to reverse.

An independent Technical Decision Review can help assess a significant technology proposal, challenge its assumptions and examine the architectural, operational and commercial implications before you commit.

Sometimes the best investment is not in the technology itself, but in making sure you are buying the right thing.