Skip to content
FREN Book a call
( SaaS UX )

B2B SaaS UX: ten principles I learned building my own

I designed SaaS products for clients for fifteen years. Then I co-founded one. What I learned answering support tickets myself comes down to ten principles.

· 3 min read · SaaS UX

B2B SaaS UX: ten principles I learned building my own

( Key facts )

A B2B SaaS product is judged in the second week of use, not in the demo. Ten principles drawn from designing WeeFizz, Reformer Society and fifteen years of SaaS for clients: fast first value, one action per screen, real data, useful errors, clear pricing, measurement.

Author
Vladimir Spalaikovitch, Senior UX/UI Designer, Product Designer and Digital Art Director
Published
Updated
Reading
3 min · 706 words

A B2B SaaS product is judged in the second week of use, not in the demo. Its users often did not choose the tool, they use it several times a day, and they drop it the moment it wastes their time. These ten principles come from designing [WeeFizz](/en/work/weefizz/), [Reformer Society](/en/work/reformer-society/) and fifteen years of SaaS work for clients.

1. First value before first configuration

A new user should see something useful before setting anything up. On WeeFizz, a new client's dashboard shows realistic demo data, and the first size recommendation can be tested in thirty seconds. Configuration comes later, once the user understands why they are doing it.

What to measure: time to first value, not the tutorial completion rate.

2. One primary action per screen

Every screen answers one question: what should the user do here? One primary action, visually dominant. The others are secondary. When two actions compete for the spot, the screen is badly split.

3. Never an empty screen

An empty table, a chart with no data, a list with no items: every empty state is an opportunity. It explains what will appear here, offers the action that will fill the screen, or shows an example. On Reformer Society, a studio with no videos sees how to import one from Dropbox in three steps.

4. Density is a setting, not a verdict

Expert users want to see fifty rows; beginners want ten with room to breathe. Offer a density setting and hideable columns instead of deciding for everyone. The table is the most used component in a SaaS product: that is where time is won or lost.

5. Every error says what to do

"An error occurred" is an insult. An error message says what happened, why if that helps, and above all what to do now. It is written for a stressed user who will read it once. Technical codes go in a collapsible detail, not in the headline.

6. Roles are visible, not guessed

In a multi-user SaaS product, everyone should know what they can do and why they cannot do the rest. A disabled button with no explanation generates a ticket. A disabled button labeled "Admins only" does not.

7. Perceived speed is a feature

A SaaS product used a hundred times a day does not forgive slowness. Immediate visual feedback, progressive loading, optimistic actions, intermediate states. And on the technical side: optimized images, batched requests, caching. Speed is designed in, not optimized at the end.

8. The design system is the contract with developers

A SaaS product lives for years and changes teams. Without a design system, every sprint adds another button variant. With a system named the same way in Figma and in code, consistency outlives the people. See Design system: where to start.

9. Pricing makes sense without calling sales

Plans, limits, what is included and what is not, monthly and annual prices: everything should be readable on one page, and usable by someone comparing three tools on a Friday evening. Trial, plan change and cancellation flows are full-fledged screens, not formalities. Opaque pricing drives people away; a cancellation trap costs you your reputation.

10. Measure before and after

Every interface change starts from a measured indicator and is checked against the same indicator. Without measurement, design is an opinion. With measurement, it is a decision. The product's own analytics must be readable too: on WeeFizz, the analytics redesign replaced decorative charts with comparable bars and an explicit confidence indicator.

Three traps specific to B2B

  • Designing for the buyer instead of the user. The buyer sees the demo; the user lives with the tool. Both matter, but the second one decides the renewal.
  • Piling up features requested by big clients. Every feature added for one client is complexity imposed on all the others. Prefer settings and permissions.
  • Neglecting the internal back office. The support team uses the product more than any client. A fast back office means fast support, and a client who stays.

Going further

The UX/UI for B2B SaaS page details the screens that matter and the engagement formats. A UX/UI audit shows where your product stands on these ten principles.

( FAQ · 03 )

Frequently asked questions

What is the most important UX principle for a SaaS product?

Get the user to real first value as fast as possible, before any configuration. A SaaS product that asks for ten settings before showing anything useful loses most of its trials.

How do you measure the UX of a SaaS product?

Time to first value, activation rate, return rate at seven and thirty days, task time on frequent actions, volume and nature of support tickets. Measure before and after every change.

Does a B2B SaaS product need to be beautiful?

It needs to be clear, fast and predictable. Beauty helps when it reinforces hierarchy and trust. A polished interface sells better during the trial; a clear interface retains after the purchase.

( Next · 04 )

Keep reading

  1. UX/UI for B2B SaaS

    B2B SaaS UX/UI designer: onboarding, dashboards, data, back offices, pricing, white label. Cofounder and CPO of a SaaS, 20 years designing business tools.SaaS UX/UIRead
  2. WeeFizz

    WeeFizz case study: designing a size recommendation SaaS for fashion. E-commerce widget on four CMS platforms, dashboard, back office. Co-founder and CPO.SaaS · Fit tech · AIRead
  3. Design system: where to start when you are starting from zero

    How to start a design system: the right order for foundations (tokens, type, spacing), the first twelve components, Figma and code, minimal documentation.Starting a design system: foundations, first components, Figma and code. · 3 minRead
  4. UX/UI audit

    UX/UI audit by a senior designer: expert review of user flows, accessibility and design system, with a prioritized, costed action plan. Two weeks, actionable.Senior UX/UI audit: flows, accessibility, prioritized action plan in two weeks.AuditRead