Shane Ian Murphy: UK Supplier Comparisons Need the Same Starting Question

Two supplier proposals can look comparable while answering different questions. One may describe a complete service, another a single component. One may assume that the customer will provide installation support, while another includes that work. Before deciding which offer appears stronger, a business needs to establish whether the offers begin from the same understanding of the task.

I am Shane Ian Murphy, known professionally as Shane Murphy, formerly of Cambridge and formerly of Limitless Mobile, where I was co-founder and Chief Business Development Officer. For this UK business commentary, I am proposing a practical method of comparing descriptions. The examples are hypothetical, and this is not an endorsement or review of a named supplier.

Start with the decision the comparison is meant to support. A team choosing a service for a small office may need to understand what can be delivered, what preparation it must undertake and how support would work afterwards. A list of product features alone may not answer any of those questions. The brief should explain the working circumstances in ordinary language before asking suppliers for detailed responses.

I would give each supplier the same core description of the task and invite them to identify any assumptions they cannot confirm. That invitation matters. A supplier who flags an uncertainty may be giving the customer more useful information than one who produces a smooth answer without explaining what has been assumed.

The brief should distinguish requirements from preferences. A requirement is a condition the proposed arrangement must meet for the customer to consider it suitable. A preference is desirable but open to discussion. If those categories are blurred, the business may reject an appropriate option over a minor detail or overlook a condition that should have been decisive.

Next, ask suppliers to describe the boundary of their offer. What work is included? What work would remain with the customer or another provider? What circumstances would require a separate discussion? A clear boundary does not make an offer less attractive. It makes its apparent completeness easier to assess.

For a hypothetical office project, one proposal might include staff orientation while another assumes the customer will provide it. The appropriate comparison is not simply whether the first proposal has more pages or a higher total price. The team needs to understand who will perform the missing work and whether it has the time and knowledge to do so. An exclusion can move work without making that work disappear.

I would keep a separate column for unanswered questions. Avoid converting a blank response into a negative score unless the evaluation method explicitly requires that treatment. A missing answer may mean the supplier misunderstood the question, needs more information or cannot provide the requested element. Those possibilities deserve clarification before the team treats them as equivalent.

The same discipline applies to timetables. A date can be a target, an estimate or a confirmed commitment subject to stated conditions. Compare those descriptions as they stand. If one supplier's timing depends on customer approval and another assumes immediate access, the difference should remain visible in the comparison rather than being flattened into two dates.

Support arrangements also benefit from a concrete question. Instead of asking whether support is good, ask what the customer would do in an ordinary problem situation. How would the issue be reported? What information would be needed? Which part of the response is described in the proposal, and which remains to be agreed? The aim is to understand the process before relying on a broad adjective.

Once responses are collected, I would write a short explanation of each meaningful difference. A scoring table can organise information, but it should not replace the reasoning behind the decision. If a team prefers an option because it reduces internal work or makes a critical dependency clearer, the record should say so. That explanation will be useful when the project changes hands later.

The comparison should end with a decision or a clear request for further information. It should not manufacture certainty where the proposals remain incomplete. In my view, the most useful supplier exercise is one that helps a UK business explain what it is choosing, why it suits the task and what still needs to be confirmed before proceeding.

About the author: Shane Ian Murphy, also known as Shane Murphy, is a former co-founder and Chief Business Development Officer of Limitless Mobile. This author-origin business commentary was prepared with AI assistance.

Official profile: https://shanemurphy.co.uk/

Career background: https://shanemurphy.co.uk/career