B2B SaaS Platform UX/UI Overhaul
Budget / Salary€750–1,500
TypeFreelance project
LocationRemote
Posted2 hours ago
Senior UX/UI Product Designer for Complex B2B SaaS Platform
We are looking for an experienced Senior UX/UI Product Designer to work on a large, multi-module B2B SaaS platform.
This is NOT a simple booking app or a small website redesign.
The product is a broad business-management ecosystem covering operational, financial, customer-facing and administrative workflows.
The designer will audit the existing product, build a scalable design system, and progressively redesign/document the complete UX across the SaaS application, public website, customer booking experience, mobile application and internal/admin interfaces.
PRODUCT SCOPE
The platform includes areas such as:
- Dashboard and business overview
- Calendar and scheduling
- Booking lifecycle
- Customer CRM
- Employees, teams, departments and permissions
- Services, categories, products and resources
- Multiple locations
- Payments and transactions
- Invoices, taxes and financial settings
- Subscription and plan management
- POS
- Payroll / staff operations
- Loyalty and rewards
- Memberships
- Packages
- Gift cards
- Coupons
- Events
- Custom forms
- Notifications and communications
- Reports and analytics
- External integrations
- Accounting integrations
- Security, MFA, sessions and audit UX
- Privacy and data-management flows
- Support/help
- AI-related functionality
- Voice / AI receptionist interfaces
- Internal operator/admin interfaces
- Customer booking/self-service
- Public website
- Mobile application
Some functionality already exists, some is under development and some belongs to future phases.
The designer must NOT invent unsupported features.
PHASE 1 — PRODUCT & UX AUDIT
Before redesigning major areas, you will:
- Review the existing application and UI
- Inventory current screens, routes and workflows
- Capture and organize screenshots
- Map user roles and permissions
- Identify missing/inconsistent UX
- Classify screens as KEEP / IMPROVE / REDESIGN / MISSING / FUTURE
- Produce a structured UX/UI Gap Register
We do not want someone to redesign the entire navigation before understanding the existing system.
DESIGN SYSTEM
Create a professional Figma design system covering:
- Colors and semantic tokens
- Typography
- Spacing and grid
- Radius and elevation
- Iconography
- Breakpoints
- Components
- Forms
- Tables
- Cards
- Navigation
- Modals/drawers
- Toasts
- Filters/search
- Domain-specific SaaS components
Full Light and Dark mode support is required.
Dark mode must be part of the token system, not a later visual skin.
RESPONSIVE + RTL/LTR
The system must work across:
- Desktop
- Large desktop
- Tablet
- Mobile web
- Mobile app
The product is international and must support both LTR and RTL/Arabic.
Designs must account for:
- Long translations
- Arabic layouts
- Localized dates
- Currencies
- Numbers
- Mixed RTL/LTR content
COMPLETE UX STATES
Professional SaaS design requires more than happy-path screens.
Relevant flows should include:
- Loading
- Empty
- First-use
- Success
- Validation errors
- System errors
- No permission
- Disabled
- Destructive confirmation
- Expired
- Locked
- Disconnected/reconnect
- Offline where relevant
SAAS APPLICATION
Work will progressively cover:
- App shell and navigation
- Authentication
- Signup/onboarding
- Dashboard
- Calendar
- Bookings
- CRM
- Staff/team
- Services
- Products/resources
- Locations
- Payments/finance
- Billing/subscriptions
- POS
- Reports
- Integrations
- Notifications
- Security/privacy
- Settings
- Internal/admin interfaces
Any existing production route discovered during the audit is considered part of the product inventory even if it is not explicitly listed above.
CUSTOMER BOOKING EXPERIENCE
The customer-facing booking experience is an independent UX surface.
Typical flow:
Service
→ Staff/resource
→ Date/time
→ Customer details
→ Payment/deposit where required
→ Review
→ Confirmation
→ Reschedule/cancel/self-service
The objective is a simple, conversion-focused customer experience.
PUBLIC WEBSITE
We also require UX/UI for the public website, including:
- Homepage
- Product overview
- Feature pages
- Industry/solution pages
- Pricing
- Integrations
- Security/trust
- AI/voice pages where approved
- Partners
- Affiliate
- Resources
- Company/contact
The website should explain a large SaaS ecosystem clearly without becoming a feature dump.
MOBILE
A mobile product experience is also part of the scope.
Mobile must NOT simply be the desktop dashboard compressed onto a smaller screen.
Typical priorities:
- Today
- Calendar
- Upcoming bookings
- Customers
- Notifications
- Quick actions
- Booking details
- Staff schedules
- Settings/security
ROLES & PERMISSIONS
The platform has multiple user types, including:
- Owner/Admin
- Manager
- Staff
- Customer
- Internal platform operator
- Partner/Affiliate where applicable
Permission differences must be intentionally designed.
INTEGRATIONS
We need reusable provider-neutral UX patterns for:
- Integration catalog
- Connect
- OAuth/API setup
- Connected state
- Sync state
- Error
- Reconnect
- Disconnect
- Mapping
- Webhook status
This also applies to future accounting-platform integrations.
WORDPRESS / EXTERNAL WEBSITE INTEGRATION
Relevant UX may include:
- Connection state
- Setup guidance
- Connect/disconnect
- Errors
- Booking-widget configuration
Authentication/security architecture will be defined by engineering.
AI / VOICE
The platform includes AI and voice-related functionality.
Design only capabilities confirmed by current product truth.
Do not create fictional AI functionality for presentation purposes.
ACCESSIBILITY
We expect accessibility-conscious design:
- WCAG AA-oriented contrast
- Focus states
- Clear labels
- Accessible errors
- Good mobile touch targets
- Status not communicated by color alone
- Reduced-motion consideration
FIGMA & HANDOFF
Figma is the canonical design workspace.
Expected structure:
- Foundations
- Components
- Patterns
- Website
- SaaS
- Mobile
- Customer booking
- Internal/admin
- Archive
Final work should include:
- Component specifications
- Responsive behavior
- Interaction notes
- Validation behavior
- Screen states
- Prototype links
- Edge cases
- Developer-ready handoff
WORKING PROCESS
Expected milestones:
1. Product Audit + UX Gap Register
2. Foundations + Design System
3. Core SaaS flows
4. Extended SaaS modules
5. Public Website
6. Mobile + Customer Experience
7. Final UX QA + Engineering Handoff
The exact plan can be refined after the initial audit.
WHO WE ARE LOOKING FOR
Strong preference for designers with experience in:
- Complex SaaS
- B2B dashboards
- CRM / ERP / operational systems
- Scheduling platforms
- Finance/payment interfaces
- Multi-role systems
- Design systems
- Responsive SaaS
- Mobile product UX
Experience focused only on landing pages or simple mobile apps is not enough.
WHEN APPLYING, PLEASE SEND:
1. Your strongest SaaS/dashboard work
2. A Figma design-system example
3. A complex workflow you designed
4. Examples involving tables, calendars, CRM, finance or operational dashboards
5. Light/Dark mode experience
6. RTL/Arabic experience if available
7. How you would approach the initial audit
8. Availability and preferred working model
9. Confirmation that you are comfortable with a long-term multi-phase product
We are looking for a PRODUCT DESIGNER, not only a visual/graphic designer.
The objective is to build a coherent, scalable UX system for a serious international SaaS platform while respecting existing functionality, engineering constraints and future growth.
We are looking for an experienced Senior UX/UI Product Designer to work on a large, multi-module B2B SaaS platform.
This is NOT a simple booking app or a small website redesign.
The product is a broad business-management ecosystem covering operational, financial, customer-facing and administrative workflows.
The designer will audit the existing product, build a scalable design system, and progressively redesign/document the complete UX across the SaaS application, public website, customer booking experience, mobile application and internal/admin interfaces.
PRODUCT SCOPE
The platform includes areas such as:
- Dashboard and business overview
- Calendar and scheduling
- Booking lifecycle
- Customer CRM
- Employees, teams, departments and permissions
- Services, categories, products and resources
- Multiple locations
- Payments and transactions
- Invoices, taxes and financial settings
- Subscription and plan management
- POS
- Payroll / staff operations
- Loyalty and rewards
- Memberships
- Packages
- Gift cards
- Coupons
- Events
- Custom forms
- Notifications and communications
- Reports and analytics
- External integrations
- Accounting integrations
- Security, MFA, sessions and audit UX
- Privacy and data-management flows
- Support/help
- AI-related functionality
- Voice / AI receptionist interfaces
- Internal operator/admin interfaces
- Customer booking/self-service
- Public website
- Mobile application
Some functionality already exists, some is under development and some belongs to future phases.
The designer must NOT invent unsupported features.
PHASE 1 — PRODUCT & UX AUDIT
Before redesigning major areas, you will:
- Review the existing application and UI
- Inventory current screens, routes and workflows
- Capture and organize screenshots
- Map user roles and permissions
- Identify missing/inconsistent UX
- Classify screens as KEEP / IMPROVE / REDESIGN / MISSING / FUTURE
- Produce a structured UX/UI Gap Register
We do not want someone to redesign the entire navigation before understanding the existing system.
DESIGN SYSTEM
Create a professional Figma design system covering:
- Colors and semantic tokens
- Typography
- Spacing and grid
- Radius and elevation
- Iconography
- Breakpoints
- Components
- Forms
- Tables
- Cards
- Navigation
- Modals/drawers
- Toasts
- Filters/search
- Domain-specific SaaS components
Full Light and Dark mode support is required.
Dark mode must be part of the token system, not a later visual skin.
RESPONSIVE + RTL/LTR
The system must work across:
- Desktop
- Large desktop
- Tablet
- Mobile web
- Mobile app
The product is international and must support both LTR and RTL/Arabic.
Designs must account for:
- Long translations
- Arabic layouts
- Localized dates
- Currencies
- Numbers
- Mixed RTL/LTR content
COMPLETE UX STATES
Professional SaaS design requires more than happy-path screens.
Relevant flows should include:
- Loading
- Empty
- First-use
- Success
- Validation errors
- System errors
- No permission
- Disabled
- Destructive confirmation
- Expired
- Locked
- Disconnected/reconnect
- Offline where relevant
SAAS APPLICATION
Work will progressively cover:
- App shell and navigation
- Authentication
- Signup/onboarding
- Dashboard
- Calendar
- Bookings
- CRM
- Staff/team
- Services
- Products/resources
- Locations
- Payments/finance
- Billing/subscriptions
- POS
- Reports
- Integrations
- Notifications
- Security/privacy
- Settings
- Internal/admin interfaces
Any existing production route discovered during the audit is considered part of the product inventory even if it is not explicitly listed above.
CUSTOMER BOOKING EXPERIENCE
The customer-facing booking experience is an independent UX surface.
Typical flow:
Service
→ Staff/resource
→ Date/time
→ Customer details
→ Payment/deposit where required
→ Review
→ Confirmation
→ Reschedule/cancel/self-service
The objective is a simple, conversion-focused customer experience.
PUBLIC WEBSITE
We also require UX/UI for the public website, including:
- Homepage
- Product overview
- Feature pages
- Industry/solution pages
- Pricing
- Integrations
- Security/trust
- AI/voice pages where approved
- Partners
- Affiliate
- Resources
- Company/contact
The website should explain a large SaaS ecosystem clearly without becoming a feature dump.
MOBILE
A mobile product experience is also part of the scope.
Mobile must NOT simply be the desktop dashboard compressed onto a smaller screen.
Typical priorities:
- Today
- Calendar
- Upcoming bookings
- Customers
- Notifications
- Quick actions
- Booking details
- Staff schedules
- Settings/security
ROLES & PERMISSIONS
The platform has multiple user types, including:
- Owner/Admin
- Manager
- Staff
- Customer
- Internal platform operator
- Partner/Affiliate where applicable
Permission differences must be intentionally designed.
INTEGRATIONS
We need reusable provider-neutral UX patterns for:
- Integration catalog
- Connect
- OAuth/API setup
- Connected state
- Sync state
- Error
- Reconnect
- Disconnect
- Mapping
- Webhook status
This also applies to future accounting-platform integrations.
WORDPRESS / EXTERNAL WEBSITE INTEGRATION
Relevant UX may include:
- Connection state
- Setup guidance
- Connect/disconnect
- Errors
- Booking-widget configuration
Authentication/security architecture will be defined by engineering.
AI / VOICE
The platform includes AI and voice-related functionality.
Design only capabilities confirmed by current product truth.
Do not create fictional AI functionality for presentation purposes.
ACCESSIBILITY
We expect accessibility-conscious design:
- WCAG AA-oriented contrast
- Focus states
- Clear labels
- Accessible errors
- Good mobile touch targets
- Status not communicated by color alone
- Reduced-motion consideration
FIGMA & HANDOFF
Figma is the canonical design workspace.
Expected structure:
- Foundations
- Components
- Patterns
- Website
- SaaS
- Mobile
- Customer booking
- Internal/admin
- Archive
Final work should include:
- Component specifications
- Responsive behavior
- Interaction notes
- Validation behavior
- Screen states
- Prototype links
- Edge cases
- Developer-ready handoff
WORKING PROCESS
Expected milestones:
1. Product Audit + UX Gap Register
2. Foundations + Design System
3. Core SaaS flows
4. Extended SaaS modules
5. Public Website
6. Mobile + Customer Experience
7. Final UX QA + Engineering Handoff
The exact plan can be refined after the initial audit.
WHO WE ARE LOOKING FOR
Strong preference for designers with experience in:
- Complex SaaS
- B2B dashboards
- CRM / ERP / operational systems
- Scheduling platforms
- Finance/payment interfaces
- Multi-role systems
- Design systems
- Responsive SaaS
- Mobile product UX
Experience focused only on landing pages or simple mobile apps is not enough.
WHEN APPLYING, PLEASE SEND:
1. Your strongest SaaS/dashboard work
2. A Figma design-system example
3. A complex workflow you designed
4. Examples involving tables, calendars, CRM, finance or operational dashboards
5. Light/Dark mode experience
6. RTL/Arabic experience if available
7. How you would approach the initial audit
8. Availability and preferred working model
9. Confirmation that you are comfortable with a long-term multi-phase product
We are looking for a PRODUCT DESIGNER, not only a visual/graphic designer.
The objective is to build a coherent, scalable UX system for a serious international SaaS platform while respecting existing functionality, engineering constraints and future growth.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.