B2B SaaS UX design awards: judging software people are paid to use
B2B software is judged differently: the user didn't choose it, the data is messy, and the admin screens matter. What we look for in enterprise and B2B SaaS entries, and how to enter one well.
Consumer products are chosen; B2B products are issued. The person using your software didn't pick it, can't leave it, and will spend more hours in it this year than in any app they love. That changes what good means — and it's why B2B SaaS UX design awards entries are judged with a different set of questions.
1. Expertise is a design target, not a compromise
Consumer design optimises for the first five minutes. B2B design has to optimise for the thousandth hour without abandoning the first. The products that score well hold both: a clear path for the new user, and a fast path for the person who has done this 400 times.
Only the first five minutes
- Wizards that can't be skipped
- Confirmation on every routine action
- No keyboard path through frequent tasks
- Density fixed at "comfortable" forever
Both audiences
- Guided path that fades once it's learned
- Undo instead of "Are you sure?" for reversible things
- Command palette, shortcuts, bulk actions
- A density the user controls
2. The admin surface is part of the product
Roles, permissions, audit logs, SSO configuration, billing, data export. This is where enterprise software is most complex and least designed — and it's usually the surface that decides renewal, because it's where the person who signs the cheque actually lives.
- Permissions that can be understood in one screen. A matrix a person can read beats a hundred toggles.
- A dry run. "If I make Sam a Manager, what changes?" answered before you save it.
- Audit that answers questions. Not a log dump — a filterable record of who changed what, phrased in the product's own nouns.
- Export that's honest. If the data can go in, it must be able to come out, in a format that isn't a punishment.
3. Real data is ugly, and design has to survive it
B2B data arrives from a migration: duplicate records, names in the wrong fields, fifteen-year-old entries with fields that no longer exist. Editors ask for a realistic tenant precisely to see this, and entries that only demo clean data give away that nobody tested at scale.
- Long strings4Company names that run to 120 characters. Do they truncate meaningfully or destroy the layout?
- Large volumes450,000 rows. Is the table still usable, or does it become a loading state?
- Missing values3Is an empty field distinguishable from a zero?
- Duplicates3Can a user merge them, or must they call support?
- Legacy fields2What happens to data from a feature you removed?
4. Integrations are the experience
Most B2B products sit in a chain. If a sync fails, the interface has to say which one, when, what didn't arrive and what to do — and it has to say it where the missing data would have been, not only in a settings page nobody visits.
Silent partial failure is the single most damaging pattern in enterprise software, because it destroys trust in data the user can't independently verify. Products that handle it well — with per-record provenance and an honest "last synced" state — score conspicuously higher.
5. Onboarding that respects the buyer's timeline
Enterprise onboarding isn't a modal tour; it's a project with a kickoff, a migration and a training session. The design question is what the product does between signing and the first real use. Entries that show a genuine time-to-value path — sandbox data, import validation, a checklist an admin can hand to their team — are showing a discipline most products skip entirely.
6. Accessibility, because procurement asks
In B2B, accessibility isn't only ethics — it's a question in the purchasing questionnaire and, in the public sector, a legal requirement. An independent score on accessibility, published with the conditions it was measured under, is unusually useful in a sales cycle.
What to send
A tenant with realistic messy data and a reviewer account with admin rights — editors need to see the permissions surface. Then: the densest table in the product, a failed integration state, the permissions screen, and the audit log. One measured outcome: time-to-first-value, support contacts about a specific flow, or the task time that fell after a redesign.
Most enter Product Experience with a B2B or Enterprise subcategory, plus Design Systems or UX Research & Strategy depending on where the year went. Start an entry.
Multi-tenancy, roles and the screens nobody demos
B2B products serve organisations, not people, and the organisational layer is where the design debt collects. Editors ask for an admin account precisely to see it.
| Compared on | Designed | Inherited |
|---|---|---|
| Switching tenant | Obvious, fast, and the current one always visible | A dropdown that silently changes context |
| Invites | Role chosen at invite, explained in words | Invite now, permissions later, somewhere else |
| Offboarding | Transfer ownership of their work, then remove | Delete the user and orphan everything |
| Billing | Who pays, for what, and what happens at the limit | A link to a third-party portal |
Deprecating a feature people depend on
Consumer products remove features and users complain. B2B products remove features and someone's job stops working. How a product handles that is a design question, and entries that can show it well are showing a maturity that is hard to fake: notice periods, in-product warnings targeted at the people actually using the feature, a migration path, and an honest explanation.
Where the evidence usually is
B2B teams often say they have no usability data, then turn out to be sitting on more than consumer teams: support ticket categories, onboarding call recordings, the questions asked in every implementation, the fields customers always get wrong. Those are research findings. Put them in the entry.
Questions we get asked
Our buyers aren't our users. Which do we design the entry around?
The users. Editors score the experience of using the product. Mention the buyer in the case study if the constraint shaped the design — that context is useful — but the score follows the daily user.
Is enterprise software judged more leniently because it's complex?
No, but it is judged in context. Density and configurability are expected; ambiguity, dead ends and undiscoverable actions are not excused by complexity.
Can we enter a product with a custom implementation per client?
Yes — enter a representative instance and say how much varies. If every client sees something different, say what's constant, since that's what you actually designed.
How much does accessibility matter for internal enterprise tools?
As much as anywhere, and often more: employees can't choose not to use the tool, and public-sector and large-enterprise buyers ask about it in procurement.
Assessed work in business software
Chosen by score from the work the editors have assessed, not by hand.
- b2b
- saas
- enterprise
- industry
Written by
The UXE editors
The team that selects the work, uses it, scores the seven criteria and writes every verdict on this site.
Keep reading
Craft & practice6 min read
What separates the best SaaS dashboard UX design from the rest
The patterns behind the best SaaS dashboard UX design: default views that answer a question, density that respects real data, states that are designed, and the performance budget nobody talks about.
The UXE editors
Judging & criteria6 min read
Digital product design awards: a guide for SaaS and product teams
Why most digital product design awards are built for marketing sites, what a product team should look for instead, and how to enter a SaaS product so we see the work that actually took the year.
The UXE editors
Craft & practice5 min read
Information architecture that scores: labels, depth and the way back
Information architecture is one of the seven UXE criteria. What editors test — labels people would use themselves, depth that matches the task, search that works, and a way back from anywhere.
The UXE editors