Procurement & vendor selection advisory

Supplier offers rarely arrive on the same basis. This engagement helps leadership and procurement teams define the requirement, test the evidence and document the tradeoffs before committing.

When this engagement helps

• Competing proposals have different scope, exclusions and operating assumptions.
• An AI or technology supplier needs a structured commercial and operational review.
• Acceptance criteria, support responsibilities, renewal terms or exit arrangements remain unclear.

What the work can produce

The final scope is agreed around your decision. Depending on that scope, deliverables can include:

Define the decision before scoring the offers

Start with the business problem, the required capability and the constraints that cannot be traded away. Ask each supplier to respond to the same brief and identify exclusions. Agree the criteria and weights before looking at totals.

A scorecard is useful only if the team understands what each score means. Record the supporting document, demonstration or test and name the reviewer. Leave an unanswered question visible instead of awarding points for a promise.

Treat mandatory requirements as gates

A high weighted score cannot compensate for failure to meet a requirement the business considers essential. Examples might include technical compatibility, an agreed data-handling requirement, support coverage or a necessary acceptance test. Your responsible specialists define the actual gates.

Classify each gate as passed, unresolved or failed. A proposal with an unresolved gate needs evidence before final selection. A proposal with a failed mandatory gate requires a documented change in the requirement or removal from consideration.

Examine the operating and exit terms

Look beyond the initial price to implementation dependencies, recurring costs, service responsibilities, renewals and what happens if the relationship ends. Ask who will own the service after handover and what evidence demonstrates successful acceptance.

The advisory review identifies business questions for the relevant technical and legal reviewers. Contract advice and jurisdiction-specific conclusions require the appropriate qualified professionals; they are not implied by a commercial comparison.

Put the decision in writing

A useful decision record explains why the preferred option fits the requirement, which tradeoffs were accepted and which conditions remain open. It also states what would change the recommendation. Keep the evidence with the record so a new stakeholder can understand the reasoning.

Use the free vendor evaluation scorecard to structure a first comparison. The worked example shows why an unresolved requirement matters more than a small difference in total score.

Can we use this for AI suppliers or industrial equipment?

The comparison structure can be adapted to both, but the mandatory conditions and evidence differ. AI evaluation may require model-behaviour and data-use evidence; industrial equipment evaluation may require capacity, installation, maintenance and technical acceptance evidence. A generic score is not a substitute for those checks.

What does the first conversation cover?

Bring the requirement, current proposals, known constraints and decision deadline. We agree the supplier comparison to review, the stakeholders involved and the required deliverables, then confirm scope, timing and fees before starting.