Case study · 2026

AI-Assisted Bid Evaluation

AI-Assisted Bid Evaluation

Designing AI to support complex procurement decisions

I led the UX/UI design of an AI-assisted bid evaluation experience that helps procurement teams analyse large volumes of supplier information, compare bids and interrogate complex submissions through natural-language queries.


Role
Lead Product Designer

Team
Product · Engineering · QA

Stage

Prototype → Development QA

Focus
AI Product Design · Decision Support · Trust · Complex Data

I owned: problem framing · interaction model · UX/UI · prototyping · validation · design QA

Blue tiled grid representing a configurable system
Blue tiled grid representing a configurable system

The PROBLEM

Bid evaluation meant finding answers across large amounts of fragmented information.

Bid evaluation meant finding answers across large amounts of fragmented information.

Procurement teams needed to review supplier submissions containing pricing, exclusions, validity dates, technical responses, method statements and supporting documents.

The information required to make a decision existed across multiple documents and bidders, making comparison time-consuming and increasing the effort required to identify important differences.

The opportunity for AI wasn’t simply to add a chatbot. It was to help users surface relevant information while keeping the underlying evidence and decision-making process understandable.

AI-assisted decision support

Procurement · Enterprise SaaS · Data-heavy workflows · AI

UNDERSTANDING THE WORKFLOW

UNDERSTANDING THE WORKFLOW

Before defining the assistant, I mapped the existing evaluation workflow and worked with Product and domain stakeholders to identify where evaluators spent effort finding, comparing and verifying information. This helped separate problems suited to AI assistance from decisions that needed to remain with the evaluator.

PRODUCT STRATEGY

The question wasn’t “Where can we add AI?” It was “Where can AI reduce evaluation effort without taking the decision away from the user?”

The question wasn’t “Where can we add AI?” It was “Where can AI reduce evaluation effort without taking the decision away from the user?”

I worked with Product, Engineering and stakeholders to understand the needs, constraints and dependencies across buyer and supplier workflows. Rather than treating each side independently, I mapped how catalogue configuration, pricing, fulfilment and returns affected what users experienced on the opposite side.

This helped identify where the marketplace needed shared rules and where buyer and supplier experiences needed to remain deliberately different.

Summarise

Reduce the effort required to review long supplier documents by extracting key information such as pricing, exclusions, validity dates and method statements.

Compare

Help evaluators identify differences between bidders, including pricing, technical scores, document completeness and item-level values.

Interrogate

Allow users to ask specific questions about a bidder or across the full bid set without manually navigating between documents.

This framed the assistant as a decision-support tool rather than an autonomous evaluator.

USER NEEDS

I designed the interaction around real evaluation questions, not generic AI prompts.

I designed the interaction around real evaluation questions, not generic AI prompts.

Price

  • Who is the cheapest bidder?

  • Who is the most expensive?

  • What is bidder 7’s total price?

  • Compare the price of this item across suppliers.

Quality

  • Who has the highest technical score?

  • Which bidder offers the strongest price-quality balance?

Completeness

  • Which bidders are missing BOQ information?

  • Which submissions have incomplete documents?

Commercial detail

Commercial detail

  • What exclusions has this supplier listed?

  • What is the validity period of the bid?

Capacity / risk

  • Does this supplier have capacity given their other projects?


  • Does this supplier have capacity given their other projects?

Cross-bid analysis

  • Summarise the differences between these bidders.


  • Summarise the differences between these bidders.

Blue tiled grid representing a configurable system
Blue tiled grid representing a configurable system

INTERACTION MODEL

I kept AI inside the evaluation workflow rather than sending users into a separate experience.

I kept AI inside the evaluation workflow rather than sending users into a separate experience.

I designed the AI Assistant as a contextual panel within the bid evaluation experience. Users could continue viewing bidder information while asking questions, reviewing summaries and comparing results.

Bid evaluation

→ Ask question

→ AI response

→ Supporting evidence

→ Continue evaluation

Keeping the assistant within the evaluation context reduced the need to move between separate tools and helped users maintain sight of the underlying bid information.

DISCOVERABILITY

AI needed to be useful before users knew what to ask.

AI needed to be useful before users knew what to ask.

Procurement users may understand the evaluation problem without immediately knowing how to phrase an AI query. I introduced suggested questions to demonstrate the assistant’s capabilities and provide low-effort entry points into common evaluation tasks.

Blue tiled grid representing a configurable system
Blue tiled grid representing a configurable system

INFORMATION ARCHITECTURE

Users needed both document-level detail and a consolidated bidder view.

Users needed both document-level detail and a consolidated bidder view.

Document summary

Surface the important information inside an individual submission, such as:

  • totals

  • exclusions

  • validity dates

  • method statements

  • missing information

Consolidated bidder summary

Separating these levels helped prevent dense AI output from becoming another source of complexity.

TRUST & CONTROL

The AI could surface evidence and comparisons without silently making the procurement decision.

The AI could surface evidence and comparisons without silently making the procurement decision.

Some evaluation questions naturally moved beyond retrieval into judgement — for example comparing price and quality, identifying the highest technical score or asking which submission represented better value.

I designed responses to make the reasoning visible by surfacing the relevant values and comparison criteria, rather than presenting an unexplained answer.

Blue tiled grid representing a configurable system
Blue tiled grid representing a configurable system

AI UX PRINCIPLES

Trust came from making AI behaviour visible and reviewable.

Trust came from making AI behaviour visible and reviewable.

Context

Responses should make clear which bidder, documents or comparison set they refer to.

Evidence

Important conclusions should point users back to supporting information.

Control

Users remain responsible for the evaluation and can continue investigating the underlying submission.

Consistency

AI interactions should use the same design-system patterns and hierarchy as the wider product.

PROTOTYPING

Testing the assistant against realistic evaluation complexity.

Testing the assistant against realistic evaluation complexity.

I used scenarios with large bidder sets to explore how the assistant behaved when users moved between individual supplier questions and cross-bid comparisons.

25 Bidders

Bidder set

→ individual supplier query

→ cross-bid comparison

→ missing information

→ return to evaluation

Blue tiled grid representing a configurable system
Blue tiled grid representing a configurable system

DESIGN QA & DELIVERY

The work continued after the prototype.

I worked with Engineering and QA as the assistant moved into development, reviewing implementation against the intended interaction model and design-system standards.

I worked with Engineering and QA as the assistant moved into development, reviewing implementation against the intended interaction model and design-system standards.

Layout

Panel height and header hierarchy

Components

Query chips, textarea, button radius

Content

AI Assistant hierarchy and suggested-query treatment

Consistency

Alignment with the wider design system

These details mattered because consistency with the wider product was important for making the AI experience feel like part of the platform rather than a bolted-on feature.

These details mattered because consistency with the wider product was important for making the AI experience feel like part of the platform rather than a bolted-on feature.

WHAT I LEARNED

Designing AI meant designing uncertainty as well as interaction.

Designing AI meant designing uncertainty as well as interaction.

Useful before impressive

AI needed to reduce real evaluation effort rather than simply demonstrate capability.


Evidence before confidence

Users needed to understand why an answer was being surfaced.


Context before conversation

The strongest interactions happened when AI understood where users were in the evaluation workflow.


The project shifted my focus from designing a chatbot to designing an AI-supported decision system.

DESIGN OUTCOME

A more focused way to navigate complex bid information.

The design established a clear interaction model for introducing AI into bid evaluation — combining document summarisation, cross-bid comparison and conversational querying within the existing procurement workflow.

Faster access
Key information surfaced without manually reviewing every document.

Comparable
Bidder information structured for easier cross-supplier analysis.

Reviewable
AI outputs designed to remain connected to the evidence behind them.

Reflection

The challenge wasn’t designing a chatbot. It was deciding when AI should assist, explain and step aside.

The challenge wasn’t designing a chatbot. It was deciding when AI should assist, explain and step aside.

This project reinforced that AI product design is as much about boundaries as capability. The strongest experience was not the one where AI did the most, but the one where it reduced effort while preserving context, evidence and user control.

Federica Sanchi

Lead Product Designer · London, UK