Article6 min readUpdated
SaaS Product Design: Roles, Setup and Empty Dashboards
SaaS product design basics for B2B teams: how to plan user roles and permissions, design first-run setup, and fix empty dashboards that confuse new users.
Suppose a company in Pune sells attendance software to factories. The first customer signs up. The owner of the factory logs in and sees a dashboard full of empty charts, a blank table, and a button that says "Add". He does not know what to add first. He closes the tab and calls the sales team.
This happens often in business software. The product is strong, but the first 10 minutes are weak. This article covers the basics of SaaS product design for B2B products: roles and permissions, first-run setup, and empty dashboards. SaaS means software that customers use online, usually by paying a regular fee.
Why B2B software is different from a consumer app
A consumer app usually has one person using it for themselves. A B2B product has a company using it, and that company has many people with different jobs.
That changes the design in three ways.
- Many roles. The owner, the manager and the junior staff member need different screens.
- The buyer is not the user. The person who pays may never open the product daily. Others use it every day, and they did not choose it.
- Setup comes before use. A company must add its people, data and rules before the product is useful.
Good B2B UX respects these facts. It does not treat every user as the same person. For the admin side of this, see my notes on admin dashboard UI/UX design.
Start with roles, before screens
The most common design mistake I see is drawing screens first and thinking about roles later. Then a developer asks, "Who can see this?" and nobody knows.
Begin with a simple role sheet. Take the factory attendance example.
| Role | Main job | Can see | Can change |
|---|---|---|---|
| Owner | Checks cost and overall picture | All reports, all factories | Plans, billing, all settings |
| Factory manager | Runs one factory | Own factory's staff and attendance | Shifts, leave approvals |
| Supervisor | Marks daily attendance | Own team only | Daily attendance entries |
| Accountant | Prepares salary | Attendance summaries | Export only |
This table is small, but it answers dozens of design questions. Each role gets its own home screen, its own menu and its own limits.
Keep the number of roles small
Start with 3 or 4 roles. Add a custom role system only when customers ask for it. Many early products build complex permission settings that nobody uses. A fixed set of clear roles is easier to learn, easier to build and easier to test.
Design what a person cannot do
A role-based access screen is not only about what is visible. It is also about what happens when a person is blocked. Suppose a supervisor taps "Billing". What do they see?
- A blank page is bad. It looks like a bug.
- A hidden menu item is often best. If a person can never use a feature, do not show it.
- A clear message is right when a person could ask for access. For example: "Only owners can change billing. Ask your owner for access."
Also design the view as another role option for owners and for your own support team. It saves many hours of explaining.
Design the invite flow
Roles are only real when people join. Design the screen where an owner invites a colleague. The fields are usually name, phone number or email, and role. Many Indian teams share a WhatsApp group more than email, so allow an invite link that can be sent on WhatsApp. Show clearly what the new person will be able to do before the owner presses Send.
Design the first-run setup
First-run setup is the path from "account created" to "first useful result". Your aim is to make this path short.
Here is the order I plan for the factory example.
- Ask one or two questions only. "How many factories?" "How many workers?" Use the answers to prepare the account.
- Add the first real data. Let the owner add one worker, or upload a sheet of workers. Let the user import from Excel if the customers already keep data there.
- Show a result at once. After one worker is added, mark that worker present for today and show the summary.
- Invite the next person. Only after the user has seen value, suggest inviting a manager.
Avoid long forms before the product shows any value. Each extra field costs you some new accounts. For general patterns, read app onboarding UX best practices.
A setup checklist helps
A small checklist at the top of the dashboard works well: "Add workers, Set shifts, Invite a manager". Each item has a tick when done. The checklist tells the user what is left, and it lets them leave and return later without feeling lost.
Offer sample data, honestly
Some products offer a sample account with fake data so a user can explore. This helps. Label it clearly as sample data, and make it easy to delete. Never mix fake and real data.
Fix the empty dashboard
An empty dashboard is the first thing every new customer sees. Yet designers often design the dashboard only with full data, because that looks good in a presentation.
Design three versions of every dashboard screen.
- Empty. No data yet. Say what will appear here and how to start. Example: "Attendance for today will appear here. Add your first worker to begin." Add one clear button.
- Partial. A little data. Charts with one point look strange, so use simple numbers instead of charts until there is enough data.
- Full. The version you usually draw, with real volume. Check that long names, big numbers and many rows still fit.
Do not leave an empty table with only headings. Do not show a chart with a flat line at zero. Do not write "No data found", because it sounds like an error.
Each role needs its own empty state
The owner's empty dashboard and the supervisor's empty dashboard are different. A supervisor on day one needs "Mark today's attendance". An owner on day one needs "Add your first factory". Use the role sheet to write both.
Dashboard design: show decisions, not decoration
A dashboard should help a person decide something. Ask for each widget: "What action might this lead to?" If the answer is "none", remove it.
- Put the most important number at the top left, in large type.
- Show change over time only when it helps a decision.
- Make tables sortable and searchable, and keep the columns that matter.
- On a phone, show the one or two numbers a manager needs, and move the rest behind a tap.
Business software in India is often opened on a mid-range phone, even by senior people. Plan for small screens and weak networks. See designing for low-end phones and slow networks.
Words matter in business software
Use the words your customers use. A factory manager says "shift" and "attendance", not "workforce scheduling module". Write short labels, and explain any unavoidable term once. My notes on UX writing and microcopy go into more detail.
How I approach a SaaS design project
I follow my five stages. I understand the customer company and list its roles. I map the flow for each role, from login to the main task. I wireframe the screens, including empty states. I design the interface and set up a shared set of components. Finally, I prototype and hand off with clear files for developers.
The price of a SaaS design depends on the number of screens and the number of user roles, which is why I quote each project individually. You can read more about the factors in how much UI/UX design costs in India.
If you are planning business software and want the roles and first-run setup designed with care, see my UI/UX design service or get in touch.
Frequently asked questions
What is role based access in a SaaS product?
+
It means each user sees and changes only what their role allows. For example, an owner can change billing, while a supervisor can only mark attendance.
How many user roles should a first SaaS version have?
+
Start with 3 or 4 clear roles. Add custom roles later, only if customers ask for them.
What is an empty state in a dashboard?
+
It is the screen a user sees before any data exists. A good empty state explains what will appear and gives one clear button to start.
How long should SaaS onboarding be?
+
As short as possible. Aim to get a new account to one useful result in a few steps, then ask for more details later.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.