← Back to work
Requis · Enterprise SaaS · Product Design

Requis: Simplifying Complex Enterprise Workflows

Improving the clarity, discoverability, and usability of essential workflows across a B2B marketplace and procurement platform.

OutcomeImproved critical Lot Management workflows through customer feedback and cross-functional collaboration. Following a feature-flagged rollout and public release, the customer-facing team reported fewer lot-editing support requests.

RoleProduct Designer
TimelineJul 2024 to Jan 2026
FocusEnterprise UX · Interaction Design
Requis Marketplace Lots screen: browsing available industrial lots from vetted suppliers, with search, category and country filters, and lot cards showing seller, method, and condition.

Overview

Requis is a B2B platform supporting marketplace, procurement, inventory, and customer relationship management workflows.

As a Product Designer, I worked across multiple areas of the platform with product, engineering, and customer-facing teams. This case study focuses on three Lot Management improvements: clearer toolbar actions, easier filtering, and consolidated lot editing, with Procurement and CRM work shown as supporting examples.

How we found the focus

From symptoms to a clear focus.

Recurring support requests revealed friction across critical workflows.

Rather than treating every usability issue as equally urgent, we addressed the friction preventing users from completing important workflows before tackling less urgent improvements.

From Feedback to Design

The feedback shaped three design principles that guided each change:

Recognizable actions

Make important functionality understandable without guesswork.

Familiar workflows

Preserve established interaction patterns where possible.

Consolidated tasks

Bring related actions and navigation together to simplify workflows.

A Closer Look: Lot Management

In Requis, a lot is a collection of assets prepared for listing on the marketplace. Lot Management allows users to organize these assets, manage listing information, and prepare them for sale through options such as Buy Now, Make Offer, Auction, or Inquire.

What I Changed

01

Making Critical Actions Easier to Discover

The problem

Recurring support tickets showed customers struggling to identify important actions on the Lot Listing Preview page, particularly attaching documents and adding assets. The actions existed, but they were represented by small, unlabeled icons, so customers sometimes needed help finding functionality that was already there.

My design decision

I added visible text labels to the existing toolbar actions and kept the toolbar in its established location on the page.

Lot Listing Preview before the change: management actions shown as icons only
Before: Important management actions relied on unlabeled icons.
Lot Listing Preview after the change: actions paired with visible text labels
After: Labeled actions in the same toolbar position.
Up close
Close-up of the toolbar before: a Listed status and six unlabeled icons
Before: Six icons, no labels.
Close-up of the toolbar after: the same actions labeled Unlist Lot, Lot Edit, Attach, Image Edit, Add Assets, and Go Back
After: The same actions in the same place, now labeled: Unlist Lot, Lot Edit, Attach, Image Edit, Add Assets, Go Back.
Why it mattered

Clearer actions, familiar placement. I introduced visible labels while preserving the toolbar's existing location to improve discoverability without requiring returning users to relearn the interface.

02

Making Filtering Easier to Find and Use

The problem

Managing a large number of lots meant narrowing the list by attributes such as sale method and status, but the filters were hidden inside the settings menu, behind the gear icon. Feedback from the internal customer-facing team, who manage large numbers of lots, showed they needed a quicker way to filter.

My design decision

I moved filtering out of the settings menu into a dedicated filter panel, opened directly from the list toolbar, so the lot list stays visible while users refine results. Active filters appear as removable chips above the table, with a Clear All option.

Manage Lots before the change: no filtering options visible from the main list
Before: Filters were hidden inside the settings menu.
Manage Lots after the change: dedicated filter panel with active filters shown above the list
After: A filter panel beside the list, with active filters shown above the table.
Up close
Close-up of the list toolbar before: filters were hidden inside the settings menu, behind the gear icon
Before: Filters lived inside the settings menu, behind the gear icon (outlined).
Close-up after: active filter chips for Sale Method and Status with Clear All, and the toolbar control that opens the filter panel
After: Active filters as removable chips with Clear All, and the toolbar control that opens the filter panel.
Why it mattered

Filters where people already look. Bringing filters out of settings and into the list toolbar, and keeping active filters visible above the table, made it quick to narrow a long list and always clear which filters were shaping the results.

03

Bringing Lot Editing Into One Place

The problem

The Edit Lot page contained many sections of information, but its structure wasn't visible from the editing view. Section navigation was available through Lot Preview, but it wasn't consolidated on the Lot Edit page, so users had little indication of what information was available or where to find it while editing.

My design decision

I brought section navigation into the Lot Edit page itself, covering Info, Description, Seller Terms, Finance, Questions, Inspection, Shipping/Pickup, and Images, with a clear path back to Lot Preview.

Edit Lot before the change: no section structure visible from the main editing view
Before: Sections of the lot weren't visible from the editing view.
Edit Lot after the change: persistent section navigation across Info, Description, Seller Terms, Finance, Questions, Inspection, Shipping/Pickup, and Images
After: Section navigation on the Lot Edit page, with Back to Lot Preview.
Up close
Close-up of the Edit Lot header before: title and Select Sale Method, no section navigation
Before: The Edit Lot header: no section navigation.
Close-up of the Edit Lot header after: Back to Lot Preview, Select Sale Method, and tabs for Info, Description, Seller Terms, Finance, Questions, Inspection, Shipping/Pickup, and Images
After: Section tabs on the edit page: Info, Description, Seller Terms, Finance, Questions, Inspection, Shipping/Pickup, Images.
Why it mattered

One place for every editing task. Consolidating editing navigation within the Lot Edit page gave users one place to access and move between related editing tasks.

Validation & Outcome

The redesigned workflows were first introduced to a small group of customers through a feature-flagged release. Feedback from customers and the internal team helped validate the improvements before wider availability.

01

Successful task completion

Invited customers successfully edited and published their lots during the feature-flagged release.

02

Fewer support requests

The customer-facing team reported fewer lot-editing support tickets during the feature-flagged release and after the changes became publicly available.

03

Easier internal workflows

The internal customer-facing team reported that the updated filtering and Lot Edit experiences made their work easier.

Reported, qualitative outcomes. Several improvements were released together, so they reflect the combined changes rather than any single one.

Designing Across the Platform

Beyond Lot Management, I also designed across Procurement and CRM.

Procurement

Designed and refined responsive interfaces and interactions across complex procurement workflows, including the mobile experience of a procurement project, from the workspace overview to requests, suppliers, and commercial questions.

Procurement project overview on mobile: project summary with counts for suppliers, RFxs, and members
Overview
Project requests (RFxs) list on mobile
Requests
Current project suppliers on mobile
Suppliers
Current commercial questions on mobile
Commercial Questions

CRM: Connecting CRM Accounts to the Requis Network

Requis was building its own CRM so customers could manage their relationships inside the platform instead of relying on a separate tool such as Salesforce.

A new feature I designed: from a CRM account, users find the matching company in the Requis network, verify it's the right one, and create the connection, and when the company isn't in the network yet, they can invite it directly from the same flow.

CRM feature flow: start the connection, find and verify a matching company, connect it to the CRM account, invite a company that isn't in the network yet, and choose which contacts to invite

Designing for Consistency

Working across Lot Management, Procurement, and CRM, I reused the same building blocks so moving between areas felt like one product, while adapting them to each workflow's needs.

Reusable patterns

Used familiar interactions and components that could work across multiple features.

Clear hierarchy

Created consistent treatment of primary information, actions, and supporting content.

Responsive behavior

Considered how layouts and interactions adapted across different screen sizes.

One Lot Detail experience, adapted across desktop, tablet, and mobile. Desktop uses a multi-column layout with a separate actions panel, tablet reorganizes the content within a narrower layout, and mobile prioritizes a readable, vertically stacked presentation. Click any screen to enlarge it.

Requis lot detail on a desktop viewport
Desktop
Requis lot detail on a tablet viewport
Tablet
Requis lot detail on a mobile viewport
Mobile

Working With Product & Engineering

I worked closely with product managers, engineers, and customer-facing teams to translate feedback and product requirements into practical design improvements.

Our discussions helped us prioritize issues affecting essential workflows and understand technical constraints. I explored interface solutions, refined designs through feedback, and collaborated with engineers to support implementation.

Working on an established platform also meant considering how changes would affect existing users, not just how an individual screen could be improved.

What I Learned

Working on Requis reinforced that improving a complex product doesn't always mean redesigning it.

The Lot Preview improvements were a good example. The functionality already existed, but users struggled to recognize it. Adding clear labels while preserving familiar controls helped address the problem without disrupting established workflows.

The experience strengthened how I approach product design: understand the friction first, then make changes that solve the problem without introducing unnecessary complexity.

← Back to all projectsNext project: Tour Management App →