Cloud services · Employment work
Sahabah Cloud Platform
Turning a large cloud service ecosystem into one understandable client and admin experience
Confidentiality safe visualCloud service lifecycle
Discover
→Decide
→Act
→Manage
Product details are explained through architecture and journey models without exposing private screens customer data or internal systems
01 · The problem
What needed to change
The platform brings together technical services with very different configuration billing and support requirements. Customers needed a clear path from discovery and purchase to activation management renewal and support while internal teams needed reliable administrative control.
02 · My real role
Design Lead and UI UX Developer
Hawsabah / Digital Pages employee
03 · Decisions I made
Turning complexity into direction
- Structured the product around services tasks and customer status instead of internal technical terminology
- Created reusable journeys and components across products without hiding service specific requirements
- Separated Saudi domain approval rules from global domain flows while keeping one coherent experience
- Made responsive behavior and implementation QA part of design delivery rather than a final check
04 · Systems and journeys
The experience I shaped
01Marketing website and landing pages
02Client portal and admin dashboard
03Cart checkout bundles and domain configuration
04Saudi and global domains VPS Titan Mail SSL DNS and hosting
05Billing reports tickets knowledge base and service management
06Transactional email templates and operational states
05 · Challenges
Constraints I designed through
- High technical and regulatory complexity
- Many connected services with different lifecycles
- Maintaining consistency across client admin and marketing surfaces
- Protecting confidential product and customer information
06 · Team and developers
How I worked
I worked across design development business analysis management marketing support and operations. The Figma workspace grew into more than 3200 comments reviews and decisions reflecting continuous alignment critique approvals QA and developer validation.
07 · Result and impact
What the work changed
Established a clearer scalable product structure across the cloud ecosystem
Reduced inconsistency through reusable patterns and a shared design direction
Created a stronger bridge between business requirements technical constraints and the final interface