Product Thinking · Published August 16, 2026
Empty States in B2B Products
The first thing a user sees is not a feature but a blank page. Empty states decide whether they can start.
In consumer products an empty state is an illustration and a line of copy. In B2B it is different: a user opening an empty list assumes the system is broken or that they lack permission.
An empty state answers three questions
Why is it empty? No data yet, no permission, or filters too narrow? These three must be distinguished.
How do I start? Offer a clear action: create the first record, import a template, request access.
Is empty normal? Some pages legitimately have no data early on, and that needs saying.
A common mistake
Using 'no data' as universal copy. It explains neither the cause nor the next step.
We prepare three variants by scenario: no results for this filter, nothing created yet, and no access, each with its own action.
An empty state is the user's first conversation with the system. Writing it well is worth more than adding two more buttons.
← Previous post
Frontend Monitoring: Finding Out Before the White Screen
Next post →
Making Dashboards Actually Used: Three Design Principles
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →