Professional technology environment representing Technology & Vendor Selection
10 · IT Consultancy

Technology & Vendor Selection

Choose technology against clear requirements rather than persuasive feature lists.

Registered activity62020 — Information technology consultancy activities
Service categoryIT Consultancy
Indicative duration2–4 weeks
Starting pricefrom £1,200
Client typesBusiness, organisations & private clients
Delivery areaUnited Kingdom & European Union

Select a platform or supplier against written operational requirements instead of the longest feature list.

Technology and vendor selection turns an intended business outcome into a defensible purchasing decision. Requirements are developed from real workflows, users, information, integrations and operating constraints before products are scored. This reduces the risk of selecting the most persuasive demonstration or the longest feature list while overlooking adoption, data ownership, support and implementation effort.

The engagement creates a transparent evidence trail from must-have requirements to shortlist, supplier questions, fit-gap findings and recommendation. Commercial claims remain distinguishable from verified capability, and lifecycle issues such as migration, integration, administration, renewal and exit are considered alongside initial licence price.

When this service is usually considered.

The examples below help frame suitability. The actual requirement, risks and intended outcome are confirmed during the initial review.

  1. 01

    Several products appear similar, but internal stakeholders disagree about which requirements are genuinely essential.

  2. 02

    Supplier demonstrations are driving the conversation before current workflows, exceptions and data needs have been documented.

  3. 03

    An ageing platform must be replaced and the organisation needs to understand migration, integration and operational implications.

  4. 04

    Competing proposals use different assumptions, making price and scope difficult to compare fairly.

  5. 05

    Leadership wants an independent recommendation and a clear record of how the decision was reached.

What the assessment may cover.

Every item is selected and bounded in the written proposal. Inclusion here describes capability, not an automatic promise that all activities fit the starting price.

01

Outcome and workflow requirements

Definition of priority outcomes, users, journeys, exceptions, information, volumes, controls and constraints relevant to selection.

02

Selection framework

Separation of essential, desirable and out-of-scope requirements with transparent scoring and disqualification rules.

03

Market and shortlist review

Identification or assessment of a proportionate set of options against the agreed problem and organisational context.

04

Supplier evidence process

Structured questions, demonstration scenarios and evidence requests designed to test important workflows and dependencies.

05

Fit, risk and lifecycle analysis

Comparison of functional fit, integration, data, implementation, administration, support, cost drivers and exit constraints.

06

Recommendation and next steps

A written recommendation, conditions, unresolved questions and practical actions before contract or implementation commitment.

Useful artefacts, decisions and working results.

The output is designed to support operation, delivery or a clearly defined next decision—not to create presentation volume without practical value.

01

Selection criteria and weighted scorecard

An agreed requirement set and weighted scorecard linked to priority workflows, users, constraints and measurable outcomes.

02

Shortlist and evidence summary

A shortlist and evidence summary showing why options were included, excluded or require further clarification.

03

Risk, integration and ownership review

A fit-gap, integration, data, ownership and risk review with assumptions and supplier dependencies made visible.

04

Recommendation and implementation considerations

A documented recommendation and implementation considerations for leadership, procurement or the next project stage.

Common use cases.

These examples show how the service can be applied. They are illustrative and do not represent claims of completed client engagements.

Use case 01

CRM or case platform

Compare products against real customer, case, permission, reporting and integration requirements.

Use case 02

Workflow and automation tool

Evaluate whether configuration capability, exception handling and administration fit the intended process.

Use case 03

Infrastructure or managed provider

Assess service boundaries, support, resilience, cost and transition implications across supplier proposals.

Use case 04

Specialist SaaS replacement

Select a replacement while accounting for migration, retained records, connected systems and exit from the current service.

How NORYVIA approaches Technology Selection.

The method is adapted to the service rather than repeating one generic project formula across every requirement.

01

Criteria before demonstrations

Important requirements and scenarios are agreed before polished supplier presentations shape stakeholder expectations.

02

Evidence over assertion

Supplier statements, product documentation, demonstrations and confirmed contractual commitments are distinguished.

03

Evaluate the whole lifecycle

Implementation, integration, administration, support, renewal, data extraction and exit matter alongside subscription price.

04

Keep the decision auditable

Scores, assumptions, exceptions and stakeholder decisions remain traceable so the recommendation can be challenged constructively.

Six stages with visible decisions.

Activities can overlap where appropriate, but each stage has a clear purpose and produces evidence for the next one.

01

Decision brief

Confirm the outcome, stakeholders, budget context, timetable, current commitments and authority boundaries.

02

Requirements

Map priority workflows, users, data, integrations, controls, volumes and non-functional needs.

03

Framework and shortlist

Agree weighting and evidence rules, then identify a proportionate group of realistic options.

04

Evaluation

Review material, run structured demonstrations or questions and record fit, gaps, risks and dependencies.

05

Commercial and operating view

Compare lifecycle cost drivers, implementation assumptions, support, ownership and exit implications.

06

Recommendation

Present the preferred route, conditions, unresolved matters and actions before commitment.

The disciplines brought into the work.

The precise technical or advisory depth depends on the accepted scope, available evidence and client environment.

01

Requirements

  • Outcome and workflow definition
  • User and permission needs
  • Data and reporting requirements
  • Integration and volume constraints
  • Essential and desirable criteria
02

Evaluation

  • Weighted decision scorecards
  • Structured demonstration scenarios
  • Fit-gap and risk analysis
  • Supplier evidence tracking
  • Implementation assumption review
03

Decision pack

  • Lifecycle cost drivers
  • Data ownership and exit view
  • Operating responsibility
  • Recommendation conditions
  • Implementation-readiness actions

Information and access needed from the client.

Good delivery depends on timely, authorised access to relevant people and evidence. Missing inputs are surfaced as assumptions or constraints rather than quietly filled with guesses.

  1. 01

    The decision timetable, budget context and people authorised to set priorities.

  2. 02

    Current workflows, pain points, volumes, exceptions and user groups.

  3. 03

    Existing systems, data, integration, contract and migration constraints.

  4. 04

    Supplier proposals or products already under consideration, if any.

  5. 05

    Access to representative users and technical or operational owners.

A defined starting point—not a blank cheque.

The displayed price is an indicative starting guide for a bounded initial engagement. Before work begins, a written proposal confirms the selected activities, deliverables, assumptions, client responsibilities, exclusions, timetable, payment schedule and any third-party costs.

Indicative engagement shapes

Requirements and comparison briefTypically 1–2 weeks
Shortlist and structured evaluationTypically 2–4 weeks
Formal multi-supplier processPlanned around supplier response and decision stages

Factors that may change scope, price or duration

  1. 01

    Number and complexity of workflows, user groups and requirements to assess.

  2. 02

    Size of the market scan or number of suppliers and proposals in scope.

  3. 03

    Depth of demonstration, integration, data, security and cost evaluation required.

  4. 04

    Number of stakeholder workshops and decision rounds.

  5. 05

    Required format for scorecards, supplier questions and recommendation outputs.

What is not automatically included.

Boundaries protect both parties from assumptions. A separate requirement can still be assessed and included where it is suitable and confirmed in writing.

01

Supplier performance guarantee

The review relies on available evidence and cannot guarantee future product capability, roadmap, service quality or commercial behaviour.

02

Legal and regulated procurement advice

Contract negotiation, legal review and formal public or regulated procurement require appropriate specialist support.

03

Implementation by default

Configuration, migration, integration and training are separate activities unless a later written scope includes them.

Questions about Technology Selection.

Project-specific answers depend on the current environment, intended outcome and evidence available during review.

Yes. The engagement can test an existing shortlist, provided the decision criteria are agreed and the scope allows material alternatives or gaps to be raised.

Supplier communication, demonstrations and question management can be included. The proposal states who contacts suppliers and which commercial information the client is authorised to share.

NORYVIA presents the service as independent consultancy and does not position a recommendation as vendor-sponsored. Any material commercial relationship would need to be disclosed.

No. Price is assessed with implementation, integration, administration, support, risk and exit. The chosen weighting reflects the client's agreed priorities.

Start a conversation about Technology Selection.

Use the structured questionnaire to explain the current situation. NORYVIA will review suitability and respond with questions or a proposed next step.