Technology decisions
Price the change, not just the software.
Put data, integration, process change, training and ongoing ownership beside the supplier quote before you compare options.
Consider a hypothetical business comparing two new customer-management systems. One proposal has the lower annual licence fee, so it initially looks like the obvious choice. But it also needs more data clean-up, a new integration, changes to team responsibilities and ongoing administration. The useful comparison is not simply one subscription against another. It is the cost and effort of making each option work.
Start with the outcome and the operating change
Write down what the investment is expected to improve and which parts of the current way of working must change. This might include how enquiries are assigned, how customer records are maintained or how managers obtain reliable information. Keep the scope specific enough to test against each option.
A feature has little value on its own if the business process, data or ownership needed to use it is missing. Separate capabilities that are ready to use from those that depend on configuration, custom work or a change elsewhere.
Build a whole-change view
Place the supplier quote inside a broader change map. You do not need false precision at an early stage, but you do need to show where cost, internal effort and uncertainty sit.
- Software: licences, required modules and likely usage growth.
- Implementation: configuration, migration, integration and testing.
- Business change: process design, training, communications and temporary capacity.
- Operation: administration, support, supplier management and future changes.
- Exit: data extraction, contractual constraints and the work needed to move again.
Keep cash, effort and uncertainty separate
A cost paid to a supplier and time required from your team are different pressures. Record both. A low external implementation fee may still require substantial input from people who already have operational responsibilities. If that capacity is not available, the plan needs another route rather than an optimistic assumption.
Use ranges where the evidence is incomplete and name what would narrow them. For example, migration effort may depend on the condition of existing records; integration effort may depend on an interface that has not yet been demonstrated. Mark those items as unresolved instead of burying them inside a contingency percentage.
Compare options over a useful period
Separate one-off change costs from recurring operating costs, then compare the options across a period relevant to the decision. Keep assumptions visible: expected users, volume, support model, contract term and any planned business change. The purpose is not to produce a perfect forecast. It is to make different cost profiles and dependencies comparable.
Finish with the decision still to be made, the evidence required and the person accountable for it. A cheaper option may remain the right choice, but the reasoning should reflect the work needed to realise it.
Rethink’s technology second opinion can examine a defined platform choice or supplier proposal and make the gaps, dependencies and next evidence visible. If the decision proceeds, delivery support can be scoped separately to help turn it into a workable change.