Product Design / B2B SaaS
B2B SaaS Product Design
B2B SaaS product design is the design of software a company buys for its teams: the workspace an admin sets up, the roles that decide who can do what, the single sign-on and provisioning that IT requires and the plan limits that billing enforces. Gestures designs B2B SaaS products for the two people inside every account, the admin who configures the product and the member who works in it every day.
B2B SaaS product design with Gestures costs $2,250 per week, $4,000 for a two-week sprint or $7,500 per month for ongoing work as the product moves to larger customers. Every plan covers strategy, design and review on a scope agreed before work starts.
Method
Design for the admin and the member separately
A B2B SaaS product serves people with different jobs inside the same customer account, so Gestures names each one and the screens they depend on before designing a single flow.
| Person | Main job in the product | Screens they depend on |
|---|---|---|
| Admin | Main job in the productSet up the workspace and control access | Screens they depend onMembers, roles, single sign-on, billing and the audit log |
| Member | Main job in the productFinish daily work | Screens they depend onThe core workflow, notifications and personal settings |
| Budget owner | Main job in the productPay for the product and justify the spend | Screens they depend onInvoices, seats in use and the plan comparison |
| IT or security reviewer | Main job in the productConfirm the product meets company policy | Screens they depend onSingle sign-on, provisioning, session rules and data export |
Members rarely see the admin screens and admins rarely do the daily work, so each group gets its own navigation entry point, its own empty states and its own notifications.
Permissions
A permission model people can predict
Roles fail when an admin cannot predict what a member will see, so we design the permission model as a matrix with your engineers first and the role settings screen second. The matrix below is an illustrative example, not a recommended set of roles.
| Action | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| Invite members | OwnerYes | AdminYes | MemberNo | ViewerNo |
| Change the plan and billing details | OwnerYes | AdminNo | MemberNo | ViewerNo |
| Edit shared records | OwnerYes | AdminYes | MemberYes | ViewerNo |
| Export workspace data | OwnerYes | AdminYes | MemberIf the admin allows it | ViewerNo |
| View the audit log | OwnerYes | AdminYes | MemberNo | ViewerNo |
Every cell becomes a screen state: a control that is hidden, a control that is disabled with the reason stated, or a request for access that reaches the right admin.
Identity
Single sign-on and provisioning that IT can verify
Larger customers connect a B2B SaaS product to their identity provider, so sign-on and provisioning screens are part of the product a deal depends on. SCIM, specified in RFC 7643 and RFC 7644, is the standard protocol identity providers use to create, update and remove user accounts in another product, and the admin screens must show every change it makes.
- Single sign-on setup in numbered steps, with values to copy and a test sign-in before it is enforced.
- An emergency sign-in for the account owner while single sign-on is enforced.
- Users created by the identity provider marked as managed, with locked fields and the reason they are locked.
- A provisioning log listing accounts created, updated and deactivated, with the time of each change.

Plan limits
Plan limits that explain themselves at the moment of use
A plan limit appears in the middle of someone's work, so the screen must say what is blocked, who can lift the limit and what it costs, without sending the person to the pricing page.
| Moment | Screen behavior |
|---|---|
| Approaching a seat or usage limit | Screen behaviorThe remaining amount shown where the work happens, and a notice to the admin |
| A member reaches a limit | Screen behaviorWhat is blocked, who can lift it and a request that goes to the admin |
| An admin reaches a limit | Screen behaviorThe plan that removes it, the price difference and when the change takes effect |
| Downgrading a plan | Screen behaviorThe features, seats and data affected, listed before the admin confirms |
Audit and export
Audit logs and data export for the security review
An audit log answers who changed what and when, and customers ask for it during security reviews and after incidents. We design the audit log as a searchable record, not an activity feed.
- Each entry with the actor, the action, the affected record, the time and the source of the request.
- Filters by person, action type and date range, with the time zone stated.
- Export of the filtered log, and the retention period written on the screen.
- A full workspace export that states its format and what it includes before the admin starts it.
Experience
B2B product work behind this page
Scope and cost
B2B SaaS product design scope and cost with Gestures
B2B SaaS product design with Gestures costs $2,250 per week, $4,000 for a two-week sprint or $7,500 per month for ongoing work. The plan follows the number of account-level areas in scope.
| Scope | What it covers | Plan |
|---|---|---|
| Roles and permissions | What it coversThe permission matrix, role settings, access requests and every hidden and disabled state | PlanWeekly sprint, $2,250 per week |
| Enterprise readiness | What it coversSingle sign-on, provisioning, audit log and data export | PlanTwo-week sprint, $4,000 |
| Plans and limits | What it coversLimit moments, upgrade and downgrade flows and the billing settings | PlanWeekly sprint, $2,250 per week |
| A product moving upmarket | What it coversAdmin and member experiences, workflows and a shared design system | PlanMonthly partnership, $7,500 per month |
For an overview of B2B SaaS work and who owns what in a project, see our B2B SaaS product and website design page. The overview screens and reports customers open first are covered by B2B SaaS dashboard design, and the website that sells the product by B2B SaaS website design. Our guide to onboarding around the first useful action covers workspace setup.
Monthly partnership
$7,500$10,500USD / month
Studio $7,500 + Growth $3,000 / month
For a B2B product moving from small teams to larger companies. Set the current focus each month and review what needs attention next.
Strategy · Design · Review
Work starts within 1 day of payment.
Cancel anytime.
Start your projectWeekly sprint
$2,250$4,000USD / week / 2 weeks
+ $3,000 / month for Growth
For one account-level area, such as roles and permissions, single sign-on setup or plan limits. Agree the permission rules and the engineering contact before starting.
Save $500 with two weeks: $4,000 instead of $4,500.
Strategy · Design · Review
Work starts within 1 day of payment.
Cancel anytime.
Start your projectAdd Growth to a studio plan
SEO, content strategy and content production, alongside your design team. Growth is billed monthly. Cancel anytime.
+$3,000 / month
Compare all plans or book a call to agree the first account-level area.
Questions
Questions about B2B SaaS product design
How much does B2B SaaS product design cost?
B2B SaaS product design with Gestures costs $2,250 per week, $4,000 for a two-week sprint or $7,500 per month. Single sign-on, provisioning, audit log and export together fit a two-week sprint. See pricing for every plan.
Do you design for multiple workspaces or organizations?
Yes. We design the workspace switcher, invitations across workspaces and the rules for what an admin of one workspace can see in another, with your engineers' tenancy model as the starting point.
Can you redesign permissions without breaking existing accounts?
Yes. We map every existing role to the new model, design the migration notice admins see and keep the old behavior visible until each admin confirms the change.
Do you write the copy for limits, errors and permission messages?
Yes. Every message for a blocked action, a limit or a missing permission is written with the reason and the next step, and listed in one inventory for your team to review.
What do you need from our team to start?
We need the current roles and what each can do, the plan limits, a test workspace with sample data and an engineer who can answer questions about the account model.
Do you design B2B SaaS dashboards too?
Yes. Role-based overview screens, reports, exports and data tables are covered on our B2B SaaS dashboard design page.
Can you build the product too?
Yes, for new products and first versions. Our AI-native product development service takes a prototype to a working product.
A conversation
Send us the admin screen your customers ask about most
Share the account-level screen that creates the most questions from admins, and the roles your product uses today. We can agree the first area and whether Gestures is the right fit. For the wider service, see product design.