SourceWise comparison interface
SourceWise evidence correction panel
SourceWise recommendation evidence
SOURCEWISE · PRODUCT SYSTEM
PRODUCT DESIGNUX CASE STUDY2026

SourceWise

Designed an AI-assisted comparison tool that helps hospitality staff turn scattered supplier quotes into clear, confident decisions.

TIMELINE
5 weeks
TEAM
Solo project
ROLE
Product Designer
SKILLS
Figma, FigJam
LONG STORY SHORT

From inconsistent quotes to a verifiable decision

Hospitality staff who handle purchasing, often without formal procurement training, still compare supplier quotes manually across spreadsheets, PDFs, emails, and even photos of handwritten notes or paper brochures. This makes the process slow, fragmented, and easy to get wrong.

01 — AI Extraction

Pulls and normalizes quote data automatically, cutting manual comparison work.

02 — Full Traceability

Every value stays linked to its original source: nothing is a black box.

03 — Editable Oversight

Users can adjust extracted data directly, keeping control over the final decision.

How might we help hospitality staff turn scattered, inconsistent supplier quotes into a confident purchasing decision?

COMPETITIVE ANALYSIS

Where existing tools fall short

Most tools focus on ongoing ordering and inventory, with supplier comparison as a secondary feature.

5Competitors

Strengths

  • Strong ongoing ordering workflows
  • Established price comparison tools
  • Invoice-level AI extraction

Weaknesses

  • Compares past invoices, not quotes
  • Limited AI source verification
  • Limited order-level trade-off support
SPEAKING TO USERS

How hospitality teams compare suppliers today

A restaurant owner, a kitchen coordinator, and a café/bistro general manager: different roles, different levels of authority, but all responsible for comparing supplier offers.

Manual Format-Wrangling

A WhatsApp text, a PDF, a photo of a handwritten note: I retype it all by hand.

Offers Aren’t Comparable

One supplier’s ‘case’ was 12 units, another’s was 24. I almost compared them directly.

Price Isn’t the Deciding Factor

A late delivery costs me more than an 8% discount saves.

AI Needs to Earn Trust

If it’s wrong and I didn’t catch it, that’s on me, not the AI. So I’m always going to double check the big ones.
SourceWise interview questions
SYNTHESIS / AFFINITY MAP PLACEHOLDER
OPPORTUNITIES

Four research findings shaped the first prototype

Based on the interview findings, I mapped each pattern to a feature focused on reducing manual work and building trust incrementally.

Smart Offer Extraction

Structures supplier offers into one comparable format

Normalized Comparison

Converts units and pricing into an apples-to-apples view

Trade-off Guidance

Weighs delivery, MOQ, and reliability alongside price

Verifiable AI Output

Shows the source behind every number before you trust it

EXPLORING THE FIRST SOLUTION

I turned the research into two main hypotheses for the first prototype

Rather than treating the research findings as a fixed solution, I used them to form product hypotheses that I could put in front of users.

HYPOTHESIS 01

Give AI reasoning its own space

A dedicated AI reasoning step would make supplier trade-offs easier to understand.

AI observation concept
HYPOTHESIS 02

Verify extracted information before comparing

Reviewing extracted values would build trust.

Extracted value review concept
DESIGN TENSION
A dedicated step gives the analysis more room, but takes users out of the comparison. Keeping it in context preserves the flow, but risks getting lost. Testing would settle which mattered more.
USER TESTING

I ran a lightweight testing round with 6 participants across two groups

Three hospitality professionals, plus three participants unfamiliar with the workflow as a secondary clarity check.

FINDINGS

Two parts of the first prototype didn't hold up in testing.

AI reasoning worked better in context

BEFORE
AI reasoning before iteration
AFTER
ASSUMEDAI reasoning needed its own screen.LEARNEDLeaving comparison broke the decision flow.CHANGEDMoved reasoning into Compare, with details on demand.

Verification needed less friction

BEFOREAFTER
Review extracted information before iteration
Review extracted information after iteration
ASSUMEDMore verification would build trust.LEARNEDReviewing every field added unnecessary friction.CHANGEDFocused review on uncertain and missing values.
WHAT HELD UP

Two directions were reinforced by testing

MOBILE CAPTURE

Mobile capture mattered away from the desk

I kept the dense comparison workflow desktop-first, but introduced a lightweight mobile capture flow for moments when staff receive supplier information away from the desk.

SOURCE TRACEABILITY

Users wanted to check where AI output came from

That behavior held up in testing, so I kept source verification as a core interaction instead of redesigning it.

VISUAL LANGUAGE

Clear signals for faster supplier decisions

SourceWise comparison visual language

Orange highlights key actions and decisions, while the dotted grid adds subtle structure.

SourceWise supplier status table
STATUS SYSTEM
!Missing?Uncertain·In progress✓Complete

Status labels show progress at a glance.

FINAL DESIGNS

Compare the offers, verify the evidence, explain your decision

Role-aware onboarding

Role-Aware Onboarding

The app adapts to who you are: an owner who makes decisions independently, or a staff member who needs approval.

Verifiable source evidence

Verifiable Source Evidence

Every extracted value links straight back to the sentence it came from.

From Selection to Decision

The final step turns a supplier selection into a documented decision.

Approver review summary

Approver Review Summary

A clear shareable record of which supplier was chosen and why.

RESEARCH LIMITATIONS

I mocked AI outputs to test how users would verify them, and treated three exploratory interviews as directional input rather than representative evidence.

LEARNINGS

The biggest lesson was that transparency doesn’t mean showing everything.

I was showing too much by default

Every instinct to show everything worked against the goal of keeping things simple for a non specialist. Testing usually told me which way to move.

I had defined the use case too narrowly

I designed around comparing multiple quotes, but users also saw value in organizing a single supplier offer.

Designing for trust

Users did not reject AI help. They needed to see where each value came from, and that reshaped most screens built after research.